TL;DR — Quick Summary
Fix Windows Blue Screen of Death errors by identifying the stop code, analyzing crash dumps, updating drivers, and running SFC and DISM system repair tools.
Understanding the Blue Screen of Death
A BSOD means Windows hit an unrecoverable error. Don’t panic — the stop code tells you exactly what went wrong.
Step-by-Step Diagnosis
1. Identify the Stop Code
The blue screen shows a code like IRQL_NOT_LESS_OR_EQUAL. Write it down.
2. Boot into Safe Mode
If Windows won’t boot normally:
- Power on, wait for Windows logo, hold power button to force shutdown.
- Repeat 3 times — Windows enters Automatic Repair.
- Choose Troubleshoot > Advanced Options > Startup Settings > Restart.
- Press 4 or F4 for Safe Mode.
3. Run System Repair Tools
sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth
chkdsk C: /f /rMost Common BSOD Stop Codes
| Stop Code | Common Cause | Fix |
|---|---|---|
| IRQL_NOT_LESS_OR_EQUAL | Faulty driver accessing wrong memory | Update/roll back the driver shown in crash dump |
| KERNEL_DATA_INPAGE_ERROR | Bad disk sector or failing HDD/SSD | Run chkdsk /f /r; replace drive if SMART shows errors |
| PAGE_FAULT_IN_NONPAGED_AREA | Bad RAM or corrupt driver | Run Memory Diagnostic; test with MemTest86 |
| SYSTEM_SERVICE_EXCEPTION | Antivirus conflict or corrupt system file | SFC + DISM; disable third-party antivirus |
| DRIVER_POWER_STATE_FAILURE | Device driver can’t handle sleep/wake | Update chipset + GPU drivers; disable fast startup |
| CRITICAL_PROCESS_DIED | Essential Windows process crashed | SFC + DISM; if persistent, in-place upgrade repair |
| UNEXPECTED_STORE_EXCEPTION | Storage driver or fast startup issue | Disable fast startup; update storage drivers |
| KMODE_EXCEPTION_NOT_HANDLED | Hardware or driver problem | Identify driver from dump; replace if hardware |
| WHEA_UNCORRECTABLE_ERROR | Hardware failure (CPU, RAM, or motherboard) | Check temperatures; test RAM; may need hardware replacement |
| DPC_WATCHDOG_VIOLATION | SSD firmware or storage controller | Update SSD firmware and AHCI/NVMe drivers |
Diagnostic Tools
| Tool | Purpose | How to Run |
|---|---|---|
| SFC | Scan/fix corrupt system files | sfc /scannow (admin CMD) |
| DISM | Repair Windows image | DISM /Online /Cleanup-Image /RestoreHealth |
| chkdsk | Fix disk errors | chkdsk C: /f /r (reboot required) |
| WinDbg | Analyze crash dump files | Open .dmp from C:\Windows\Minidump\ |
| Memory Diagnostic | Test RAM | mdsched.exe |
| MemTest86 | Thorough RAM test (boots from USB) | Download and boot |
| Event Viewer | Check system logs around crash time | eventvwr.msc > Windows Logs > System |
| Driver Verifier | Stress-test drivers to find faults | verifier (use carefully, can cause more BSODs) |
Quick Fixes by Symptom
| Symptom | Most Likely Cause | Quick Fix |
|---|---|---|
| BSOD after Windows Update | Bad update | Uninstall recent update from Safe Mode |
| BSOD during gaming | GPU driver or overheating | Update GPU driver; check temps with HWMonitor |
| BSOD on boot every time | Corrupt boot files | Startup Repair or bootrec /fixmbr |
| BSOD after installing new RAM | Incompatible or bad DIMM | Remove new RAM; test sticks individually |
| BSOD after driver install | Bad driver | Roll back in Device Manager from Safe Mode |
| Random BSODs, different codes | Bad RAM | Run MemTest86 overnight |
Troubleshooting
| Problem | Solution |
|---|---|
| Can’t boot at all | Use Windows installation USB > Repair > Command Prompt |
| SFC finds errors but can’t fix | Run DISM first, then SFC again |
| BSOD persists after all fixes | In-place upgrade repair (keeps files and apps) |
| Need the crash dump but can’t find it | Check C:\Windows\Minidump\ or %SystemRoot%\MEMORY.DMP |
Summary
- Read the stop code — it’s your most valuable diagnostic clue.
- SFC + DISM + chkdsk fix most software-caused BSODs.
- Driver issues cause ~70% of BSODs — update or roll back.
- RAM failures cause random BSODs with different codes — test with MemTest86.