Question BSOD every day with BugCheck

[kirkdickinson]

I have a computer that is throwing a BSOD every day at least once or twice. I have to force a reboot and there is a bugcheck. I am not sure how to read the report. Can someone please help me read this report?

I have updated WinDbg to the newest version and run Analysis on it and this is what it says:

For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`057fd6f0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff802`09ac1940=0000000000000124
0: 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: ffff9a0c3a6c1028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000b6000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000100153, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 4624

Key : Analysis.Elapsed.mSec
Value: 4700

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

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

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

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

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

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

Key : Bugcheck.Code.KiBugCheckData
Value: 0x124

Key : Bugcheck.Code.LegacyAPI
Value: 0x124

Key : Failure.Bucket
Value: 0x124_0_AuthenticAMD_PROCESSOR_CACHE_IMAGE_AuthenticAMD.sys

Key : Failure.Hash
Value: {d6c4d869-cd29-1e48-0267-5766712959d2}

Key : Hypervisor.Enlightenments.Value
Value: 0

Key : Hypervisor.Enlightenments.ValueHex
Value: 0

Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 0

Key : Hypervisor.Flags.ApicEnlightened
Value: 0

Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 0

Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key : Hypervisor.Flags.CpuManager
Value: 0

Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 0

Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 0

Key : Hypervisor.Flags.Epf
Value: 0

Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 0

Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 0

Key : Hypervisor.Flags.MaxBankNumber
Value: 0

Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0

Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0

Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 0

Key : Hypervisor.Flags.Phase0InitDone
Value: 0

Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key : Hypervisor.Flags.RootScheduler
Value: 0

Key : Hypervisor.Flags.SynicAvailable
Value: 0

Key : Hypervisor.Flags.UseQpcBias
Value: 0

Key : Hypervisor.Flags.Value
Value: 0

Key : Hypervisor.Flags.ValueHex
Value: 0

Key : Hypervisor.Flags.VpAssistPage
Value: 0

Key : Hypervisor.Flags.VsmAvailable
Value: 0

Key : Hypervisor.RootFlags.AccessStats
Value: 0

Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 0

Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 0

Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key : Hypervisor.RootFlags.HostTimelineSync
Value: 0

Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key : Hypervisor.RootFlags.IsHyperV
Value: 0

Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 0

Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 0

Key : Hypervisor.RootFlags.MceEnlightened
Value: 0

Key : Hypervisor.RootFlags.Nested
Value: 0

Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 0

Key : Hypervisor.RootFlags.Value
Value: 0

Key : Hypervisor.RootFlags.ValueHex
Value: 0

Key : SecureKernel.HalpHvciEnabled
Value: 0

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffff9a0c3a6c1028

BUGCHECK_P3: b6000000

BUGCHECK_P4: 100153

FILE_IN_CAB: MEMORY.DMP

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: DecodeProcess.exe

STACK_TEXT:
fffff802`09ac1938 fffff802`058b97aa : 00000000`00000124 00000000`00000000 ffff9a0c`3a6c1028 00000000`b6000000 : nt!KeBugCheckEx
fffff802`09ac1940 fffff802`02a515b0 : 00000000`00000000 ffff9a0c`3a6c1028 ffff9a0c`372aa710 ffff9a0c`3a6c1028 : nt!HalBugCheckSystem+0xca
fffff802`09ac1980 fffff802`059bbaae : 00000000`00000000 fffff802`09ac1a29 ffff9a0c`3a6c1028 ffff9a0c`372aa710 : PSHED!PshedBugCheckSystem+0x10
fffff802`09ac19b0 fffff802`058bb0d1 : ffff9a0c`3b279070 ffff9a0c`3b279070 ffff9a0c`372aa760 ffff9a0c`372aa710 : nt!WheaReportHwError+0x46e
fffff802`09ac1a90 fffff802`058bb443 : 00000000`00000000 ffff9a0c`372aa760 ffff9a0c`372aa710 00000000`00000000 : nt!HalpMcaReportError+0xb1
fffff802`09ac1c00 fffff802`058bb320 : ffff9a0c`372a7710 00000000`00000001 fffff802`09ac1e00 00000000`00000000 : nt!HalpMceHandlerCore+0xef
fffff802`09ac1c50 fffff802`058ba865 : ffff9a0c`372a7710 fffff802`09ac1ef0 00000000`00000000 00000000`00000000 : nt!HalpMceHandler+0xe0
fffff802`09ac1c90 fffff802`058bd025 : ffff9a0c`372a7710 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpHandleMachineCheck+0xe9
fffff802`09ac1cc0 fffff802`05912be9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalHandleMcheck+0x35
fffff802`09ac1cf0 fffff802`0580e57a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9
fffff802`09ac1d20 fffff802`0580e237 : 00000000`00000000 fffff802`0580e16c ffff9a0c`4c027080 00000000`00000000 : nt!KxMcheckAbort+0x7a
fffff802`09ac1e60 fffff802`058110ed : ffff9a0c`4c027080 00000000`00000000 fffff883`00000000 ffff9a0c`3c0a6bb0 : nt!KiMcheckAbort+0x277
fffff883`a6a49b00 00007ff8`3f42f814 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceRepeat+0x39
000000b0`594ff618 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`3f42f814


MODULE_NAME: AuthenticAMD

IMAGE_NAME: AuthenticAMD.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x124_0_AuthenticAMD_PROCESSOR_CACHE_IMAGE_AuthenticAMD.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {d6c4d869-cd29-1e48-0267-5766712959d2}

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

 

[RLGL]

From Google andMicrosoft:

This bug check is typically related to physical hardware failures. It can be heat related or a result of defective hardware, memory, or even a processor that's beginning to fail or has failed. If over-clocking has been enabled, try disabling it. Confirm that any cooling systems such as fans are functional. Run system diagnostics to confirm that the system memory isn't defective. It's less likely, but possible, that a driver is causing the hardware to fail with this bug check.

To learn more about general bug check troubleshooting, see Blue screen data.

 

[jfelano]

Are your temps ok? Have you verified your cpu fan is spinning? If all is well, then try running a cpu test or mem test. That's where I would look first.

 

[Brainonska511]

You could try Blue screen viewer to read the .dmp file that has been generated. It might flag a driver that could be linked to a hardware issue.

Any recent hardware changes or software/driver updates that preceded this issue?

 

[kirkdickinson]

You could try Blue screen viewer to read the .dmp file that has been generated. It might flag a driver that could be linked to a hardware issue.

Any recent hardware changes or software/driver updates that preceded this issue?

No recent changes. Is an old computer though. I have replaced the case fan about a year ago and put a new fan/cooler on the cpu. It is an older computer though. AMD FX-4300 I believe.