Windows 10: WHEA Uncrrectable Error 124

Dzmitrij Malashchenko · Nov 7, 2022

Hi guys, i received after analysing this result. I have a brandnew PC from digitec.ch https://www.digitec.ch/de/s1/product/captiva-r65-854-amd-ryzen-9-5950x-32-gb-2000-gb-ssd-pc-17342698. The pc crashes always after returning in a game to menu.... Can someone help me and tell, what is the actual problem which is causing the pc crash / pc restart? ** Bugcheck Analysis ** *********

:)

Dzmitrij Malashchenko · Nov 8, 2022

WHEA Uncrrectable Error (124)

Hi guys, i received after analysing this result. I have a brandnew PC from digitec.ch https://www.digitec.ch/de/s1/product/captiva-r65-854-amd-ryzen-9-5950x-32-gb-2000-gb-ssd-pc-17342698. The pc crashes always after returning in a game to menu.... Can someone help me and tell, what is the actual problem which is causing the pc crash / pc restart?

*
* 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: ffffe40adc202028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000bc000800, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000001010135, 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: 2796

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 20153

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

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

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

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

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

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

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: 110722-14390-01.dmp

BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffe40adc202028

BUGCHECK_P3: bc000800

BUGCHECK_P4: 1010135

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: VALORANT-Win64-Shipping.exe

STACK_TEXT:
ffffac80`8d49b918 fffff805`404b448a : 00000000`00000124 00000000`00000000 ffffe40a`dc202028 00000000`bc000800 : nt!KeBugCheckEx
ffffac80`8d49b920 fffff805`3be115b0 : 00000000`00000000 ffffe40a`dc202028 ffffe40a`d92f04f0 ffffe40a`dc202028 : nt!HalBugCheckSystem+0xca
ffffac80`8d49b960 fffff805`405b65ae : 00000000`00000000 ffffac80`8d49ba09 ffffe40a`dc202028 ffffe40a`d92f04f0 : PSHED!PshedBugCheckSystem+0x10
ffffac80`8d49b990 fffff805`404b5db1 : ffffe40a`e3387900 ffffe40a`e3387900 ffffe40a`d92f0540 ffffe40a`d92f04f0 : nt!WheaReportHwError+0x46e
ffffac80`8d49ba70 fffff805`404b6123 : 00000000`0000000e ffffe40a`d92f0540 ffffe40a`d92f04f0 00000000`0000000e : nt!HalpMcaReportError+0xb1
ffffac80`8d49bbe0 fffff805`404b6000 : ffffe40a`d9102a10 00000060`00000000 ffffac80`8d49be00 00000018`00000048 : nt!HalpMceHandlerCore+0xef
ffffac80`8d49bc30 fffff805`404b5545 : ffffe40a`d9102a10 ffffac80`8d49bed0 00000000`00000000 00000000`00000000 : nt!HalpMceHandler+0xe0
ffffac80`8d49bc70 fffff805`404b7d05 : ffffe40a`d9102a10 00010018`00000058 00030000`00000043 01d5acdd`d73ef652 : nt!HalpHandleMachineCheck+0xe9
ffffac80`8d49bca0 fffff805`4050d789 : 01d8eddc`a06e527c 00000000`00018000 00000000`00017c00 00070075`00040020 : nt!HalHandleMcheck+0x35
ffffac80`8d49bcd0 fffff805`404080fa : 00650078`0065002e 00000070`00000030 000a0000`00000000 00010018`00000058 : nt!KiHandleMcheck+0x9
ffffac80`8d49bd00 fffff805`40407db7 : ffffac80`00000000 fffff805`40407cec ffffe40a`eec90080 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffffac80`8d49be40 fffff805`40222396 : ffffac80`00000000 ffffe40a`eec91080 00000000`0000000b fffff60a`417d779c : nt!KiMcheckAbort+0x277
fffff60a`417d7760 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeferredReadySingleThread+0xe6

MODULE_NAME: AuthenticAMD

IMAGE_NAME: AuthenticAMD.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x124_0_AuthenticAMD_PROCESSOR__UNKNOWN_IMAGE_AuthenticAMD.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {035dcc87-485b-74b3-1c1b-ee50cb0c2865}

Followup: MachineOwner
---------
Click to expand...

Kreij · Nov 8, 2022

What does this error mean?

Code 124 is not necessarily overheating.
The WHEA-Logger events in the log are what is being thrown.
The MCI devices us the WHEA (Windows Hardware Error Architecture) for reporting stuff.

StingRayish · Nov 8, 2022

Please help: BSOD 124 WHEA uncorrectable error / Windows 10

Hi Sumit,

I have downloaded the test module from Intel and ran every single one of them, my processor passed them all with flying colors.

But the Windows is still crashing producing the same damp files with the code 124 WHEA uncorrectable error.

I'm really confused.

Thank you.

Windows 10: WHEA Uncrrectable Error 124

WHEA Uncrrectable Error 124

WHEA Uncrrectable Error 124

WHEA Uncrrectable Error 124

WHEA Uncrrectable Error 124 - Similar Threads - WHEA Uncrrectable Error

WHEA UNCORRECTABLE ERROR 124

WHEA UNCORRECTABLE ERROR 124

WHEA UNCORRECTABLE ERROR 124

WHEA - BUGCHECK_CODE: 124

WHEA - BUGCHECK_CODE: 124

WHEA Uncrrectable Error 124

WHEA Uncrrectable Error 124

PLS HELP! BIOS WHEA 124 Error

Random reboot while gaming - WHEA ERROR 124