Share via

Windows WHEA Uncorrectable Error

Anonymous
2023-01-08T16:59:28+00:00

Hello, I have been having a windows WHEA Uncorrectable ERROR for about two months now. It happens when I attempt to play a game on my M.2 SSD. I have tried 2 brand new SSDs all give me the same issue. If I use a HDD I get no issues when running my game. I have replaced my motherboard, cpu & SSD no fix. I have read many forums and articles and tried almost every tip and trick that has been recommended.I have no minidump file as they do not get created when I get a BSOD. The only DMP file I was able to find is when I go to ( Windows -> LiveKernelReports -> WHEA) when I analyze that I get:
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: ffff9c04189ee8c0, Address of the nt!_WHEA_ERROR_RECORD structure.

Arg3: 00000000bea00000, High order 32-bits of the MCi_STATUS value.

Arg4: 0000000001000108, 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: 2687 

Key  : Analysis.DebugAnalysisManager 

Value: Create 

Key  : Analysis.Elapsed.mSec 

Value: 2788 

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: 343 

Key  : Analysis.Init.Elapsed.mSec 

Value: 8818 

Key  : Analysis.Memory.CommitPeak.Mb 

Value: 84 

Key  : Bugcheck.Code.DumpHeader 

Value: 0x124 

Key  : Bugcheck.Code.Register 

Value: 0x5650f1a0 

Key  : Dump.Attributes.AsUlong 

Value: 18 

Key  : Dump.Attributes.KernelGeneratedTriageDump 

Value: 1 

FILE_IN_CAB: WHEA-20230106-1536.dmp

DUMP_FILE_ATTRIBUTES: 0x18

Kernel Generated Triage Dump

Live Generated Dump

BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffff9c04189ee8c0

BUGCHECK_P3: bea00000

BUGCHECK_P4: 1000108

PROCESS_NAME: smss.exe

STACK_TEXT:

ffff81875650f150 fffff8073855e2cf : ffff9c04189ee8a0 0000000000000000 ffff9c04189ee8c0 0000000000000022 : nt!LkmdTelCreateReport+0x13e

ffff81875650f690 fffff8073855e1c6 : ffff9c04189ee8a0 fffff80700000000 000000d800000000 000000d84617fac0 : nt!WheapReportLiveDump+0x7b

ffff81875650f6d0 fffff807383cb141 : 0000000000000001 ffff81875650fb40 000000d84617fac0 0000000000000238 : nt!WheapReportDeferredLiveDumps+0x7a

ffff81875650f700 fffff80738252927 : 0000000000000000 ffff9c0418bd6030 0000000000000103 0000000000000000 : nt!WheaCrashDumpInitializationComplete+0x59

ffff81875650f730 fffff8073800caf8 : ffff9c041ae30000 ffff9c041ae35d00 ffff81875650fb40 ffff9c0400000000 : nt!NtSetSystemInformation+0x1f7

ffff81875650fac0 00007ffe556305f4 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x28

000000d84617fa68 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffe`556305f4

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


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: ffff9c04189ee8c0, Address of the nt!_WHEA_ERROR_RECORD structure.

Arg3: 00000000bea00000, High order 32-bits of the MCi_STATUS value.

Arg4: 0000000001000108, 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: 2687 

Key  : Analysis.DebugAnalysisManager 

Value: Create 

Key  : Analysis.Elapsed.mSec 

Value: 2788 

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: 343 

Key  : Analysis.Init.Elapsed.mSec 

Value: 8818 

Key  : Analysis.Memory.CommitPeak.Mb 

Value: 84 

Key  : Bugcheck.Code.DumpHeader 

Value: 0x124 

Key  : Bugcheck.Code.Register 

Value: 0x5650f1a0 

Key  : Dump.Attributes.AsUlong 

Value: 18 

Key  : Dump.Attributes.KernelGeneratedTriageDump 

Value: 1 

FILE_IN_CAB: WHEA-20230106-1536.dmp

DUMP_FILE_ATTRIBUTES: 0x18

Kernel Generated Triage Dump

Live Generated Dump

BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffff9c04189ee8c0

BUGCHECK_P3: bea00000

BUGCHECK_P4: 1000108

PROCESS_NAME: smss.exe

STACK_TEXT:

ffff81875650f150 fffff8073855e2cf : ffff9c04189ee8a0 0000000000000000 ffff9c04189ee8c0 0000000000000022 : nt!LkmdTelCreateReport+0x13e

ffff81875650f690 fffff8073855e1c6 : ffff9c04189ee8a0 fffff80700000000 000000d800000000 000000d84617fac0 : nt!WheapReportLiveDump+0x7b

ffff81875650f6d0 fffff807383cb141 : 0000000000000001 ffff81875650fb40 000000d84617fac0 0000000000000238 : nt!WheapReportDeferredLiveDumps+0x7a

ffff81875650f700 fffff80738252927 : 0000000000000000 ffff9c0418bd6030 0000000000000103 0000000000000000 : nt!WheaCrashDumpInitializationComplete+0x59

ffff81875650f730 fffff8073800caf8 : ffff9c041ae30000 ffff9c041ae35d00 ffff81875650fb40 ffff9c0400000000 : nt!NtSetSystemInformation+0x1f7

ffff81875650fac0 00007ffe556305f4 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x28

000000d84617fa68 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffe`556305f4

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


