Error Medic

Blue Screen of Death Windows 10: Complete Troubleshooting Guide (BSOD Fix)

Fix Blue Screen of Death on Windows 10 with step-by-step CMD commands, driver fixes, and memory diagnostics. Covers IRQL, Critical Process Died & more.

Last updated:
Last verified:
2,099 words
Key Takeaways
  • Most Windows 10 BSODs are caused by faulty drivers, corrupt system files, bad RAM, or recent Windows updates that introduced incompatibilities.
  • Stop codes like IRQL_NOT_LESS_OR_EQUAL, CRITICAL_PROCESS_DIED, KERNEL_SECURITY_CHECK_FAILURE, MEMORY_MANAGEMENT, and SYSTEM_SERVICE_EXCEPTION each point to distinct root causes that can be diagnosed systematically.
  • Quick fix path: Boot into Safe Mode, run 'sfc /scannow' and 'DISM /Online /Cleanup-Image /RestoreHealth' in CMD as Administrator, then check Device Manager for driver issues and use Windows Memory Diagnostic for RAM faults.
  • ASUS-specific BSODs often trace back to ASUS-branded utility software (Armory Crate, AI Suite) or out-of-date BIOS/chipset drivers — uninstall or update these first.
  • If BSODs started after a Windows Update, use 'wusa /uninstall /kb:XXXXXXXX' or roll back via Settings > Update & Security > View Update History.
Fix Approaches Compared
MethodWhen to UseTimeRisk
sfc /scannow (System File Checker)Corrupt or missing Windows system files5-20 minLow
DISM RestoreHealthSFC cannot repair files; WinSxS store corrupted15-30 minLow
Driver Rollback / UpdateBSOD after driver or Windows Update install5-15 minLow-Medium
Windows Memory Diagnostic / MemTest86MEMORY_MANAGEMENT or random unexplained BSODs30-480 minLow
Uninstall Recent Windows UpdateBSOD immediately after cumulative update5-10 minLow
Startup Repair (WinRE)Cannot boot to desktop at all10-20 minLow
Clean Boot (msconfig)Isolate third-party software conflicts10-30 minLow
BIOS/UEFI Firmware UpdateASUS or other OEM-specific BSODs, chipset errors20-40 minMedium
Reset / Reinstall Windows 10All other methods failed; persistent BSODs60-180 minHigh (data loss risk)

Understanding the Blue Screen of Death on Windows 10

A Blue Screen of Death (BSOD), formally known as a Stop Error, occurs when Windows 10 encounters a critical failure from which it cannot safely recover. The OS halts all processes, dumps memory to a file (typically located at C:\Windows\Minidump\), and reboots. Each BSOD displays a stop code — a hexadecimal or named code that identifies the failure category.

Common stop codes you will encounter include:

  • IRQL_NOT_LESS_OR_EQUAL (0x0000000A) — A kernel-mode process or driver attempted to access a memory address at an improper IRQL (Interrupt Request Level). Almost always a driver bug.
  • CRITICAL_PROCESS_DIED (0x000000EF) — A critical Windows process (such as csrss.exe, wininit.exe, or smss.exe) unexpectedly terminated.
  • KERNEL_SECURITY_CHECK_FAILURE (0x00000139) — A kernel component violated a security check; often caused by incompatible or corrupt drivers.
  • MEMORY_MANAGEMENT (0x0000001A) — Serious memory management error; often hardware RAM failure or corrupt page file.
  • SYSTEM_SERVICE_EXCEPTION (0x0000003B) — An exception occurred while executing a system service routine; driver or system file corruption.
  • UNEXPECTED_STORE_EXCEPTION (0x00000154) — Storage device (HDD/SSD) failure or driver issue with the storage stack.
  • PAGE_FAULT_IN_NONPAGED_AREA (0x00000050) — System attempted to access a memory page that was not present; bad RAM or driver.

Step 1: Record the Stop Code and Find the Minidump

When a BSOD occurs, photograph or note the stop code displayed on the blue screen. Windows 10 shows it in plain English (e.g., "CRITICAL_PROCESS_DIED") along with a hex code.

After rebooting, open Event Viewer (eventvwr.msc) and navigate to: Windows Logs > System Filter by Event ID 41 (Kernel-Power, unexpected shutdown) and 1001 (BugCheck) to find BSOD logs.

Minidump files are stored at: C:\Windows\Minidump\

Use WinDbg (Windows Debugger from the Microsoft Store) or the free tool WhoCrashed to analyze .dmp files. WinDbg command to analyze a dump:

!analyze -v

Step 2: Boot into Safe Mode if You Cannot Reach the Desktop

If Windows keeps crashing at startup, access Windows Recovery Environment (WinRE):

  1. Force-shutdown your PC 3 times during the boot logo to trigger Automatic Repair mode.
  2. Go to: Troubleshoot > Advanced Options > Startup Settings > Restart
  3. Press F4 for Safe Mode or F5 for Safe Mode with Networking.

Alternatively, boot from a Windows 10 installation USB and choose Repair your computer.


Step 3: Run System File Checker and DISM

Open Command Prompt as Administrator and run:

sfc /scannow

This scans and repairs protected Windows system files. If it reports that it "found corrupt files but was unable to fix some of them," escalate to DISM:

DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

After DISM completes, re-run sfc /scannow and reboot.


Step 4: Check and Update Drivers

Drivers are the #1 cause of BSODs. After a Windows Update, older drivers may become incompatible.

To identify the faulty driver:

  • Open Device Manager (devmgmt.msc)
  • Look for devices with a yellow warning icon
  • Right-click > Properties > Driver tab

To roll back a driver:

  • Right-click device > Properties > Driver tab > Roll Back Driver

