Critical process termination and unexpected store exceptions recorded.
Critical process termination and unexpected store exceptions recorded.
So, I received my NVMe M.2 RMA from Samsung a few days back and early this morning I installed it. I chose to keep Windows 11 as my operating system because I wasn’t quite ready for Linux yet. Check out my previous forum post for more details; they didn’t find the problem and offered a replacement. They actually sent me a brand-new 990 Pro 2TB instead of the refurbished 980 Pro 2TB, which is really great.
I installed it using the Windows 11 media creation tool they provided directly from Microsoft. I also tried a custom AutoUnattend.xml from Schneegans, if you need it, I can share it. After installation, I followed the usual steps, changed settings, and played a bunch of games on Steam. During one session I got the first BSOD—“UNEXPECTED_STORE_EXCEPTION.” I restarted, looked it up, followed various Microsoft support guides, ran chkdsk and sfc /scannow via cmd, updated several things, and even attempted to force a Windows update by moving files around.
The BSOD seemed to appear when the computer was doing heavy tasks, like launching a game. Unlike before, it wasn’t a WHEA BSOD, there were no entries in Event Viewer, and there were no logs from the file creation error I experienced with my old Windows 10 drive. I’ve collected several photos of almost every BSOD error since the first one after installing Windows. Honestly, I don’t want to wipe and reinstall Windows just because it keeps BSODing again.
I’m leaning toward the motherboard being the issue, as it’s caused me many problems and I had to replace the first one when I got it from Micro Center. I’d have ordered a RMA, but I’m curious about these error codes—could it be a Windows 11 problem or something else? I might try a clean Windows reinstall without deleting files, but first I want to see what these codes mean.
I can recreate the BSOD by launching GTA into story mode and watching it trigger the crash from a bird’s-eye view. I also have some videos of the errors.
Here are my specs from the previous thread:
- Micro Center bundle: 7900X, ROG B650E-F
- RAM: some 2x16GB G.Skill Flare X5 (link provided)
- Motherboard: Arctic LF3 360 with MX-6 Paste MSI 6650 XT
- Storage: MX-6 Paste MSI 850x990 Pro 2TB (brand new)
- I’m using a 2.5" SATA SSD with Windows 10 and never had BSODs.
I’m considering dual monitors, but since my 980 was RMA’d and worked fine on Windows 10, it’s possible the issue is with the M.2 slot or motherboard. I’ll keep taking pictures and videos of the BSODs before making any changes. I’m planning to run a 3DMark stress test to see if that triggers the problem, but I’ll post the results soon.
Well, there's your problem Actually, I suspect this stuff has much to do with it, as you've probably removed too much. Reinstall from scratch, no weeding out the telemetry just yet, try again. Alternatively, as you're about to RMA the mainboard anyway, have a good look at the bottom of the CPU cooler: is the peel removed? But, it may just be a bad PSU. Try another one (1000W minimum if possible) to rule it out for sure.
yeah, that's why I've only just now upgraded to win11, have stuck with win10 before, and I would've gone with linux mint but I'm still too inexperienced with it (have it on a drive for another pc) to use it for my main if this is the case, it's just more win11 crap that win11 thinks it needs coz I used the exact same autounattend file with my win10 thumb drive and it worked no problem yes, the peel is removed, temps are not an issue whatsoever, highly, highly doubt it's the psu since as I mentioned, pc runs perfectly fine, zero BSODs with that other SATA SSD I used while my 980 was RMA'ed im gonna try a few more things before i fully wipe again coz im saving all the steam downloads for overnight
Hi once more. You're not usually dealing with M.2/motherboard issues—you mostly face errors or crashes pointing to the faulty part. Unexpected_Store_Exception refers to a storage-related problem. Critical_Process_Died isn't a direct storage error, but it indicates storage issues nearby, often signaling corruption that affects data storage.