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: ffffe6020379f020, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000bea00000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000108, 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: 2467
Key : Analysis.Elapsed.mSec
Value: 2481
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 155
Key : Analysis.Init.Elapsed.mSec
Value: 5590
Key : Analysis.Memory.CommitPeak.Mb
Value: 94
Key : Bugcheck.Code.LegacyAPI
Value: 0x124
Key : Dump.Attributes.AsUlong
Value: 18
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Failure.Bucket
Value: LKD_0x124_0_AuthenticAMD_PROCESSOR__UNKNOWN_IMAGE_AuthenticAMD.sys
Key : Failure.Hash
Value: {f59f17e7-f24e-04f5-3f16-e9425b2acba5}
BUGCHECK_CODE: 124
BUGCHECK_P1: 0
BUGCHECK_P2: ffffe6020379f020
BUGCHECK_P3: bea00000
BUGCHECK_P4: 108
FILE_IN_CAB: WHEA-20231119-2118.dmp
DUMP_FILE_ATTRIBUTES: 0x18
Kernel Generated Triage Dump
Live Generated Dump
PROCESS_NAME: smss.exe
STACK_TEXT:
ffffcd86`36aa6f30 fffff801`3fc071f7 : ffffe602`0379f000 00000000`00000000 ffffe602`0379f020 000000f1`d427faa8 : nt!LkmdTelCreateReport+0x1d9
ffffcd86`36aa7470 fffff801`3fc070ee : ffffe602`0379f000 ffffcd86`36aa7b60 00000000`00000000 00000000`00000000 : nt!WheapReportLiveDump+0x7b
ffffcd86`36aa74b0 fffff801`3fa50195 : 00000000`00000001 ffffcd86`36aa7b60 00000000`00000000 00000000`00000000 : nt!WheapReportDeferredLiveDumps+0x7a
ffffcd86`36aa74e0 fffff801`3f94fde1 : 00000000`00000000 00000000`00000000 00000000`00000001 fffff801`4393a22c : nt!WheaCrashDumpInitializationComplete+0x59
ffffcd86`36aa7510 fffff801`3f62b6e8 : ffffe602`0cc63080 00000000`00000000 00000000`0000022c 00000000`00000001 : nt!NtSetSystemInformation+0x971
ffffcd86`36aa7ae0 00007ffe`861f2a84 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000f1`d427fa48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`861f2a84
MODULE_NAME: AuthenticAMD
IMAGE_NAME: AuthenticAMD.sys
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: LKD_0x124_0_AuthenticAMD_PROCESSOR__UNKNOWN_IMAGE_AuthenticAMD.sys
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {f59f17e7-f24e-04f5-3f16-e9425b2acba5}
Followup: MachineOwner
---------
drive.google.com
