Question Motherboard stops seeing M.2 NVMe boot drive after BSOD

eternalabys

Honorable
Nov 8, 2018
159
5
10,615
Hey everyone,

(I'll start this off with an apology for the post being so long as I tried to be as detailed as I could to try and get to the bottom of the issue, cause at this point I'm just thinking of buying a new 2TB 970 EVO Plus and hoping that it would fix the issues)

As the title reads, I've been recently having issues with my Adata XPG SX8200 Pro 512GB boot SSD giving up the ghost. Issues began months ago where it randomly BSOD'd and wouldn't load in to windows, I removed the SSD, plugged it back in to the board and it popped up again, I was dumbfounded but thought nothing of it until it happened again a while later, so I reinstalled windows and thought it would be fine.

(Well, not so recently as I've had the issue for a while but now it's ramped up to the point where I can't really play anything anymore because of it.)

Anyways, now it's happening again but even worse, originally I thought it might've been the RAM setup I was using, as I was using 2 mixed kits of 2x8GB G.SKILL Trident Z RGB and 2x8GB Crucial Ballistix RAM, both running at 3466MT/s (Which was the slowest setting of the two kits), and CL16 @ 1.35V.

So I took out the other set and tried to swap between both kits while trying to load in to a raid in Tarkov, and even at stock 2133MT/s speeds it still BSOD'd.

The error codes were random, most being WHEA_UNCORRECTABLE_ERROR's or UNEXPECTED STORE EXCEPTION's. I followed guides and multiple sfc scans showed up as having no issues, DDU'ing my GPU driver and reinstalling the latest ones yielded the same effect.

Games I tried were:EFT: Loads menu fine, but when trying to load a raid it most of the time hangs while loading map and loops the music until it possibly actually loads, or crashes with a BSOD.Doom Eternal: Hangs in game after 15-20 minutes of gameplay. Crashes to Desktop.

CS2: Irrecoverable crash while trying to load map. BSOD ensues.

FH4: Crashes to desktop 20-30 minutes in to the game.

Mind you, every single time it BSOD's, the M.2 goes invisible for the motherboard, it stops seeing it in the boot order or even the connected devices, all of my SATA drives are there on the other hand.

Only way I've found to fix it (i.e, make it boot again, is to switch off the PSU, drain the power by pressing the power button a few times, starting it back up again, even then, sometimes it doesn't see it.)

(P.S. Event Logs only indicate that the system shut down unexpectedly, though I'd be happy to share said logs if needed.)

System specs for those interested:

CPU: Ryzen 7 3700X

CPU Cooler: Arctic LFII 240

Mobo: AsRock B450M Pro4

RAM: 2x8GB G.Skill Trident Z RGB

2x8GB Crucial Ballistix

(3466MT/s CL16 1.35V)

SSD: Adata XPG SX8200 Pro 512GB

HDD: Seagate Barracuda 2TB

WD Blue 1TB

GPU: EVGA SC GTX 1080

Case: Fractal Design Meshify 2

PSU: Corsair TXM 550W

Case Fans: 3x be quiet! Silent Wings 3 120mm

3x Fractal Design Dynamic X2 GP-14 (Stock)
 
Haven't figured out what the issue with the BIOS not seeing the SSD anymore is, but sure found out that most of the blue screen errors have been the XMP setting of my RAM kit. Apparently a 3700X on a B450M Pro4 with 3600MT/s CL16 Ballistix kit of RAM, that already had a 50% chance of being faulty as it came from another PC who couldn't use them anymore, was the culprit. Just started <Mod Edit> itself essentially whenever a higher RAM load was applied. Couldn't even knock it down to 3466, had to go straight down to 3200MT/s
 
Last edited by a moderator: