Question Frequent BSODs ?

[Brifitas]

Recently I have been getting an awful amount of BSODs on my computer. They ONLY happen when I load specific games. Titles like Doom Eternal and Road 96 basically crash instantly, while titles like Titanfall 2 and CSGO never crashed once. Temps were also fine all the time. My graphics drivers are fully updated and so is my BIOS. I also set my XMP settings to default. I also uninstalled all of my display drivers and reinstalled them, but it didn't work. My final attempt was to uninstall Valorant to make sure that the anti-cheat wasn't causing a problem. NONE of these worked at the slightest. My guess now is that it could be a hardware issue, but I still haven't gotten any visual artifacts.

I have a 6750xt, 32 gb of ram, a 650W PSU and a 5600. Most of these parts were bought in the last few months brand new. I would really love some input, because these types of issues on a brand new build quite literally convinced me that this will be the last gaming PC I ever buy.

Here is a copy of one of my crash dump analysis from WinDbg

*******************************************************************************
* *
* 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: 0000000000000010, Device Driver Error
Arg2: ffffdf0fb6fc0028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: ffffdf0f9df3f92c
Arg4: ffffdf0fa105a1a0
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 4374
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 6587
Key : Analysis.Init.CPU.mSec
Value: 983
Key : Analysis.Init.Elapsed.mSec
Value: 12282
Key : Analysis.Memory.CommitPeak.Mb
Value: 144
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