For IRQL_NOT_LESS_OR_EQUAL and KERNEL_SECURITY_CHECK_FAILURE, the culprit is often:

  • Network adapter drivers (especially Realtek, Killer Ethernet/WiFi)
  • GPU drivers (NVIDIA/AMD)
  • ASUS utility drivers (Armory Crate, AI Suite III)

Enable Driver Verifier (advanced) to catch misbehaving drivers:

verifier /standard /all

Warning: This will cause deliberate BSODs to identify the bad driver. Disable after testing:

verifier /reset

Step 5: Run Windows Memory Diagnostic for MEMORY_MANAGEMENT Errors

Press Win + R, type mdsched.exe, and press Enter. Choose Restart now and check for problems.

For deeper testing, download and run MemTest86 from a bootable USB — run at least 2 full passes (each pass takes 30-60+ minutes). Any errors indicate failing RAM. Try:

  1. Reseating RAM sticks (remove and firmly re-insert)
  2. Testing one stick at a time
  3. Replacing faulty sticks

Step 6: Check Storage Drives for UNEXPECTED_STORE_EXCEPTION

Run CHKDSK on your system drive:

chkdsk C: /f /r /x

Schedule it for next reboot if the drive is in use. Also check drive health with:

wmic diskdrive get status

or use CrystalDiskInfo (free tool) to read S.M.A.R.T. data.


Step 7: Uninstall Problematic Windows Updates

If BSODs started after a Windows Update:

  1. Go to Settings > Update & Security > Windows Update > View Update History > Uninstall Updates
  2. Or use CMD:
wusa /uninstall /kb:XXXXXXXXX

(Replace XXXXXXXXX with the KB number from Update History)

  1. To pause future updates temporarily:
reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU" /v NoAutoUpdate /t REG_DWORD /d 1 /f

Step 8: ASUS-Specific BSOD Fixes

ASUS systems running Armory Crate, AI Suite III, or GPU Tweak are prone to BSODs due to aggressive system-level access by these utilities.

  1. Uninstall Armory Crate via Settings > Apps
  2. Also remove the Armory Crate Service using the official ASUS Armoury Crate Uninstall Tool
  3. Update BIOS/UEFI from the ASUS support website for your specific model
  4. Update chipset drivers from AMD or Intel's official websites (not Windows Update)
  5. Update Realtek Audio/LAN drivers directly from ASUS support page

Step 9: Perform a Clean Boot to Isolate Software

msconfig

Go to the Services tab, check Hide all Microsoft services, then click Disable all. Go to the Startup tab and open Task Manager to disable all startup items. Reboot. If BSODs stop, re-enable services in batches to isolate the culprit.


Step 10: Last Resort — Reset Windows 10

If nothing works:

  1. Settings > Update & Security > Recovery > Reset this PC
  2. Choose Keep my files (reinstalls Windows, removes apps/drivers) or Remove everything (full clean install)

Alternatively, perform a clean install using the Windows 10 Media Creation Tool from Microsoft.

Frequently Asked Questions

bash
:: ============================================================
:: Windows 10 BSOD Diagnostic & Fix Commands
:: Run ALL commands in Command Prompt as Administrator
:: ============================================================

:: --- STEP 1: System File Checker ---
sfc /scannow

:: --- STEP 2: DISM Health Check & Repair ---
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

:: Re-run SFC after DISM
sfc /scannow

:: --- STEP 3: Check Disk for errors (schedule on next reboot) ---
chkdsk C: /f /r /x

:: --- STEP 4: Check drive status via WMI ---
wmic diskdrive get status, model, size

:: --- STEP 5: View recent BSOD events in Event Log ---
wevtutil qe System /q:"*[System[(EventID=41 or EventID=1001)]]" /f:text /c:10

:: --- STEP 6: List installed drivers and their status ---
driverquery /v /fo list | more

:: --- STEP 7: Enable Driver Verifier (use only for testing!) ---
:: WARNING: This will cause BSODs intentionally to catch bad drivers
:: Run this, reboot, trigger BSOD, then analyze dump and disable:
verifier /standard /all
:: To disable Driver Verifier after testing:
:: verifier /reset

:: --- STEP 8: Uninstall a specific Windows Update (replace KB number) ---
:: wusa /uninstall /kb:5034441

:: --- STEP 9: List installed updates to find the problematic KB ---
wmic qfe list brief /format:table

:: --- STEP 10: Clean Boot preparation (disable non-MS services) ---
:: Run msconfig, Services tab > Hide Microsoft services > Disable all
:: Then Startup tab > Open Task Manager > Disable all startup items
start msconfig

:: --- STEP 11: Check memory (launches Windows Memory Diagnostic) ---
start mdsched.exe

:: --- STEP 12: View minidump files for analysis ---
dir C:\Windows\Minidump\ /od

:: --- STEP 13: Export System info for offline analysis ---
msinfo32 /report C:\SystemInfo.txt

:: --- STEP 14: Reset Windows Update components (if update-related BSOD) ---
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start wuauserv
net start cryptSvc
net start bits
net start msiserver
echo Windows Update components reset successfully.

:: --- STEP 15: Check for malware with Windows Defender offline scan ---
"C:\Program Files\Windows Defender\MpCmdRun.exe" -Scan -ScanType 3
E

Error Medic Editorial

The Error Medic Editorial team is composed of senior DevOps engineers, SREs, and Microsoft-certified system administrators with 10+ years of experience diagnosing Windows OS failures, kernel panics, and enterprise system outages. We publish actionable, command-driven troubleshooting guides backed by official documentation and real-world incident analysis.

Sources

Related Articles in Windows 10 Blue Screen Of Death Windows

Explore More windows Guides