[SOLVED] How do I find the cause of my BSODs?

Aug 31, 2020
3
0
10
Hello,
So for the past few weeks, I've been having BSODs.
I built my PC myself about 10 months ago, all the parts are new and everything was fine for a long time. About a month back I started having a BSOD here and there so I started investigating.

This is my rig:
OS: Win 10 Pro (1909)
CPU: Ryzen 5 3600
Motherboard: ASUS TUF B450M Plus Gaming
Memory: Corsair Vengeance LPX 16GB (2x8GB) DDR4 DRAM 3200MHz C16
Graphics Card: EVGA RTX 2070 Super
PSU: Antec EA750G Pro 750W Gold
Hard Drives: Crucial P1 1TB 3D NAND NVMe PCIe M.2 SSD
I have two monitors: 2K 144Hz and a regular 1080p 60hz.

So at first, I tried to disable DOCP and revert everything back to stock because I thought my RAM is unstable. Turns out it wasn't it because on stock settings, I would still get BSODs.
I ran Memtest86 about 3 times (4 runs each time), ran Testmem5 and ran HCI Design Memtest. All came without errors. I also swapped the sticks.

I moved on to OCCT and the OCCT test for about 3 hours. No errors.

I then tried Prime95. ran the test for 4 hours, CPU got a little toasty but overall looked fine. No errors.

Then I tried FurMark. Stress tested my GPU for 1 hour. I saw no artifacts or crashes.

I decided this wasn't an issue with my hardware, so I started testing drivers with Windows driver verifier. I ended reinstalling Windows from scratch after encountering a test that crashed my Windows, but no dump file was generated.

It's been almost a week since I reinstalled my OS and things are not looking better. I used DDU to reinstall the Nvidia drivers, tried a bunch of different version, I installed the latest BIOS and Chipset version, but I still get BSODs.
Those BSODs are mostly happening when I play a game like Risk of Rain 2, or use Bluestacks, or simply in a Zoom meeting. I remember it crashing during regular browsing only once. It's yet to crash during CSGO for example, and I don't have a lot of other games to test it on. It's fine on Fallout New Vegas, Borderlands 3, Fall Guys and that's about all the games I've played lately. I mostly play Risk of Rain 2 though, which crashes on it's own for some reason. Devs believe it's my hardware's fault which somewhat makes sense after they viewed the logs.

I'm getting quit desperate to find the issue, I built my first PC and watching it crash all the time isn't pleasant. I was considering buying new RAM, replacing my GPU under warranty, replacing my mobo/CPU, but I can't pin point an exact issue with either of those components. I need your help..

Here is the latest screenshot from BlueScreenView:
7SL2JA6.png


Here is a link to my MEMORY.DMP file: https://drive.google.com/file/d/1D6FVfFndCmbUgzM_MT-MfvYysJIFsc4D/view?usp=sharing
Here are the minidump files separately, it contains the 5 BSODs: https://drive.google.com/file/d/13K1LmqhvEpnnEBAMORgh6C181Wy0_Qip/view?usp=sharing

Hopefully I'll be able to find my answer here.
Thanks.
 
Solution
Agreed: dump files can be analyzed - but doing so is not within the purview of most folks (including myself).

There are some forum members who can and do do that. Perhaps one of them will note your post and be able to respond according.

Reliability History is not the end-all analysis. Viewing the technical details may provide more specific information. Event History (though not as user friendly) can be revealing.

What I see in Reliability History is that "Risk of Rain.exe stopped working as 3 of the 9 critical events listed.

The other events are likely caused by you having no other choice other than to power down. Windows does not get the chance to do its' pre-shutdown housekeeping and errors result.

My suggestion is to boot...
Look in Reliability History and Event Viewer for error codes, warnings, and even informational events that correspond with the BSODs.

Power down, unplug, open the case.

Clean out dust and debris.

Reseat all cables, cards, RAM, and jumpers. Ensure that all are fully and firmly in place.

Manually download drivers directly from the applicable manufacturer website. Reinstall, and reconfigure. Use no third party tools or utilities to do so.
 
Look in Reliability History and Event Viewer for error codes, warnings, and even informational events that correspond with the BSODs.

Power down, unplug, open the case.

Clean out dust and debris.

Reseat all cables, cards, RAM, and jumpers. Ensure that all are fully and firmly in place.

Manually download drivers directly from the applicable manufacturer website. Reinstall, and reconfigure. Use no third party tools or utilities to do so.
Done all of the above.
 
Nothing in Reliability History or Event Viewer?

"I ended reinstalling Windows from scratch after encountering a test that crashed my Windows "

What test did that?
So I started using the first 3 tests and just added more and more until it crashed finally.
One of these 3 tests crashed the system:
pdLlAVq.png


The issue was that although the system crashed, no dmp files were created. So it wasn't possible to troubleshoot.
Here is a link from Microsoft that I followed: https://answers.microsoft.com/en-us...behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983

Windows Reliability Center shows the BSODs and crashes, but I don't see what benefit it has over analyzing the dmp files.
DjGY9a6.png
 
Agreed: dump files can be analyzed - but doing so is not within the purview of most folks (including myself).

There are some forum members who can and do do that. Perhaps one of them will note your post and be able to respond according.

Reliability History is not the end-all analysis. Viewing the technical details may provide more specific information. Event History (though not as user friendly) can be revealing.

What I see in Reliability History is that "Risk of Rain.exe stopped working as 3 of the 9 critical events listed.

The other events are likely caused by you having no other choice other than to power down. Windows does not get the chance to do its' pre-shutdown housekeeping and errors result.

My suggestion is to boot up the system and observe system performance. Use either Task Manager or Resource Monitor. One or the other; observe using both but only one at a time.

Observe while the system idles, while doing light work/browsing, and then while playing Risk of Rain.

Watch for system changes especially anything that precedes the BSODs.

Overall, the problems seem to occur with the system reaches some threshold stress level.

Either while gaming or while testing. Key is to identify that threshold value and what may trigger it.
 
Solution