Question What could be causing my PC to BSOD when playing certain games?

[EthanSierra]

Hello,

I got a prebuilt from SCAN Computers about a year ago, and I've been getting BSODs whenever I play certain games since I got it. For example playing God of War, I can only play for about 20-30 minutes before I get a black screen into a WHEA_UNCORRECTABLE_ERROR.

My temps when this happens are quite high, but not crazy (CPU ~85c and GPU ~70c), but I got a new case and extra fans anyway to increase the airflow and also re-applied thermal paste to my CPU but and it's still happening.

I've also re-installed windows multiple times since getting the PC, Updated my BIOS to the latest version and have the latest graphics drivers.

These are my specs and a benchmark I ran this morning:

https://www.userbenchmark.com/UserRun/56587196

Here is also the latest minidump file after it crashed this morning:, if it helps. Any help would be appreciated as I've been trying to troubleshoot this for 6 months and haven't been able to fix it.

***

• *
• 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: 0000000000000000, Machine Check Exception
Arg2: ffffcb88226b7028, Address of the nt!_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:
------------------

*

• *
• *
• 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: 3374

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 13393

Key : Analysis.IO.Other.Mb
Value: 0

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 1

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

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

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

Key : Bugcheck.Code.DumpHeader
Value: 0x124

Key : Bugcheck.Code.Register
Value: 0x124

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: 111222-9796-01.dmp

BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffcb88226b7028

BUGCHECK_P3: bc000800

BUGCHECK_P4: 1010135

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: GoW.exe

