WHEA UNCORRECTABLE ERROR authenticamd.sys

Question

Hello everyone,

This is my PC specs

AMD RYZEN 3200G

A320 S2-H MOTHERBOARD GIGABYTE

RAM 1 - 8GB HYPER X FURY 2666MHZ

RAM 2 - 8GB GAMMIX FROM ADATA 3200MHZ

SSD - M.2 NVME CRUCIAL 500GB

SATA HDD - 1TB

SMPS - COOLER MASTER 450 V2 https://1drv.ms/f/s!ArLQVpBsn4nrgTXC60tzmMex5-sc?e=FlOMhq

*******************************************************************************

* *

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

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

Arg4: 000000000003080b, 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: 4139 

Key  : Analysis.DebugAnalysisManager 

Value: Create 

Key  : Analysis.Elapsed.mSec 

Value: 4242 

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

Key  : Analysis.Init.Elapsed.mSec 

Value: 11576 

Key  : Analysis.Memory.CommitPeak.Mb 

Value: 94 

Key  : Bugcheck.Code.DumpHeader 

Value: 0x124 

Key  : Bugcheck.Code.Register 

Value: 0x124 

Key  : Dump.Attributes.AsUlong 

Value: 8 

Key  : Dump.Attributes.KernelGeneratedTriageDump 

Value: 1 

FILE_IN_CAB: 052723-4687-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8

Kernel Generated Triage Dump

BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffff880aeedee028

BUGCHECK_P3: faa00000

BUGCHECK_P4: 3080b

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:

fffff8040e6c1938 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KeBugCheckEx

MODULE_NAME: AuthenticAMD

IMAGE_NAME: AuthenticAMD.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x124_0_AuthenticAMD_PROCESSOR__UNKNOWN_IMAGE_AuthenticAMD.sys

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

Followup: MachineOwner

Answer 1

Please tell the result.

Answer 2

Thank you sir

Answer 3

Hi,

My name is Igor, it's a pleasure for me to help others and I'll do all my best to help you.

Seems you have corrupted files. Please repair system files by

DISM.exe /Online /Cleanup-Image /RestoreHealth

command from Windows PowerShell (administrator) environment.

Run Windows memory diagnostic tool and switch it to extended mode when it starts (F1 key). Note, test hang at ~21% for more than 2-3 hours means memory error too.

Turn off XMP mode in BIOS if it is turned on.

And please check your RAM modes (voltage, frequency, timings) are in compliance with numbers in the motherboard compatibility list for your RAM models.