[SOLVED] BSOD while heavy use of pc

[jhollis505]

Hello, I've build a new pc recently and have been having some issues. When I first built it, and while trying to play Deus Ex: Mankind Divided, I kept getting BSODs. I followed some info online (it was a couple of weeks ago and don't remember what I did besides updating some drivers), then my pc was working just fine. I ordered a new nvme ssd and did a fresh install of Windows 10 on it. Now I'm playing RDR 2 and am having the same issue, however, updating drivers did not correct the issue. I have tested two sets of ram with the system, both tested without errors. However, the ram I currently have in the pc, I have made the timings in the bios what they are rated for and tuned the Infinity Fabric to 1600mhz. I did try the ram out at the default settings for bit and the pc was running fine while playing RDR 2 for about a hour (it takes roughly 15 to 30 mins for the BSOD to happen), but I didn't have them on default for too long. My gpu and cpu are not overclocked. I have tested both of them with AIDA64 without issue. The only other game I have installed and have played is Prey 2017 and I have played that game for hours without having a BSOD. Any help is appreciated. And if any more info is needed, let me know. Thank you.

Here is the OneDrive link for 3 DMP files, MSinfo32, and Aida64 Summery: https://1drv.ms/u/s!AtKNBFgpKtoErFd7TPM_ipmRoXOB?e=dALiGC

Also, the newest DMP was made following info from using driver verifier, the other two were made from enabling minidumps.

Other info that might not be included with summery:
RAM: XPG Z1 3200 AX4U320038G16A-DBZ
SSD: XPG SX8200 Pro 2TB
Nvidia driver 461.92

 

[Colif]

ASUS Framework Service 2.0.2.2 - The process listens for or sends data on open ports to a LAN or the Internet.
appears to be part of armory crate

Asus Motherboard - couldn't they have chosen a name that doesn't have 1.4 million results
Most of which aren't right, cause its obvious why. I think its part of Aura Sync

we not getting anywhere, lets try driver verifer and see what it finds
https://forums.tomshardware.com/threads/driver-verifier-instructions.3686888/ follow the precautions I have shown, it can lead to boot loops so hopefully safe mode will work.

 

[gardenman]

Hi, I ran the dump file through the debugger and got the following information: https://jsfiddle.net/afg617v3/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

File information:	032121-6031-01.dmp (Mar 21 2021 - 16:01:04)
Bugcheck:	WHEA_UNCORRECTABLE_ERROR (124)
Probably caused by:	AuthenticAMD (Process: RDR2.exe)
Uptime:	0 Day(s), 1 Hour(s), 19 Min(s), and 05 Sec(s)

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[jhollis505]

I preformed the instructions for verifier. Here's the onedrive: https://1drv.ms/u/s!AtKNBFgpKtoErHCU7aISWPho3qpA?e=0Ufjvn

 

[Colif]

Hopes its more useful than the 1 line WHEA errors have been

i am waiting for Gardenman to covert it

 

[gardenman]

I ran the dump file through the debugger and got the following information: https://jsfiddle.net/nd4t1my6/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

File information:	032321-6046-01.dmp (Mar 23 2021 - 14:45:29)
Bugcheck:	DRIVER_VERIFIER_DETECTED_VIOLATION (C4)
Driver warnings:	*** WARNING: Unable to verify timestamp for RzDev_006c.sys
Probably caused by:	RzDev_006c.sys (Process: System)
Uptime:	0 Day(s), 0 Hour(s), 00 Min(s), and 06 Sec(s)

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[Colif]

razer drivers
I don't need to look

ok, i will

Aug 17 2020

RzDev_006c.sys

Razer driver

wasn't a hard guess

all by itself, no Synapse to be seen. Wonder how you remove it
Should be able to see it and remove it with https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns

 

[jhollis505]

I deleted RzDev_006c.sys using autoruns then got a BSOD whiling playing RDR 2. I opened up autoruns to check if the file was showing up, it was.

https://1drv.ms/u/s!AtKNBFgpKtoErHNAYdKMB6UBuSky?e=AEYwfr

 

[jhollis505]

Just to ask, since you've tried to help me for a few days, should I try to get my hands on a new cpu and test it on my motherboard? Would a ryzen 3000 series work or should I look for 5000 series?

EDIT: What's the likelihood that it could be my motherboard?

 

[gardenman]

I ran the dump file through the debugger and got the following information: https://jsfiddle.net/9r8mfnhy/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

File information:	032321-6140-01.dmp (Mar 23 2021 - 23:31:13)
Bugcheck:	WHEA_UNCORRECTABLE_ERROR (124)
Probably caused by:	AuthenticAMD (Process: RDR2.exe)
Uptime:	0 Day(s), 8 Hour(s), 38 Min(s), and 03 Sec(s)

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[Colif]

id like to know why its only in 1 game

Did you install Synapse? I see more razer, not less this time.

Aug 17 2020

RzDev_006c.sys

Razer driver

Nov 15 2020

RzCommon.sys

Razer Common driver (Razer Inc)

Some of the BSOD reports say its a Win 8 Driver. I believe that also means it can be a WIn 10 driver, as I never seen it say WIn 10 there. So until Driver verifer stops blaming drivers, its possible its still software.

CPU - AMD Ryzen 7 5800X - tested in AIDA
MB - Asus ROG CROSSHAIR VIII HERO latest BIOS
RAM: XPG Z1 3200 AX4U320038G16A-DBZ - how did you test it?
SSD: XPG SX8200 Pro 2TB
What GPU?
Any other storage?
What PSU?

GPU: Gigabyte 3070 gaming oc
PSU: Seasonic PX-850

passes Prime95 no errors.
passes AIDA no errors
Passed memtest

it keeps blaming different drivers, I seen it do that before, fix one, another pops up. Often its ram to blame.

