Why did Windows 11 22H2 cause a Blue Screen of Death on my PC?

Windows 11 22H2 introduced stricter driver signing enforcement, Secure Boot changes, and kernel-level security updates. These changes broke compatibility with some older drivers — especially GPU, NIC, and storage controller drivers — causing stop errors. The most commonly reported faulting modules after the 22H2 update include nvlddmkm.sys (NVIDIA), atikmpag.sys (AMD), and iaStorA.sys (Intel RST). Fix: roll back the 22H2 update via Settings → Windows Update → Update History → Uninstall Updates, or update all drivers to 22H2-compatible versions from the manufacturer's website.

How do I fix a Windows 11 Blue Screen of Death if my PC won't boot?

If Windows 11 is stuck in a BSOD boot loop, force-shutdown the PC three times during the boot animation to trigger Automatic Repair mode. From there, go to Advanced Options → Startup Settings and boot into Safe Mode. In Safe Mode, run 'sfc /scannow' and 'DISM /Online /Cleanup-Image /RestoreHealth' from an elevated Command Prompt, then uninstall recently added drivers or software. If Safe Mode also fails, boot from a Windows 11 installation USB and use Startup Repair.

What does the IRQL_NOT_LESS_OR_EQUAL BSOD mean in Windows 11?

IRQL_NOT_LESS_OR_EQUAL (stop code 0x0000000A) means a kernel-mode process or driver attempted to access memory at an interrupt request level (IRQL) that was too high. This is almost always caused by a buggy or incompatible driver. Check the faulting module listed on the blue screen (e.g., 'tcpip.sys' for network driver issues, 'nvlddmkm.sys' for NVIDIA GPU). Update or roll back that specific driver to resolve the error.

Can a failing SSD or HDD cause Blue Screen of Death in Windows 11?

Yes. A failing storage device can cause BSODs such as INACCESSIBLE_BOOT_DEVICE, NTFS_FILE_SYSTEM, or PAGE_FAULT_IN_NONPAGED_AREA. Run 'chkdsk C: /f /r /x' from an elevated Command Prompt to scan and repair disk errors. For SSDs, use the manufacturer's diagnostic tool (Samsung Magician, Crucial Storage Executive, etc.) or CrystalDiskInfo to check the S.M.A.R.T. health status. Any 'Caution' or 'Bad' S.M.A.R.T. readings indicate an imminent drive failure — back up data immediately and replace the drive.

How do I find out what caused the Blue Screen of Death in Windows 11 after the crash?

After a BSOD, open Event Viewer (eventvwr.msc) and navigate to Windows Logs → System. Look for Event ID 41 (Kernel-Power) at the exact time of the crash, which confirms an unexpected shutdown, and Event ID 1001 (BugCheck), which records the stop code and parameters. For deeper analysis, download WhoCrashed (free) or WinDbg (from the Microsoft Store) and point it to the minidump files located at C:\Windows\Minidump\. WhoCrashed will identify the faulting driver in plain English.

Windows 11 Blue Screen of Death (BSOD): Complete Fix Guide for Stop Errors

Fix Windows 11 Blue Screen of Death errors fast. Step-by-step repair for 22H2 BSODs including IRQL, MEMORY_MANAGEMENT, and kernel panic stop codes.

Last updated: March 1, 2026

Last verified: March 1, 2026

1,958 words

Key Takeaways

Most Windows 11 BSODs are caused by incompatible or outdated drivers, especially after the 22H2 update — updating or rolling back drivers resolves the majority of cases.
Faulty RAM, corrupted system files, and overheating hardware are the next most common root causes — use MemTest86, SFC, and DISM to diagnose these systematically.
Quick fix summary: Boot into Safe Mode → run 'sfc /scannow' and 'DISM /Online /Cleanup-Image /RestoreHealth' → check Event Viewer for the faulting module → update or roll back the offending driver → if persistent, run MemTest86 overnight.

Fix Approaches Compared
Method	When to Use	Time	Risk
SFC + DISM Scan	Corrupted Windows system files causing random BSODs	15–30 min	Low
Driver Rollback / Update	BSOD started after a Windows Update or driver install (e.g., 22H2)	10–20 min	Low
MemTest86 RAM Test	Random BSODs with MEMORY_MANAGEMENT or BAD_POOL_HEADER stop codes	4–8 hours	None
Windows Startup Repair	System won't boot at all; stuck in BSOD loop	20–40 min	Low
System Restore	BSOD appeared after a recent software or driver change	20–30 min	Medium
Clean Boot	Identifying third-party software causing kernel conflicts	30–60 min	Low
Reset / Reinstall Windows	All other methods failed; persistent unrecoverable BSOD loop	2–4 hours	High — data loss risk

