Screen displays a steady blue color continuously.
Screen displays a steady blue color continuously.
So a month back I replaced my CPU cooler and then did a fresh Windows 11 setup after facing several crashes. I thought a clean install to Windows 10 might help, but the blue screens kept appearing. I suspected it could be related to my GPU since those errors usually pop up during games or when the driver disconnects unexpectedly. I replaced my old GPU and the issue stopped, but it still didn’t resolve. I’ve checked SFCscan, memory diagnostics, disk scans, and updated all drivers. My system specs are: Ryzen 7 2700X, RX 580, GTX 960, 16GB RAM, 3200MHz. I’m really unsure what’s causing this and would appreciate any advice or tips from others.
Focus on the blue screen occurrences and consider a mini dump. The troubleshooting section has pinned posts offering different guidance and required statistics. A full parts inventory is essential, which might point to a HDD failure. Memory issues are a frequent reason for crashes after startup, and underpowered power supplies are another possibility—though your setup likely doesn’t match typical culprits. Verifying memory health is usually part of the process. It may not find anything immediately, but it’s a free option that takes some time. Memtest86 is outdated yet functional. A few clean passes can reduce the likelihood of memory failure without eliminating it entirely.
It seems the blue screen issue varies each time, but most often relates to memory problems. I checked the Windows memory diagnostic and it reported no problems.
There exists an older, more nuanced method that comes before memtest86. It can be slow and depends on having multiple memory sticks, making it less practical in some cases. You insert just one stick and let the process begin. If an error occurs, switch to the other stick; if it passes, the issue likely lies elsewhere. It can detect subtle faults that memtest86 might overlook. I’m unsure about the current built-in memory check. Usually, a few complete runs of memtest86 are sufficient to identify other issues before focusing on the single stick test. It’s a useful approach for catching problems others miss.
So it stopped working at the 3/4 section with 94 errors detected.