Why does my Windows 11 PC show BSOD immediately after a Windows Update?

A cumulative or driver update may have introduced an incompatible component. Boot into Safe Mode, go to Settings → Windows Update → Update History → Uninstall Updates, and remove the most recent update (look for KB numbers with yesterday's or today's date). You can also use System Restore to roll back to the pre-update state. Microsoft regularly releases hotfix patches for update-caused BSODs — check the Windows Health Dashboard at aka.ms/windowshealth for known issues.

What does 'DRIVER_IRQL_NOT_LESS_OR_EQUAL' mean and how do I fix it on Windows 11 or 8?

This stop code (0x000000D1) means a kernel-mode driver tried to access pageable memory at an Interrupt Request Level (IRQL) too high for that access. The fix is to identify the faulting driver from the minidump using BlueScreenView or WinDbg (look for IMAGE_NAME), then update, roll back, or uninstall that driver. Common culprits are network adapter drivers (e.g., NETIO.SYS), VPN clients, antivirus kernel modules, and outdated USB drivers. Running 'verifier /standard /driver ' can help isolate the issue.

How do I fix BSOD on Windows Vista with STOP: 0x0000007E?

Stop code 0x7E (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED) on Vista is most often caused by a corrupt or incompatible driver, especially after hardware changes. Boot into Safe Mode (F8 at startup), open Device Manager and look for yellow warning icons, uninstall recently added hardware drivers. Also run 'sfc /scannow' from an elevated command prompt and ensure Vista SP2 is installed. If the crash is hardware-related, test RAM with MemTest86 and check SMART data on the hard drive with 'chkdsk /f /r'.

My Windows 11 BSOD shows CRITICAL_PROCESS_DIED — what caused it and how do I fix it?

CRITICAL_PROCESS_DIED means a Windows system process essential to OS operation (like winlogon.exe, lsass.exe, or csrss.exe) terminated unexpectedly. Common causes: malware infection killing protected processes, corrupted system files, failing storage causing OS file read errors, or a bad Windows update. Fix steps: (1) Run a full malware scan in Safe Mode with Windows Defender offline scan, (2) Run 'sfc /scannow' and 'DISM /Online /Cleanup-Image /RestoreHealth', (3) Run 'chkdsk C: /f /r' to check disk, (4) Check Event Viewer → Windows Logs → System for critical errors logged just before the crash.

Does a BSOD always mean my hardware is failing?

No — the majority of BSODs are caused by software: drivers, corrupted OS files, malware, or bad Windows updates. Hardware failure (failing RAM, dying SSD/HDD, overheating CPU, or unstable power supply) does cause BSODs but is less common. Stop codes like WHEA_UNCORRECTABLE_ERROR, MEMORY_MANAGEMENT (persistent), and Hardware Malfunction are stronger indicators of physical hardware problems. Always rule out software causes first (SFC, DISM, driver updates) before assuming hardware failure. If MemTest86 passes and chkdsk shows no errors but BSODs persist, check CPU temperatures with HWInfo64 and run a stress test with Prime95 to rule out thermal throttling or power instability.

BSOD on Windows 11 (and Windows 8/Vista): Complete Fix Guide for Blue Screen of Death Errors

Fix BSOD on Windows 11, 8, and Vista with step-by-step commands, driver rollbacks, memory checks, and registry fixes. Resolve blue screen errors fast.

Last updated: March 1, 2026

Last verified: March 1, 2026

2,300 words

Key Takeaways

Root Cause 1: Faulty, outdated, or incompatible device drivers (especially GPU, NIC, and storage drivers) are the #1 trigger for BSOD on Windows 11, 8, and Vista — stop codes like DRIVER_IRQL_NOT_LESS_OR_EQUAL and PAGE_FAULT_IN_NONPAGED_AREA point directly to driver corruption.
Root Cause 2: Corrupted system files, failed Windows Updates, or damaged RAM/storage hardware cause critical stop errors such as CRITICAL_PROCESS_DIED, MEMORY_MANAGEMENT, and IRQL_NOT_LESS_OR_EQUAL across all Windows versions.
Quick Fix Summary: Boot into Safe Mode, run 'sfc /scannow' and 'DISM /RestoreHealth' to repair system files, use Windows Memory Diagnostic or MemTest86 to check RAM, roll back or uninstall the most recently installed drivers, and analyze minidump files in WinDbg or BlueScreenView to identify the exact failing module.

