Why does Windows 11 keep crashing with a Blue Screen of Death after the 22H2 update?

Windows 11 22H2 introduced stricter driver model enforcement and changes to Secure Boot and TPM handling. The most common culprits are outdated NVIDIA/AMD GPU drivers, Intel graphics drivers incompatible with the new kernel, and third-party security software (antivirus, VPN drivers) that conflict with the updated kernel. Fix: Roll back the 22H2 update via Settings > Windows Update > Update history > Uninstall updates, update all drivers before re-applying the update, or uninstall conflicting security software.

How do I fix WHEA_UNCORRECTABLE_ERROR on Windows 11?

WHEA_UNCORRECTABLE_ERROR (stop code 0x0000124) indicates a hardware error — typically CPU, RAM, or GPU instability. Common causes include: CPU overclocking beyond stable limits, failing RAM, overheating components, or a degraded PSU. Steps to fix: (1) Disable any CPU/GPU overclocking in BIOS and reset to default settings. (2) Run Windows Memory Diagnostic and MemTest86 for RAM errors. (3) Check CPU and GPU temperatures using HWMonitor — CPU should be under 95°C under load. (4) Update BIOS/UEFI firmware from your motherboard manufacturer. (5) Run 'sfc /scannow' and 'DISM /Online /Cleanup-Image /RestoreHealth'.

My Windows 11 PC is stuck in a BSOD boot loop and I cannot get to the desktop. What do I do?

When Windows 11 cannot boot due to a BSOD loop: (1) Force the PC off three times during the boot animation — Windows will open Automatic Repair. (2) Go to Advanced Options > Startup Settings > Restart > press F4 for Safe Mode. (3) If Safe Mode works, uninstall recent updates (Settings > Windows Update > Update history > Uninstall updates) or roll back the latest driver. (4) If Safe Mode also BSODs, boot from a Windows 11 USB installer, choose Repair your computer > Troubleshoot > Advanced Options > Startup Repair or System Restore. (5) As a last resort, use Command Prompt from WinRE to run 'sfc /scannow' and 'chkdsk C: /f /r'.

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (stop code 0x000000D1) means a kernel-mode driver tried to access pageable memory at an incorrect interrupt request level (IRQL), indicating a buggy driver. The stop screen typically names the offending .sys file. Fix: (1) Note the .sys filename on the BSOD screen. (2) Open Device Manager and find the device associated with that driver. (3) Roll back or uninstall the driver. (4) Download the latest stable driver from the manufacturer's website (not Windows Update). (5) If the driver is a network adapter, try updating chipset and NIC drivers. (6) Run Driver Verifier to confirm the specific driver if the .sys file is not shown.

Can a virus or malware cause Windows 11 Blue Screen of Death?

Yes, though it is less common than hardware or driver issues. Rootkits and kernel-level malware can corrupt system files or inject malicious code into driver space, triggering stop codes like SYSTEM_SERVICE_EXCEPTION or KERNEL_SECURITY_CHECK_FAILURE. To rule out malware: (1) Boot into Safe Mode with Networking. (2) Run Microsoft Defender Offline Scan: open Windows Security > Virus & threat protection > Scan options > Microsoft Defender Offline scan. (3) Use Malwarebytes Free for a second opinion scan. (4) Run 'sfc /scannow' after cleaning to repair any files the malware corrupted. If the system is severely compromised, a clean reinstall of Windows 11 is the safest resolution.

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

Fix Windows 11 Blue Screen of Death errors fast. Step-by-step repair guide covering DRIVER_IRQL, MEMORY_MANAGEMENT, WHEA_UNCORRECTABLE_ERROR & more. Updated for

Last updated: March 1, 2026

Last verified: March 1, 2026

2,474 words

Key Takeaways

Root Cause 1: Faulty, outdated, or incompatible device drivers (most common culprit — especially after Windows 11 22H2 updates) triggering stop codes like DRIVER_IRQL_NOT_LESS_OR_EQUAL or SYSTEM_THREAD_EXCEPTION_NOT_HANDLED.
Root Cause 2: Defective or mismatched RAM, overheating CPU/GPU, or failing storage drives causing hardware-level stop codes such as MEMORY_MANAGEMENT, WHEA_UNCORRECTABLE_ERROR, and PAGE_FAULT_IN_NONPAGED_AREA.
Quick Fix Summary: Boot into Safe Mode, run 'sfc /scannow' and 'DISM /Online /Cleanup-Image /RestoreHealth', update or roll back the offending driver identified in Event Viewer or WinDbg, run Windows Memory Diagnostic, and check disk health with 'chkdsk /f /r' — resolve 90%+ of BSOD cases within 30 minutes.

