Windows 11 Blue Screen (BSOD) Fix: Stop Codes, Causes & Step-by-Step Solutions
Fix Windows 11 blue screen errors (BSOD) including KERNEL_SECURITY_CHECK_FAILURE, PFN_LIST_CORRUPT, CRITICAL_PROCESS_DIED & more. Step-by-step guide with comman
- Most Windows 11 BSODs are caused by faulty, outdated, or incompatible drivers — especially GPU drivers like nvlddmkm.sys, amdkmdag.sys, and network drivers like netio.sys or tcpip.sys.
- Hardware issues such as failing RAM, corrupted NTFS file system metadata, or overheating CPUs/GPUs trigger stop codes like MEMORY_MANAGEMENT (0x0000001A), PFN_LIST_CORRUPT (0x0000004E), and KERNEL_SECURITY_CHECK_FAILURE.
- Quick fix summary: Boot into Safe Mode, identify the stop code from Event Viewer or BlueScreenView, run SFC /scannow and DISM, update or roll back problematic drivers, and run Windows Memory Diagnostic — most BSODs are resolved within these five steps.
| Method | When to Use | Time | Risk |
|---|---|---|---|
| Update / Roll Back Driver | BSOD tied to specific .sys file (nvlddmkm.sys, amdkmdag.sys, netio.sys) | 5–15 min | Low |
| SFC /scannow + DISM | Corrupted system files, NTFS.sys, ntoskrnl.exe BSODs after update | 15–30 min | Low |
| Windows Memory Diagnostic / MemTest86 | MEMORY_MANAGEMENT, PFN_LIST_CORRUPT, BAD_POOL_CALLER stop codes | 30 min – 8 hrs | None |
| Clean Boot / Disable Startup Programs | Random or frequent BSODs, gaming BSODs, third-party software conflicts | 10–20 min | Low |
| Startup Repair / Recovery Environment | Blue screen loop on startup, 0xc000021a, INACCESSIBLE_BOOT_DEVICE | 15–45 min | Low |
| System Restore or Feature Update Rollback | BSOD started after a Windows 11 update or driver update | 20–60 min | Medium |
| Reset This PC / Clean Install | Persistent BSOD loop with no other fix working | 1–3 hrs | High (data loss possible) |
Understanding Windows 11 Blue Screen Errors (BSOD)
A Blue Screen of Death (BSOD), officially called a Stop Error or Bug Check, occurs when Windows 11 encounters a critical condition from which it cannot safely recover. The screen displays a QR code pointing to www.windows.com/stopcode and a stop code such as KERNEL_SECURITY_CHECK_FAILURE, CRITICAL_PROCESS_DIED, or a hex code like 0x0000004E. Since Windows 11, Insider builds may also show a Green Screen of Death — functionally identical to the BSOD.
Common stop codes and their primary suspects:
- KERNEL_SECURITY_CHECK_FAILURE — Corrupted drivers, RAM, or malware
- PFN_LIST_CORRUPT (0x0000004E) — Faulty RAM or storage driver
- BAD_POOL_CALLER (0x000000C2) — Driver writing to invalid memory pool
- MEMORY_MANAGEMENT (0x0000001A) — RAM hardware failure
- CRITICAL_PROCESS_DIED — Core Windows process crash, often after update
- SYSTEM_SERVICE_EXCEPTION (0x0000003B) — Driver or system service fault
- IRQL_NOT_LESS_OR_EQUAL (0x000000D1) — Driver accessing memory at wrong IRQL
- 0xC000021A — Winlogon or CSRSS process failure, often boot-loop
- INACCESSIBLE_BOOT_DEVICE — Storage driver or NVMe controller issue
- APC_INDEX_MISMATCH — Driver APC state mismatch, often audio/GPU driver
- WDF_VIOLATION — Windows Driver Framework violation
- DRIVER_POWER_STATE_FAILURE — Driver not handling sleep/wake correctly
- ATTEMPTED_WRITE_TO_READONLY_MEMORY — Driver overwriting protected memory
- DRIVER_OVERRAN_STACK_BUFFER — Stack buffer overflow in driver
- PDC_WATCHDOG_TIMEOUT — Power dependency coordinator timeout
- INTERNAL_POWER_ERROR — Power subsystem driver failure
- BUGCODE_NDIS_DRIVER — Network driver fault
- RDR_FILE_SYSTEM — Network redirector or SMB driver issue
Step 1: Read and Record the Stop Code
The first thing to do when Windows 11 shows a blue screen is note the exact stop code shown on screen. It will appear as both a human-readable name (e.g., KERNEL_SECURITY_CHECK_FAILURE) and sometimes a hex value. The QR code on screen links to https://www.windows.com/stopcode for general guidance.
If the screen flashes too fast to read:
- Press Win + R, type
sysdm.cpl, press Enter. - Go to Advanced → Startup and Recovery → Settings.
- Under System failure, uncheck Automatically restart — this lets you read the BSOD.
Step 2: Analyze the BSOD Log (Event Viewer & BlueScreenView)
Using Event Viewer:
- Press Win + X, select Event Viewer.
- Navigate to Windows Logs → System.
- Filter by Critical events. Look for Event ID 41 (unexpected shutdown) or 1001 (BugCheck).
- The BugCheck event will show the stop code and the faulting module.
Using BlueScreenView (free tool):
- Download BlueScreenView from NirSoft: https://www.nirsoft.net/utils/blue_screen_view.html
- It reads minidump files from
C:\Windows\Minidump\and displays the exact driver or module that caused the crash. - Look at the highlighted row in pink/red — that driver is the likely culprit.
Minidump location: C:\Windows\Minidump\*.dmp
Ensure minidumps are enabled:
- Run
sysdm.cpl→ Advanced → Startup and Recovery → Settings. - Set Write debugging information to Small memory dump (256 KB).
Step 3: Boot Into Safe Mode (If Stuck in BSOD Loop)
If Windows 11 keeps restarting to a blue screen:
- Force shut down 3 times in a row during boot — Windows will enter Automatic Repair mode.
- Click Advanced options → Troubleshoot → Advanced options → Startup Settings → Restart.
- Press 4 to enable Safe Mode or 5 for Safe Mode with Networking.
Alternatively, boot from a Windows 11 USB and select Repair your computer.
Step 4: Update or Roll Back Problematic Drivers
Most Windows 11 BSODs are driver-related. Common offenders include:
- nvlddmkm.sys — NVIDIA GPU driver
- amdkmdag.sys — AMD GPU driver
- netio.sys / tcpip.sys — Network stack
- ntfs.sys — File system driver
- stornvme.sys — NVMe storage driver
- dxgmms2.sys — DirectX graphics scheduler
- klhk.sys — Kaspersky antivirus driver
- vgk.sys — Valorant anti-cheat driver
- btha2dp.sys — Bluetooth audio driver
- cldflt.sys — OneDrive cloud filter driver
- fltmgr.sys — File system filter manager
- acpi.sys — ACPI/power management driver
- amifldrv64.sys — BIOS/UEFI flash driver
To update a driver:
- Press Win + X → Device Manager.
- Right-click the device → Update driver → Search automatically.
To roll back a driver:
- Device Manager → right-click device → Properties → Driver tab → Roll Back Driver.
For NVIDIA BSODs: Use DDU (Display Driver Uninstaller) in Safe Mode to cleanly remove the GPU driver, then reinstall the latest stable version from https://www.nvidia.com/drivers
For AMD BSODs: Use AMD Cleanup Utility, then reinstall from https://www.amd.com/support
Step 5: Repair System Files (SFC and DISM)
Corrupted Windows system files cause BSODs like CRITICAL_PROCESS_DIED, NTFS_FILE_SYSTEM, and SYSTEM_SERVICE_EXCEPTION. Run the following from an elevated Command Prompt:
sfc /scannow
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
Restart after completion and monitor for further crashes.
Step 6: Test RAM (For Memory-Related Stop Codes)
For MEMORY_MANAGEMENT, PFN_LIST_CORRUPT, BAD_POOL_CALLER:
Windows Memory Diagnostic (built-in):
- Press Win + R, type
mdsched.exe, press Enter. - Choose Restart now and check for problems.
- Review results in Event Viewer → System → filter for source MemoryDiagnostics-Results.
MemTest86 (more thorough):
- Download from https://www.memtest86.com
- Run at least 2 full passes. Any errors indicate faulty RAM.
- Try reseating RAM sticks or testing one stick at a time.
Step 7: Check Storage Health
For NTFS_FILE_SYSTEM, INACCESSIBLE_BOOT_DEVICE, stornvme.sys BSODs:
chkdsk C: /f /r /x
This schedules a disk check on the next reboot. Also check NVMe SSD health using the manufacturer's tool (Samsung Magician, WD Dashboard, CrystalDiskInfo).
Step 8: Fix Blue Screen After Windows 11 Update
If the BSOD started after a Windows Update:
- Boot into Safe Mode.
- Go to Settings → Windows Update → Update history → Uninstall updates.
- Remove the most recent cumulative update.
- Or use:
wusa /uninstall /kb:XXXXXXX(replace XXXXXXX with KB number).
For 0xC000021A stop code specifically — often caused by a failed update corrupting Winlogon or CSRSS:
- Boot from Windows 11 USB → Repair your computer → Command Prompt.
- Run
sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows - Then
bootrec /fixmbrandbootrec /fixboot.
Step 9: Brand/OEM-Specific BSOD Fixes
- Acer blue screen Windows 11: Update Acer Care Center and all Acer-specific drivers. Check for BIOS updates at https://www.acer.com/support
- Lenovo blue screen Windows 11: Update Lenovo Vantage, check for BIOS/UEFI updates, and disable "Intel Platform Trust Technology" if causing ACPI conflicts.
- VMware blue screen Windows 11: Ensure Hyper-V compatibility mode is enabled in VMware settings for Windows 11 guests.
- Gaming BSODs (vgk.sys, nvlddmkm.sys): Update game anti-cheat software, GPU drivers, and ensure your system meets thermal/power requirements.
Step 10: Reset or Reinstall Windows 11 (Last Resort)
If all else fails:
- Go to Settings → System → Recovery → Reset this PC.
- Choose Keep my files first. If BSOD persists, choose Remove everything.
- For unbootable systems, use Windows 11 installation media and perform a clean install.
Create Windows 11 installation media at: https://www.microsoft.com/software-download/windows11
Frequently Asked Questions
# ============================================================
# Windows 11 BSOD Diagnostic & Fix Commands
# Run all commands in an elevated Command Prompt (Run as Admin)
# ============================================================
# --- STEP 1: Check recent BSOD events in Event Log ---
wevtutil qe System /q:"*[System[Provider[@Name='Microsoft-Windows-WER-SystemErrorReporting'] and (EventID=1001)]]" /f:text /c:5
# --- STEP 2: Run System File Checker ---
sfc /scannow
# --- STEP 3: Run DISM to repair Windows image ---
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
# --- STEP 4: Check and repair disk (schedule for next reboot) ---
chkdsk C: /f /r /x
# --- STEP 5: Run Windows Memory Diagnostic ---
mdsched.exe
# --- STEP 6: Find stop code from most recent minidump using WinDbg (if installed) ---
# Install WinDbg from Microsoft Store first, then:
# windbg -z C:\Windows\Minidump\<latestdump>.dmp
# Inside WinDbg: !analyze -v
# --- STEP 7: List all installed drivers and export to file ---
driverquery /v /fo csv > C:\drivers_list.csv
# --- STEP 8: Check driver verifier status ---
verifier /query
# --- STEP 9: Enable Driver Verifier to catch problematic drivers (reboot required) ---
# WARNING: Only use temporarily -- may cause more BSODs until culprit found
verifier /standard /all
# To reset/disable Driver Verifier:
verifier /reset
# --- STEP 10: Uninstall a recent Windows Update by KB number ---
# Replace XXXXXXX with actual KB number from Update History
wusa /uninstall /kb:XXXXXXX /quiet /norestart
# --- STEP 11: Restore system from restore point (if available) ---
rstrui.exe
# --- STEP 12: Rebuild BCD (use in WinRE command prompt if boot fails) ---
bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd
# --- STEP 13: SFC scan offline (run from WinRE if system won't boot) ---
# Replace C: with actual Windows drive letter in WinRE
sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows
# --- STEP 14: Get BSOD minidump summary using PowerShell ---
Get-WinEvent -LogName System | Where-Object {$_.Id -eq 41} | Select-Object -First 10 TimeCreated, Message | Format-List
# --- STEP 15: Check for overheating (requires WMIC) ---
wmic /namespace:\\root\wmi PATH MSAcpi_ThermalZoneTemperature get CurrentTemperature
# Note: Divide result by 10 and subtract 273.15 to convert to Celsius
# --- STEP 16: Clean boot prep - disable non-Microsoft services ---
msconfig
# In System Configuration: Services tab > Hide all Microsoft services > Disable all > Apply > RestartError Medic Editorial
The Error Medic Editorial team consists of senior DevOps engineers, SREs, and Windows system administrators with over 15 years of combined experience diagnosing and resolving OS-level failures, driver conflicts, and system crashes across enterprise and consumer Windows environments. Our guides are built from real incident data, Microsoft documentation, and hands-on lab testing.
Sources
- https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-code-reference2
- https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/analyzing-a-kernel-mode-dump-file
- https://support.microsoft.com/en-us/windows/fix-blue-screen-errors-in-windows-11-b2e8e25e-e8a8-46e3-94a1-8ff40b3d0c0e
- https://www.nirsoft.net/utils/blue_screen_view.html
- https://learn.microsoft.com/en-us/windows-hardware/drivers/devtest/driver-verifier
- https://answers.microsoft.com/en-us/windows/forum/all/windows-11-blue-screen-errors/
- https://www.memtest86.com/