Solved Weird BSOD when Gaming/Benchmarking | Happens Only When GPU + SSD are running together

Hi everyone, recently I've been encountering a consistent BSOD every time I launch a game or run GPU + SSD benchmarks together.
The only two errors I get are "CRITICAL_PROCESS_DIED" or "UNEXPECTED_STORE_EXCEPTION".
Basically, anything that heavily utilizes the SSD & GPU at the same time causes a BSOD.

I've attached the V2 Log Collector logs in this post.

PC Specification:

Windows 11 23H2, OS Build: 22631.2715
AMD Ryzen 9 5900x
MSI RTX 3080 SuprimX 10GB
ASUS ROG Crosshair 8 Hero Motherboard
G.SKILL 32GB RAM, DDR4 - 3600mhz
WD_BLACK SN850x 2TB Gen4 SSD (purchased 7 months ago)
NZXT C850 80+ GOLD PSU


How to reproduce this problem:

-Run any AAA game (GTA V, Forza Horizon 5, Cyberpunk 2077): BSOD.
-Run SSD Benchmark (CrystalDiskMark) + GPU Benchmark (Furmark) at the same time: BSOD.

-Only run SSD Benchmark (CrystalDiskMark): NO BSOD.
-Only run GPU Benchmark (Furmark): NO BSOD.
-Regular PC Usage (Browsing, watching videos, etc): NO BSOD.

Troubleshooting done before posting here:

-Checked temperature of SSD/GPU, both do not overheat. SSD and GPU max out at 70-75c.
-Updated to the latest version of Windows 11 & Nvidia Drivers.
-Ran sfc /scannow
-Updated SSD firmware to the latest version (620361WD)
-Clean re-install of latest Nvidia Drivers (with DDU).
-Rolling back Nvidia driver to last known stable version.
-Turned off all overclocking, including PBO (set to disabled in BIOS).
-Installed latest AMD Chipset Drivers.
-Updated BIOS to the latest version (ver 4702).
-Re-seated the RAM sticks.
-Removed the GPU, cleaned it and installed it back again.
-Removed the SSD, installed it back again.
-Checked and re-inserted the GPU Power Connectors.
-Did a complete re-install of Windows 11 and all drivers.

Kindly help me fix this as I am unable to play any games or point to what is causing the problem here.
Thank you.

There are no dumps in the upload and the System log covers only a 9 minute window, so there isn't very much info to go on I'm afraid.

I will say that the CRITICAL_PROCESS_DIED and UNEXPECTED_STORE_EXCEPTION bugchecks are most usually seen with RAM problems. I would suggest either downloading Memtest86 (free) and running that twice (so you do 8 iterations of the 13 different tests) or (better yet) remove one RAM stick and run on just one for a day or two, then swap sticks and run on just the other for a day or two. You'll soon see whether one stick BSODs and the other doesn't.

If your RAM looks good then we'll need much more data. Don't clear dump files and don't clear logs!

ubuysa said:

There are no dumps in the upload and the System log covers only a 9 minute window, so there isn't very much info to go on I'm afraid.

I will say that the CRITICAL_PROCESS_DIED and UNEXPECTED_STORE_EXCEPTION bugchecks are most usually seen with RAM problems. I would suggest either downloading Memtest86 (free) and running that twice (so you do 8 iterations of the 13 different tests) or (better yet) remove one RAM stick and run on just one for a day or two, then swap sticks and run on just the other for a day or two. You'll soon see whether one stick BSODs and the other doesn't.

If your RAM looks good then we'll need much more data. Don't clear dump files and don't clear logs!

Click to expand...

Hi, thanks for responding. I will download Memtest86 tonight and let it run.
I will get back and update this post if I find anything.

Also, apologies for posting my problem on another forum. I didn't mean to make multiple posts, it's just that my account here was not approved for some time which is why I originally posted this on TomsHardware.

Please perform the following steps:

1) Run:

Tuneup plus:



Post a share link into this thread using one drive, drop box, or google drive



2) Run: Sea Tools for Windows Long Generic test > post a share link into this thread using one drive, drop box, or google drive
(All drives)

https://www.seagate.com/content/dam...shared/downloads/SeaToolsWindowsInstaller.exe

https://www.seagate.com/content/dam...ds/seatools/_shared/downloads/100869623_B.pdf


3) Run: HD Tune (free or trial): post a share link into this thread using one drive, drop box, or google drive

HD Tune website

(All drives)
a) Health
b) Benchmark
c) Full error scan


4) These can run overnight while sleeping:
a) Sea Tools for Windows Long Generic test
b) HD Tune Full error scan

Hi everyone, I'm here to give an update on my BSOD problem. I managed to fix it but I do not know what was causing it.
Here's what I did (and I'm sorry if it doesn't work for you): I completely dismantled my PC, cleaned every component and cable and re-assembled it back again. This fixed the issue and my PC does not BSOD anymore when gaming/benchmarking.

I really tried hard to pinpoint what was causing this, but I couldn't.
My assumption is that it was a loose connection somewhere. I doubt if it was dust because I clean my PC every month.

I would also like to mention, I did run Memtest86 twice as suggested by @ubuysa, but there were 0 errors and both the tests passed.

Thanks to everyone here for attempting to help me with this.

Memtest86 is good but no RAM tester can find all RAM issues. As I mentioned, those BSODs are typical of RAM problems, so perhaps just re-seating the RAM did the trick. Glad it's sorted anyway.

Please post a new V2 if there are any hangs, freezes, or unexpected shutdowns and restarts during the next few days.

zbook said:

Please post a new V2 if there are any hangs, freezes, or unexpected shutdowns and restarts during the next few days.

Click to expand...

Will do so, thank you!

Hi everyone, I'm back here to give an update on my findings. Last month, I had a BSOD issue which I managed to fix by completely disassembling my PC and re-wiring it back again.

Today, I started experiencing this issue once again. Upon inspecting the cables, I noticed my custom sleeved 24 pin connector cable (which connects to the PSU's 24 pin cable) was slightly disconnected. I removed it and re-inserted it back again firmly and my BSOD has stopped.

I don't know if this will fix your issue, but it certainly did fix mine.
Please check if your 24 pin connector is firmly connected to the PSU or the PSU cable (if you're using a custom sleeved cable).