BSOD Windows 11: How to Fix Blue Screen of Death Errors (All Versions Including Windows 8 & Vista)
Fix BSOD on Windows 11, 8, and Vista with expert step-by-step commands, driver fixes, memory tests, and registry repairs. Stop crash loops fast.
- Root Cause 1: Faulty or outdated drivers (especially GPU, NIC, and storage drivers) are the #1 cause of BSODs across Windows 11, Windows 8, and Windows Vista — stop codes like PAGE_FAULT_IN_NONPAGED_AREA and DRIVER_IRQL_NOT_LESS_OR_EQUAL almost always point here.
- Root Cause 2: Corrupt system files, bad RAM, or a failing hard drive/SSD trigger stop codes like CRITICAL_PROCESS_DIED, MEMORY_MANAGEMENT, and NTFS_FILE_SYSTEM — requiring SFC, DISM, MemTest86, or CHKDSK.
- Quick Fix Summary: Boot into Safe Mode → run 'sfc /scannow' and 'DISM /Online /Cleanup-Image /RestoreHealth' → roll back or update suspect drivers → run Windows Memory Diagnostic → check Event Viewer for the faulting module → if all else fails, perform an in-place upgrade repair.
| Method | When to Use | Time | Risk |
|---|---|---|---|
| SFC /scannow + DISM | Corrupted system files, CRITICAL_PROCESS_DIED, random BSODs | 10–30 min | Low |
| Driver Rollback / Update | DRIVER_IRQL, PAGE_FAULT, SYSTEM_THREAD_EXCEPTION after hardware change | 5–15 min | Low |
| Windows Memory Diagnostic / MemTest86 | MEMORY_MANAGEMENT, WHEA_UNCORRECTABLE_ERROR, random BSODs | 30 min – 8 hrs | None |
| CHKDSK /f /r | NTFS_FILE_SYSTEM, BAD_POOL_HEADER on HDD/SSD | 1–4 hrs | Low (data safe) |
| System Restore | BSOD started after recent update or software install | 20–40 min | Medium (reverses changes) |
| Startup Repair / Bootrec | BSOD loop preventing Windows from booting at all | 15–30 min | Low |
| In-place Upgrade Repair (Windows 11) | Persistent BSODs after all other steps fail, no data loss desired | 1–2 hrs | Low |
| Clean Install | Unrecoverable corruption, repeated BSODs after all fixes | 2–4 hrs | High (data loss) |
Understanding the BSOD Error
A Blue Screen of Death (BSOD) — officially called a Stop Error — occurs when Windows encounters a fatal system error it cannot safely recover from. The system halts to prevent data corruption or hardware damage. On Windows 11, BSODs display a sad face emoji and a QR code. On Windows 8, you see a simpler sad face. On Windows Vista, the classic blue-on-white text format appears.
Common BSOD stop codes you may encounter include:
CRITICAL_PROCESS_DIED(0x000000EF)PAGE_FAULT_IN_NONPAGED_AREA(0x00000050)DRIVER_IRQL_NOT_LESS_OR_EQUAL(0x000000D1)SYSTEM_THREAD_EXCEPTION_NOT_HANDLED(0x0000007E)MEMORY_MANAGEMENT(0x0000001A)NTFS_FILE_SYSTEM(0x00000024)WHEA_UNCORRECTABLE_ERROR(0x00000124)BAD_POOL_HEADER(0x00000019)KERNEL_SECURITY_CHECK_FAILURE(0x00000139)
Step 1: Identify the Exact Stop Code and Faulting Module
Before fixing anything, you need to know what crashed and why.
1a. Read the BSOD screen directly.
On Windows 11/8, the stop code is shown at the bottom of the blue screen (e.g., DRIVER_IRQL_NOT_LESS_OR_EQUAL). On Vista, you'll see a hex code like 0x000000D1.
1b. Analyze the memory dump file.
Windows saves crash dumps at C:\Windows\Minidump\. Use the free tool WinDbg (Windows Debugger) or WhoCrashed to analyze them:
- Open WinDbg Preview from the Microsoft Store
- Go to File > Open Dump File > select the
.dmpfile - Type
!analyze -vin the command window - Look for
IMAGE_NAME:(the faulting driver, e.g.,nvlddmkm.sys= NVIDIA GPU driver)
1c. Check Event Viewer.
Press Win + X → Event Viewer → Windows Logs → System. Filter for Critical and Error events around the crash timestamp. Look for Event ID 41 (Kernel-Power — unexpected shutdown) or Event ID 1001 (BugCheck).
Step 2: Boot Into Safe Mode
If your PC BSODs before Windows fully loads, you must enter Safe Mode:
Windows 11 / Windows 8:
- Hold
Shiftand click Restart, or boot from Windows installation media - Go to Troubleshoot → Advanced Options → Startup Settings → Restart
- Press
4orF4to boot into Safe Mode (or5/F5for Safe Mode with Networking)
Windows Vista:
- Tap
F8repeatedly during boot - Select
Safe ModeorSafe Mode with Networking
Step 3: Repair System Files with SFC and DISM
Corrupted Windows system files are a leading BSOD cause. Run these commands from an elevated Command Prompt (Run as Administrator):
sfc /scannow
Wait for the scan to complete. If it reports Windows Resource Protection found corrupt files but was unable to fix some of them, run DISM next (Windows 10/11 only):
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
After DISM completes, re-run sfc /scannow to confirm all files are repaired. Restart your PC after completion.
Step 4: Update or Roll Back Drivers
Driver-related stop codes (DRIVER_IRQL_NOT_LESS_OR_EQUAL, PAGE_FAULT_IN_NONPAGED_AREA, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED) almost always point to a specific .sys file. The WinDbg !analyze -v output will name it.
To roll back a driver:
- Press
Win + X→ Device Manager - Locate the device (e.g., Display Adapters → your GPU)
- Right-click → Properties → Driver tab → Roll Back Driver
To update a driver:
- Visit the manufacturer's website (NVIDIA, AMD, Intel, Realtek, etc.)
- Download the latest driver for your OS version
- Uninstall the old driver first using DDU (Display Driver Uninstaller) in Safe Mode for GPU drivers
- Install the new driver and restart
To force-uninstall a problematic driver via command line:
pnputil /delete-driver oem12.inf /uninstall /force
(Replace oem12.inf with the INF file name found in Device Manager → Driver Details)
Step 5: Test Your RAM
Memory errors cause erratic BSODs. Use the built-in Windows Memory Diagnostic:
- Press
Win + R→ typemdsched.exe→ press Enter - Choose
Restart now and check for problems - Windows will run the test on next boot and report results
For a deeper test, download MemTest86 (free, bootable USB). Run it for at least 2 full passes (overnight recommended). Any errors = faulty RAM that must be replaced.
If you have multiple RAM sticks, try removing them one at a time to isolate the bad module.
Step 6: Check the Hard Drive / SSD
Stop codes like NTFS_FILE_SYSTEM, BAD_POOL_HEADER, or INACCESSIBLE_BOOT_DEVICE can indicate storage issues.
Run CHKDSK from an elevated Command Prompt:
chkdsk C: /f /r /x
(You'll be prompted to schedule it on next restart — type Y and restart)
For SSD health, check with manufacturer tools (Samsung Magician, Crucial Storage Executive) or use:
wmic diskdrive get status
For a more detailed S.M.A.R.T. report, download CrystalDiskInfo (free). Any Caution or Bad status = replace the drive.
Step 7: Repair the Boot Record (If PC Won't Boot)
If Windows won't load at all due to a BSOD loop, boot from Windows installation media and open Command Prompt via Repair Your Computer:
bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd
Restart after each command succeeds. If bootrec /fixboot returns Access is denied, first run:
diskpart
list disk
select disk 0
list partition
select partition 1
assign letter=G
exit
bcdboot C:\Windows /s G: /f ALL
Step 8: Perform a Windows 11 In-Place Upgrade Repair
If all previous steps fail on Windows 11, an in-place upgrade repair reinstalls Windows without deleting your files or applications:
- Download the Windows 11 Installation Assistant from Microsoft's official site
- Run it and choose
Upgrade this PC now - On the
Choose what to keepscreen, selectKeep personal files and apps - Complete the upgrade — this replaces all system files
This resolves deep OS corruption that SFC/DISM cannot fix.
Windows Vista and Windows 8 Specific Notes
Windows Vista reached end of life in April 2017. BSODs on Vista often stem from incompatible drivers for newer hardware, lack of security patches, or simply aging hardware. Microsoft no longer provides updates. Your best path is upgrading to a supported OS. If you must maintain Vista:
- Use Driver Verifier (
verifier.exe) to isolate faulty drivers - Run
sfc /scannowfrom Recovery Console or DVD boot - Keep Vista on isolated hardware only
Windows 8 (8.0) reached end of life in January 2016; Windows 8.1 ended support in January 2023. Windows 8 BSODs are most commonly caused by driver incompatibilities with 8.1 updates or UEFI/Secure Boot misconfigurations. Always upgrade to Windows 8.1 minimum (free upgrade), then to Windows 10 or 11 if hardware supports it.
Frequently Asked Questions
# ============================================================
# BSOD Diagnostic & Repair Script for Windows 11 / 10 / 8
# Run as Administrator in PowerShell or Command Prompt
# ============================================================
# --- 1. Check and repair system files ---
Write-Host "[1/7] Running System File Checker..." -ForegroundColor Cyan
sfc /scannow
# --- 2. DISM repair (Windows 10/11 only) ---
Write-Host "[2/7] Running DISM RestoreHealth..." -ForegroundColor Cyan
DISM /Online /Cleanup-Image /RestoreHealth
# --- 3. Re-run SFC after DISM ---
Write-Host "[3/7] Re-running SFC post-DISM..." -ForegroundColor Cyan
sfc /scannow
# --- 4. Schedule CHKDSK on next reboot ---
Write-Host "[4/7] Scheduling CHKDSK on C: for next reboot..." -ForegroundColor Cyan
echo Y | chkdsk C: /f /r /x
# --- 5. List recent crash dump files ---
Write-Host "[5/7] Recent minidump files (crash logs):" -ForegroundColor Cyan
Get-ChildItem "C:\Windows\Minidump" -ErrorAction SilentlyContinue | Sort-Object LastWriteTime -Descending | Select-Object -First 10 | Format-Table Name, LastWriteTime, Length
# --- 6. Export last 20 critical/error events from System log ---
Write-Host "[6/7] Exporting recent critical System events..." -ForegroundColor Cyan
Get-WinEvent -LogName System -MaxEvents 200 | Where-Object { $_.LevelDisplayName -in @('Critical','Error') } | Select-Object -First 20 | Format-List TimeCreated, Id, Message | Out-File "$env:USERPROFILE\Desktop\BSOD_Events.txt"
Write-Host "Events saved to Desktop\BSOD_Events.txt" -ForegroundColor Green
# --- 7. List drivers sorted by date (newest first, to spot recently installed drivers) ---
Write-Host "[7/7] Recently installed drivers:" -ForegroundColor Cyan
Get-WmiObject Win32_PnPSignedDriver | Select-Object DeviceName, DriverVersion, DriverDate, InfName | Sort-Object DriverDate -Descending | Select-Object -First 20 | Format-Table -AutoSize
# --- Optional: Run Windows Memory Diagnostic ---
# Uncomment the line below to schedule a RAM test on next reboot
# mdsched.exe
# --- Optional: Enable verbose BSOD minidumps (Small Memory Dump 256 KB) ---
# reg add "HKLM\SYSTEM\CurrentControlSet\Control\CrashControl" /v CrashDumpEnabled /t REG_DWORD /d 3 /f
# reg add "HKLM\SYSTEM\CurrentControlSet\Control\CrashControl" /v MinidumpDir /t REG_EXPAND_SZ /d "%%SystemRoot%%\Minidump" /f
Write-Host "
Diagnostic complete. Review BSOD_Events.txt on your Desktop." -ForegroundColor Yellow
Write-Host "If CHKDSK was scheduled, restart your PC now to run the disk check." -ForegroundColor YellowError Medic Editorial
The Error Medic Editorial team consists of senior DevOps engineers, Windows SREs, and system administrators with 10+ years of experience diagnosing and resolving critical OS failures across enterprise and consumer environments. Our guides are tested on real hardware and virtual machines running Windows 11, Windows 10, Windows 8.1, and legacy systems including Windows Vista. We specialize in turning cryptic stop codes into clear, actionable repair procedures.
Sources
- https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-code-reference2
- https://support.microsoft.com/en-us/windows/blue-screen-errors-in-windows-11-5c6b5c60-7de9-4b94-9ae2-a0f8c7c3e4e4
- https://learn.microsoft.com/en-us/windows-hardware/drivers/devtest/driver-verifier
- https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/sfc
- https://answers.microsoft.com/en-us/windows/forum/all/how-to-read-a-bsod-minidump-file/f5674b39-a438-4eda-9c74-4ac2d5b2f5e1
- https://stackoverflow.com/questions/tagged/windows-error-reporting