FILE_IN_CAB: 052923-13156-01.dmp
BUGCHECK_CODE: 124
BUGCHECK_P1: 10
BUGCHECK_P2: ffffdf0fb6fc0028
BUGCHECK_P3: ffffdf0f9df3f92c
BUGCHECK_P4: ffffdf0fa105a1a0
BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffffdc8a`5ecfa448 fffff805`049b9abc : 00000000`00000124 00000000`00000010 ffffdf0f`b6fc0028 ffffdf0f`9df3f92c : nt!KeBugCheckEx
ffffdc8a`5ecfa450 fffff805`049ba619 : ffffdf0f`b627d290 ffffdf0f`b627d290 ffffdf0f`9df3f900 ffffdf0f`b48d4378 : nt!WheaReportHwError+0x3ec
ffffdc8a`5ecfa530 fffff805`049ba735 : 00000000`00000000 00000000`00000062 ffffdf0f`b627d290 00000000`00000000 : nt!WheaHwErrorReportSubmitDeviceDriver+0xe9
ffffdc8a`5ecfa560 fffff805`07843721 : 00000000`00000000 ffffdc8a`5ecfa780 ffffdf0f`a105a1a0 01000000`00100000 : nt!WheaReportFatalHwErrorDeviceDriverEx+0xf5
ffffdc8a`5ecfa5c0 fffff805`0783cb00 : 00000000`00000000 ffffdf0f`a105a1a0 ffffdf0f`9df9c1a0 00000000`00000001 : storport!StorpWheaReportError+0x9d
ffffdc8a`5ecfa650 fffff805`0780f07c : 00000000`00000000 ffffffff`fffe7960 00000000`00000000 00000000`00000000 : storport!StorpMarkDeviceFailed+0x358
ffffdc8a`5ecfa8e0 fffff805`078cc33d : fffff805`05125440 ffffdf0f`9df96020 00000000`00000000 00000000`00000000 : storport!StorPortNotification+0x91c
ffffdc8a`5ecfa9b0 fffff805`078cf55a : ffffdf0f`00000001 00000000`c1000002 ffffdf0f`9df96020 00000000`00000003 : stornvme!ControllerReset+0x1a1
ffffdc8a`5ecfaa30 fffff805`078ce4af : ffffdf0f`9df96020 ffffdf0f`a105a050 ffffdf0f`b62b0340 80000000`00002000 : stornvme!NVMeControllerReset+0x10a
ffffdc8a`5ecfaa60 fffff805`0783a1f5 : ffffdf0f`b62b0340 ffffdf0f`a105a050 ffffdf0f`b217e040 ffffdf0f`9b8d5a60 : stornvme!NVMeControllerAsyncResetWorker+0x3f
ffffdc8a`5ecfaa90 fffff805`04643f85 : ffffdf0f`cbb1eba0 ffffdf0f`cbb1eba0 ffffdf0f`a105a050 fffff805`2ce76af0 : storport!StorPortWorkItemRoutine+0x45
ffffdc8a`5ecfaac0 fffff805`0468e5c5 : ffffdf0f`b2341040 ffffdf0f`b2341040 fffff805`04643e50 00000000`00000000 : nt!IopProcessWorkItem+0x135
ffffdc8a`5ecfab30 fffff805`047265f5 : ffffdf0f`b2341040 00000000`00000080 ffffdf0f`9b8c4080 ffff98fb`88600000 : nt!ExpWorkerThread+0x105
ffffdc8a`5ecfabd0 fffff805`048048d8 : ffffa900`b4040180 ffffdf0f`b2341040 fffff805`047265a0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffdc8a`5ecfac20 00000000`00000000 : ffffdc8a`5ecfb000 ffffdc8a`5ecf4000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28

MODULE_NAME: AuthenticAMD
IMAGE_NAME: AuthenticAMD.sys
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: 0x124_16_AuthenticAMD__UNKNOWN_IMAGE_AuthenticAMD.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {590f0c83-3219-aceb-da4c-6b8bc7c00f79}
Followup: MachineOwner

 

[ubuysa]

That's only the dump triage analysis, you should always post the minidump so we can analyse it fully.

That said, there is enough information in the call stack to diagnose what happened. You've had an NVMe drive problem...

STACK_TEXT: 
ffffdc8a`5ecfa448 fffff805`049b9abc     : 00000000`00000124 00000000`00000010 ffffdf0f`b6fc0028 ffffdf0f`9df3f92c : nt!KeBugCheckEx
ffffdc8a`5ecfa450 fffff805`049ba619     : ffffdf0f`b627d290 ffffdf0f`b627d290 ffffdf0f`9df3f900 ffffdf0f`b48d4378 : nt!WheaReportHwError+0x3ec
ffffdc8a`5ecfa530 fffff805`049ba735     : 00000000`00000000 00000000`00000062 ffffdf0f`b627d290 00000000`00000000 : nt!WheaHwErrorReportSubmitDeviceDriver+0xe9
ffffdc8a`5ecfa560 fffff805`07843721     : 00000000`00000000 ffffdc8a`5ecfa780 ffffdf0f`a105a1a0 01000000`00100000 : nt!WheaReportFatalHwErrorDeviceDriverEx+0xf5    <=====finally the WHEA bugcheck is generated
ffffdc8a`5ecfa5c0 fffff805`0783cb00     : 00000000`00000000 ffffdf0f`a105a1a0 ffffdf0f`9df9c1a0 00000000`00000001 : storport!StorpWheaReportError+0x9d
ffffdc8a`5ecfa650 fffff805`0780f07c     : 00000000`00000000 ffffffff`fffe7960 00000000`00000000 00000000`00000000 : storport!StorpMarkDeviceFailed+0x358    <=====Then the storage driver marks the drive as failed
ffffdc8a`5ecfa8e0 fffff805`078cc33d     : fffff805`05125440 ffffdf0f`9df96020 00000000`00000000 00000000`00000000 : storport!StorPortNotification+0x91c
ffffdc8a`5ecfa9b0 fffff805`078cf55a     : ffffdf0f`00000001 00000000`c1000002 ffffdf0f`9df96020 00000000`00000003 : stornvme!ControllerReset+0x1a1
ffffdc8a`5ecfaa30 fffff805`078ce4af     : ffffdf0f`9df96020 ffffdf0f`a105a050 ffffdf0f`b62b0340 80000000`00002000 : stornvme!NVMeControllerReset+0x10a      <=====This is where the problem starts
ffffdc8a`5ecfaa60 fffff805`0783a1f5     : ffffdf0f`b62b0340 ffffdf0f`a105a050 ffffdf0f`b217e040 ffffdf0f`9b8d5a60 : stornvme!NVMeControllerAsyncResetWorker+0x3f
ffffdc8a`5ecfaa90 fffff805`04643f85     : ffffdf0f`cbb1eba0 ffffdf0f`cbb1eba0 ffffdf0f`a105a050 fffff805`2ce76af0 : storport!StorPortWorkItemRoutine+0x45
ffffdc8a`5ecfaac0 fffff805`0468e5c5     : ffffdf0f`b2341040 ffffdf0f`b2341040 fffff805`04643e50 00000000`00000000 : nt!IopProcessWorkItem+0x135
ffffdc8a`5ecfab30 fffff805`047265f5     : ffffdf0f`b2341040 00000000`00000080 ffffdf0f`9b8c4080 ffff98fb`88600000 : nt!ExpWorkerThread+0x105
ffffdc8a`5ecfabd0 fffff805`048048d8     : ffffa900`b4040180 ffffdf0f`b2341040 fffff805`047265a0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffdc8a`5ecfac20 00000000`00000000     : ffffdc8a`5ecfb000 ffffdc8a`5ecf4000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28

I've seen this situation twice and very recently. In one case this appeared to be a power problem and your 650W PSU is at the bare minimum for that 6750XT graphics card. My guess is that the popwer spikes that certain games cause is what's overloading the PSU and causing power issues on the motherboard.

