The Blue Screen of Death has been around since Windows 95, and despite Microsoft trying to make it less terrifying over the years (it’s actually a Frowny Face of Death now in Windows 11), it still strikes fear into anyone who sees it. The good news: most BSODs are fixable, and the cryptic stop code at the bottom of the screen tells you exactly where to start looking. Here’s how to read those codes and what to do about the most common ones.
First, capture the error code
When a BSOD appears, write down or photograph two things: the stop code (the text in capital letters like SYSTEM_SERVICE_EXCEPTION or DRIVER_IRQL_NOT_LESS_OR_EQUAL) and any filename mentioned below it (like nvlddmkm.sys or ndis.sys). These are your starting points.
If your PC reboots before you can read the screen, disable automatic restart. Right-click This PC > Properties > Advanced system settings > Startup and Recovery > Settings. Uncheck “Automatically restart” under System failure. The next BSOD will stay on screen until you manually reset.
For more detail, install BlueScreenView (free from NirSoft). It reads minidump files from past BSODs and shows you stop codes, filenames involved, and timestamps – even for crashes you didn’t catch in real time.
The five most common BSOD codes and what they mean
PAGE_FAULT_IN_NONPAGED_AREA – Usually bad RAM or a corrupt driver. Run Windows Memory Diagnostic first, then MemTest86 for thorough memory checking. If RAM passes, look at the named driver file in the crash dump.
DRIVER_IRQL_NOT_LESS_OR_EQUAL – A driver tried to access memory it shouldn’t have. Almost always a driver problem. Check the named file in the crash – if it’s ndis.sys or netio.sys, your network driver. If it’s nvlddmkm.sys, your NVIDIA GPU driver. Roll back or update that specific driver.
KERNEL_SECURITY_CHECK_FAILURE – Windows detected memory corruption and stopped to prevent damage. Bad RAM, failing storage drive, or in some cases overclocking that’s gone unstable. Reset XMP/EXPO profiles to default, run memory and storage diagnostics.
SYSTEM_SERVICE_EXCEPTION – A system service crashed. Often a corrupt Windows file or third-party antivirus conflict. Run sfc /scannow and dism /online /cleanup-image /restorehealth from an elevated command prompt to repair Windows files.
WHEA_UNCORRECTABLE_ERROR – Hardware-level error caught by the Windows Hardware Error Architecture. This one is bad news – it usually means CPU, motherboard, or memory hardware failure. Check temps, reseat RAM, and if it persists, the CPU or motherboard may need replacement.
Update or roll back drivers
If a specific driver file is named in the crash dump, that’s your first target. GPU drivers are the most common BSOD source by a wide margin.
For NVIDIA drivers, download Display Driver Uninstaller (DDU). Boot into Safe Mode. Run DDU to fully remove all NVIDIA driver remnants. Reboot, then install a known-stable driver version (not always the latest – check r/NVIDIA or the GeForce forums for current “stable” recommendations).
For AMD GPU drivers, same approach with DDU works. AMD’s Adrenalin software also has a “Factory Reset” install option that cleans previous installations.
For network drivers (ndis.sys, netio.sys), download the latest from your motherboard or laptop manufacturer’s website. Avoid using Windows Update for network drivers because the generic versions sometimes lag behind manufacturer releases.
Check Windows file integrity
Corrupt Windows system files cause a surprising number of BSODs. Two built-in tools fix most cases.
Open Command Prompt as Administrator. Run “sfc /scannow” and let it complete. This scans protected Windows files for corruption and replaces damaged ones from a local backup.
If sfc reports it found problems but couldn’t fix them, run “dism /online /cleanup-image /restorehealth” next. DISM downloads fresh Windows files from Microsoft to repair the local backup that sfc uses. After DISM completes (can take 20+ minutes), run “sfc /scannow” again.
Check your RAM
Bad RAM is one of the most common BSOD causes and one of the easiest to verify definitively.
Quick check: Windows Memory Diagnostic. Search for it in Start, click “Restart now and check for problems.” Windows runs a basic memory scan on reboot. Takes 15-20 minutes.
Thorough check: MemTest86 (free at memtest86.com). Create a bootable USB stick using their tool, boot from it, and let it run at least one full pass (4 hours+). Any errors found mean the RAM stick is defective and needs replacement. RAM is one of the few PC components with lifetime warranties from most major brands.
If you’ve overclocked your RAM via XMP or EXPO, reset the BIOS to defaults and see if BSODs continue. Some memory profiles run beyond what the motherboard or CPU memory controller can handle stably.
Check storage drive health
A failing SSD or HDD can trigger BSODs when Windows can’t read essential system files. Even SSDs that report as “healthy” can have subtle problems that show up in stress tests.
Download CrystalDiskInfo. Check the Health Status column for each drive. “Good” means fine. “Caution” means start watching closely. “Bad” means back up immediately and replace the drive.
For deeper diagnostics on SSDs, your drive’s manufacturer probably has a dedicated tool: Samsung Magician, Crucial Storage Executive, Western Digital Dashboard. These tools run health checks specific to that drive’s firmware and can sometimes update firmware to fix known bugs.
Recent changes matter
If BSODs started after a specific event, that event is almost certainly the cause:
New hardware installed: Pull it out, see if BSODs stop. Bad sticks of RAM are common, but it could also be a faulty GPU, sound card, or USB device.
Windows update: Uninstall via Settings > Windows Update > Update History. Microsoft pushes problematic updates occasionally and rolling back can resolve issues until they fix it.
Driver update: Roll back via Device Manager > right-click device > Properties > Driver tab > Roll Back Driver.
New software installed: Especially antivirus, system utilities, or anything with kernel-level access. Uninstall recent additions and see if BSODs stop.
When all else fails
If you’ve worked through driver rollbacks, sfc/dism, memory tests, and storage checks without finding the cause, two options remain.
Clean Windows install. Back up your data to external drive, then reinstall Windows 11 fresh from a Microsoft installation USB. This eliminates every possible software cause. If BSODs continue after a clean install, the problem is definitively hardware.
Hardware diagnosis. With software ruled out, suspects are: GPU (try swapping if possible), CPU (rare to fail outside of overheating), PSU (failing units cause weird symptoms including BSODs), and motherboard (check for visible damage like bulging capacitors).
Common questions about BSODs
Why does my PC blue screen randomly with no clear pattern?
Random BSODs without a workload pattern usually point to hardware: bad RAM, failing storage, or a dying PSU. Software-caused BSODs typically correlate with specific actions (launching a game, plugging in a USB device, opening certain apps). Use BlueScreenView to read past minidump files and look for repeated stop codes or driver files. Patterns there often reveal the cause that real-time observation missed.
Is BSOD always hardware?
No. Estimated 60-70% of BSODs trace back to driver problems (software). Hardware failures account for 20-30%. Pure Windows bugs are the remaining slice. Always rule out drivers and Windows file corruption before suspecting hardware – those fixes are free and fast. Hardware replacement is a last resort.
Does overclocking cause BSODs?
Yes, when overclocks become unstable. CPU, GPU, and RAM overclocks all stress components beyond their guaranteed stable range. As components age, what was stable last year might not be stable today. Reset to default speeds in BIOS and see if BSODs stop. If they do, dial back your overclock to a more conservative setting.
Can a virus cause BSOD?
Modern malware rarely causes intentional BSODs since attackers prefer to stay hidden. But poorly-written malware or rootkits can absolutely destabilize Windows enough to crash it. Run Windows Defender full scan and Malwarebytes Free as a second opinion. If you have ongoing BSODs and any scan finds threats, complete the cleanup and watch for changes.
