[SOLVED] DELL XPS-9100 started crashing - WHEA_UNCORRECTABLE_ERROR (124)

[BlaqC]

My PC is about 8 years old and has started crashing every couple of days. The screen will turn white, grey or black and nothing but power-cycling has any effect.

Event Viewer doesn't show much of interest; most crashes don't seem to generate an entry.

• 
  ■I do have one set of four WHEA-Logger entries (one for each CPU core 0, 2, 4, 6): event 18, "A fatal hardware error has occurred. / Reported by component: Processor Core / Error Source: Machine Check Exception / Error Type: Internal Timer Error"
  ■Two BugCheck 1001's in the last two weeks. Sample: "The computer has rebooted from a bugcheck. The bugcheck was: 0x0000005c (0x0000000000000500, 0x0000000004000000, 0x00000000fbffffff, 0x00000000ffffffff). A dump was saved in: C:\WINDOWS\Minidump\121618-22046-01.dmp. Report Id: 6a647778-f92a-4c68-972e-b3bb614e7a2e."
  ■In both cases, my PC crashes more often than that.

Here are links to the HWINFO64 report and its sensor readings.

I have blown out the dust, cleaned the RAM contacts and reseated them, and personally measured the PSU voltages (without load) on all pins:

• 
  ■+3.3V measures at 3.41
  ■+5V = 5.20
  ■+12V = 12.5
  -12V = -12.57

Do you see anything in the HWINFO64 report or sensors that raises a red flag? Thanks.

 

[BlaqC]

Here's the WinDbg analysis. What should be my next steps?
_____


Microsoft (R) Windows Debugger Version 10.0.17763.132 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\122418-7812-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*c:\cache*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*c:\cache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 17134 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff800`7d213000 PsLoadedModuleList = 0xfffff800`7d5c1150
Debug session time: Mon Dec 24 08:52:47.311 2018 (UTC - 5:00)
System Uptime: 0 days 0:00:03.091
Loading Kernel Symbols
...............................................................
......
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, ffff9c8cc1bef038, 0, 0}

Probably caused by : GenuineIntel

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffff9c8cc1bef038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


KEY_VALUES_STRING: 1


STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.17134.472 (WinBuild.160101.0800)

DUMP_TYPE: 2

BUGCHECK_P1: 0

BUGCHECK_P2: ffff9c8cc1bef038

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BUGCHECK_STR: 0x124_GenuineIntel

CPU_COUNT: 8

CPU_MHZ: af0

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 1a

CPU_STEPPING: 5

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: CHARLES-DELL

ANALYSIS_SESSION_TIME: 12-24-2018 13:16:34.0516

ANALYSIS_VERSION: 10.0.17763.132 amd64fre

STACK_TEXT:
ffffb105`2b2fb6f0 fffff800`7d69b901 : 00000000`00000000 ffff9c8c`c1bef010 ffff9c8c`bf23fcb0 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x7b
ffffb105`2b2fbc20 fffff800`7d4d15a8 : ffff9c8c`c1bef010 fffff800`7d32dc11 00000000`00000000 ffff9c8c`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x2d
ffffb105`2b2fbc50 fffff800`7d4d222b : fffff800`7d5b2500 ffff9c8c`bf23fcb0 ffff9c8c`bf23fcb0 fffff800`7d858140 : nt!WheapProcessWorkQueueItem+0x48
ffffb105`2b2fbc90 fffff800`7d2c8b05 : 00000000`00000000 ffff9c8c`bf26e700 ffff9c8c`bf23fcb0 ffff9c8c`c1bf1fd8 : nt!WheapWorkQueueWorkerRoutine+0x2b
ffffb105`2b2fbcc0 fffff800`7d3432d7 : ffff9c8c`bf26e700 00000000`00000080 ffff9c8c`bf2cd440 ffff9c8c`bf26e700 : nt!ExpWorkerThread+0xf5
ffffb105`2b2fbd50 fffff800`7d3c4516 : ffffb280`bbe81180 ffff9c8c`bf26e700 fffff800`7d343290 00000000`00000000 : nt!PspSystemThreadStartup+0x47
ffffb105`2b2fbda0 00000000`00000000 : ffffb105`2b2fc000 ffffb105`2b2f6000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


THREAD_SHA1_HASH_MOD_FUNC: 26acd050bd9f055d0a04825d57b9e0e6be9c1a07

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: e1ca14ad460db17fee32f4b133c79439b72309bb

THREAD_SHA1_HASH_MOD: 30a3e915496deaace47137d5b90c3ecc03746bf6

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_MAE_PRV

BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_MAE_PRV

PRIMARY_PROBLEM_CLASS: 0x124_GenuineIntel_PROCESSOR_MAE_PRV

TARGET_TIME: 2018-12-24T13:52:47.000Z

OSBUILD: 17134

OSSERVICEPACK: 472

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2018-12-14 01:53:05

BUILDDATESTAMP_STR: 160101.0800

BUILDLAB_STR: WinBuild

BUILDOSVER_STR: 10.0.17134.472

ANALYSIS_SESSION_ELAPSED_TIME: 937

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x124_genuineintel_processor_mae_prv

FAILURE_ID_HASH: {19475660-b379-74ba-2292-20e44ea2824d}

Followup: MachineOwner
---------

 

[BlaqC]

In the end, it was the video card. After I replaced the motherboard battery, reseated all connectors, cleaned the RAM connectors, reseated the CPU and replaced the thermal paste, examined the mobo for bulging or burst capacitors… what did the trick was replacing the video card with some used $20 card from Kijiji for testing purposes.

The system has run like a champ for over a week.