That said, you should also download the diagnostics tool for your NVMe SSD and run their diagnostics on the drive. Also use the tool to check for driver and/or firmware updates.

 

[Brifitas]

That's only the dump triage analysis, you should always post the minidump so we can analyse it fully.

That said, there is enough information in the call stack to diagnose what happened. You've had an NVMe drive problem...

STACK_TEXT:
ffffdc8a`5ecfa448 fffff805`049b9abc     : 00000000`00000124 00000000`00000010 ffffdf0f`b6fc0028 ffffdf0f`9df3f92c : nt!KeBugCheckEx
ffffdc8a`5ecfa450 fffff805`049ba619     : ffffdf0f`b627d290 ffffdf0f`b627d290 ffffdf0f`9df3f900 ffffdf0f`b48d4378 : nt!WheaReportHwError+0x3ec
ffffdc8a`5ecfa530 fffff805`049ba735     : 00000000`00000000 00000000`00000062 ffffdf0f`b627d290 00000000`00000000 : nt!WheaHwErrorReportSubmitDeviceDriver+0xe9
ffffdc8a`5ecfa560 fffff805`07843721     : 00000000`00000000 ffffdc8a`5ecfa780 ffffdf0f`a105a1a0 01000000`00100000 : nt!WheaReportFatalHwErrorDeviceDriverEx+0xf5    <=====finally the WHEA bugcheck is generated
ffffdc8a`5ecfa5c0 fffff805`0783cb00     : 00000000`00000000 ffffdf0f`a105a1a0 ffffdf0f`9df9c1a0 00000000`00000001 : storport!StorpWheaReportError+0x9d
ffffdc8a`5ecfa650 fffff805`0780f07c     : 00000000`00000000 ffffffff`fffe7960 00000000`00000000 00000000`00000000 : storport!StorpMarkDeviceFailed+0x358    <=====Then the storage driver marks the drive as failed
ffffdc8a`5ecfa8e0 fffff805`078cc33d     : fffff805`05125440 ffffdf0f`9df96020 00000000`00000000 00000000`00000000 : storport!StorPortNotification+0x91c
ffffdc8a`5ecfa9b0 fffff805`078cf55a     : ffffdf0f`00000001 00000000`c1000002 ffffdf0f`9df96020 00000000`00000003 : stornvme!ControllerReset+0x1a1
ffffdc8a`5ecfaa30 fffff805`078ce4af     : ffffdf0f`9df96020 ffffdf0f`a105a050 ffffdf0f`b62b0340 80000000`00002000 : stornvme!NVMeControllerReset+0x10a      <=====This is where the problem starts
ffffdc8a`5ecfaa60 fffff805`0783a1f5     : ffffdf0f`b62b0340 ffffdf0f`a105a050 ffffdf0f`b217e040 ffffdf0f`9b8d5a60 : stornvme!NVMeControllerAsyncResetWorker+0x3f
ffffdc8a`5ecfaa90 fffff805`04643f85     : ffffdf0f`cbb1eba0 ffffdf0f`cbb1eba0 ffffdf0f`a105a050 fffff805`2ce76af0 : storport!StorPortWorkItemRoutine+0x45
ffffdc8a`5ecfaac0 fffff805`0468e5c5     : ffffdf0f`b2341040 ffffdf0f`b2341040 fffff805`04643e50 00000000`00000000 : nt!IopProcessWorkItem+0x135
ffffdc8a`5ecfab30 fffff805`047265f5     : ffffdf0f`b2341040 00000000`00000080 ffffdf0f`9b8c4080 ffff98fb`88600000 : nt!ExpWorkerThread+0x105
ffffdc8a`5ecfabd0 fffff805`048048d8     : ffffa900`b4040180 ffffdf0f`b2341040 fffff805`047265a0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffdc8a`5ecfac20 00000000`00000000     : ffffdc8a`5ecfb000 ffffdc8a`5ecf4000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28

I've seen this situation twice and very recently. In one case this appeared to be a power problem and your 650W PSU is at the bare minimum for that 6750XT graphics card. My guess is that the popwer spikes that certain games cause is what's overloading the PSU and causing power issues on the motherboard.

That said, you should also download the diagnostics tool for your NVMe SSD and run their diagnostics on the drive. Also use the tool to check for driver and/or firmware updates.

Ah I see. My PSU is also the oldest hardware on my PC. Where do I download a diagnostics tool? Is that a microsoft program?

 

[ubuysa]

What make and model is your SSD?

Could you please download the V2 log collector from here and upload the zip file it produces. No user-identifiable data is collected.