Why does my Windows 11 PC keep blue screening after a Windows Update?

Cumulative updates occasionally ship with driver compatibility issues or corrupt system files during installation. Go to Settings → Windows Update → Update History → Uninstall Updates and remove the most recent Cumulative Update. You can also run 'DISM /Online /Cleanup-Image /RestoreHealth' followed by 'sfc /scannow' in an elevated Command Prompt to repair any files damaged during the update process. Check Microsoft's known issues page for your specific KB number to see if a fix is already in progress.

What does the stop code DRIVER_IRQL_NOT_LESS_OR_EQUAL mean on Windows 11?

This stop code (0x000000D1) means a driver attempted to access a memory address at an improper IRQL (interrupt request level). The BSOD screen will usually name the offending .sys file (e.g., 'tcpip.sys' for networking drivers or 'nvlddmkm.sys' for NVIDIA GPUs). Fix it by rolling back or updating the named driver via Device Manager. If no driver is named, run Driver Verifier ('verifier /standard /all' in Safe Mode) to identify the culprit, then disable it with 'verifier /reset' after testing.

How do I fix a BSOD on Windows 8 when the PC won't boot at all?

On Windows 8 and 8.1, force-shutdown the PC three consecutive times to trigger the Automatic Repair environment. Then navigate to Troubleshoot → Advanced Options → Startup Settings → Restart and press 4 for Safe Mode. From Safe Mode, open Command Prompt as Administrator and run 'sfc /scannow'. If the boot loader is corrupt, boot from a Windows 8 installation USB and run 'bootrec /fixmbr', 'bootrec /fixboot', and 'bootrec /rebuildbcd' from the recovery Command Prompt.

Can a BSOD on Windows Vista be caused by antivirus software?

Yes. On Windows Vista, third-party antivirus drivers (especially older versions) that hook into the kernel at a low level frequently cause BSODs such as SYSTEM_SERVICE_EXCEPTION or PAGE_FAULT_IN_NONPAGED_AREA. Boot into Safe Mode (press F8 at startup), uninstall the antivirus application, and reboot normally to test. Vista also benefits from installing all available Service Packs and hotfixes, as Microsoft released numerous kernel stability patches post-launch. Check C:\Windows\Minidump for crash logs that identify the antivirus .sys file.

How do I prevent future BSODs on Windows 11?

Proactive steps include: (1) Keep Windows Update and all drivers current via Settings → Windows Update and Device Manager. (2) Enable automatic memory dumps under System Properties → Advanced → Startup and Recovery. (3) Monitor system temperatures with HWMonitor or HWiNFO — sustained CPU temps above 95°C or GPU above 90°C cause thermal BSODs. (4) Run 'chkdsk C: /f /r' quarterly to catch early disk issues. (5) Avoid beta or unsigned drivers. (6) After any hardware change, run Windows Memory Diagnostic immediately to rule out RAM issues.

BSOD Windows 11: How to Fix Blue Screen of Death Errors (Complete Guide)

Fix BSOD errors on Windows 11, 8, and Vista with step-by-step commands, driver rollbacks, memory tests, and registry repairs. Resolve stop codes fast.

Last updated: March 1, 2026

Last verified: March 1, 2026

1,948 words

Key Takeaways

Root Cause 1: Faulty, outdated, or incompatible device drivers are the #1 trigger for BSOD stop codes such as DRIVER_IRQL_NOT_LESS_OR_EQUAL (0x000000D1) and PAGE_FAULT_IN_NONPAGED_AREA (0x00000050).
Root Cause 2: Corrupted system files, bad RAM modules, overheating hardware, or incompatible Windows updates (especially cumulative updates on Windows 11 22H2/23H2) cause CRITICAL_PROCESS_DIED (0x000000EF) and SYSTEM_SERVICE_EXCEPTION (0x0000003B).
Quick Fix Summary: Boot into Safe Mode, run 'sfc /scannow' and DISM repair commands, update or roll back suspect drivers, run Windows Memory Diagnostic, and if needed perform a Startup Repair or clean-boot troubleshooting sequence.

Fix Approaches Compared
Method	When to Use	Time	Risk
SFC + DISM System File Repair	Corrupted OS files, random BSODs after update	10-30 min	Low
Driver Rollback / Update	BSOD after installing new hardware or Windows update	5-15 min	Low
Windows Memory Diagnostic	BSOD with MEMORY_MANAGEMENT (0x0000001A) or random crashes	30-60 min	None
Uninstall Recent Windows Update	BSOD started immediately after Patch Tuesday or cumulative update	10-20 min	Low
Startup Repair (WinRE)	Cannot boot into Windows at all; looping BSOD	15-40 min	Low
System Restore	BSOD started after a specific software or driver installation	20-45 min	Low-Medium
Reset This PC (Keep Files)	Persistent BSODs that survive all other fixes	1-3 hours	Medium
Clean Windows 11 Reinstall	Hardware confirmed good but OS is severely corrupted	2-4 hours	High (data loss)

