Frequent BSODs

Bufitos 0 Reputation points
2023-05-31T23:33:41.8066667+00:00

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:
ffffb2045e0d7448 fffff8015c1b9abc : 0000000000000124 0000000000000010 ffffe48ba2aef028 ffffe48b8c77e92c : nt!KeBugCheckEx
ffffb2045e0d7450 fffff8015c1ba619 : ffffe48b9da2c010 ffffe48b9da2c010 ffffe48b8c77e900 ffffe48b960a8388 : nt!WheaReportHwError+0x3ec
ffffb2045e0d7530 fffff8015c1ba735 : 0000000000000000 0000000000000062 ffffe48b9da2c010 aaaaaaaaaaaaaaaa : nt!WheaHwErrorReportSubmitDeviceDriver+0xe9
ffffb2045e0d7560 fffff8015ea43721 : 0000000000000000 ffffb2045e0d7780 ffffe48b8c8631a0 0100000000100000 : nt!WheaReportFatalHwErrorDeviceDriverEx+0xf5
ffffb2045e0d75c0 fffff8015ea3cb00 : 0000000000000000 ffffe48b8c8631a0 ffffe48b905331a0 0000000000000001 : storport!StorpWheaReportError+0x9d
ffffb2045e0d7650 fffff8015ea0f07c : 0000000000000000 fffffffffffe7960 0000000000000000 0000000000000000 : storport!StorpMarkDeviceFailed+0x358
ffffb2045e0d78e0 fffff8015eacc33d : fffff8015c925440 ffffe48b8c81d020 0000000000000000 0000000000000000 : storport!StorPortNotification+0x91c
ffffb2045e0d79b0 fffff8015eacf55a : ffffe48b00000001 00000000c1000002 ffffe48b8c81d020 0000000000000003 : stornvme!ControllerReset+0x1a1
ffffb2045e0d7a30 fffff8015eace4af : ffffe48b8c81d020 ffffe48b8c863050 ffffe48ba1ce94f0 8000000000002000 : stornvme!NVMeControllerReset+0x10a
ffffb2045e0d7a60 fffff8015ea3a1f5 : ffffe48ba1ce94f0 ffffe48b8c863050 ffffe48b94f54040 ffffe48b8b09c050 : stornvme!NVMeControllerAsyncResetWorker+0x3f
ffffb2045e0d7a90 fffff8015be43f85 : ffffe48ba3349b60 ffffe48ba3349b60 ffffe48b8c863050 fffff8017e3b6af0 : storport!StorPortWorkItemRoutine+0x45
ffffb2045e0d7ac0 fffff8015be8e5c5 : ffffe48ba45a2640 ffffe48ba45a2640 fffff8015be43e50 ffffe48b00000000 : nt!IopProcessWorkItem+0x135
ffffb2045e0d7b30 fffff8015bf265f5 : ffffe48ba45a2640 0000000000000080 ffffe48b8b0cc140 0000000000000000 : nt!ExpWorkerThread+0x105
ffffb2045e0d7bd0 fffff8015c0048d8 : fffff8015782d180 ffffe48ba45a2640 fffff8015bf265a0 0000000000000000 : nt!PspSystemThreadStartup+0x55
ffffb2045e0d7c20 0000000000000000 : ffffb2045e0d8000 ffffb2045e0d1000 0000000000000000 0000000000000000 : 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

Not Monitored
Not Monitored
Tag not monitored by Microsoft.
37,728 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. workforce45 626 Reputation points
    2023-06-01T15:29:23.42+00:00

    Hi Bufitos,

    Issue reported: We are getting a blue screen error with an error code “WHEA_UNCORRECTABLE_ERROR (124)”, that happens when we load specific games like Doom Eternal and Road 96.

    Observation: This kind of error is a hardware error; we should ensure that all drivers supporting hardware should be installed in a machine. We may miss out some essential drivers, which are not easily available on an OEM website, in such cases, we should contact the OEM and get the machine all updated drivers and software based on a user experience. After we ensure that all drivers are installed and the machine is up to date, we should check Windows Updates under Settings and we also have an option to check for optional Updates under Advanced options in Windows Updates. We should download and install all Updates followed by a restart.

    Troubleshooting:

    • We first need to take a backup of our entire machine including data files and bookmarks.
    • Then we should check the list of the software and applications installed in a machine.
    • We should uninstall the games, which are causing the machine to get a blue screen error.
    • We should also uninstall, third-party security/cleanup/antivirus software and their traces.
    • We need to delete the entries of uninstalled games and applications from the Registry, which are located under HKEY_CURRENT_USER/Software and HKEY_LOCAL_MACHINE/Software.

    NOTE: You should not edit registry data that does not belong to your application unless it is necessary. If there is an error in the registry, your system may not function properly. If this happens, you can restore the registry to the state it was in when you last started the computer successfully. For more information, see the help for your operating system.

    • After we remove entries of uninstalled software/applications from the registry from above mentioned registry hives. Open ‘Command Prompt’ under admin rights and type ‘CHKDSK /f’ then enter and then type ‘Y’ and hit enter again. We should restart the machine after giving a command for Check disk scan.
    • Once the machine is restarted, we need to delete folders of the uninstalled applications/games from c/drive under Program Files, Program Files (x86) and Program data (Hidden Folder). Then open ‘Command Prompt’ under admin rights and type ‘CHKDSK /r’ then enter and then type ‘Y’ and hit enter again. At the same time, we should remove temporary files in a Temp folder and run a Disk Cleanup followed by a restart.
    • We then need to download and install the games in reference from an authenticated source and validate if we have a current version that support/comply with machine configuration followed by a restart and test the machine.
    • If the above-mentioned troubleshooting doesn’t fix a problem, then we need to follow Windows Recovery options under Settings, we can try to perform a Windows Repair or Reset based on our results.

    Please update with your findings!

    Sincerely,

    CK

    0 comments No comments