[SOLVED] Need urgent help with BSoD 0x124 WHEA UNCORRECTABLE ERROR

Feb 12, 2022
4
0
10
Hello everyone,

So, I've recently started getting a WHEA_UNCORRECTABLE_ERROR BSoD,
I have run hardware and software diagnostics on every component in my laptop, all pass,
Nothing is overclocked.

Used windows memory diagnostics and Lenovo system diagnostics on RAM, no issues,
Used Intel diagnostic tool and Lenovo system diagnostics on the processor, no issues,

Did the same for almost every component, no issues.

Event logger shows some unusual things, however, I'm not sure if they're related.
Code:
The driver \Driver\WudfRd failed to load for the device PCI\VEN_8086&DEV_9A03&SUBSYS_380C17AA&REV_05\3&11583659&0&20.

Code:
The driver \Driver\WudfRd failed to load for the device ROOT\SYSTEM\0001.

Code:
6062 - Lso was triggered
Plus some DistributedCOM warnings.

I checked out the BDoS minidump file, I also ran !errrec on it, here's the result.
Code:
FAILURE_BUCKET_ID:  0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys
Code:
Microsoft (R) Windows Debugger Version 10.0.22549.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


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


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 22000 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 22000.1.amd64fre.co_release.210604-1628
Machine Name:
Kernel base = 0xfffff804`58000000 PsLoadedModuleList = 0xfffff804`58c29bc0
Debug session time: Sat Feb 12 11:20:03.566 2022 (UTC + 2:00)
System Uptime: 0 days 0:03:34.186
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`58416220 48894c2408      mov     qword ptr [rsp+8],rcx ss:ffff9c01`57a6c920=0000000000000124
10: 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
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffac8e90baf028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000100110a, Low order 32-bits of the MCi_STATUS value.

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    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                ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2608

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 9062

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

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

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

    Key  : WER.OS.Branch
    Value: co_release

    Key  : WER.OS.Timestamp
    Value: 2021-06-04T16:28:00Z

    Key  : WER.OS.Version
    Value: 10.0.22000.1


FILE_IN_CAB:  021222-11546-01.dmp

BUGCHECK_CODE:  124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffac8e90baf028

BUGCHECK_P3: be000000

BUGCHECK_P4: 100110a

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Wrath.exe

STACK_TEXT:  
ffff9c01`57a6c918 fffff804`5850171b     : 00000000`00000124 00000000`00000000 ffffac8e`90baf028 00000000`be000000 : nt!KeBugCheckEx
ffff9c01`57a6c920 fffff804`561d10c0     : 00000000`00000000 ffff9c01`57a6c9f9 ffffac8e`90baf028 ffffac8e`90baf028 : nt!HalBugCheckSystem+0xeb
ffff9c01`57a6c960 fffff804`5863fa03     : 00000000`00000000 ffff9c01`57a6c9f9 ffffac8e`90baf028 ffffac8e`8f1dfe50 : PSHED!PshedBugCheckSystem+0x10
ffff9c01`57a6c990 fffff804`5850310d     : ffffac8e`94b2aa80 ffffac8e`94b2aa80 ffffac8e`8f1dfea0 bfebfbff`7ffafbbf : nt!WheaReportHwError+0x393
ffff9c01`57a6ca60 fffff804`58503558     : 00000000`0000000a ffffac8e`00000000 00000000`00000000 00000000`0000000a : nt!HalpMcaReportError+0xb1
ffff9c01`57a6cbc0 fffff804`585033ec     : ffffac8e`8ef39580 afafafaf`00000001 00000000`00000000 afafafaf`00000000 : nt!HalpMceHandlerCore+0x138
ffff9c01`57a6cc20 fffff804`58503691     : 00000000`00000010 00000000`00000001 00000000`00000000 afafafaf`afafafaf : nt!HalpMceHandler+0xe0
ffff9c01`57a6cc60 fffff804`58502856     : 00000000`00000000 00000000`00000000 ffff9c01`57a6cef0 afafafaf`afafafaf : nt!HalpMceHandlerWithRendezvous+0xc9
ffff9c01`57a6cc90 fffff804`5850520b     : ffffac8e`8ef39580 afafafaf`afafafaf afafafaf`afafafaf afafafaf`afafafaf : nt!HalpHandleMachineCheck+0x62
ffff9c01`57a6ccc0 fffff804`585657f9     : afafafaf`afafafaf afafafaf`afafafaf afafafaf`afafafaf afafafaf`afafafaf : nt!HalHandleMcheck+0x3b
ffff9c01`57a6ccf0 fffff804`58425dfe     : afafafaf`afafafaf afafafaf`afafafaf afafafaf`afafafaf afafafaf`afafafaf : nt!KiHandleMcheck+0x9
ffff9c01`57a6cd20 fffff804`58425a28     : 00000000`00000000 00000000`00000000 00000018`9a12f1b0 00000000`00000000 : nt!KxMcheckAbort+0x7e
ffff9c01`57a6ce60 00007ff9`f4fb2949     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x2a8
00000018`9a12f150 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`f4fb2949


MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys

OS_VERSION:  10.0.22000.1

BUILDLAB_STR:  co_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

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

10: kd> !errrec ffffac8e90baf028
===============================================================================
Common Platform Error Record @ ffffac8e90baf028
-------------------------------------------------------------------------------
Record Id     : 01d81ff1382d2d25
Severity      : Fatal (1)
Length        : 1067
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 2/12/2022 9:20:03 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffffac8e90baf0a8
Section       @ ffffac8e90baf1c8
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    @ ffffac8e90baf0f0
Section       @ ffffac8e90baf288
Offset        : 608
Length        : 128
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    @ ffffac8e90baf138
Section       @ ffffac8e90baf308
Offset        : 736
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    @ ffffac8e90baf180
Section       @ ffffac8e90baf42c
Offset        : 1028
Length        : 39
Flags         : 0x00000000
Severity      : Informational

*** Unknown section format ***

I just got this laptop and I still have 2 years of installments to pay it off, I would genuinely appreciate any help.

Thank you.
 
Solution
I monitored both GPU and CPU temperatures at crash times.
CPU was aroun 69C and GPU was 54C

Basically, your motherboard thinks that your system is having power issues and it is resetting the CPU. You will want to list out all of your drivers and confirm that you do not have any software overclock driver installed. You need to make sure you do not have and overclock in the bios as well.
For example, people often have two copies of certain overclock drivers and can cause problems like this. (first driver tweaks the CPU voltage, then the second driver tweaks the voltage again and causes a power problem)

you could also have a driver that was released before your CPU and bios release date. old drivers do not have the...

Colif

Win 11 Master
Moderator
I just got this laptop and I still have 2 years of installments to pay it off, I would genuinely appreciate any help.
if its brand new, I would take it back and ask them to fix it as you shouldn't get BSOD on new laptop. Especially not this one.

WHEA - Windows Hardware Error Architecture
Can be caused by any hardware and some drivers
can be caused by overclocking - I assume it isn't
can be caused by overclocking software such of Intel Extreme Overclocking utility, so remove if you have it
Can be caused by heat
Can be fixed by updating BIOS

Your report is typical of what I see in WHEA errors, it doesn't tell me a lot.
 
Feb 12, 2022
4
0
10
if its brand new, I would take it back and ask them to fix it as you shouldn't get BSOD on new laptop. Especially not this one.

WHEA - Windows Hardware Error Architecture
Can be caused by any hardware and some drivers
can be caused by overclocking - I assume it isn't
can be caused by overclocking software such of Intel Extreme Overclocking utility, so remove if you have it
Can be caused by heat
Can be fixed by updating BIOS

Your report is typical of what I see in WHEA errors, it doesn't tell me a lot.

It is not overclocked,
BIOS is up to date,
Temp is stable,

Can this truly be a hardware issue if it passed all diagnostic tests thrown at it?
 

Colif

Win 11 Master
Moderator
software tests aren't perfect, they can check if it works to a point but if there is a physical fault, it may not see it.

what tests have you run on hardware? there are only so many you can run
we can't check if its motherboard, not sure about power supply in laptop.
what model lenovo laptop is it?
 
Feb 12, 2022
4
0
10
software tests aren't perfect, they can check if it works to a point but if there is a physical fault, it may not see it.

what tests have you run on hardware? there are only so many you can run
we can't check if its motherboard, not sure about power supply in laptop.
what model lenovo laptop is it?

It is a Lenovo legion 5 running a i7 11800H

I used the Intel processor diagnostic tool
As for the lenovo tests i ran:
BT instructions test,
x87 Floating point test,
MMX test,
SSE test,
AES test,
Stress test

I also ran tests on the mother board:
Chipset,
PCI-PCIe,
RTC,
USB.