As well in my event viewer, I see the following errors:
The driver \Driver\WudfRd failed to load for the device HID\VID_1532&PID_0529&MI_03&Col02\8&33609df2&0&0001. (Warning)

The device driver for the Trusted Platform Module (TPM) encountered a non-recoverable error in the TPM hardware, which prevents TPM services (such as data encryption) from being used. For further help, please contact the computer manufacturer. (Error)

My PC Build is:3060 ti founders

Corsair VENGANCE RGB PRO 16gb 3200mhz

Ryzen 7 7800x 8 core processor

WDC 1 TB HDD/ SEAGATE FIRECUDA 520 SSD

650 W CoolerMaster PSU Please let me know of anything you can think of to help me fix this issue. Thank you!! If anything I said is unclear please let me know I am more than happy to clarify.


Windows for home | Windows 10 | Devices and drivers

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 No comments

13 answers

Sort by: Most helpful
  1. DYARI BARHAM 34,856 Reputation points Independent Advisor
    2023-01-10T07:26:22+00:00

    Thanks for sharing the Event Viewer Logs.

    Event Viewer logs indicates Event ID 41: "The system has rebooted without cleanly shutting down first". This event indicates that some unexpected activity prevented Windows from shutting down correctly. Such a shutdown might be caused by an interruption in the power supply or by a Stop error.

    https://learn.microsoft.com/en-us/troubleshoot/...

    Since BugcheckCode and PowerButtonTimestamp values are zero as mentioned below:

    BugcheckCode 0

    BugcheckParameter1 0x0

    BugcheckParameter2 0x0

    BugcheckParameter3 0x0

    BugcheckParameter4 0x0

    SleepInProgress 0

    PowerButtonTimestamp 0

    BootAppStatus 0

    Checkpoint 0

    This behavior might indicate a power supply problem. If the power to a computer is interrupted, the computer might shut down without generating a Stop error.

    To help isolate the problem, do the following steps:

    Disable Fast Startup:

    https://www.windowscentral.com/how-disable-wind...

    Test the RAM with the free utility MemTest86, then run a full 8 pass scan to test your RAM for physical errors:

    https://www.tenforums.com/tutorials/14201-memte...

    Check the power supply. Verify that the power supply has enough wattage to appropriately handle the installed devices.

    Check for overheating. Examine the internal temperature of the hardware and check for any overheating components.

    Test the CPU with Prime95:

    https://www.tenforums.com/tutorials/16474-prime...

    Please let me know if you need further assistance and keep me updated.

    ____________________________________________________________

    Standard Disclaimer: There are links to non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the sites before you decide to download and install it.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2023-01-09T15:42:01+00:00

    Here are my logs

    https://1drv.ms/u/s!Aghqm-wPVulikjyqiyRHech6ny4F?e=On54yu (system log)

    https://1drv.ms/u/s!Aghqm-wPVulikj-0GvhPfG9Yn8QI?e=OYbxeD (administrative events log)I uploaded the administrative event log and the system logs.

    Was this answer helpful?

    0 comments No comments
  3. DYARI BARHAM 34,856 Reputation points Independent Advisor
    2023-01-09T07:33:42+00:00

    Thanks for updating me. Kindly share the Event viewer logs:

    https://www.yourwindowsguide.com/2017/12/how-to...

    Regards,

    ____________________________________________________________

    Standard Disclaimer: There are links to non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the sites before you decide to download and install it.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2023-01-08T20:04:41+00:00

    I installed the chipset drivers as well the new BIOS and I still get the same BSOD. No mini dump was created from the BSOD I only have the one I sent in my original post. I have nothing overclocked everything is stock.

    Was this answer helpful?

    0 comments No comments
  5. DYARI BARHAM 34,856 Reputation points Independent Advisor
    2023-01-08T18:34:36+00:00

    Hi XxLe9endXx11,

    I'm Dyari. Thanks for reaching out. I will be happy to assist you in this regard.

    The minidump analysis indicates AuthenticAMD.sys as a cause of the BSOD which is related to AMD processor.

    To troubleshoot this issue, kindly Download then install the latest version of BIOS & Chipset drivers only from the manufacturer's website.

    If you are overclocking your PC, try running everything (CPU, GPU, system memory) at their stock speeds. See if the issue is still reproducible. Or, turn off XMP profile or set it to Auto.

    Please do not hesitate to ask if you need further assistance.

    Stay safe

    Was this answer helpful?

    0 comments No comments