Fix Approaches Compared
Method	When to Use	Time	Risk
SFC & DISM System File Repair	Corrupted system files after update or crash	10-20 min	Low
Driver Rollback / Uninstall	BSOD started after a driver or Windows update	5-15 min	Low
Windows Memory Diagnostic	Random BSODs with MEMORY_MANAGEMENT or PAGE_FAULT stop codes	15-30 min	None
CHKDSK Disk Scan	BSODs involving file system errors or NTFS stop codes	20-60 min	Very Low
Startup Repair (WinRE)	System won't boot past the BSOD loop	10-20 min	Low
Driver Verifier	Intermittent BSODs needing exact driver identification	1-8 hrs (stress)	Medium — may cause more BSODs intentionally
Clean Boot / Safe Mode	Isolate third-party software vs. driver conflict	10-15 min	None
System Restore	BSOD appeared after a specific change and restore point exists	20-40 min	Low
Reset / Reinstall Windows 11	All else fails or OS is severely corrupted	1-3 hrs	High — data loss risk without backup

Understanding Windows 11 Blue Screen of Death

A Blue Screen of Death (BSOD) — officially called a Stop Error or Bug Check — occurs when Windows 11 detects a fatal system error from which it cannot safely recover. The system halts, dumps memory to disk, and restarts. On Windows 11, the BSOD screen displays a sad face emoji, a brief description, a QR code, and a stop code such as:

DRIVER_IRQL_NOT_LESS_OR_EQUAL
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
MEMORY_MANAGEMENT
WHEA_UNCORRECTABLE_ERROR
PAGE_FAULT_IN_NONPAGED_AREA
CRITICAL_PROCESS_DIED
KERNEL_SECURITY_CHECK_FAILURE
NTFS_FILE_SYSTEM
VIDEO_TDR_FAILURE

Windows 11 version 22H2 introduced a wave of new BSOD reports, primarily due to incompatible GPU drivers, Secure Boot conflicts, and TPM-related issues. If you upgraded recently, that context matters greatly for diagnosis.

Step 1: Capture the Stop Code and Crash Dump

Before applying any fix, identify which BSOD you are dealing with.

1a. Read the stop code on screen. Note the stop code displayed (e.g., DRIVER_IRQL_NOT_LESS_OR_EQUAL) and any file name shown beneath it (e.g., nvlddmkm.sys for NVIDIA, dxgmms2.sys for DirectX).

1b. Open Event Viewer. Press Win + R, type eventvwr.msc, and press Enter. Navigate to Windows Logs > System. Filter by Critical events with Source = BugCheck. The Event ID 1001 entry contains the exact stop code in hexadecimal and the path to the memory dump file (usually C:\Windows\Minidump\).

1c. Analyze the minidump with WinDbg. Download WinDbg from the Microsoft Store or Windows SDK. Open the .dmp file and run !analyze -v to get the faulting module, stack trace, and root cause.

Step 2: Boot Into Safe Mode or Windows Recovery Environment (WinRE)

If Windows 11 cannot boot normally due to a BSOD loop:

Force shutdown by holding the power button three times in a row. Windows will boot into Automatic Repair mode.
Select Advanced Options > Troubleshoot > Advanced Options > Startup Settings > Restart.
Press F4 for Safe Mode or F5 for Safe Mode with Networking.

Alternatively, boot from a Windows 11 USB installer and choose Repair your computer to access WinRE without booting the installed OS.

Step 3: Repair System Files with SFC and DISM

Corrupted system files are a frequent cause of stop errors, especially after failed updates.

Run System File Checker:

sfc /scannow

This scans all protected system files and replaces corrupted versions. Requires administrator command prompt.

If SFC reports errors it could not fix, run DISM first:

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

DISM downloads replacement files from Windows Update. After DISM completes, rerun sfc /scannow.

Step 4: Update or Roll Back the Offending Driver

Drivers cause the majority of Windows 11 BSODs. If the stop screen names a .sys file, that is your suspect.

Common culprits and their drivers:

nvlddmkm.sys — NVIDIA display driver
atikmpag.sys / atikmdag.sys — AMD GPU driver
igdkmd64.sys — Intel integrated graphics
dxgmms2.sys — DirectX graphics kernel
ntfs.sys — NTFS file system driver
storport.sys — Storage driver

To roll back a driver:

Press Win + X > Device Manager.
Expand the relevant category (e.g., Display adapters).
Right-click the device > Properties > Driver > Roll Back Driver.

To update a driver: Right-click device > Update driver > Search automatically for drivers, or download the latest driver directly from the manufacturer's website (NVIDIA, AMD, Intel).

To uninstall a problematic driver entirely: Right-click device > Uninstall device, check Delete the driver software for this device, and reboot. Windows will reinstall a generic driver.

For GPU drivers, use Display Driver Uninstaller (DDU) in Safe Mode for a completely clean removal before reinstalling.

Step 5: Test RAM with Windows Memory Diagnostic

Defective RAM frequently causes MEMORY_MANAGEMENT, PAGE_FAULT_IN_NONPAGED_AREA, and WHEA_UNCORRECTABLE_ERROR stop codes.

Press Win + R, type mdsched.exe, press Enter.
Choose Restart now and check for problems.
The tool runs two passes by default. Press F1 to switch to Extended mode for thorough testing.
Results appear after reboot in Event Viewer under Windows Logs > System (source: MemoryDiagnostics-Results).

For deeper testing, use MemTest86 (bootable, hardware-level, runs outside Windows) for overnight passes.

If RAM errors are found: Reseat the RAM sticks, try one stick at a time to isolate the faulty module, and test each stick individually.

Step 6: Check Disk Health with CHKDSK

File system errors and bad sectors on your drive trigger stop codes like NTFS_FILE_SYSTEM and CRITICAL_PROCESS_DIED.

Run from an elevated command prompt:

chkdsk C: /f /r /x

/f — Fixes file system errors
/r — Locates bad sectors and recovers readable data
/x — Forces the volume to dismount first

You will be prompted to schedule the scan on next reboot. Type Y and restart.

For NVMe/SSD health, also check using:

powershell -command "Get-PhysicalDisk | Get-StorageReliabilityCounter | Select-Object DeviceId, Temperature, Wear, ReadErrorsTotal, WriteErrorsTotal"

Or use CrystalDiskInfo for a GUI-based SMART status overview.

Step 7: Use Driver Verifier to Pinpoint Intermittent BSODs

If BSODs are infrequent and the stop code changes each time, Driver Verifier forces buggy drivers to crash immediately and loudly.

Open an elevated command prompt and run verifier.
Select Create standard settings > Select driver names from a list.
Check only non-Microsoft drivers (third-party).
Reboot. The system will BSOD faster with the faulting driver named explicitly.
Analyze the new dump with WinDbg's !analyze -v.
After identifying the driver, disable Verifier: verifier /reset then reboot.

Warning: Driver Verifier will cause intentional crashes. Do not leave it running on a production machine indefinitely.

Step 8: Perform a System Restore

If you have a restore point from before the BSODs began:

Boot into WinRE > Advanced Options > System Restore.
Choose a restore point dated before the issue started.
Confirm and restore. This will not affect personal files but will remove drivers and apps installed after the restore point.

Step 9: Reset or Reinstall Windows 11

As a last resort when all else fails:

Option A — Reset (keeps files): Settings > System > Recovery > Reset this PC > Keep my files.

Option B — Clean install: Create a Windows 11 bootable USB using the Media Creation Tool. Boot from USB, choose Custom installation, and format the system partition.

Always back up important data to an external drive before proceeding.

Windows 11 22H2 Specific Fixes

The 22H2 update introduced several known BSOD triggers:

KB5017321 / KB5017026 patch conflicts: Uninstall via Settings > Windows Update > Update history > Uninstall updates.
Secure Boot + third-party antivirus conflict: Temporarily disable third-party AV in Safe Mode and test.
Intel 12th/13th Gen CPU instability: Update Intel ME firmware and chipset drivers from the OEM's support page.
AMD fTPM stuttering/BSOD: Update AMD chipset drivers and BIOS to latest version from motherboard manufacturer.

Frequently Asked Questions

powershell

# ============================================================
# Windows 11 BSOD Diagnostic & Repair Script
# Run as Administrator in PowerShell
# ============================================================