Fix Approaches Compared
Method	When to Use	Time	Risk
SFC + DISM System File Repair	Corrupted OS files, failed updates, recurring random BSODs	15-45 minutes	Low
Driver Rollback / Uninstall	BSOD started after driver or Windows update installation	5-15 minutes	Low
Windows Memory Diagnostic / MemTest86	MEMORY_MANAGEMENT or random BSODs with no clear software cause	30 min – 8 hours	None
Minidump Analysis with WinDbg / BlueScreenView	Identifying the exact faulty driver or module from crash logs	10-30 minutes	None
Startup Repair via WinRE	System won't boot at all, repeated BSODs at startup	20-40 minutes	Low
System Restore / Reset This PC	All software fixes failed, system unstable after update	30-120 minutes	Medium (data loss possible on Reset)
Check Disk (chkdsk)	NTFS_FILE_SYSTEM or storage-related stop codes	20-60 minutes	Low
BIOS/UEFI Firmware Update	Hardware incompatibility BSODs on new hardware or after CPU upgrade	15-30 minutes	Medium (brick risk if interrupted)

Understanding BSOD on Windows 11, 8, and Vista

A Blue Screen of Death (BSOD) — technically a Stop Error — occurs when the Windows kernel encounters a condition it cannot safely recover from. The system halts completely to prevent data corruption. On Windows 11 you'll see a sad emoji face with a QR code; on Windows 8 you see a simpler sad-face screen; on Vista you see the classic blue text wall with a STOP code like STOP: 0x0000007E.

All BSODs share the same anatomy:

Stop Code (e.g., CRITICAL_PROCESS_DIED, PAGE_FAULT_IN_NONPAGED_AREA)
Faulting Module (e.g., ntoskrnl.exe, nvlddmkm.sys, NETIO.SYS)
Memory Address where the fault occurred
Minidump file written to C:\Windows\Minidump\ for post-mortem analysis

Step 1: Capture the Stop Code and Minidump

Before fixing anything, identify what you're dealing with.

On Windows 11/10/8:

Go to Settings → System → About → Advanced system settings → Startup and Recovery → Settings.
Ensure Write debugging information is set to Small memory dump (256 KB) and the path is %SystemRoot%\Minidump.
After a crash, minidump files (.dmp) appear in C:\Windows\Minidump\.
Note the exact stop code displayed on the blue screen (take a photo with your phone if the crash is fast).

Common Windows 11 stop codes and their meanings:

DRIVER_IRQL_NOT_LESS_OR_EQUAL — Driver accessing invalid memory address at elevated IRQL
PAGE_FAULT_IN_NONPAGED_AREA — Memory page requested is not in RAM (bad RAM or driver)
CRITICAL_PROCESS_DIED — A critical OS process (lsass.exe, csrss.exe, etc.) crashed
MEMORY_MANAGEMENT — Serious memory subsystem error
SYSTEM_SERVICE_EXCEPTION — Driver or service violated memory access rules
KERNEL_SECURITY_CHECK_FAILURE — Kernel-mode data structure corruption (often malware or old driver)
NTFS_FILE_SYSTEM — NTFS filesystem corruption on disk
WHEA_UNCORRECTABLE_ERROR — Hardware error (CPU, RAM, power instability)

On Windows Vista (legacy): Stop codes appear as hex: STOP: 0x0000007E (0xFFFFFFFFC0000005, ...) — map these to symbolic names using Microsoft's Stop Error Reference.

Step 2: Boot Into Safe Mode

If Windows won't start normally:

Windows 11/8:

At login screen, hold Shift and click Restart.
Navigate to Troubleshoot → Advanced Options → Startup Settings → Restart.
Press F4 for Safe Mode or F5 for Safe Mode with Networking.

Windows Vista:

Press F8 repeatedly during boot.
Select Safe Mode from the Advanced Boot Options menu.

