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

 

[ubuysa]

I do wish people would upload the dump files to the cloud rather than post the analyze -v output. Dump analysis is WAY more complex than just analyze -v....

 

[kirkdickinson]

I do wish people would upload the dump files to the cloud rather than post the analyze -v output. Dump analysis is WAY more complex than just analyze -v....

The computer won't allow me to copy the DMP file. It says I don't have permission. Even logged in as ADMIN. I had to use WinDbg to get any access to it.

 

[Ralston18]

Update your post to include full system hardware specs and OS information.

Include PSU and disk drive(s).

= = = =

Set BugCheck aside for the moment.

Look in Reliability History/Monitor and Event Viewer for error codes, warnings, or even informational events just before or at the time of the BSODs.

Reliability History is much more user friendly and the time line format can reveal patterns.

Event Viewer requires more time and effort to navigate and understand.

To help with Event Viewer:

How To - How to use Windows 10 Event Viewer | Tom's Hardware Forum (tomshardware.com)

You can on any given entries for more details. The details may or may not be helpful.

Pay attention to the error codes.

 

[ubuysa]

The computer won't allow me to copy the DMP file. It says I don't have permission. Even logged in as ADMIN. I had to use WinDbg to get any access to it.

The dump you posted in the full kernel dump (C:\Windows\Memory.dmp, though should still be able to upload it. That you can't indicates there is some sort of a permissions a problem within Windows.

From the !analyze -v output it's clear you've had a machine check exception and that's a hardware error. The 0x124 BSOD can, in some rare circumstances, be caused by a flaky driver, but from what I can see there this looks like a hardware failure.

How many of these 0x124 BSODs have you had? It would be useful if you download and run the SysnativeBSODCollectionApp and upload the resulting zip file. The file contains no personally identifying information and most of the files are txt files so you can look through the output before uploading it. Do not delete or modify anything however.

 

[Deleted member 2969713]

The dump you posted in the full kernel dump (C:\Windows\Memory.dmp, though should still be able to upload it. That you can't indicates there is some sort of a permissions a problem within Windows.

I had to mess with the most recent dump file's permissions in order to upload them to Dropbox on my BSOD thread.

The computer won't allow me to copy the DMP file. It says I don't have permission. Even logged in as ADMIN. I had to use WinDbg to get any access to it.

Right click the dump file, select "Properties," click the "Security" tab, click "Advanced," click "Continue," click "Add," click "Select a principle," then type your Windows username in the text box and click "OK," then click the checkmark for "Full control," and then click "OK," then "OK," then "Yes," then exit from the Properties window. You should now be able to upload the file or do whatever you want with it. But you may not wish to upload a full kernel dump for privacy reasons.

To create a minidump instead, type in "advanced system settings" in the start menu and click "View advanced system settings," click "Settings" under "Startup and Recovery," then in the dropdown box under "Write debugging information" select "Small memory dump (256 KB)" and click "OK." The next time your system has a BSOD, a minidump will be created at C:\Windows\Minidump and you can upload that. You'll probably need to follow the above instructions to give yourself the permissions needed to do so.