Question WHEA_UNCORRECTABLE_ERROR BSOD

[Vangoule]

For the last few days I've been dealing with intermitted BSOD's with either WHEA_UNCORRECTABLE_ERROR, a watchdog error or just a black screen. I've dusted my entire PC just incase it was overheating and didn't notice a hotspot temp of 106C on my GPU which seemed dodgy but not sure if it's related. It mostly happens when I'm alt tabbed from a game like PathOfExile

Here is what the minidump analysis came back with:

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2624

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 3734

Key : Analysis.Init.CPU.mSec
Value: 405

Key : Analysis.Init.Elapsed.mSec
Value: 6382

Key : Analysis.Memory.CommitPeak.Mb
Value: 103


FILE_IN_CAB: 051622-12734-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
Kernel Generated Triage Dump

BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffff8588e4e6d028

BUGCHECK_P3: b2000000

BUGCHECK_P4: 30005

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: PathOfExile.ex

STACK_TEXT:
ffffab80fd9a08f8 fffff80424f0164b : 0000000000000124 0000000000000000 ffff8588e4e6d028 00000000b2000000 : nt!KeBugCheckEx
ffffab80fd9a0900 fffff804216f10c0 : 0000000000000000 ffffab80fd9a09d9 ffff8588e4e6d028 ffff8588e4e6d028 : nt!HalBugCheckSystem+0xeb
ffffab80fd9a0940 fffff8042503f9f3 : 0000000000000000 ffffab80fd9a09d9 ffff8588e4e6d028 ffff8588e389be70 : PSHED!PshedBugCheckSystem+0x10
ffffab80fd9a0970 fffff80424f0303d : ffff8588e9052900 ffff8588e9052900 ffff8588e389bec0 bfebfbff7ffafbff : nt!WheaReportHwError+0x393
ffffab80fd9a0a40 fffff80424f03488 : 0000000000000002 ffff858800000000 0000000000000000 0000000000000002 : nt!HalpMcaReportError+0xb1
ffffab80fd9a0ba0 fffff80424f0331c : ffff8588e3137e00 0000000000000001 0000000000000000 0000000000000000 : nt!HalpMceHandlerCore+0x138
ffffab80fd9a0c00 fffff80424f035c1 : 0000000000000010 0000000000000001 0000000000000000 0000000000000000 : nt!HalpMceHandler+0xe0
ffffab80fd9a0c40 fffff80424f02786 : 0000000000000000 0000000000000000 ffffab80fd9a0ed0 0000004f00520000 : nt!HalpMceHandlerWithRendezvous+0xc9
ffffab80fd9a0c70 fffff80424f0513b : ffff8588e3137e00 0000000000000000 0000000000000000 0000000000000000 : nt!HalpHandleMachineCheck+0x62
ffffab80fd9a0ca0 fffff80424f65719 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!HalHandleMcheck+0x3b
ffffab80fd9a0cd0 fffff80424e266fe : 0000000000000000 000000060000023e 0000000000000000 0000000000000000 : nt!KiHandleMcheck+0x9
ffffab80fd9a0d00 fffff80424e26328 : 0000000000000000 0000000000000000 0000008571bfed90 0000000000000000 : nt!KxMcheckAbort+0x7e
ffffab80fd9a0e40 00007ff623b35d30 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiMcheckAbort+0x2a8
0000008571bfec98 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ff6`23b35d30


MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {5371cb52-c3d9-558e-47d4-d31c09567ca2}

Followup: MachineOwner

Previously no logs were being created but this recent crash was just a black screen and did create a log (Hopefully not due to me breaking something else when dusting).

The computer is 3 years old and was a customized PC from PC SPECIALIST. Here is the specs and temps at idle as reported by HWMonitor: https://prnt.sc/jYpe8IrFjKCA

I'm lost on what to even check now... I've done memtest which reported no issues, tried installing windows 11 incase there was something wrong in windows, updated all my drivers except BIOS, intel processor diagnostic tool passed.

Checking the bug report using !errec:

!errrec ffff8588e4e6d028
===============================================================================
Common Platform Error Record @ ffff8588e4e6d028
-------------------------------------------------------------------------------
Record Id : 01d8692883cfa11d
Severity : Fatal (1)
Length : 1003
Creator : Microsoft
Notify Type : Machine Check Exception
Timestamp : 5/16/2022 15:16:43 (UTC)
Flags : 0x00000000

===============================================================================
Section 0 : Processor Generic
-------------------------------------------------------------------------------
Descriptor @ ffff8588e4e6d0a8
Section @ ffff8588e4e6d1c8
Offset : 416
Length : 192
Flags : 0x00000001 Primary
Severity : Fatal

*
* *
* *
* Either you specified an unqualified symbol, or your debugger *
* doesn't have full symbol information. Unqualified symbol *
* resolution is turned off by default. Please either specify a *
* fully qualified symbol module!symbolname, or enable resolution *
* of unqualified symbols by typing ".symopt- 100". Note that *
* enabling unqualified symbol resolution with network symbol *
* server shares in the symbol path may cause the debugger to *
* appear to hang for long periods of time when an incorrect *
* symbol name is typed or the network symbol server is down. *
* *
* For some commands to work properly, your symbol path *
* must point to .pdb files that have full type information. *
* *
* Certain .pdb files (such as the public OS symbols) do not *
* contain the required information. Contact the group that *
* provided you with these symbols if you need this command to *
* work. *
* *
* Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION *
* *
*
*
* *
* *
* Either you specified an unqualified symbol, or your debugger *
* doesn't have full symbol information. Unqualified symbol *
* resolution is turned off by default. Please either specify a *
* fully qualified symbol module!symbolname, or enable resolution *
* of unqualified symbols by typing ".symopt- 100". Note that *
* enabling unqualified symbol resolution with network symbol *
* server shares in the symbol path may cause the debugger to *
* appear to hang for long periods of time when an incorrect *
* symbol name is typed or the network symbol server is down. *
* *
* For some commands to work properly, your symbol path *
* must point to .pdb files that have full type information. *
* *
* Certain .pdb files (such as the public OS symbols) do not *
* contain the required information. Contact the group that *
* provided you with these symbols if you need this command to *
* work. *
* *
* Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION *
* *
*
No valid data fields are present.

===============================================================================
Section 1 : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor @ ffff8588e4e6d0f0
Section @ ffff8588e4e6d288
Offset : 608
Length : 64
Flags : 0x00000000
Severity : Fatal

*
* *
* *
* Either you specified an unqualified symbol, or your debugger *
* doesn't have full symbol information. Unqualified symbol *
* resolution is turned off by default. Please either specify a *
* fully qualified symbol module!symbolname, or enable resolution *
* of unqualified symbols by typing ".symopt- 100". Note that *
* enabling unqualified symbol resolution with network symbol *
* server shares in the symbol path may cause the debugger to *
* appear to hang for long periods of time when an incorrect *
* symbol name is typed or the network symbol server is down. *
* *
* For some commands to work properly, your symbol path *
* must point to .pdb files that have full type information. *
* *
* Certain .pdb files (such as the public OS symbols) do not *
* contain the required information. Contact the group that *
* provided you with these symbols if you need this command to *
* work. *
* *
* Type referenced: hal!_WHEA_XPF_PROCESSOR_ERROR_SECTION *
* *
*
*
* *
* *
* Either you specified an unqualified symbol, or your debugger *
* doesn't have full symbol information. Unqualified symbol *
* resolution is turned off by default. Please either specify a *
* fully qualified symbol module!symbolname, or enable resolution *
* of unqualified symbols by typing ".symopt- 100". Note that *
* enabling unqualified symbol resolution with network symbol *
* server shares in the symbol path may cause the debugger to *
* appear to hang for long periods of time when an incorrect *
* symbol name is typed or the network symbol server is down. *
* *
* For some commands to work properly, your symbol path *
* must point to .pdb files that have full type information. *
* *
* Certain .pdb files (such as the public OS symbols) do not *
* contain the required information. Contact the group that *
* provided you with these symbols if you need this command to *
* work. *
* *
* Type referenced: hal!_WHEA_XPF_PROCESSOR_ERROR_SECTION *
* *
*
No valid data fields are present.

===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ ffff8588e4e6d138
Section @ ffff8588e4e6d2c8
Offset : 672
Length : 292
Flags : 0x00000000
Severity : Fatal

*
* *
* *
* Either you specified an unqualified symbol, or your debugger *
* doesn't have full symbol information. Unqualified symbol *
* resolution is turned off by default. Please either specify a *
* fully qualified symbol module!symbolname, or enable resolution *
* of unqualified symbols by typing ".symopt- 100". Note that *
* enabling unqualified symbol resolution with network symbol *
* server shares in the symbol path may cause the debugger to *
* appear to hang for long periods of time when an incorrect *
* symbol name is typed or the network symbol server is down. *
* *
* For some commands to work properly, your symbol path *
* must point to .pdb files that have full type information. *
* *
* Certain .pdb files (such as the public OS symbols) do not *
* contain the required information. Contact the group that *
* provided you with these symbols if you need this command to *
* work. *
* *
* Type referenced: hal!_WHEA_XPF_MCA_SECTION *
* *
*
*
* *
* *
* Either you specified an unqualified symbol, or your debugger *
* doesn't have full symbol information. Unqualified symbol *
* resolution is turned off by default. Please either specify a *
* fully qualified symbol module!symbolname, or enable resolution *
* of unqualified symbols by typing ".symopt- 100". Note that *
* enabling unqualified symbol resolution with network symbol *
* server shares in the symbol path may cause the debugger to *
* appear to hang for long periods of time when an incorrect *
* symbol name is typed or the network symbol server is down. *
* *
* For some commands to work properly, your symbol path *
* must point to .pdb files that have full type information. *
* *
* Certain .pdb files (such as the public OS symbols) do not *
* contain the required information. Contact the group that *
* provided you with these symbols if you need this command to *
* work. *
* *
* Type referenced: hal!_WHEA_XPF_MCA_SECTION *
* *
*
*
* *
* *
* Either you specified an unqualified symbol, or your debugger *
* doesn't have full symbol information. Unqualified symbol *
* resolution is turned off by default. Please either specify a *
* fully qualified symbol module!symbolname, or enable resolution *
* of unqualified symbols by typing ".symopt- 100". Note that *
* enabling unqualified symbol resolution with network symbol *
* server shares in the symbol path may cause the debugger to *
* appear to hang for long periods of time when an incorrect *
* symbol name is typed or the network symbol server is down. *
* *
* For some commands to work properly, your symbol path *
* must point to .pdb files that have full type information. *
* *
* Certain .pdb files (such as the public OS symbols) do not *
* contain the required information. Contact the group that *
* provided you with these symbols if you need this command to *
* work. *
* *
* Type referenced: hal!_WHEA_XPF_MCA_SECTION *
* *
*
*
* *
* *
* Either you specified an unqualified symbol, or your debugger *
* doesn't have full symbol information. Unqualified symbol *
* resolution is turned off by default. Please either specify a *
* fully qualified symbol module!symbolname, or enable resolution *
* of unqualified symbols by typing ".symopt- 100". Note that *
* enabling unqualified symbol resolution with network symbol *
* server shares in the symbol path may cause the debugger to *
* appear to hang for long periods of time when an incorrect *
* symbol name is typed or the network symbol server is down. *
* *
* For some commands to work properly, your symbol path *
* must point to .pdb files that have full type information. *
* *
* Certain .pdb files (such as the public OS symbols) do not *
* contain the required information. Contact the group that *
* provided you with these symbols if you need this command to *
* work. *
* *
* Type referenced: hal!_WHEA_XPF_MCA_SECTION *
* *
*
Error : Unknown (Proc 0 Bank 0)
Status : 0x0000000000000000

===============================================================================
Section 3 : {c34832a1-02c3-4c52-a9f1-9f1d5d7723fc}
-------------------------------------------------------------------------------
Descriptor @ ffff8588e4e6d180
Section @ ffff8588e4e6d3ec
Offset : 964
Length : 39
Flags : 0x00000000
Severity : Informational

* Unknown section format *

 

[johnbl]

For the last few days I've been dealing with intermitted BSOD's with either WHEA_UNCORRECTABLE_ERROR, a watchdog error or just a black screen. I've dusted my entire PC just incase it was overheating and didn't notice a hotspot temp of 106C on my GPU which seemed dodgy but not sure if it's related. It mostly happens when I'm alt tabbed from a game like PathOfExile

Here is what the minidump analysis came back with:




Previously no logs were being created but this recent crash was just a black screen and did create a log (Hopefully not due to me breaking something else when dusting).

The computer is 3 years old and was a customized PC from PC SPECIALIST. Here is the specs and temps at idle as reported by HWMonitor: https://prnt.sc/jYpe8IrFjKCA

I'm lost on what to even check now... I've done memtest which reported no issues, tried installing windows 11 incase there was something wrong in windows, updated all my drivers except BIOS, intel processor diagnostic tool passed.

Checking the bug report using !errec:

you should put the minidump on a server so it can be looked at with the windows debugger.
better if you have a kernel memory dump, it includes the logs and what is running on all cpus, usb subsystem and plug and play.
generally you will need to change the memory dump type to kernel.
check for file c:\windows\memory.dmp

 

[Vangoule]

I'll see what I can do, I originally change it to mini dump in the hopes of actually getting a memory dumps as previously it was failing. Here's the minidump: https://drive.google.com/file/d/1KZgLRWM17enIq3eie_sWXHSXO5c-B2Xi/view?usp=sharing

 

[johnbl]

I'll see what I can do, I originally change it to mini dump in the hopes of actually getting a memory dumps as previously it was failing. Here's the minidump: https://drive.google.com/file/d/1KZgLRWM17enIq3eie_sWXHSXO5c-B2Xi/view?usp=sharing

I would run autoruns from microsoft https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns
find the menu options to hide microsoft entries. then look at the list

I would disable your old usb drivers from 2010
silib.sys, and siusbxp.sys
I would also disable applecharger.sys from 2013
and reboot and see if it has any effect.

system was running 1 hour 50 mins before bugcheck.
i did not see a direct cause of the bugcheck.

 

[Vangoule]

Here is the autoruns file: https://drive.google.com/file/d/1KHospKFKjH8Ho0CYJDFrla1t403bxyc-/view?usp=sharing

There's a lot in red, not really sure what this is saying though, just that it's unverified I guess?

As for disabling drivers, how would one go about this? Doing it through device manager, I cannot find where to see what the .sys names correlate.

 

[Vangoule]

Ran Timespy Extreme for 20 passes, no crash - 106C Hot Spot Temp, 75C GPU Temp, the hot spot temp is concerning but doesn't seem to be the issue.
Ran Prime95 CPU Stress Test - CPU hit 97C, and crashed. Seems like it's my CPU overheating?

 

[Vangoule]

Tested again after changing fan curve on H115i to EXTREME from QUIET, seems to be running massively cooler at 80C while running Prime95, it still crashed on balance in a weird way in which SUDDENLY the temps just jumped up to 98C, questioning if something is wrong with pump now.

 

[johnbl]

Tested again after changing fan curve on H115i to EXTREME from QUIET, seems to be running massively cooler at 80C while running Prime95, it still crashed on balance in a weird way in which SUDDENLY the temps just jumped up to 98C, questioning if something is wrong with pump now.

pump run via controller thru usb bus?

 

[Vangoule]

It's an AIO so presumably controller, ICUE allows the changing of fan modes. Here are the temperatures/RPM's... I just reset the overclock and ran Prime95. This is interesting as it no longer crashes at all though, so that's good I guess?
It's not good when running at 100C though... So it must be the CPU cooler eitherway, perhaps something with voltage/temperature interaction before causing the crash. Reset everything so RAM is trash speeds now and CPU auto turbo around 4.7GHZ instead of 5-4.8.
Voltage was maxing out at 1.5 previously, and now maxed at 1.3 after reset.

 

[johnbl]

the cpu starts thermal shutdown at 100 C
it could explain the general error reported from inside the cpu.