I don't think its the CPU but I also seen them pass tests and still be cause.

I don't want to guess its Motherboard. I would be more inclined to get a repair shop to look at it, they can test with parts they know work and it removes the guessing.
I feel its less expensive and I hate to see people replace parts just to keep getting same errors. It makes me feel like I failed.

 

[jhollis505]

I deleted those files using autoruns and received another BSOD.

https://1drv.ms/u/s!AtKNBFgpKtoErHUrStANbLcu-wML?e=dWxzr8

 

[gardenman]

I ran the dump file through the debugger and got the following information: https://jsfiddle.net/9y2rz4ex/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

File information:	032421-7593-01.dmp (Mar 24 2021 - 13:38:19)
Bugcheck:	WHEA_UNCORRECTABLE_ERROR (124)
Probably caused by:	AuthenticAMD (Process: RDR2.exe)
Uptime:	0 Day(s), 14 Hour(s), 06 Min(s), and 30 Sec(s)

Comment:
I don't think additional dumps are going to help us, at least at this point. It's definitely screaming "hardware problem", but figuring out which hardware is the issue here.

Also, using software to test hardware isn't a perfect science. We've seen it in the past, where people pass memtest only later to change the RAM out and have their system fixed. That's only an example, I'm not saying your issue is (or is not) RAM.

I also suggest taking it a repair shop, as Colif suggested. They can try different hardware out.

 

[Colif]

Every single report is more or less the same thing

they all have a memory address causing nt!KeBugCheckEx
one line of text per error.,.. nothing for me to latch onto

032121-6031-01.dmp
ffff890171d1b938 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KeBugCheckEx
032121-6046-01.dmp
ffff950010467938 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KeBugCheckEx
032121-5937-01.dmp
ffffb5816c68d938 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KeBugCheckEx
032021-5875-01.dmp
ffff8880ec77f938 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KeBugCheckEx
032421-7593-01.dmp
ffffc90139860938 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KeBugCheckEx
032321-6140-01.dmp
ffffe50088e60938 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KeBugCheckEx

And its not the same address each time. In fact it doesn't repeat at all.

Sure, the driver verifer errors were different, but most of the time I get some hint as to what cause is.

it could be CPU, Memory, Motherboard.
2 if those things have been tested but software tests aren't perfect
NO actual tests for motherboard besides swap all the gear onto another one.

I would love to be able to tell you its this... but I can't. If I sent you to Tenforums I could guess they blame CPU, they always seem to on people I send there. They might see something I am missing.

 

[jhollis505]

id like to know why its only in 1 game

Well the only two games I currently have installed are Prey 2017 and RDR 2. But Prey wasn't having these issues. I can try another more modern game and see what happens.

I did make a post on tenforums and they told me to buy another cpu to test.

 

[Colif]

You already suggested the CPU idea so if you are willing to do it, go ahead. it could be a bad CPU, the memory controller is on CPU.

so wonder what main difference is between both games, is rdr more graphics intense or uses more ram. or open world just makes CPU work harder

 

[jhollis505]

I just installed COD Cold War and its been running smoothly for over a hour. I'll try another open world game and I'll update.

 

[Colif]

i wonder if logging sensors during game play might show us something
Download HWINFO - https://www.hwinfo.com/download/
when you open the app, click the tick box next to show sensors only, and click run
in the next window, click on the button to the right of the clock in bottom row, it shows "logging start" if you hover over it.
this opens file explorer, it lets you create a log file which tracks all the sensors on MB while you play game
it doesn't auto start logging at startup (its a feature thats been requested for last 6 years) so you will need to restart

I made this guide - https://forums.tomshardware.com/threads/how-to-use-hwinfo-to-track-sensor-values-on-ryzen.3693704/

now the results are in CSV form which can be read in Excel or Google Docs
If you want us to look, upload to onedrive and show a link. I am not expert on those outputs and I might get someone else to look at them...
I might see if anyone else has any smart ideas too.

 

[jhollis505]

I got a BSOD while having HWiNfo logging, here's the log: https://1drv.ms/u/s!AtKNBFgpKtoErHcCQPQqCLqqstix?e=jPMlE0

 

[Colif]

i have asked for more opinions, if no one answers in next few hours I will look at logs and see if anything obvious.

 

[jhollis505]

i have asked for more opinions, if no one answers in next few hours I will look at logs and see if anything obvious.

Any chance there's an update for this?

Also, I was thinking about some open world games to try that tend to be cpu heavy or heavy on pcs in general and I thought of Assassin's Creed Unity. So I installed it and I got a BSOD. So at least its not just RDR 2.

DMP file: https://1drv.ms/u/s!AtKNBFgpKtoErHvUJJAC3_L9e6kn?e=yHM9yM

 

[Colif]

well, i had hoped one person would look but he may not have been in.

I can't see anything obvious but I am not best person to read these. Nothing stands out. its not power, thats for sure

 

[jhollis505]

I did get a notification that someone had edited the HwiNFO log, so I believe someone had looked at it and made it into an excel file.

 

[Colif]

that was probably me. I thought i was changing my copy, not the original

 

[gardenman]

I ran the dump file through the debugger and got the following information: https://jsfiddle.net/wej28dvz/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

File information:	032621-6187-01.dmp (Mar 26 2021 - 00:37:09)
Bugcheck:	WHEA_UNCORRECTABLE_ERROR (124)
Probably caused by:	AuthenticAMD (Process: chrome.exe)
Uptime:	0 Day(s), 9 Hour(s), 28 Min(s), and 16 Sec(s)

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[jhollis505]

I played AC Unity last night for a little bit more than 2 hours with no BSOD. I also played RDR 2 today for about a hour with no BSOD. I'll try to play them a bit more in the next couple of days to see if I can get a BSOD.