STACK_TEXT:
ffffa9015edf2938 fffff8057d2b6b3a : 0000000000000124 0000000000000000 ffffcb88226b7028 00000000bc000800 : nt!KeBugCheckEx
ffffa9015edf2940 fffff8057a5815b0 : 0000000000000000 ffffcb88226b7028 ffffcb88210ada10 ffffcb88226b7028 : nt!HalBugCheckSystem+0xca
ffffa9015edf2980 fffff8057d3b8cae : 0000000000000000 ffffa9015edf2a29 ffffcb88226b7028 ffffcb88210ada10 : PSHED!PshedBugCheckSystem+0x10
ffffa9015edf29b0 fffff8057d2b8461 : ffffcb8827a3a880 ffffcb8827a3a880 ffffcb88210ada60 ffffcb88210ada10 : nt!WheaReportHwError+0x46e
ffffa9015edf2a90 fffff8057d2b87d3 : 0000000000000008 ffffcb88210ada60 ffffcb88210ada10 0000000000000008 : nt!HalpMcaReportError+0xb1
ffffa9015edf2c00 fffff8057d2b86b0 : ffffcb88210ac5c0 0000000000000000 ffffa9015edf2e00 0000000000000000 : nt!HalpMceHandlerCore+0xef
ffffa9015edf2c50 fffff8057d2b7bf5 : ffffcb88210ac5c0 ffffa9015edf2ef0 0000000000000000 0000000000000000 : nt!HalpMceHandler+0xe0
ffffa9015edf2c90 fffff8057d2ba3b5 : ffffcb88210ac5c0 0000000000000000 0000000000000000 0000000000000000 : nt!HalpHandleMachineCheck+0xe9
ffffa9015edf2cc0 fffff8057d30fe39 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!HalHandleMcheck+0x35
ffffa9015edf2cf0 fffff8057d209eba : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiHandleMcheck+0x9
ffffa9015edf2d20 fffff8057d209b77 : 0000000000000000 0000000000000000 00007ff38ecdaa00 0000000000000000 : nt!KxMcheckAbort+0x7a
ffffa9015edf2e60 00007ff73c40dedd : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiMcheckAbort+0x277
0000003f545fdef0 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ff7`3c40dedd


MODULE_NAME: AuthenticAMD

IMAGE_NAME: AuthenticAMD.sys

STACK_COMMAND: .cxr; .ecxr ; 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
---------

EDIT: I have uploaded some dump files to Dropbox if it helps to debug them:

Dumps.zip

Shared with Dropbox

www.dropbox.com

 

[EthanSierra]

Other games this happens on:

Modern Warfare II
Satifactory
GTA V
Overwatch 2
Elden Ring

I can play games like League of Legends, Persona 5, Factorio without any issues.

 

[Roland Of Gilead]

Hey there,

Did you clear CMOS after bios update? If not, do that, and let's rule that out.

BSODS can often be ram related. Try run memtest86+ outside of windows (create a bootable thumb drive).

The WHEA_UNCORRECTABLE_ERROR can be related to a hardware issue, so could be any number of things.

85c is pretty high for a gaming load. No matter what game I play my CPU never gets above 65-70c max. What cooler do you have? Case and airflow?

 

[Colif]

CPU 5600X
MB: Asus Prime B450M
Ram - 16gb Corsair Vengeance LPX
GPU - RTX 3060
Storage - WD Blue SN550 NVMe
1tb Seagate hdd
what PSU?

WHEA - WIndows Hardware Error Architecture.
Its an error called by CPU but not necessarily caused by it.
Can be hardware, can sometimes be software
remove any overclocks
remove any overclocking software - so things like AI Suite, Ryzen Master
Can be caused by heat, so if its in games, check the heatsinks and fans are clear of dust - what case do you have now?

Userbenchmark thinks you have an older bios than you do

are all the dumps WHEA errors? I might just do last 5 right now, and see what they show.
Conversion of dumps

report - Click run as fiddle to see report

Spoiler

File: 111322-9703-01.dmp (Nov 13 2022 - 20:21:00)
BugCheck: [WHEA_UNCORRECTABLE_ERROR (124)]
Probably caused by: memory_corruption (Process: GoW.exe)
Uptime: 0 Day(s), 11 Hour(s), 09 Min(s), and 45 Sec(s)

File: 111322-8812-01.dmp (Nov 13 2022 - 22:15:42)
BugCheck: [WHEA_UNCORRECTABLE_ERROR (124)]
Probably caused by: AuthenticAMD (Process: GoW.exe)
Uptime: 0 Day(s), 0 Hour(s), 18 Min(s), and 01 Sec(s)

File: 111222-9796-01.dmp (Nov 13 2022 - 09:10:45)
BugCheck: [WHEA_UNCORRECTABLE_ERROR (124)]
Probably caused by: memory_corruption (Process: GoW.exe)
Uptime: 0 Day(s), 6 Hour(s), 07 Min(s), and 04 Sec(s)

File: 111222-10078-01.dmp (Nov 13 2022 - 03:03:09)
BugCheck: [WHEA_UNCORRECTABLE_ERROR (124)]
Probably caused by: memory_corruption (Process: GoW.exe)
Uptime: 2 Day(s), 7 Hour(s), 54 Min(s), and 05 Sec(s)

File: 110722-11812-01.dmp (Nov 7 2022 - 19:16:33)
BugCheck: [MEMORY_MANAGEMENT (1A)]
Probably caused by: memory_corruption (Process: MsMpEng.exe)
Uptime: 3 Day(s), 9 Hour(s), 56 Min(s), and 23 Sec(s)

Comment: The GPU tweaking driver "iomap64.sys" was found on your system. (AI Suite or GPU Tweak 2)

since you reinstalled windows a few times, good chance its hardware.

Try running Prime 95 overnight, it goes for 17 hours
https://www.guru3d.com/files-details/prime95-download.html
Prime 95 Instructions - https://appuals.com/how-to-run-a-cpu-stress-test-using-prime95/
it will check ram, CPU & PSU

I won't be here tomorrow as its stormy here but I will look in when I can.

 

[EthanSierra]

Thanks so much for your reply, the new case I got is an NZXT H7 Flow, and I also got 3 extra 120mm Corsair fans, but it hasn't actually had much impact on my temps. I am still running the stock AMD CPU cooler, so I'm planning on upgrading that to a liquid CPU cooler this week.

I'll run Prime 95 overnight tonight and post the results in the morning.

I've tried 2 different PSUs and had the same crashes, the one that came with the prebuilt was a Corsair CV550 550w, but I have since replaced it with an EVGA 750 B5 750w from my last build.

 

[EthanSierra]

I also reset my BIOS to factory default after updating it. Only the latest dump file was from a crash after updating and resetting the BIOS

 

[Colif]

temps are high but 5600x can run at up to 95c so it shouldn't be too hot for CPU.
Case looks airy enough - https://nzxt.com/en-AU/product/h7-flow

 

[Roland Of Gilead]

Thanks so much for your reply, the new case I got is an NZXT H7 Flow, and I also got 3 extra 120mm Corsair fans, but it hasn't actually had much impact on my temps. I am still running the stock AMD CPU cooler, so I'm planning on upgrading that to a liquid CPU cooler this week.

I'll run Prime 95 overnight tonight and post the results in the morning.

I've tried 2 different PSUs and had the same crashes, the one that came with the prebuilt was a Corsair CV550 550w, but I have since replaced it with an EVGA 750 B5 750w from my last build.

Why are you running Prime overnight? This is a major load, and not representative of everyday use. Sure, if you're aiming for absolute stability, then this is okay. But not needed.

You would also expect high temps with stock cooler.

 

[Colif]

i suggested Prime as its about only test we have for AMD CPU, and it would at least check the CPU is alright. We have to start somewhere. It also checks ram and PSU.

other places to look are:
ram:
Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors. Memtest is created as a bootable USB so that you don’t need windows to run it

WD Nvme - https://www.google.com/search?client=firefox-b-d&q=westernd+digital+dashboard
Seagate hdd - https://www.seagate.com/au/en/support/downloads/seatools/