Understanding Windows 11 Blue Screen of Death

A Blue Screen of Death (BSOD), formally called a Stop Error or Bug Check, occurs when Windows 11 encounters a fatal system error it cannot recover from. The screen displays a stop code such as:

IRQL_NOT_LESS_OR_EQUAL
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
MEMORY_MANAGEMENT
PAGE_FAULT_IN_NONPAGED_AREA
KERNEL_SECURITY_CHECK_FAILURE
CRITICAL_PROCESS_DIED
BAD_POOL_HEADER
WHEA_UNCORRECTABLE_ERROR

Windows 11 22H2 introduced new driver signing requirements, updated Secure Boot enforcement, and kernel changes that broke compatibility with several legacy drivers — making BSODs more frequent immediately after the update.

Step 1: Record the Stop Code and Faulting Module

When the BSOD appears, note the exact stop code at the bottom of the blue screen (e.g., 0x0000007E) and the faulting file name (e.g., ntfs.sys, nvlddmkm.sys). If the system reboots too fast:

Press Win + R, type sysdm.cpl, and press Enter.
Go to Advanced → Startup and Recovery → Settings.
Uncheck Automatically restart under System failure.
Also check that Write an event to the system log is enabled.

This forces Windows to remain on the blue screen so you can read the stop code.

Step 2: Check the Windows Event Log and Minidump

Windows stores crash dump files at C:\Windows\Minidump\. Use Windows Debugger (WinDbg) or the free WhoCrashed utility to analyze them.

In Event Viewer (eventvwr.msc), navigate to: Windows Logs → System

Filter for Event ID 41 (Kernel-Power) and Event ID 1001 (BugCheck). These entries reveal the exact timestamp and stop code associated with each crash.

Step 3: Boot into Safe Mode

If you cannot reach the desktop:

Force shutdown the PC three times in a row during boot — Windows will enter Automatic Repair mode.
Click Advanced Options → Troubleshoot → Advanced Options → Startup Settings → Restart.
Press 4 or F4 to boot into Safe Mode, or 5 for Safe Mode with Networking.

In Safe Mode, only essential Microsoft drivers load, which lets you confirm whether a third-party driver is responsible.

Step 4: Run SFC and DISM to Repair System Files

Open an elevated Command Prompt (Run as Administrator) and execute:

sfc /scannow

Wait for it to complete (do not interrupt). If it reports "Windows Resource Protection found corrupt files but was unable to fix some of them," follow up with DISM:

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

After DISM finishes, run sfc /scannow again. Reboot and check whether BSODs persist.

Step 5: Update or Roll Back Drivers

The most common cause of Windows 11 22H2 BSODs is an incompatible driver — especially GPU drivers (NVIDIA nvlddmkm.sys, AMD atikmpag.sys), network adapters, and storage controllers.

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 drivers:

For NVIDIA: Download the latest Game Ready or Studio driver from nvidia.com and perform a clean install using DDU (Display Driver Uninstaller).
For AMD: Use AMD Cleanup Utility before installing the latest Adrenalin driver.
For all other drivers: Use Windows Update → Advanced options → Optional updates to get Microsoft-validated driver packages.

Step 6: Test RAM with MemTest86

If the stop code is MEMORY_MANAGEMENT, BAD_POOL_HEADER, or PAGE_FAULT_IN_NONPAGED_AREA, RAM corruption is likely.

Download MemTest86 from memtest86.com and create a bootable USB.
Boot from the USB and let it run for at least 2 full passes (ideally overnight).
Any errors (shown in red) indicate faulty RAM. Try reseating the RAM sticks first; if errors persist, replace the failing module.

You can also run the built-in Windows Memory Diagnostic:

Press Win + R, type mdsched.exe, choose Restart now and check for problems.

Step 7: Check for Overheating

WHEA_UNCORRECTABLE_ERROR and KERNEL_SECURITY_CHECK_FAILURE can be caused by overheating CPUs or GPUs.

Download HWiNFO64 or Core Temp and monitor temperatures under load:

CPU should stay below 95°C (most Intel/AMD consumer processors).
GPU should stay below 90°C.

