BSOD WHEA_UNCORRECTABLE_ERROR

Question

BSOD WHEA_UNCORRECTABLE_ERROR

Anonymous

Hi,

Can anyone help analyze the minidump and help me understand why my PC is crashing? It occurs randomly while I run some games. I have a 3080ti newly installed. but it is crashing on non-GPU intensive games.

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

Loading Dump File [C:\Users\me\Desktop\031823-8453-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 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff804`66400000 PsLoadedModuleList = 0xfffff804`6702a310
Debug session time: Sat Mar 18 21:06:26.068 2023 (UTC - 4:00)
System Uptime: 0 days 0:55:11.690
Loading Kernel Symbols
...............................................................
................................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
.........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`667fa110 48894c2408      mov     qword ptr [rsp+8],rcx ss:ffffc680`131648f0=0000000000000124
7: 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: ffffdb0675435028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000f2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000030005, 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: 3202

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 8799

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 1

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x124

    Key  : Bugcheck.Code.Register
    Value: 0x124

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1

FILE_IN_CAB:  031823-8453-01.dmp

BUGCHECK_CODE:  124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffdb0675435028

BUGCHECK_P3: f2000000

BUGCHECK_P4: 30005

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Heaven.exe

STACK_TEXT:  
ffffc680`131648e8 fffff804`668b688a     : 00000000`00000124 00000000`00000000 ffffdb06`75435028 00000000`f2000000 : nt!KeBugCheckEx
ffffc680`131648f0 fffff804`637115b0     : 00000000`00000000 ffffdb06`75435028 ffffdb06`6f1f32d0 ffffdb06`75435028 : nt!HalBugCheckSystem+0xca
ffffc680`13164930 fffff804`669b8ace     : 00000000`00000000 ffffc680`131649d9 ffffdb06`75435028 ffffdb06`6f1f32d0 : PSHED!PshedBugCheckSystem+0x10
ffffc680`13164960 fffff804`668b81b1     : ffffdb06`75464900 ffffdb06`75464900 ffffdb06`6f1f3320 ffffdb06`6f1f32d0 : nt!WheaReportHwError+0x46e
ffffc680`13164a40 fffff804`668b8523     : 00000000`00000007 ffffdb06`6f1f3320 ffffdb06`6f1f32d0 00000000`00000007 : nt!HalpMcaReportError+0xb1
ffffc680`13164bb0 fffff804`668b8400     : ffffdb06`6f0cb0b8 00000000`00000001 00000000`00000000 00000000`00000000 : nt!HalpMceHandlerCore+0xef
ffffc680`13164c00 fffff804`668b8651     : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : nt!HalpMceHandler+0xe0
ffffc680`13164c40 fffff804`668b78bb     : 00000000`00000000 00000000`00000000 ffffc680`13164ed0 00000000`00000000 : nt!HalpMceHandlerWithRendezvous+0xc9
ffffc680`13164c70 fffff804`668ba105     : ffffdb06`6f0cb0b8 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpHandleMachineCheck+0x5f
ffffc680`13164ca0 fffff804`6690fbc9     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalHandleMcheck+0x35
ffffc680`13164cd0 fffff804`6680acba     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9
ffffc680`13164d00 fffff804`6680a977     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffffc680`13164e40 00000000`5aad8516     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277
00000000`18e9f4a8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x5aad8516

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.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

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

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

3 answers

Answer 1

Thanks for the update. The dmp file indicates that the Intel processor is causing the crash this can be heat-related, driver problems, or other hardware issues. Please try each below suggestion.

If you have overclocked your CPU or enabled XMP/DOCP. Please reset your BIOS settings to their optimal default.
There are also errors related to Malwarebytes. Try to fully uninstall this third-party antivirus using their Uninstall/Support tool.
Make sure your processor and peripherals are not overheating.
Ensure the CPU cooler fan is properly attached to the processor.
Go to the motherboard Manufacturer's support website and check for the latest chipset and BIOS updates. Download the drivers directly from the Manufacturer's support website. Don't use any driver updater software to download the drivers.
Clean and install the Nvidia Graphics Drivers. Download the latest drivers from the Manufacturer's support website.

Select Custom Install then perform a clean installation.

Restart your computer.

Power supply and motherboard problems can also cause this error.

Make sure that all power cables are correctly attached.

Answer 2

Anonymous

here's the dump file thanks!

031823-8453-01.zip

0 comments

Answer 3

Hi, I'm Jan and I'm happy to help you today. I'm sorry you're having this problem. This error will only appear if a fatal hardware error has occurred. Please share the latest dmp files for us to diagnose as there might be other drivers causing the computer crash/BSOD. Thank you

Please find this folder.

C:\Windows\Minidump

Put the files in a zip

upload files to OneDrive

Share the link here.

Thank you

Share via

BSOD WHEA_UNCORRECTABLE_ERROR

3 answers