WHEA_UNCORRECTABLE_ERROR

Hello, Michal Zajac_594

Welcome to the Microsoft Community

Thank you for your feedback. I have analyzed the blue screen log you provided.

According to the information provided by the dmp file, the system has a WHEA_UNCORRECTABLE_ERROR (124) is a serious hardware error, which usually means that the system has detected an unrecoverable error in the hardware. This error code usually means that there is a hardware problem or the driver is incompatible with the hardware.

The module that caused the error is

IMAGE_NAME: AuthenticAMD.sys, AuthenticAMD.sys usually points to system files or drivers related to AMD processors.

The stack traceback shows that this blue screen error occurred when the system was running and was caused by Grand Theft Auto V (GTA5.exe)

Based on the above analysis, you can try the following methods, which may help your current problem.

Method 1. Make sure that all hardware drivers in the system are updated, especially drivers and chipset drivers related to AMD processors. It is recommended to download and install the latest drivers from the official website of the hardware manufacturer.

Method 2. Go to the device manufacturer's website to check and update the BIOS/UEFI firmware to the latest version. This can solve many problems related to hardware compatibility.

Method 3. Check the hardware, specifically, focus on the following points

1. Memory and hard disk

Use the Windows Memory Diagnostic Tool or MemTest86 to check if there are any errors in the memory. At the same time, please replace the memory slots and reseat the memory modules to ensure that the sockets are clean and tightly inserted. Please use the diagnostic tool provided by the hard disk manufacturer to check the health of the hard disk. Or check and repair file system errors (chkdsk tool).

To check the health of the hard disk, open the command prompt (as an administrator), enter the following command and press Enter:

shell

chkdsk C: /f /r

You may be prompted to run a disk check the next time you restart. Enter Y and press Enter, then restart the computer.

Disclaimer: Running chkdsk checks the file system and file system metadata of the volume to find logical errors and physical errors. To avoid unnecessary trouble, please follow the above steps step by step, do not interrupt or cancel during the operation, and back up important data.

Check the memory. Use the Windows Memory Diagnostic tool to check if there are any errors in the memory. Press Win + R to open the Run dialog box, enter mdsched.exe and press Enter. Select "Restart now and check for problems (recommended)" or "Check for problems the next time you start the computer."

2. CPU. Please check if the CPU is overheating. Make sure the heat sink and fan are working properly. Also make sure that the CPU is not overclocked or restored to the default frequency.
3. Power supply. Please check if the power supply is stable and can provide enough power.

Method 4. Disable unnecessary devices. Some external devices and additional hardware may cause conflicts. Try to disable or disconnect unnecessary devices, including external hard drives, USB devices, etc.

Method 5. Please use third-party hardware testing tools (such as AIDA64, Prime95, etc.) to stress test the system to find out potential hardware problems.

Best regards

Brian - Microsoft Community Support Specialist

Thank you Brian for your response.

I have done all of the above checks:

Method 1. Make sure that all hardware drivers in the system are updated, especially drivers and chipset drivers related to AMD processors. It is recommended to download and install the latest drivers from the official website of the hardware manufacturer.

Method 2. Go to the device manufacturer's website to check and update the BIOS/UEFI firmware to the latest version. This can solve many problems related to hardware compatibility.

Chipset, BIOS and graphic card drivers all up to date.

Method 3. Check the hardware, specifically, focus on the following points

1. Memory and hard disk

Use the Windows Memory Diagnostic Tool or MemTest86 to check if there are any errors in the memory. At the same time, please replace the memory slots and reseat the memory modules to ensure that the sockets are clean and tightly inserted. Please use the diagnostic tool provided by the hard disk manufacturer to check the health of the hard disk. Or check and repair file system errors (chkdsk tool).

To check the health of the hard disk, open the command prompt (as an administrator), enter the following command and press Enter:

shell

chkdsk C: /f /r

You may be prompted to run a disk check the next time you restart. Enter Y and press Enter, then restart the computer.

Disclaimer: Running chkdsk checks the file system and file system metadata of the volume to find logical errors and physical errors. To avoid unnecessary trouble, please follow the above steps step by step, do not interrupt or cancel during the operation, and back up important data.

Check the memory. Use the Windows Memory Diagnostic tool to check if there are any errors in the memory. Press Win + R to open the Run dialog box, enter mdsched.exe and press Enter. Select "Restart now and check for problems (recommended)" or "Check for problems the next time you start the computer."

