Help with BSOD dumpfile

Question

I keep getting blue screens, I got them once a month but now I get them even multiple times for a day.

AMD 5900X

XFX 5700XT

RAM 64 GB 4x Crucial Ballistix BL2K16G32C16U4R 3200 MHz, DDR4, DRAM

MSI MAG B550 TOMAHAWK

(No overclock, Temperatures are fine I have a Noctua d15 for CPU and the PC is not hard stressed)

In all the dump files I have crashes with blizzard games or APP, Don't know if is it something casual.

https://1drv.ms/u/s!AkFZHDBIH_WGgUKW7acKAcP-v5zF?e=5qwVdW

This is the last one I got.

******************************************************************************
*                                                                             *
*                        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
WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffc803068d3028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000bc800800, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000060c0859, 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                ***
***                                                                   ***
*************************************************************************
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2764

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 11983

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

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

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

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1

BUGCHECK_CODE:  124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffc803068d3028

BUGCHECK_P3: bc800800

BUGCHECK_P4: 60c0859

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Battle.net.exe

STACK_TEXT:  
ffff9180`735f6938 fffff804`316b440a     : 00000000`00000124 00000000`00000000 ffffc803`068d3028 00000000`bc800800 : nt!KeBugCheckEx
ffff9180`735f6940 fffff804`2ff315b0     : 00000000`00000000 ffffc803`068d3028 ffffc802`fbbf6bc0 ffffc803`068d3028 : nt!HalBugCheckSystem+0xca
ffff9180`735f6980 fffff804`317b61ee     : 00000000`00000000 ffff9180`735f6a29 ffffc803`068d3028 ffffc802`fbbf6bc0 : PSHED!PshedBugCheckSystem+0x10
ffff9180`735f69b0 fffff804`316b5d31     : ffffc803`05e77900 ffffc803`05e77900 ffffc802`fbbf6c10 ffffc802`fbbf6bc0 : nt!WheaReportHwError+0x46e
ffff9180`735f6a90 fffff804`316b60a3     : 00000000`00000008 ffffc802`fbbf6c10 ffffc802`fbbf6bc0 00000000`00000008 : nt!HalpMcaReportError+0xb1
ffff9180`735f6c00 fffff804`316b5f80     : ffffc802`fbaef5c0 485f7373`00000000 ffff9180`735f6e00 cccccccc`cccccccc : nt!HalpMceHandlerCore+0xef
ffff9180`735f6c50 fffff804`316b54c5     : ffffc802`fbaef5c0 ffff9180`735f6ef0 00000000`00000000 cccccccc`00000073 : nt!HalpMceHandler+0xe0
ffff9180`735f6c90 fffff804`316b7c85     : ffffc802`fbaef5c0 cccccccc`cccccccc 00630072`006f0046 006b0061`00570065 : nt!HalpHandleMachineCheck+0xe9
ffff9180`735f6cc0 fffff804`3170d519     : 006c0064`0074006e 006c0064`002e006c cccccccc`0000006c cccccccc`cccccccc : nt!HalHandleMcheck+0x35
ffff9180`735f6cf0 fffff804`31605cfa     : 00000073`006e006f cccccccc`cccccccc 006f006c`006c0041 00430064`00650077 : nt!KiHandleMcheck+0x9
ffff9180`735f6d20 fffff804`316059b7     : 00000000`00000000 00000000`00000000 00000000`0375edf4 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffff9180`735f6e60 00000000`5a37caa6     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277
00000000`06a3fc08 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x5a37caa6

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD.sys

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0x124_0_AuthenticAMD_PROCESSOR__UNKNOWN_IMAGE_AuthenticAMD.sys

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

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

Answer 1

Okay LocketAP.

Answer 2

Ok, now I understood what you meant, sorry if I got it wrong but I'm not a superexpert.

When I built the PC I created an XMP profile for the ram in the bios and changed there the value of the ram from 2666 to 3200.

Now after your message I've removed the profile and instead I've changed the ram value from 2666 to 3200 on the main page without touching the profiles.

I will try like this if it will be stable.

If it will be not stable I will try with your last message.

Answer 3

Hi LocketAP,

Okay, try setting the RAM to its default clock speed and test if your system is stable.

If not, to try to force Windows 10 show any faulting drivers, the best option would be to turn on Driver Verifier, let your PC crash 3 times, then you must turn off Driver Verifier, and finally, upload any newly created minidump files

https://answers.microsoft.com/en-us/windows/for...

Answer 4

The CPU is not overclocked.

For the Ram the only thing I did was to change the 2666mhz from the bios to 3200 since the Motherboard was showing the 2666mhz in the bios when installed.

How can I fix it?

The ram is the following

Crucial Ballistix BL2K16G32C16U4R 3200 MHz, DDR4, DRAM (4slots 16x4 for a total of 64 GB)

Answer 5

Hi LocketAP,

I am Dave, an Independent Advisor, I will help you with this.

All your minidump files indicate memory (RAM) corruption and a driver (AuthenticAMD.sys) that is associated to your AMD processor as contributing factors to the crashes.

Are you overclocking your CPU, if so, stop that and if there is an XMP profile set on your RAM in BIOS, or you are in any way setting a clock speed on your RAM in BIOS, turn that off.