Understanding the Blue Screen of Death on Windows 11

A Blue Screen of Death (BSOD) — also called a Stop Error — occurs when Windows encounters a critical system fault it cannot recover from safely. The OS halts all processes, writes a memory dump to disk, and displays a blue screen with a stop code. On Windows 11, the BSOD also shows a QR code and a sad-face emoji (:(), while Windows 8 introduced the modernized layout and Windows Vista used the classic wall-of-text format.

Common stop codes you will encounter include:

DRIVER_IRQL_NOT_LESS_OR_EQUAL (0x000000D1) — driver accessing restricted memory
PAGE_FAULT_IN_NONPAGED_AREA (0x00000050) — invalid memory address referenced
CRITICAL_PROCESS_DIED (0x000000EF) — critical OS process terminated unexpectedly
SYSTEM_SERVICE_EXCEPTION (0x0000003B) — unhandled exception in system service
MEMORY_MANAGEMENT (0x0000001A) — RAM corruption or misconfiguration
KERNEL_SECURITY_CHECK_FAILURE (0x00000139) — data structure integrity violation
WHEA_UNCORRECTABLE_ERROR (0x00000124) — hardware-level uncorrectable error

Step 1: Record the Stop Code and Boot into Safe Mode

When the BSOD appears, photograph the screen or note:

The stop code (e.g., CRITICAL_PROCESS_DIED)
The failing module listed below the QR code (e.g., nvlddmkm.sys = NVIDIA driver)

If Windows keeps rebooting into BSOD:

Force-shutdown the PC three times to trigger Automatic Repair.
Go to Advanced Options → Startup Settings → Restart → Press 4 to boot Safe Mode.
Alternatively, press F8 during boot on Windows Vista/8 systems.

Step 2: Analyze the Memory Dump

Windows writes crash dumps to C:\Windows\Minidump\. Open **Event Viewer** (eventvwr.msc) → Windows Logs → System and filter for Error events at the crash timestamp.

For deeper analysis, download WinDbg from the Microsoft Store and run:

!analyze -v

This outputs the faulting driver, memory address, and call stack — critical for identifying the root cause.

Step 3: Repair Corrupted System Files with SFC and DISM

Open Command Prompt as Administrator and run the following sequence:

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

Wait for each command to complete. If SFC reports Windows Resource Protection found corrupt files but was unable to fix some of them, boot from Windows installation media and run:

sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows

Step 4: Update or Roll Back Drivers

If the BSOD names a .sys file (e.g., ntfs.sys, dxgkrnl.sys, nvlddmkm.sys):

Open Device Manager (devmgmt.msc).
Right-click the suspect device → Properties → Driver tab.
Click Roll Back Driver if the option is available.
If rolling back is not available, right-click → Update driver → Search automatically.
For GPU BSODs, download the latest driver directly from NVIDIA, AMD, or Intel and perform a Clean Installation.

Check driver verifier (use only in Safe Mode, revert after testing):

verifier /standard /all

Restart and reproduce the crash; the verifier will identify the offending driver. Disable after testing:

verifier /reset

Step 5: Test RAM with Windows Memory Diagnostic

Press Win+R, type mdsched.exe, press Enter.
Choose Restart now and check for problems.
After restart, the tool runs automatically. Check results in Event Viewer → Windows Logs → System, filter by source MemoryDiagnostics-Results.

For advanced RAM testing, use MemTest86 (bootable USB) and run at least two full passes. Any errors confirm faulty RAM requiring replacement.

Step 6: Uninstall Problematic Windows Updates

If the BSOD started after a specific update:

Go to Settings → Windows Update → Update History → Uninstall Updates.
Identify and uninstall the most recent Cumulative Update or Quality Update.
Via Command Prompt:

wusa /uninstall /kb:KB5031354 /quiet /norestart

(Replace KB number with the relevant update.)

Pause updates for 7 days while Microsoft issues a fix.

Step 7: Check Disk Health

A failing drive can cause NTFS_FILE_SYSTEM or INACCESSIBLE_BOOT_DEVICE BSODs.

chkdsk C: /f /r /x

For NVMe/SSD drives, use the manufacturer's diagnostic tool (Samsung Magician, Crucial Storage Executive, CrystalDiskInfo) to check the health status and reallocated sector count.

Step 8: Perform a Startup Repair (When You Cannot Boot)

Boot from Windows 11 installation USB.
Repair your computer → Troubleshoot → Advanced Options → Startup Repair.
If Startup Repair fails, try Command Prompt from WinRE:

bootrec /fixmbr
bootrec /fixboot
bootrec /rebuildbcd

Step 9: System Restore or Reset

If all else fails:

System Restore: Go to Advanced Options → System Restore and choose a restore point before the BSODs began.
Reset This PC: Settings → System → Recovery → Reset this PC → Keep my files to reinstall Windows while preserving personal data.

Windows Vista and Windows 8 Specific Notes

Windows Vista: BSODs often stem from incompatible drivers after Service Pack installation. Use verifier.exe and check C:\Windows\Minidump with WinDbg. Disable Driver Signature Enforcement at boot (F8 menu) to test unsigned drivers.

Windows 8/8.1: The automatic reboot loop can hide BSODs. Disable auto-restart: System Properties → Advanced → Startup and Recovery → uncheck Automatically restart. Windows 8 also introduced Automatic Repair — if it loops, boot to Safe Mode via msconfig → Boot tab → Safe boot.

Frequently Asked Questions

powershell

# ============================================================
# Windows BSOD Diagnostic & Repair Script
# Run as Administrator in PowerShell
# Compatible with Windows Vista, 8, 11
# ============================================================

Write-Host "=== Step 1: Check System File Integrity ==="
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Write-Host "`n=== Step 2: Check Disk Health ==="
# Schedule chkdsk on next reboot (C: drive)
echo Y | chkdsk C: /f /r /x

Write-Host "`n=== Step 3: List Recent Minidump Files ==="
$minidumpPath = "C:\Windows\Minidump"
if (Test-Path $minidumpPath) {
    Get-ChildItem -Path $minidumpPath -Filter "*.dmp" | Sort-Object LastWriteTime -Descending | Select-Object Name, LastWriteTime, Length
} else {
    Write-Host "No minidump folder found. Enable small memory dumps in System Properties."
}

Write-Host "`n=== Step 4: Extract Last BSOD Event from Event Log ==="
Get-WinEvent -LogName System | Where-Object { $_.Id -eq 41 -or $_.Id -eq 1001 -or $_.Id -eq 6008 } | Select-Object -First 10 | Format-List TimeCreated, Id, Message

Write-Host "`n=== Step 5: List Recently Installed Drivers ==="
Get-WmiObject Win32_PnPSignedDriver | Sort-Object DriverDate -Descending | Select-Object -First 20 DeviceName, DriverVersion, DriverDate, InfName | Format-Table -AutoSize

Write-Host "`n=== Step 6: Check for Pending Windows Updates ==="
(New-Object -ComObject Microsoft.Update.Session).CreateUpdateSearcher().Search("IsInstalled=0").Updates | Select-Object Title, IsDownloaded

Write-Host "`n=== Step 7: Check RAM Configuration ==="
Get-WmiObject -Class Win32_PhysicalMemory | Select-Object BankLabel, Capacity, Speed, Manufacturer, PartNumber | Format-Table -AutoSize

Write-Host "`n=== Step 8: Verify Boot Configuration ==="
bcdedit /enum all

Write-Host "`n=== Step 9: Temperature & Hardware Status (requires admin) ==="
# Check for overheating events
Get-WinEvent -LogName System | Where-Object { $_.Message -like "*thermal*" -or $_.Message -like "*overheat*" } | Select-Object -First 5 TimeCreated, Message

Write-Host "`n=== Step 10: Export Full System Info ==="
$reportPath = "$env:USERPROFILE\Desktop\BSOD_SystemReport_$(Get-Date -Format 'yyyyMMdd_HHmmss').txt"
Get-ComputerInfo | Out-File -FilePath $reportPath
Write-Host "System info saved to: $reportPath"

Write-Host "`n=== Diagnostic Complete ==="
Write-Host "Review minidumps with WinDbg from the Microsoft Store for deep analysis."
Write-Host "Run: windbg -z C:\Windows\Minidump\<filename>.dmp then type: !analyze -v"

# To enable Driver Verifier (ONLY in Safe Mode, REVERT after testing):
# verifier /standard /all
# To reset Driver Verifier:
# verifier /reset

# To uninstall a specific Windows Update (replace KB number):
# wusa /uninstall /kb:KB5031354 /quiet /norestart

Error Medic Editorial

The Error Medic Editorial team consists of senior DevOps engineers, SREs, and Microsoft-certified system administrators with 10+ years of experience diagnosing and resolving Windows kernel errors, BSOD stop codes, and enterprise infrastructure failures. Our guides combine real-world incident data, official Microsoft documentation, and community-validated fixes to help users at every skill level resolve critical system errors quickly and safely.

Sources

Explore More windows Guides

Acer Aspire Blue Screen of Death Fix: How to Stop BSOD Crashes on Acer Laptops

Fix Acer Aspire Blue Screen of Death errors fast. Step-by-step guide covering driver updates, RAM checks, overheating, and Windows repair commands.

Acer Aspire Blue Screen of Death Fix: Step-by-Step Troubleshooting Guide (BSOD Errors Solved)

Fix Acer Aspire blue screen of death errors fast. Covers MEMORY_MANAGEMENT, DRIVER_IRQL, KERNEL_SECURITY_CHECK and more. Step-by-step commands included.

Acer Aspire Blue Screen of Death Fix: Stop Codes, Causes & Complete Solutions

Fix Acer Aspire Blue Screen of Death errors fast. Covers MEMORY_MANAGEMENT, DRIVER_IRQL, KERNEL_SECURITY_CHECK_FAILURE & more with exact commands.