BSOD/sometimes black screen reset on new pc build during games

Hi there,
I just finished my r5 7600x, Gigabyte 4070, Aorus b650 elite AX, corsair vengeance 32gb 6400 cl32, corsair RM750 build and I'm getting seemingly random intermittent hard crashes or blue screens. I've tried completely wiping nvidia drivers, ran windows memory diagnostics, and reinstalled windows. Not sure what the problem is but this is getting very frustrating. Any help would be GREATLY appreciated. Thank you!

- - - Updated - - -

Here's another link to the v2 collector log on drop box if that makes it easier:
Dropbox - DESKTOP-68K1LR8-(2023-07-23_02-44-23).zip - Simplify your life

Hello and welcome!

The two dumps (from 22nd) are inconclusive really. One is a classic IRQL_NOT_LESS_OR_EQUAL during a networking operation. The other is a REFERENCE_BY_POINTER, which means that a driver mishandled object reference counts. These could be due to a rogue third-party driver that we don't see in the dumps - that's not unusual - or it could be flaky hardware, and RAM is always the first port of call when you suspect hardware. I can also see that you're using DDR5 RAM and that's still a relatively new technology.

In addition, there are several error messages in your system log from the RADAR_PRE_LEAK_64 feature, and for a variety of executables. The RADAR_PRE_LEAK_64 error is caused by the Windows memory leak detector, it's designed to highlight applications that are misusing memory. When we have this message for a variety of applications (rather than just one) the focus moves to suspecting the RAM itself.

First off, if you're overclocking or undervolting the CPU please remove these and run at stock frequencies and voltages until we've solved your issue.

The Windows memory diagnostics is not a particularly thorough tool, so I'd like you to download Memtest86 (free). Use the imageUSB.exe tool extracted from the download to make a bootable USB drive (1GB is plenty big enough) and then boot that USB drive. Memtest86 will start running as soon as it boots, if no errors have been found after the 4 iterations of the 13 different tests that the free version does, please restart Memtest86 and do another 4 iterations.

Let's see how that goes before we move on to other diagnostics.

ubuysa said:

Hello and welcome!

The two dumps (from 22nd) are inconclusive really. One is a classic IRQL_NOT_LESS_OR_EQUAL during a networking operation. The other is a REFERENCE_BY_POINTER, which means that a driver mishandled object reference counts. These could be due to a rogue third-party driver that we don't see in the dumps - that's not unusual - or it could be flaky hardware, and RAM is always the first port of call when you suspect hardware. I can also see that you're using DDR5 RAM and that's still a relatively new technology.

In addition, there are several error messages in your system log from the RADAR_PRE_LEAK_64 feature, and for a variety of executables. The RADAR_PRE_LEAK_64 error is caused by the Windows memory leak detector, it's designed to highlight applications that are misusing memory. When we have this message for a variety of applications (rather than just one) the focus moves to suspecting the RAM itself.

First off, if you're overclocking or undervolting the CPU please remove these and run at stock frequencies and voltages until we've solved your issue.

The Windows memory diagnostics is not a particularly thorough tool, so I'd like you to download Memtest86 (free). Use the imageUSB.exe tool extracted from the download to make a bootable USB drive (1GB is plenty big enough) and then boot that USB drive. Memtest86 will start running as soon as it boots, if no errors have been found after the 4 iterations of the 13 different tests that the free version does, please restart Memtest86 and do another 4 iterations.

Let's see how that goes before we move on to other diagnostics.

Hi there! Sorry it took a while to respond, I just wanted to be sure. The problem was definitely the ram. I ran memtest86 and got no errors, but I figured I would just go get some new ram at best buy anyways because it was nearby, and sure enough that fixed it. Thank you so so so much for the help. You telling me that it was likely the ram itself probably saved me weeks of troubleshooting.

That's good news. No memory tester is ever 100% accurate but 8 iterations of Memtest86 generally finds about 95% of RAM problems. I guess yours were in the other 5%!