Blue Screen of Death Windows 10: Complete Troubleshooting Guide (BSOD Fix)
Fix Blue Screen of Death on Windows 10 caused by driver issues, memory faults, or updates. Step-by-step CMD commands and repair tools included.
- The most common BSOD causes on Windows 10 are corrupt or incompatible drivers, faulty RAM, failing hard drives, and malicious software — each producing a specific stop code like IRQL_NOT_LESS_OR_EQUAL, MEMORY_MANAGEMENT, or CRITICAL_PROCESS_DIED.
- Windows updates can introduce driver conflicts or corrupt system files, triggering BSODs immediately after installation — rolling back the update or the specific driver resolves this in most cases.
- Quick fixes include running 'sfc /scannow' and 'DISM /Online /Cleanup-Image /RestoreHealth' in an elevated Command Prompt, booting into Safe Mode to isolate the problem, and using Windows Memory Diagnostic to test RAM integrity.
- ASUS-specific BSODs are frequently caused by ASUS Armoury Crate, AI Suite, or ATK drivers conflicting with Windows kernel — uninstalling or updating these resolves the issue.
- If repeated BSODs occur, enable kernel crash dumps, analyze them with WinDbg or WhoCrashed, and identify the exact faulting module before applying a targeted fix.
| Method | When to Use | Time | Risk |
|---|---|---|---|
| SFC + DISM (CMD) | Corrupt system files after update or malware | 10–30 min | Low |
| Driver Rollback / Uninstall | BSOD started after driver or Windows update | 5–15 min | Low |
| Windows Memory Diagnostic | Random BSODs, MEMORY_MANAGEMENT stop code | 15–60 min | None |
| Startup Repair (WinRE) | System won't boot past BSOD | 10–20 min | Low |
| System Restore | BSOD appeared after recent software change | 20–40 min | Medium |
| Update Rollback (Settings) | BSOD immediately after Windows Update | 10–20 min | Low |
| Safe Mode + Clean Boot | Isolating software or service causing BSOD | 15–30 min | Low |
| WinDbg Crash Dump Analysis | Recurring BSOD, need exact root cause | 30–90 min | None |
| CHKDSK Disk Scan | UNEXPECTED_STORE_EXCEPTION or disk-related stops | 20–120 min | Low |
| Windows Reset / Reinstall | All else fails, persistent hardware-unrelated BSOD | 60–180 min | High |
Understanding the Blue Screen of Death on Windows 10
A Blue Screen of Death (BSOD) — officially called a Stop Error or Bug Check — occurs when Windows 10 detects a critical failure it cannot recover from safely. The system halts to prevent data corruption or hardware damage, writing a memory dump file before restarting. Every BSOD displays a stop code (e.g., CRITICAL_PROCESS_DIED, IRQL_NOT_LESS_OR_EQUAL) that points directly to the failure category.
The dump files are saved to C:\Windows\Minidump\ or as a full memory dump at C:\Windows\MEMORY.DMP. Analyzing these is the fastest path to a real fix.
Common Stop Codes and Their Meanings
| Stop Code | Primary Cause |
|---|---|
IRQL_NOT_LESS_OR_EQUAL |
Driver accessing invalid memory address |
MEMORY_MANAGEMENT |
Faulty RAM or corrupt memory subsystem |
CRITICAL_PROCESS_DIED |
Essential Windows process terminated unexpectedly |
KERNEL_SECURITY_CHECK_FAILURE |
Kernel data structure corruption, often drivers |
SYSTEM_SERVICE_EXCEPTION |
System service crashed, often GPU/network drivers |
UNEXPECTED_STORE_EXCEPTION |
Storage device (SSD/HDD) error or file system corruption |
PAGE_FAULT_IN_NONPAGED_AREA |
Invalid memory reference, bad RAM or driver |
Step 1: Identify the Stop Code and Faulting Module
The first step is always to capture the exact stop code. If the machine reboots too quickly:
- Go to Settings → System → About → Advanced system settings.
- Under Startup and Recovery, click Settings.
- Uncheck Automatically restart so you can read the stop code.
- Check Write debugging information and set it to Small memory dump (256 KB).
Then use WhoCrashed (free tool) or WinDbg from the Microsoft Store to open the .dmp file. In WinDbg, run:
!analyze -v
This outputs the faulting driver, module name, and memory address — giving you a precise target.
Step 2: Fix Corrupt System Files (SFC + DISM)
This resolves BSODs caused by corrupt Windows system files, especially after a failed update.
Open Command Prompt as Administrator (Win + X → Windows Terminal (Admin) or search cmd, right-click → Run as administrator).
sfc /scannow
Wait for 100% completion. If it reports "Windows Resource Protection found corrupt files but was unable to fix some of them," run DISM first:
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
After DISM completes, re-run sfc /scannow. Restart and check if the BSOD recurs.
Step 3: Roll Back a Problematic Driver or Windows Update
Rolling back a driver:
- Press
Win + X→ Device Manager. - Expand the relevant category (Display adapters, Network adapters, etc.).
- Right-click the device → Properties → Driver tab → Roll Back Driver.
If Roll Back is greyed out, the previous driver version was not saved. In this case, download an older driver version from the manufacturer's website and install it manually.
Rolling back a Windows Update:
- Go to Settings → Update & Security → Windows Update → View update history → Uninstall updates.
- Sort by Installed On descending.
- Right-click the most recent update → Uninstall.
Alternatively, via CMD:
wusa /uninstall /kb:XXXXXXX /quiet /norestart
Replace XXXXXXX with the KB number of the problematic update.
Step 4: Test RAM with Windows Memory Diagnostic
For MEMORY_MANAGEMENT or random BSODs, bad RAM is a prime suspect.
- Press
Win + R, typemdsched.exe, press Enter. - Choose Restart now and check for problems.
- Windows boots into the diagnostic tool and runs two passes.
- After reboot, results appear in Event Viewer under Windows Logs → System, source
MemoryDiagnostics-Results.
For deeper testing, use MemTest86 (bootable USB) — run for at least 2 passes (4+ recommended).
If errors are found, test each RAM stick individually by removing sticks one at a time to isolate the faulty module.
Step 5: Scan the Disk for Errors (UNEXPECTED_STORE_EXCEPTION)
Storage errors cause UNEXPECTED_STORE_EXCEPTION and PAGE_FAULT_IN_NONPAGED_AREA. Run:
chkdsk C: /f /r /x
You'll be prompted to schedule a check on next restart. Type Y and reboot. The scan can take 30–120 minutes depending on drive size.
For SSDs, also check drive health:
wmic diskdrive get status
Or use CrystalDiskInfo for detailed S.M.A.R.T. data.
Step 6: Boot into Safe Mode to Isolate the Problem
If Windows can start:
- Hold
Shiftwhile clicking Restart. - Go to Troubleshoot → Advanced options → Startup Settings → Restart.
- Press 4 for Safe Mode or 5 for Safe Mode with Networking.
If Windows cannot start (constant BSOD loop):
- Boot from Windows 10 installation media (USB/DVD).
- Choose Repair your computer → Troubleshoot → Advanced options → Startup Settings.
In Safe Mode, only essential drivers load. If the BSOD disappears in Safe Mode, a third-party driver or startup program is the culprit. Use msconfig to perform a clean boot and re-enable services one by one to identify the offender.
Step 7: ASUS-Specific BSOD Fixes
ASUS laptops and desktops (especially ROG, TUF, and VivoBook series) frequently encounter BSODs from:
- Armoury Crate and Aura Sync drivers
- AI Suite 3 interfering with power management
- ATK Package (keyboard hotkey driver) conflicts
- MyASUS application drivers
Fix: Uninstall ASUS software from Settings → Apps, then run the Armoury Crate Uninstall Tool from the ASUS support page. Reboot. Reinstall only the components you need from the latest versions on the ASUS support site.
Also update BIOS: many ASUS BSOD issues are resolved via BIOS firmware updates available at support.asus.com.
Step 8: Use Startup Repair (When Windows Won't Boot)
Boot from Windows 10 installation media:
- Troubleshoot → Advanced options → Startup Repair
Windows automatically scans for and attempts to fix boot-related issues. If Startup Repair fails, use:
bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd
Run these from the Command Prompt in Windows Recovery Environment (WinRE).
Step 9: Last Resort — Windows Reset or Reinstall
If all diagnostic steps fail and the BSOD persists:
- Go to Settings → Update & Security → Recovery.
- Under Reset this PC, click Get started.
- Choose Keep my files (reinstalls Windows, keeps personal data) or Remove everything (clean slate).
For a complete reinstall, download the Windows 10 Media Creation Tool from Microsoft, create a bootable USB, and perform a clean installation.
Frequently Asked Questions
:: ============================================================
:: Windows 10 BSOD Diagnostic and Fix Commands
:: Run all commands in an elevated Command Prompt (Admin)
:: ============================================================
:: --- STEP 1: Repair corrupt system files ---
sfc /scannow
:: --- STEP 2: Repair Windows image with DISM ---
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
:: Re-run SFC after DISM completes
sfc /scannow
:: --- STEP 3: Scan disk for errors (schedule on reboot) ---
chkdsk C: /f /r /x
:: Type Y when prompted and restart
:: --- STEP 4: Check basic disk health via WMI ---
wmic diskdrive get model,status,size
:: --- STEP 5: View recent BSOD stop codes from Event Log ---
wevtutil qe System /q:"*[System[Provider[@Name='Microsoft-Windows-WER-SystemErrorReporting']]]" /f:text /c:10
:: --- STEP 6: List all installed drivers with date (find recent ones) ---
driverquery /v /fo csv | sort
:: --- STEP 7: Export driver list to a file for review ---
driverquery /v /fo csv > C:\drivers_list.csv
:: --- STEP 8: Check Windows Update history for recent updates ---
wmic qfe list brief /format:table
:: --- STEP 9: Uninstall a specific Windows Update by KB number ---
:: Replace XXXXXXX with the actual KB number from update history
wusa /uninstall /kb:XXXXXXX /quiet /norestart
:: --- STEP 10: Enable minidump creation for future BSODs ---
reg add "HKLM\SYSTEM\CurrentControlSet\Control\CrashControl" /v CrashDumpEnabled /t REG_DWORD /d 3 /f
reg add "HKLM\SYSTEM\CurrentControlSet\Control\CrashControl" /v AutoReboot /t REG_DWORD /d 0 /f
reg add "HKLM\SYSTEM\CurrentControlSet\Control\CrashControl" /v MinidumpsCount /t REG_DWORD /d 50 /f
:: --- STEP 11: View minidump file list ---
dir C:\Windows\Minidump\ /od
:: --- STEP 12: Run Windows Memory Diagnostic ---
mdsched.exe
:: (Will prompt to restart and run memory test)
:: --- STEP 13: Fix boot records if Windows won't start (run from WinRE CMD) ---
bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd
:: --- STEP 14: Check for startup items causing conflicts ---
msconfig
:: Navigate to Services tab -> Hide all Microsoft services -> Disable all -> Restart
:: --- STEP 15: Run System File Checker in offline mode (from WinRE) ---
:: Replace D: with the drive letter of your Windows installation
sfc /scannow /offbootdir=D:\ /offwindir=D:\Windows
:: ============================================================
:: PowerShell: Analyze recent critical errors in Event Log
:: ============================================================
:: Run in elevated PowerShell:
:: Get-WinEvent -FilterHashtable @{LogName='System'; Level=1,2} -MaxEvents 50 | Format-List TimeCreated, Id, MessageError Medic Editorial
The Error Medic Editorial team is composed of senior DevOps engineers, SREs, and Windows system administrators with over a decade of experience diagnosing and resolving operating system failures across enterprise and consumer environments. We specialize in translating complex kernel-level error analysis into actionable, step-by-step troubleshooting guides that both power users and IT professionals can follow. Every guide is tested against real-world failure scenarios before publication.
Sources
- https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-code-reference2
- https://support.microsoft.com/en-us/windows/troubleshoot-blue-screen-errors-5c62726c-6489-52da-a372-3831d059a888
- https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/using-the-analyze-extension
- https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/sfc
- https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-recovery-environment--windows-re--technical-reference
- https://stackoverflow.com/questions/tagged/bsod
- https://answers.microsoft.com/en-us/windows/forum/all/blue-screen-of-death-windows-10/9e5e8b44-8e44-48a5-9eff-e3a55c1f4c5a