In Safe Mode, only essential drivers load — if BSODs stop in Safe Mode, the cause is almost certainly a third-party driver or startup program.

Step 3: Repair System Files with SFC and DISM

Open Command Prompt as Administrator and run these commands in order:

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

SFC scans and repairs protected Windows system files using the Windows Component Store. DISM repairs the Component Store itself using Windows Update as the source. After both complete, restart and check if BSODs recur.

If SFC reports: Windows Resource Protection found corrupt files but was unable to fix some of them — boot from Windows installation media, open Recovery Command Prompt, and run:

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

Step 4: Analyze Minidump Files

Option A — BlueScreenView (no install required):

Download BlueScreenView from NirSoft.
It automatically loads all .dmp files from C:\Windows\Minidump\.
Look at the Caused By Driver column — this is your primary suspect.

Option B — WinDbg (most accurate):

Install Windows Debugging Tools from the Windows SDK.
Open WinDbg, go to File → Open Crash Dump, select the .dmp file.
Run: !analyze -v
Look for IMAGE_NAME: and MODULE_NAME: in the output.

If the faulting module is a third-party .sys file (e.g., nvlddmkm.sys = NVIDIA, iaStorAC.sys = Intel RST), proceed to driver fix.

Step 5: Fix Driver-Related BSODs

Roll back a driver:

Press Win+X → Device Manager.
Right-click the suspect device → Properties → Driver → Roll Back Driver.

Uninstall and clean-install driver:

In Device Manager, right-click → Uninstall device → check Delete the driver software for this device.
For GPU drivers, use Display Driver Uninstaller (DDU) in Safe Mode for a complete wipe.
Download fresh drivers from the manufacturer's official site and install.

Disable driver signature enforcement (temporary diagnosis): At startup, press F7 (Startup Settings) to disable driver signature enforcement and see if the BSOD is caused by an unsigned driver.

Step 6: Check RAM with Windows Memory Diagnostic

Press Win+R, type mdsched.exe, press Enter.
Select Restart now and check for problems.
The tool runs on reboot and reports errors on the next Windows login.

For thorough testing (especially for WHEA_UNCORRECTABLE_ERROR or MEMORY_MANAGEMENT), use MemTest86 from a bootable USB — run at least two full passes overnight.

If RAM errors are found: reseat DIMMs, test sticks individually, and replace faulty sticks.

Step 7: Check Disk Health

For NTFS_FILE_SYSTEM or storage-related BSODs:

chkdsk C: /f /r /x

This schedules a disk check on the next reboot. For SSD health, use:

wmic diskdrive get status

or manufacturer tools (CrystalDiskInfo, Samsung Magician, Intel MAS).

Step 8: Windows-Version-Specific Fixes

Windows 11 specific:

Disable Memory Integrity (Core Isolation) if a driver is incompatible: Settings → Privacy & Security → Windows Security → Device Security → Core Isolation Details → toggle off Memory Integrity.
Check Windows Update for cumulative updates that patch known BSOD-causing bugs.
Roll back a bad Windows 11 update: Settings → Windows Update → Update History → Uninstall Updates.

Windows 8 specific:

Use Automatic Repair: boot from installation media → Repair Your Computer → Troubleshoot → Automatic Repair.
Run: bootrec /fixmbr && bootrec /fixboot && bootrec /rebuildbcd if BSOD occurs at boot.

Windows Vista specific:

Vista's Stop errors often stem from unsigned or 32-bit-only drivers. Use verifier /standard /all carefully in Safe Mode to identify the culprit.
Vista SP2 is critical — ensure it is installed before all other fixes.
Disable UAC temporarily during diagnosis if Stop 0x0000007B (INACCESSIBLE_BOOT_DEVICE) appears.

Step 9: Last Resort — System Restore or Reset

System Restore (preserves files):

Press Win+R → rstrui.exe
Choose a restore point dated before BSODs began.

Reset This PC (nuclear option):

Settings → System → Recovery → Reset this PC.
Choose Keep my files (or Remove everything for clean slate).
This reinstalls Windows while optionally preserving personal data.

