cancel
Showing results for 
Search instead for 
Did you mean: 

PC Drivers & Software

Bufitos
Journeyman III

Frequent BSOD

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 and chipset 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. I also ran chkdsk /f /r, sfc /scannow, and DISM /Online /Cleanup-Image /RestoreHealth on my PC. 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, a B550M PG Riptide 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: ffffe48ba2aef028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: ffffe48b8c77e92c
Arg4: ffffe48b8c8631a0

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

*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 4078

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 7774

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

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

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

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: 053123-7515-01.dmp

BUGCHECK_CODE: 124

BUGCHECK_P1: 10

BUGCHECK_P2: ffffe48ba2aef028

BUGCHECK_P3: ffffe48b8c77e92c

BUGCHECK_P4: ffffe48b8c8631a0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffb204`5e0d7448 fffff801`5c1b9abc : 00000000`00000124 00000000`00000010 ffffe48b`a2aef028 ffffe48b`8c77e92c : nt!KeBugCheckEx
ffffb204`5e0d7450 fffff801`5c1ba619 : ffffe48b`9da2c010 ffffe48b`9da2c010 ffffe48b`8c77e900 ffffe48b`960a8388 : nt!WheaReportHwError+0x3ec
ffffb204`5e0d7530 fffff801`5c1ba735 : 00000000`00000000 00000000`00000062 ffffe48b`9da2c010 aaaaaaaa`aaaaaaaa : nt!WheaHwErrorReportSubmitDeviceDriver+0xe9
ffffb204`5e0d7560 fffff801`5ea43721 : 00000000`00000000 ffffb204`5e0d7780 ffffe48b`8c8631a0 01000000`00100000 : nt!WheaReportFatalHwErrorDeviceDriverEx+0xf5
ffffb204`5e0d75c0 fffff801`5ea3cb00 : 00000000`00000000 ffffe48b`8c8631a0 ffffe48b`905331a0 00000000`00000001 : storport!StorpWheaReportError+0x9d
ffffb204`5e0d7650 fffff801`5ea0f07c : 00000000`00000000 ffffffff`fffe7960 00000000`00000000 00000000`00000000 : storport!StorpMarkDeviceFailed+0x358
ffffb204`5e0d78e0 fffff801`5eacc33d : fffff801`5c925440 ffffe48b`8c81d020 00000000`00000000 00000000`00000000 : storport!StorPortNotification+0x91c
ffffb204`5e0d79b0 fffff801`5eacf55a : ffffe48b`00000001 00000000`c1000002 ffffe48b`8c81d020 00000000`00000003 : stornvme!ControllerReset+0x1a1
ffffb204`5e0d7a30 fffff801`5eace4af : ffffe48b`8c81d020 ffffe48b`8c863050 ffffe48b`a1ce94f0 80000000`00002000 : stornvme!NVMeControllerReset+0x10a
ffffb204`5e0d7a60 fffff801`5ea3a1f5 : ffffe48b`a1ce94f0 ffffe48b`8c863050 ffffe48b`94f54040 ffffe48b`8b09c050 : stornvme!NVMeControllerAsyncResetWorker+0x3f
ffffb204`5e0d7a90 fffff801`5be43f85 : ffffe48b`a3349b60 ffffe48b`a3349b60 ffffe48b`8c863050 fffff801`7e3b6af0 : storport!StorPortWorkItemRoutine+0x45
ffffb204`5e0d7ac0 fffff801`5be8e5c5 : ffffe48b`a45a2640 ffffe48b`a45a2640 fffff801`5be43e50 ffffe48b`00000000 : nt!IopProcessWorkItem+0x135
ffffb204`5e0d7b30 fffff801`5bf265f5 : ffffe48b`a45a2640 00000000`00000080 ffffe48b`8b0cc140 00000000`00000000 : nt!ExpWorkerThread+0x105
ffffb204`5e0d7bd0 fffff801`5c0048d8 : fffff801`5782d180 ffffe48b`a45a2640 fffff801`5bf265a0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffb204`5e0d7c20 00000000`00000000 : ffffb204`5e0d8000 ffffb204`5e0d1000 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
---------

0 Likes
0 Replies