I've been experiencing frequent BSODs (Blue Screens of Death) that point to ntoskrnl.exe. Here's what I've tried so far: I removed my GPU and am now using integrated graphics, and I also rolled back to a system image from over a year ago on a different hard drive. I've performed several system file checks, disk checks, and even ran Memtest86 on my RAM while reseating it. My setup includes an Intel Core i9-14900K CPU, Corsair liquid cooling, and 128 GB of DDR5 RAM. The red flag for me is that I'm still crashing even when trying to boot from a USB drive with no other drives connected. It leads me to believe there might be a hardware issue, possibly with the CPU. I've ruled out the power supply since issues arise even without power-hungry components. I'm considering checking the RAM further by removing some sticks, and maybe doing a BIOS update, but I'm unsure how to proceed with isolating and testing the CPU. I've also linked recent dump files for review.
2 Answers
You mentioned the crashes occur even without the GPU and while trying different hard drives, which points towards a more fundamental hardware issue. I'd recommend trying to reseat the CPU and check for any bent pins on the socket. If everything looks good, you might want to see if there’s an available BIOS update that can help stabilize things. If it's still acting up, you may want to consider testing with a different CPU if you have access to one, just to definitely rule it out.
It sounds like you've done a solid amount of troubleshooting already! To start testing your CPU, you might want to try running a stress test using a tool like Prime95 or AIDA64. These can help identify if the CPU is causing instability under load.
Also, it wouldn’t hurt to double-check your cooling system; sometimes overheating can cause erratic system crashes. If stress testing shows errors or crashes, it could indicate that your CPU is indeed failing. Good luck and keep us updated!
Definitely check your cooling first; overheating can mask itself as a CPU issue. I had similar issues before and it was just a bad cooler!
Reseating the CPU is a great call! My friend's system started acting up, and it turned out to be a bad connection there.