I've been having some serious trouble with my computer for the past few months with Blue Screen of Death (BSOD) issues. It started with occasional 'Unexpected Store Exception' errors mainly when I was pushing my computer hard, like when playing Minecraft with a ton of mods or streaming video. However, things have escalated quickly. Now I'm getting BSODs just trying to record audio in Audacity or even watching YouTube.
The errors have evolved from just the 'Unexpected Store Exception' to alternating with 'Memory Management' and now, this past week, I'm also encountering 'Kernel Data InPage Error'. I've scanned my RAM and it didn't show any errors, but I did notice a small scratch on one stick, though it still works. I even removed that stick, but the BSODs haven't stopped.
Here are my specs: Intel Core i9 9900K, Gygabyte Z390 AORUS PRO, 16GB DDR4 RAM (with one stick removed), and an NVIDIA GeForce RTX 3060. My main drive is a 1TB SSD, plus two internal HDDs and an external HDD for editing projects.
I had an incident a while back when an external sound mixer fell into my PC and caused a hard crash, but there were no immediate BSODs after that. I really don't want to replace my computer if it can be fixed without new parts. Any advice would be appreciated!
2 Answers
First things first, we need to look at the dump files generated by those BSODs. If you're able to boot into Windows normally or in Safe Mode, check the C:WindowsMinidump folder for any dump files. Make sure to zip them up and upload them to a file sharing service like mediafire or catbox. More dump files will give us better insight into the issues your system is facing!
Thanks for uploading the dump files! From what I've seen, Kernel Data Inpage Error and Unexpected Store Exception usually indicate that your system drive is having some issues. Can you tell me what make and model your SSD is and how long you've had it?
It's a Samsung 970 EVO Plus 1TB. I bought it from Amazon on June 25, 2021, so it's around 4 years old now. The properties show it's working properly, but the driver date seems weird—June 2006? That can't be right, right?