Windows 10: Random BSOD - through gaming and general use

Can someone help me figure out what hardware is causing the problem? Computer was fine when I had a 5600x in it. Upgraded the 5800x and cleared CMOS before installation and BSOD started happening. Tried reseating the ram, M.2, all power cables, and GPU. Also, reinstalled windows but the error keeps happening. Planning to take out the CPU and reseat it but waiting on the new thermal paste to be shipped. Ryzen master shows MHz for CPU before and after windows reinstallation.


Specs:

Mobo - MSI B550 Gaming Carbon wifi

CPU - Ryzen 5800x

GPU - MSI 3070 Gaming TRIO

PSU - EVGA 750 GQ 80+ gold

Ram - Corsair Vengence RGB 32GB 4x8 3600mhz

cooler - Corsair Hydro H115i

Storage - WD 3D 500GB M.2 w/ Seagate Barracuda 2TB


Link for miniDump: https://www.dropbox.com/s/r4yi97lcscr790z/Minidump.zip?dl=0


Windbg info:

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

Arguments:

Arg1: 0000000000000000, Machine Check Exception

Arg2: ffff800c8cc03028, Address of the 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:

------------------



fffff8005fe0f330: Unable to get Flags value from nt!KdVersionBlock

fffff8005fe0f330: Unable to get Flags value from nt!KdVersionBlock

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

*** ***

*** ***

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

*** ***

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

fffff8005fe0f330: Unable to get Flags value from nt!KdVersionBlock

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

*** ***

*** ***

*** 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.Sec

Value: 2



Key : Analysis.DebugAnalysisProvider.CPP

Value: Create: 8007007e on DESKTOP-RAF9JVH



Key : Analysis.DebugData

Value: CreateObject



Key : Analysis.DebugModel

Value: CreateObject



Key : Analysis.Elapsed.Sec

Value: 7



Key : Analysis.Memory.CommitPeak.Mb

Value: 81



Key : Analysis.System

Value: CreateObject





BUGCHECK_CODE: 124



BUGCHECK_P1: 0



BUGCHECK_P2: ffff800c8cc03028



BUGCHECK_P3: bc000800



BUGCHECK_P4: 1010135



BLACKBOXBSD: 1 !blackboxbsd





BLACKBOXNTFS: 1 !blackboxntfs





BLACKBOXPNP: 1 !blackboxpnp





BLACKBOXWINLOGON: 1



CUSTOMER_CRASH_COUNT: 1



PROCESS_NAME: DCv2.e



STACK_TEXT:

ffffda81`bf860938 fffff800`5f6b37ba : 00000000`00000124 00000000`00000000 ffff800c`8cc03028 00000000`bc000800 : nt!KeBugCheckEx

ffffda81`bf860940 fffff800`5c6215b0 : 00000000`00000000 ffff800c`8cc03028 ffff800c`89fed760 ffff800c`8cc03028 : nt!HalBugCheckSystem+0xca

ffffda81`bf860980 fffff800`5f7b532e : 00000000`00000000 ffffda81`bf860a29 ffff800c`8cc03028 ffff800c`89fed760 : PSHED!PshedBugCheckSystem+0x10

ffffda81`bf8609b0 fffff800`5f6b50e1 : ffff800c`8b4f0a80 ffff800c`8b4f0a80 ffff800c`89fed7b0 ffff800c`89fed760 : nt!WheaReportHwError+0x46e

ffffda81`bf860a90 fffff800`5f6b5453 : 00000000`0000000b ffff800c`89fed7b0 ffff800c`89fed760 00000000`0000000b : nt!HalpMcaReportError+0xb1

ffffda81`bf860c00 fffff800`5f6b5330 : ffff800c`89efe7e8 00000000`00000000 ffffda81`bf860e00 00000000`00000000 : nt!HalpMceHandlerCore+0xef

ffffda81`bf860c50 fffff800`5f6b4875 : ffff800c`89efe7e8 ffffda81`bf860ef0 00000000`00000000 00000000`00000000 : nt!HalpMceHandler+0xe0

ffffda81`bf860c90 fffff800`5f6b7035 : ffff800c`89efe7e8 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpHandleMachineCheck+0xe9

ffffda81`bf860cc0 fffff800`5f70c769 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalHandleMcheck+0x35

ffffda81`bf860cf0 fffff800`5f6048fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9

ffffda81`bf860d20 fffff800`5f6045b7 : ffff9a05`00000000 fffff800`5f6044ec 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7a

ffffda81`bf860e60 fffff800`5f45015c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277

ffff9009`3abd6ea0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExAllocateHeapPool+0x24c





MODULE_NAME: AuthenticAMD



IMAGE_NAME: AuthenticAMD.sys



STACK_COMMAND: .thread ; .cxr ; kb



FAILURE_BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR__UNKNOWN



OS_VERSION: 10.0.19041.1



BUILDLAB_STR: vb_release



OSPLATFORM_TYPE: x64



OSNAME: Windows 10



FAILURE_ID_HASH: {92068ce4-dacf-c0d2-ac6c-91e2b9ac5b67}



Followup: MachineOwner

---------

:)

 

Random BSOD while browsing internet


BitDefender is nothing special. mwac.sys causes BSODs anywhere.
A tiny documentation can be found here: Solved Random BSODs - Windows 10 Forums
In that very thread, the suggested action apparently worked.

The storage and network filters of any third party antivirus can cause BSODs. Neither MBAM nor BitDefender is any special. For a regular antivirus, it may be shifted to an alternative; but MBAM has no alternative. So a clean install of the said program is the most feasible first step.
As far as the first step is not failing, it is better to not think for the second step. Because the BSODs are not universal, failure at the first step is not universal; and success at the second step is also not universal.
That is why I posted that my suggestion may work, or may not. Let us see where it goes.

 

Random BSOD while browsing internet

Sorry, Bitdefender is a problem: BSOD BAD_POOL_HEADER - mwac.sys - Malwarebytes Anti-Malware Help - Malwarebytes Forums

 

Random BSODs "Bad_Pool_Caller"


This BSOD happens anywhere, irrespective of BitDefender. It takes place even when the antivirus is MSE in case of Windows 7. The most common cause is an expired trial or a cracked installation. Some examples:

• Norton: Windows 7 Random bsod caused by tcpip.sys - Windows 7 Help Forums
• MBAM only: Epic BSOD error appears just after few seconds from boot Solved - Windows 7 Help Forums
• McAfee: BSOD on Internet Related Programs (tcpip.sys) - Windows 7 Help Forums
• Avast: Bad Pool Header 0x00000019 at random times - Windows 7 Help Forums
• Avira: BSOD randomly Crashes my Laptop and freezes at Memory dump 100 - Windows 7 Help Forums
• Crack: BSOD every 6 minutes, also recent freezes - Windows 7 Help Forums

We are on our way of troubleshooting. If the uninstallation and reinstallation does not work, we will take the next step.

I, in general, know what I am doing and what I am suggesting. If I feel that I am unable to control the issue, I will definitely ask for help.