Fresh install from media: If all else fails, download the Windows 11 Media Creation Tool, create a bootable USB, and perform a clean install. Always back up data first.

Frequently Asked Questions

powershell

# ============================================================
# BSOD Diagnostic & Fix Script for Windows 11 / 8 / Vista
# Run as Administrator in PowerShell or Command Prompt
# ============================================================

# --- 1. Check and display recent BSOD events from Event Log ---
Write-Host "=== Recent BSOD / Critical System Events ==="
Get-WinEvent -FilterHashtable @{LogName='System'; Level=1,2; Id=41,6008,1001} -MaxEvents 20 |
  Select-Object TimeCreated, Id, Message |
  Format-List

# --- 2. List all minidump files with timestamps ---
Write-Host "`n=== Minidump Files ==="
Get-ChildItem -Path "C:\Windows\Minidump" -Filter "*.dmp" -ErrorAction SilentlyContinue |
  Sort-Object LastWriteTime -Descending |
  Select-Object Name, LastWriteTime, @{N='SizeMB';E={[math]::Round($_.Length/1MB,2)}}

# --- 3. Repair system files (DISM then SFC) ---
Write-Host "`n=== Running DISM Health Check ==="
DISM /Online /Cleanup-Image /CheckHealth

Write-Host "`n=== Running DISM RestoreHealth (requires internet) ==="
DISM /Online /Cleanup-Image /RestoreHealth

Write-Host "`n=== Running SFC System File Checker ==="
sfc /scannow

# --- 4. Schedule disk check on next reboot ---
Write-Host "`n=== Scheduling CHKDSK on next reboot ==="
echo Y | chkdsk C: /f /r /x

# --- 5. Check RAM slots and capacity (basic hardware info) ---
Write-Host "`n=== RAM Information ==="
Get-WmiObject Win32_PhysicalMemory | Select-Object BankLabel, Capacity, Speed, Manufacturer | Format-Table -AutoSize

# --- 6. Check disk health via SMART status ---
Write-Host "`n=== Disk SMART Status ==="
Get-WmiObject -Namespace root\wmi -Class MSStorageDriver_FailurePredictStatus |
  Select-Object InstanceName, PredictFailure, Reason | Format-Table -AutoSize

# --- 7. List recently installed drivers (last 30 days) ---
Write-Host "`n=== Drivers Installed in Last 30 Days ==="
$cutoff = (Get-Date).AddDays(-30)
Get-WmiObject Win32_PnPSignedDriver |
  Where-Object { $_.DriverDate -and [datetime]::ParseExact($_.DriverDate.Substring(0,8),'yyyyMMdd',$null) -gt $cutoff } |
  Select-Object DeviceName, DriverVersion, DriverDate, Manufacturer |
  Sort-Object DriverDate -Descending |
  Format-Table -AutoSize

# --- 8. Enable Driver Verifier for next boot (use carefully, disable after diagnosis) ---
# Uncomment the line below ONLY for diagnosis — may cause intentional BSOD to catch bad drivers
# verifier /standard /all

# --- 9. Export system info for offline analysis ---
Write-Host "`n=== Exporting System Info to Desktop ==="
$outPath = "$env:USERPROFILE\Desktop\BSODReport_$(Get-Date -Format 'yyyyMMdd_HHmm').txt"
msinfo32 /report $outPath
Write-Host "Report saved to: $outPath"

# --- 10. Disable Memory Integrity (Windows 11 only) if driver incompatibility suspected ---
# Run from elevated PowerShell:
# Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity' -Name 'Enabled' -Value 0
# Restart-Computer

Write-Host "`n=== Diagnostic Complete. Review output above and check $outPath ==="

Error Medic Editorial

Error Medic Editorial is a team of senior DevOps engineers, SREs, and Windows system architects with 15+ years of combined experience diagnosing and resolving operating system failures across enterprise and consumer environments. Our contributors have worked with Fortune 500 IT departments, Microsoft Certified Partners, and open-source communities to document reproducible, command-driven solutions to the most frustrating Windows stop errors. Every guide is tested on real hardware running Windows 11, Windows 10, Windows 8, and legacy Vista systems before publication.

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.