A Blue Screen of Death looks catastrophic but is usually fixable — note the stop code, then work through driver updates, Windows updates, hardware and RAM checks, and Safe Mode. This guide covers the fixes for Windows 10 and 11.
The Blue Screen of Death (BSOD) is one of the most alarming things you can see on a Windows PC \u2014 your screen suddenly turns blue, displays a stop code, and your computer restarts. It looks catastrophic, but the good news is that most BSODs are fixable, and Windows usually tells you exactly what went wrong if you know where to look. This guide walks through reading the error, the most common causes, and step-by-step fixes for Windows 10 and 11.
Table of Contents
ToggleWhat Causes a Blue Screen of Death?
A BSOD happens when Windows hits a critical error it can’t safely recover from, so it stops everything to prevent further damage \u2014 like data corruption or hardware damage. It’s officially called a “Stop Error,” and Microsoft maintains its own official troubleshooting resource for stop code errors, worth bookmarking alongside this guide.” Windows 11 briefly displayed this screen in black during early builds before Microsoft reverted to the classic blue. Either color means the same thing: something serious enough to justify a hard stop.
How to Read Your Stop Code
Before fixing anything, look at the stop code on the blue screen \u2014 it’s the key to diagnosing the actual cause. It usually appears near the bottom as a code in ALL_CAPS_WITH_UNDERSCORES, sometimes alongside a QR code you can scan for more information. Common stop codes and what they usually mean:
- IRQL_NOT_LESS_OR_EQUAL \u2014 usually a faulty or incompatible driver
- KERNEL_SECURITY_CHECK_FAILURE \u2014 often a driver conflict or corrupted system file
- PAGE_FAULT_IN_NONPAGED_AREA \u2014 typically a RAM problem or corrupted driver
- SYSTEM_SERVICE_EXCEPTION \u2014 caused by a buggy driver or corrupted system file
- CRITICAL_PROCESS_DIED \u2014 a critical system process stopped, often from corrupted files or bad drivers
- UNMOUNTABLE_BOOT_VOLUME \u2014 Windows can’t access the boot drive, often after a problematic update
Getting Into Safe Mode First
If your PC crashes repeatedly and won’t boot normally, start in Safe Mode so you can actually apply fixes:
- If Windows boots enough to reach the sign-in screen: hold Shift and click Restart, then go to Troubleshoot > Advanced options > Startup Settings > Restart, and press F5 for Safe Mode with Networking.
- If Windows won’t boot at all: force shut down 3 times in a row (hold the power button until it turns off, then power on again). This triggers Windows’ Automatic Repair environment, from which you can reach the same Troubleshoot menu.

Fix 1: Update or Roll Back Drivers (Most Common Cause)
Faulty or outdated drivers cause the majority of BSODs, especially graphics drivers, network adapters, and storage controllers.
- Open Device Manager (right-click Start > Device Manager)
- Look for devices with a yellow warning icon \u2014 these have driver problems
- Right-click the device > Update driver > Search automatically
- If the BSOD started right after a driver update, instead right-click the device > Properties > Driver tab > Roll Back Driver
Fix 2: Run a Memory Diagnostic
Bad RAM is a common BSOD culprit, and it often shows up as different stop codes each time since the corrupted data lands in different memory locations.
- Press Windows key + R, type
mdsched.exe, and press Enter - Click Restart now and check for problems
- Your PC restarts and tests your RAM automatically, then shows results after logging back in
- If errors are found, try removing and testing one RAM stick at a time to identify the faulty one

Fix 3: Check Your Disk and System Files
Corrupted system files or a failing drive can both trigger crashes. Run these from an admin Command Prompt:
sfc /scannow\u2014 scans for and repairs corrupted Windows system filesDISM /Online /Cleanup-Image /RestoreHealth\u2014 repairs the Windows system image, useful if SFC alone can’t fix the problemchkdsk C: /f /r\u2014 checks your drive for bad sectors and file system errors (requires a restart)
If you’re also seeing high disk usage alongside crashes, our 100% disk usage guide covers that separately.
Fix 4: Uninstall a Recent Windows Update
Microsoft occasionally ships updates that break specific hardware configurations \u2014 this has happened multiple times in 2026 alone. If your BSODs started right after Windows updated, the update itself is a likely suspect.
- Go to Settings > Windows Update > Update history > Uninstall updates
- Find the most recent update and click Uninstall
- This won’t affect your personal files \u2014 it only removes that specific update
- Check Windows Update afterward; Microsoft usually ships a fix in a following update once an issue is confirmed
Fix 5: Check for Overheating
CPUs and GPUs have thermal protection that can force a crash rather than risk physical damage when they run too hot. If your BSODs happen during gaming or heavy tasks specifically (rather than at random), overheating is worth ruling out \u2014 check that vents aren’t blocked, fans are spinning, and consider reapplying thermal paste on an older PC.
Fix Operating System Not Found
Solve another serious boot error.
When to Consider a Reinstall
If you’ve worked through the fixes above and BSODs continue, it may point to failing hardware (especially a dying hard drive or RAM) or a deeper system corruption that needs a clean Windows reinstall. At that point, back up your files first, then consider a repair install or a fresh installation of Windows rather than continuing to chase individual stop codes.
Preventing Future BSODs
Once you’re past the current crash, a little maintenance goes a long way:
- Keep Windows and drivers updated, but don’t install updates the moment they drop \u2014 waiting a few days lets known issues surface first
- Run periodic
sfc /scannowchecks, especially after a rough shutdown - Keep an eye on drive health and free space
- If you’re also dealing with general sluggishness, see our guide to fixing a slow computer
→ READ NEXTWindows Data Recovery TechniquesRecover files after a crash.
Related Troubleshooting Guides
Frequently Asked Questions
Is a Blue Screen of Death dangerous to my files?Not directly \u2014 BSOD exists specifically to stop your PC before a critical error causes real damage. The risk is mostly from the sudden restart itself if you had unsaved work open.
Why do I get a different stop code every time?
This is common with RAM problems and failing drives \u2014 the corrupted data ends up in a different place each time, producing a different-looking crash with the same root cause. Do I need to reinstall Windows to fix a BSOD?
Usually not. Most BSODs trace back to a driver, a bad update, or a system file issue \u2014 all fixable without a reinstall. A clean install is really a last resort after ruling out hardware and software causes. My PC won’t boot at all after a BSOD \u2014 what now?
Force shut down three times in a row to trigger Windows’ Automatic Repair environment, then use the Troubleshoot menu to reach Safe Mode or System Restore.