Memory tests done using Memtest86 with 4 passes - no errors

Disk tests done with chkdsk after reboot - no errors

2. CPU. Please check if the CPU is overheating. Make sure the heat sink and fan are working properly. Also make sure that the CPU is not overclocked or restored to the default frequency.

CPU is not overclocked, the same for memory and GPU. CPU stress test done with prime95 for about 4h - no errors

3. Power supply. Please check if the power supply is stable and can provide enough power.

Power supply checked with tool purchased on amazon with LCD display - all good, no errors or low voltages

Method 4. Disable unnecessary devices. Some external devices and additional hardware may cause conflicts. Try to disable or disconnect unnecessary devices, including external hard drives, USB devices, etc.

I have just one hard drive connected, but only recently - system crashes started from the very beginning though. I will disconnect it anyway to check.

There is a chance, I have done something wrong, but I doubt it. Even disables Precision Boost Overdrive in BIOS, after previous suggestions, but no luck.

Also replaced PCI-e riser cable with a new one. Some time ago, I replaced memory with different (also Corsair) type, but no luck. Sent GPU card to the supplier for checks - came back ok (but I don't know how and if they tested it, as they sold me the card).

I don't know what else I could do. It crashes most of the time not when actually playing, but when I get killed and small video/movie loads up.

Latest Dump file:

************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : true
   AllowNugetExeUpdate : true
   NonInteractiveNuget : true
   AllowNugetMSCredentialProviderInstall : true
   AllowParallelInitializationOfLocalRepositories : true
   EnableRedirectToChakraJsProvider : false

   -- Configuring repositories
      ----> Repository : LocalInstalled, Enabled: true
      ----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.016 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 42

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

Loading Dump File [C:\Windows\Minidump\122824-8093-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 26100 MP (24 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff803`a3c00000 PsLoadedModuleList = 0xfffff803`a4af4850
Debug session time: Sat Dec 28 14:56:56.185 2024 (UTC + 0:00)
System Uptime: 0 days 0:21:21.804
Loading Kernel Symbols
...............................................................
................................................................
................................................................
................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000e3`5526c018).  Type ".hh dbgerr001" for details
Loading unloaded module list
........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`a40b85d0 48894c2408      mov     qword ptr [rsp+8],rcx ss:ffffb900`3b268950=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: ffffce091d968028, 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_MEMORY_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_MEMORY_ERROR_SECTION                ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1437

    Key  : Analysis.Elapsed.mSec
    Value: 1452

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27725.1000

    Key  : Analysis.Version.Description
    Value: 10.2408.27.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2408.27.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x124

    Key  : Bugcheck.Code.TargetModel
    Value: 0x124

    Key  : Dump.Attributes.AsUlong
    Value: 1008

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: 0x124_0_AuthenticAMD_MEMORY__UNKNOWN_FATAL_IMAGE_AuthenticAMD.sys

    Key  : Failure.Hash
    Value: {b0905187-9dbc-d607-4dc5-8630b9eddb7f}

BUGCHECK_CODE:  124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffce091d968028

BUGCHECK_P3: bc000800

BUGCHECK_P4: 1010135

FILE_IN_CAB:  122824-8093-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffce0932ee3080

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  GTA5.exe

STACK_TEXT:  
ffffb900`3b268948 fffff803`a40fb750     : 00000000`00000124 00000000`00000000 ffffce09`1d968028 00000000`bc000800 : nt!KeBugCheckEx
ffffb900`3b268950 fffff803`356d1250     : 00000000`00000000 ffffb900`3b268a19 ffffce09`1d968028 ffffce09`156f7500 : nt!HalBugCheckSystem+0xc0
ffffb900`3b268990 fffff803`a42b7c2b     : 00000000`00000000 ffffb900`3b268a19 ffffce09`1d968028 00000000`00000000 : PSHED!PshedBugCheckSystem+0x10
ffffb900`3b2689c0 fffff803`a40fd496     : 00000000`0000000a 00000000`0000000a ffffce09`156f7550 ffffce09`156f7500 : nt!WheaReportHwError+0x316f7b
ffffb900`3b268a80 fffff803`a40fd850     : 00000000`0000000a ffffce09`00000000 00000000`00000000 00000000`00000000 : nt!HalpMcaReportError+0xb2
ffffb900`3b268bf0 fffff803`a40fd6e4     : ffffce09`156fc780 00000000`00000000 ffffb900`3b268e00 00000000`00000000 : nt!HalpMceHandlerCore+0x138
ffffb900`3b268c50 fffff803`a40fcb3e     : ffffb900`3b268e60 ffffb900`3b268ef0 00000000`00000000 00000000`00000000 : nt!HalpMceHandler+0xe0
ffffb900`3b268c90 fffff803`a41003eb     : ffffb900`3b268e60 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpHandleMachineCheck+0x96
ffffb900`3b268cc0 fffff803`a4176779     : 00000247`09173b0c 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalHandleMcheck+0x6b
ffffb900`3b268cf0 fffff803`a428a17e     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9
ffffb900`3b268d20 fffff803`a4289d99     : 00000000`00000000 00000000`00000000 00000000`00000000 00000247`09173b0c : nt!KxMcheckAbort+0x7e
ffffb900`3b268e60 00007ff6`3df12a5c     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x2d9
000000e3`5d3ff6a0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff6`3df12a5c

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD.sys

STACK_COMMAND:  .process /r /p 0xffffce0936f4d080; .thread 0xffffce0932ee3080 ; kb

FAILURE_BUCKET_ID:  0x124_0_AuthenticAMD_MEMORY__UNKNOWN_FATAL_IMAGE_AuthenticAMD.sys

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {b0905187-9dbc-d607-4dc5-8630b9eddb7f}

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

Huge thanks for any help with this!

Michal Zajac

Hello, Michal Zajac_594

Welcome to the Microsoft Community

Thank you for your feedback. I have analyzed the blue screen log you provided.

According to the information provided by the dmp file, the system has a WHEA_UNCORRECTABLE_ERROR (124) is a serious hardware error, which usually means that the system has detected an unrecoverable error in the hardware. This error code usually means that there is a hardware problem or the driver is incompatible with the hardware.

The module that caused the error is

IMAGE_NAME: AuthenticAMD.sys, AuthenticAMD.sys usually points to system files or drivers related to AMD processors.

The stack traceback shows that this blue screen error occurred when the system was running and was caused by Grand Theft Auto V (GTA5.exe)

Based on the above analysis, you can try the following methods, which may help your current problem.

Method 1. Make sure that all hardware drivers in the system are updated, especially drivers and chipset drivers related to AMD processors. It is recommended to download and install the latest drivers from the official website of the hardware manufacturer.

Method 2. Go to the device manufacturer's website to check and update the BIOS/UEFI firmware to the latest version. This can solve many problems related to hardware compatibility.

Method 3. Check the hardware, specifically, focus on the following points

1. Memory and hard disk

Use the Windows Memory Diagnostic Tool or MemTest86 to check if there are any errors in the memory. At the same time, please replace the memory slots and reseat the memory modules to ensure that the sockets are clean and tightly inserted. Please use the diagnostic tool provided by the hard disk manufacturer to check the health of the hard disk. Or check and repair file system errors (chkdsk tool).

To check the health of the hard disk, open the command prompt (as an administrator), enter the following command and press Enter:

shell

chkdsk C: /f /r

You may be prompted to run a disk check the next time you restart. Enter Y and press Enter, then restart the computer.

Disclaimer: Running chkdsk checks the file system and file system metadata of the volume to find logical errors and physical errors. To avoid unnecessary trouble, please follow the above steps step by step, do not interrupt or cancel during the operation, and back up important data.

Check the memory. Use the Windows Memory Diagnostic tool to check if there are any errors in the memory. Press Win + R to open the Run dialog box, enter mdsched.exe and press Enter. Select "Restart now and check for problems (recommended)" or "Check for problems the next time you start the computer."

2. CPU. Please check if the CPU is overheating. Make sure the heat sink and fan are working properly. Also make sure that the CPU is not overclocked or restored to the default frequency.
3. Power supply. Please check if the power supply is stable and can provide enough power.

Method 4. Disable unnecessary devices. Some external devices and additional hardware may cause conflicts. Try to disable or disconnect unnecessary devices, including external hard drives, USB devices, etc.

Method 5. Please use third-party hardware testing tools (such as AIDA64, Prime95, etc.) to stress test the system to find out potential hardware problems.

Best regards

Brian - Microsoft Community Support Specialist