# --- 1. Get last 10 BSOD events from Event Log ---
Write-Host "`n[*] Fetching last 10 BugCheck (BSOD) events..." -ForegroundColor Cyan
Get-WinEvent -FilterHashtable @{LogName='System'; Id=1001; ProviderName='Microsoft-Windows-WER-SystemErrorReporting'} -MaxEvents 10 |`
    Select-Object TimeCreated, Message | Format-List

# --- 2. List all minidump files ---
Write-Host "`n[*] Listing minidump files in C:\Windows\Minidump..." -ForegroundColor Cyan
if (Test-Path "C:\Windows\Minidump") {
    Get-ChildItem "C:\Windows\Minidump" -Filter "*.dmp" | Sort-Object LastWriteTime -Descending | Select-Object Name, LastWriteTime, Length
} else {
    Write-Host "No minidump folder found. Ensure small memory dump is configured." -ForegroundColor Yellow
}

# --- 3. Configure Windows to create small memory dumps ---
Write-Host "`n[*] Ensuring Small Memory Dump (Minidump) is configured..." -ForegroundColor Cyan
$regPath = "HKLM:\SYSTEM\CurrentControlSet\Control\CrashControl"
Set-ItemProperty -Path $regPath -Name "CrashDumpEnabled" -Value 3  # 3 = Small memory dump
Set-ItemProperty -Path $regPath -Name "MinidumpDir" -Value "%SystemRoot%\Minidump"
Write-Host "Minidump configuration set." -ForegroundColor Green

# --- 4. Run System File Checker ---
Write-Host "`n[*] Running SFC /scannow (this may take several minutes)..." -ForegroundColor Cyan
sfc /scannow

# --- 5. Run DISM health restore ---
Write-Host "`n[*] Running DISM RestoreHealth..." -ForegroundColor Cyan
DISM /Online /Cleanup-Image /RestoreHealth

# --- 6. Check disk for errors (schedule on next reboot) ---
Write-Host "`n[*] Scheduling CHKDSK on next reboot for C: drive..." -ForegroundColor Cyan
echo Y | chkdsk C: /f /r /x

# --- 7. List recently installed drivers (last 30 days) ---
Write-Host "`n[*] Drivers installed/updated in the last 30 days:" -ForegroundColor Cyan
$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. Check disk SMART status via PowerShell ---
Write-Host "`n[*] Checking physical disk reliability counters..." -ForegroundColor Cyan
Get-PhysicalDisk | Get-StorageReliabilityCounter |`
    Select-Object DeviceId, Temperature, Wear, ReadErrorsTotal, WriteErrorsTotal, PowerOnHours | Format-Table -AutoSize

# --- 9. Check for overheating (requires OpenHardwareMonitor WMI or use alternative) ---
Write-Host "`n[*] Checking Windows thermal events in last 7 days..." -ForegroundColor Cyan
Get-WinEvent -FilterHashtable @{LogName='System'; ProviderName='Microsoft-Windows-Kernel-Processor-Power'} -MaxEvents 20 -ErrorAction SilentlyContinue |`
    Where-Object { $_.LevelDisplayName -eq 'Warning' -or $_.LevelDisplayName -eq 'Error' } |`
    Select-Object TimeCreated, Message | Format-List

# --- 10. Enable Driver Verifier for third-party drivers (OPTIONAL - will cause intentional crashes) ---
# Uncomment ONLY if you want to identify a specific buggy driver
# verifier /standard /driver <drivername.sys>
# To reset after identifying the driver: verifier /reset

Write-Host "`n[+] Diagnostic complete. Review output above and check C:\Windows\Minidump with WinDbg for deeper analysis." -ForegroundColor Green
Write-Host "[+] WinDbg command to analyze dump: !analyze -v" -ForegroundColor Green
Write-Host "[!] Reboot required for CHKDSK and some fixes to take effect." -ForegroundColor Yellow

Error Medic Editorial

The Error Medic Editorial team is composed of senior DevOps engineers, SREs, and Windows system administrators with 10+ years of experience diagnosing kernel crashes, BSOD stop errors, and OS-level failures across enterprise and consumer Windows environments. Our guides are tested on real hardware and validated against official Microsoft documentation, Windows Internals research, and community-verified solutions from Stack Overflow and the Microsoft Tech Community.

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.