Also, note I only get the BSoD when I run a game or so.

All normal.
 
looks like the system had some issue the motherboard reset the cpu to force a reboot. The system rebooted before the power/heating issue was resolved this caused the CPU to get a internal error on the reboot. This was detected by the CPU and the CPU called the bugcheck.

ignore the bugcheck, and focus on the primary cause of why the motherboard reset the CPU.
(most likely gpu pulled too much power due to overheating, then the motherboard reset the cpu to stop the power draw)

other things to look for:
Common causes would be blocked vents (overheating)
overclocking software for GPU causing GPU to use too much power.
overclocking software for CPU causing CPU to overheat.
bitcoin malware being loaded causing GPU to overheat and use too much power.

make sure all the fans are working, set them to max speed in bios if you can.

you can disable browser graphics acceleration for some cases of malware that use it to mine bitcoin.

key factor in the memory dump was the short system uptime.
I did not look at the actual dump file so I did not look for malware or overclock drivers. nor did i dump the cpu temp info structures. Generally temp problems go away after about 15 seconds of the reboot so they might not show in the !tzinfo structure in the memory dump anyway.
 
Last edited:
Feb 12, 2022
4
0
10
looks like the system had some issue the motherboard reset the cpu to force a reboot. The system rebooted before the power/heating issue was resolved this caused the CPU to get a internal error on the reboot. This was detected by the CPU and the CPU called the bugcheck.

ignore the bugcheck, and focus on the primary cause of why the motherboard reset the CPU.
(most likely gpu pulled too much power due to overheating, then the motherboard reset the cpu to stop the power draw)

other things to look for:
Common causes would be blocked vents (overheating)
overclocking software for GPU causing GPU to use too much power.
overclocking software for CPU causing CPU to overheat.
bitcoin malware being loaded causing GPU to overheat and use too much power.

make sure all the fans are working, set them to max speed in bios if you can.

you can disable browser graphics acceleration for some cases of malware that use it to mine bitcoin.

key factor in the memory dump was the short system uptime.
I did not look at the actual dump file so I did not look for malware or overclock drivers. nor did i dump the cpu temp info structures. Generally temp problems go away after about 15 seconds of the reboot so they might not show in the !tzinfo structure in the memory dump anyway.

I monitored both GPU and CPU temperatures at crash times.
CPU was aroun 69C and GPU was 54C
 
I monitored both GPU and CPU temperatures at crash times.
CPU was aroun 69C and GPU was 54C

Basically, your motherboard thinks that your system is having power issues and it is resetting the CPU. You will want to list out all of your drivers and confirm that you do not have any software overclock driver installed. You need to make sure you do not have and overclock in the bios as well.
For example, people often have two copies of certain overclock drivers and can cause problems like this. (first driver tweaks the CPU voltage, then the second driver tweaks the voltage again and causes a power problem)

you could also have a driver that was released before your CPU and bios release date. old drivers do not have the correct voltage/frequency tables for newer release CPU. (newer cpu use lower voltages for a given frequency, old drivers mess this up)

generally this can be seen from actual memory dump file by dumping the driver list and looking at the active cpu frequency.

with a panic dump like you had sometimes not all of the data will be put in the memory dump. in these case you can force a memory dump on a working system and look at the crash dump data.

google microsoft autoruns to get a utility that will let you look at the loaded driver info. look at the 3rd party drivers and check the names and dates. then confirm that your cpu release version is correct for any driver and bios version

your cpu was released Q2'21
Intel Core i711800H Processor 24M Cache up to 4.60 GHz Product Specifications

make sure your bios and drivers are newer than the cpu release date.

if you can not find the problem, I would go into bios and disable features of the cpu that I was not actively using.
then I would disable any bios function that allows the cpu speed to fluctuate.

you should also make sure you have fully updated windows. microsoft loads a dll that will patch cpu microcode that was not repaired/patched by the bios. These will work around known bugs in the various generations of the intel cpus.

this from your debug dump might would make me look for old versions of cpu specfic drivers:
0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys

windows does not recognize your processor id code.

looks like the intel tiger lake cpu has added additional mechanisms to reset your cpu.
Tiger Lake H: Documents and Datasheets (intel.com)
crash log user guide page 27 for diagram. this means
the windows debugger has to be updated to debug the info or that only intel tools will debug the new causes of these crashes.

i only know the older stuff.
 
Last edited:
Solution