If temperatures are high, clean dust from heatsinks, replace thermal paste, and ensure case airflow is adequate.

Step 8: Perform a Clean Boot to Isolate Software

Press Win + R, type msconfig, press Enter.
On the Services tab, check Hide all Microsoft services, then click Disable all.
On the Startup tab, click Open Task Manager and disable all startup items.
Reboot and observe whether BSODs stop.

If stable, re-enable services and startup items in batches to identify the culprit.

Step 9: Use Windows Startup Repair

If the system won't boot past the BSOD:

Boot from a Windows 11 installation USB.
Select Repair your computer → Troubleshoot → Advanced Options → Startup Repair.

Startup Repair will scan the BCD (Boot Configuration Data), MBR, and system partition for corruption and attempt automatic fixes.

Step 10: Last Resort — Reset or Reinstall Windows

If all previous steps fail:

Go to Settings → System → Recovery → Reset this PC.
Choose Keep my files for a non-destructive reset, or Remove everything for a clean slate.
Alternatively, perform a clean install from a bootable Windows 11 USB created with the Media Creation Tool.

Before resetting, back up all critical data to an external drive or cloud storage.

Frequently Asked Questions

powershell

# ============================================================
# Windows 11 BSOD Diagnostic & Repair Script
# Run in an elevated PowerShell (Administrator) session
# ============================================================

# --- 1. Display the last 10 BugCheck events from Event Log ---
Write-Host "=== Last 10 BSOD Events ==="
Get-WinEvent -FilterHashtable @{LogName='System'; Id=1001} -MaxEvents 10 |
  Select-Object TimeCreated, 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. Run System File Checker ---
Write-Host "`n=== Running SFC (this may take 10-20 minutes) ==="
sfc /scannow

# --- 4. Run DISM to repair Windows image ---
Write-Host "`n=== Running DISM RestoreHealth ==="
DISM /Online /Cleanup-Image /RestoreHealth

# --- 5. Check disk for errors (schedules check on next reboot for C:) ---
Write-Host "`n=== Scheduling CHKDSK on next reboot ==="
echo Y | chkdsk C: /f /r /x

# --- 6. 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 -ne $null -and [DateTime]::ParseExact($_.DriverDate.Substring(0,8),'yyyyMMdd',$null) -gt $cutoff } |
  Select-Object DeviceName, DriverVersion, DriverDate |
  Sort-Object DriverDate -Descending

# --- 7. Check RAM with Windows Memory Diagnostic (schedules on reboot) ---
Write-Host "`n=== Scheduling Windows Memory Diagnostic ==="
# Uncomment the line below to schedule:
# Start-Process mdsched.exe

# --- 8. Check temperatures via WMI (basic, may not work on all hardware) ---
Write-Host "`n=== CPU Temperature (MSAcpi_ThermalZoneTemperature) ==="
try {
  $temp = Get-WmiObject MSAcpi_ThermalZoneTemperature -Namespace 'root/wmi' -ErrorAction Stop
  foreach ($t in $temp) {
    $celsius = ($t.CurrentTemperature - 2732) / 10
    Write-Host "Zone: $($t.InstanceName) | Temp: $celsius C"
  }
} catch {
  Write-Host "WMI thermal data unavailable. Use HWiNFO64 for accurate readings."
}

# --- 9. Export System Info to file ---
Write-Host "`n=== Exporting System Info to Desktop ==="
$outPath = "$env:USERPROFILE\Desktop\BSODReport_$(Get-Date -Format 'yyyyMMdd_HHmmss').txt"
$info = @{
  OS        = (Get-ComputerInfo).WindowsProductName
  Version   = (Get-ComputerInfo).WindowsVersion
  Build     = (Get-ComputerInfo).OsBuildNumber
  RAM_GB    = [math]::Round((Get-ComputerInfo).TotalPhysicalMemory/1GB,1)
  Uptime    = (Get-Date) - (gcim Win32_OperatingSystem).LastBootUpTime
}
$info | Out-File $outPath
Write-Host "Report saved to: $outPath"

Write-Host "`n=== Diagnostics Complete. Reboot to apply CHKDSK and SFC fixes. ==="

Error Medic Editorial

The Error Medic Editorial team is composed of senior DevOps engineers, SREs, and Windows system administrators with a combined 40+ years of experience diagnosing OS-level failures, kernel panics, and enterprise IT incidents. We write practical, command-driven troubleshooting guides tested on real hardware and virtual machines running all current Windows releases.

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.