Error Medic

Windows 11 BSOD: Fix Blue Screen of Death Errors (Memory Management, PFN List Corrupt, Kernel Security Check Failure & More)

Fix Windows 11 BSOD errors including Memory Management, PFN List Corrupt & Kernel Security Check Failure. Step-by-step guide with real commands.

Last updated:
Last verified:
2,255 words
Key Takeaways
  • Faulty or incompatible RAM is the leading root cause of BSOD errors like MEMORY_MANAGEMENT (0x0000001A) and PFN_LIST_CORRUPT (0x0000004E) on Windows 11.
  • Corrupt or incompatible drivers — especially after a Windows 11 update — trigger KERNEL_SECURITY_CHECK_FAILURE (0x00000139) and SYSTEM_SERVICE_EXCEPTION BSODs.
  • Outdated firmware, overclocked hardware, and corrupted system files (fixed via SFC and DISM) are frequent secondary causes of BSODs on startup and after updates.
  • Quick fix summary: Boot into Safe Mode, read the BSOD stop code from Event Viewer or WinDbg, run SFC /scannow and DISM, update or roll back drivers, run Windows Memory Diagnostic, and uninstall recent Windows updates if the BSOD appeared after an update.
Fix Approaches Compared
MethodWhen to UseTimeRisk
SFC /scannow + DISMCorrupted system files, BSOD after update10-20 minLow
Driver rollback / updateBSOD after driver or Windows update, KERNEL_SECURITY_CHECK_FAILURE5-15 minLow
Windows Memory Diagnostic / MemTest86MEMORY_MANAGEMENT or PFN_LIST_CORRUPT stop codes30-120 minNone
Uninstall recent Windows Update (KB)BSOD appeared immediately after Windows Update5-10 minLow
Clean boot / Safe Mode isolationUnknown cause, BSOD on startup15-30 minNone
System RestoreBSOD started after a specific date / software install20-40 minMedium
Reset / Repair Install (in-place upgrade)All other methods failed, frequent BSODs60-120 minMedium
Replace RAM / check hardwareMemTest86 reports errors, multiple RAM-related BSODsVariableLow-Medium

Understanding Windows 11 BSOD Errors

A Blue Screen of Death (BSOD) on Windows 11 is a critical kernel-level stop error displayed when Windows encounters a fatal condition it cannot recover from. The screen shows a stop code (e.g., MEMORY_MANAGEMENT, PFN_LIST_CORRUPT, KERNEL_SECURITY_CHECK_FAILURE) and a QR code. Understanding the stop code is the first step to a targeted fix.

Common Windows 11 BSOD Stop Codes and Their Meanings

  • MEMORY_MANAGEMENT (0x0000001A): Indicates a severe memory management error. Usually caused by faulty RAM, incompatible RAM speeds (XMP/EXPO profiles), or corrupt page file.
  • PFN_LIST_CORRUPT (0x0000004E): Page Frame Number list corruption — almost always a RAM defect or a malfunctioning storage driver corrupting memory structures.
  • KERNEL_SECURITY_CHECK_FAILURE (0x00000139): A data structure integrity violation detected by the kernel. Commonly triggered by outdated or incompatible drivers (especially after Windows 11 updates), antivirus software, or hardware issues.
  • SYSTEM_SERVICE_EXCEPTION (0x0000003B): A system service threw an unhandled exception; frequently caused by corrupt drivers or conflicting software.
  • CRITICAL_PROCESS_DIED (0x000000EF): A critical OS process terminated unexpectedly, often due to corrupt system files or a failing drive.
  • IRQL_NOT_LESS_OR_EQUAL (0x0000000A): A driver attempted to access memory at an IRQL too high; almost always a driver bug.

Step 1: Read the BSOD Log in Windows 11

Before applying any fix, identify the exact stop code and the failing module.

Method A — Event Viewer:

  1. Press Win + X → select Event Viewer.
  2. Navigate to Windows Logs → System.
  3. Filter by Event ID 41 (Kernel-Power, unexpected shutdown) or Event ID 1001 (BugCheck).
  4. The event details show the stop code and the faulting module.

Method B — WinDbg (most accurate): Open an elevated PowerShell and run:

Get-EventLog -LogName System -Source "Microsoft-Windows-WER-SystemErrorReporting" -Newest 10

Or open the minidump (located at C:\Windows\Minidump\*.dmp) with WinDbg from the Microsoft Store and run !analyze -v for a full analysis.

Method C — BlueScreenView (free utility): Download NirSoft BlueScreenView, point it at C:\Windows\Minidump, and it will parse all crash dumps into a readable table showing the stop code, date, and faulting driver.


Step 2: Boot Into Safe Mode (When BSOD Occurs on Startup)

If Windows 11 won't boot due to BSOD on startup:

  1. Force three consecutive hard shutdowns (hold power button) to trigger Automatic Repair.
  2. Choose Troubleshoot → Advanced Options → Startup Settings → Restart.
  3. Press 4 for Safe Mode or 5 for Safe Mode with Networking.
  4. Once in Safe Mode, proceed with the diagnostic steps below.

Step 3: Run System File Checker and DISM

Corrupt system files are a frequent cause of BSODs, especially after Windows 11 updates.

Open an elevated Command Prompt or PowerShell as Administrator and run:

:: Step 1 - Check and repair system files
sfc /scannow

:: Step 2 - Repair the Windows image (if SFC reports unfixable corruption)
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

:: Step 3 - Run SFC again after DISM
sfc /scannow

Reboot after completion and check if the BSOD recurs.


Step 4: Update or Roll Back Drivers

KERNEL_SECURITY_CHECK_FAILURE and similar stop codes after a Windows update almost always point to an incompatible driver.

Roll back a driver:

  1. Press Win + XDevice Manager.
  2. Expand the relevant category (Display adapters, Network adapters, etc.).
  3. Right-click the device → Properties → Driver tab → Roll Back Driver.

Update all drivers via PowerShell:

# List devices with driver issues
Get-WmiObject Win32_PnPEntity | Where-Object {$_.ConfigManagerErrorCode -ne 0} | Select-Object Name, ConfigManagerErrorCode

# Update a specific driver using PnPUtil (replace with actual .inf path)
pnputil /add-driver "C:\Drivers\driver.inf" /install

For GPU drivers (NVIDIA/AMD), always download directly from the manufacturer website and perform a clean install to remove old driver remnants.


Step 5: Fix Windows 11 BSOD After Update — Uninstall Problematic KB

If the BSOD started immediately after a Windows Update, identify and remove the update:

# List recent Windows Updates
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 10

# Uninstall a specific update (replace KBxxxxxxx with actual KB number)
wusa /uninstall /kb:5034765 /quiet /norestart

Alternatively: Settings → Windows Update → Update History → Uninstall Updates, then select the most recently installed KB.

After removal, pause Windows Updates temporarily: Settings → Windows Update → Pause Updates until a fixed update is released.


Step 6: Fix Memory Management and PFN List Corrupt BSODs

These stop codes point directly at RAM.

Run Windows Memory Diagnostic:

:: Launch the built-in tool (requires reboot)
mdsched.exe

Choose "Restart now and check for problems." Windows will run two passes and report results in Event Viewer under Windows Logs → System → MemoryDiagnostics-Results (Event ID 1201).

Run MemTest86 for thorough testing: Download MemTest86 (free), write to a USB drive, boot from it, and run at least 2 full passes (each pass ~30-60 min per 8 GB of RAM). Any errors = faulty RAM that must be replaced.

Additional RAM fixes:

  • If you have XMP/EXPO profiles enabled in BIOS, try disabling them and running RAM at stock JEDEC speeds.
  • Try reseating RAM modules. If you have multiple sticks, test each one individually to isolate the faulty module.
  • Check for RAM compatibility with your specific Windows 11 motherboard model.

Step 7: Check Storage Health

A failing SSD or HDD can corrupt memory structures and cause PFN_LIST_CORRUPT or CRITICAL_PROCESS_DIED.

# Check drive health via CrystalDiskInfo or Windows built-in
# Run CHKDSK on C: drive (schedules on next reboot)
chkdsk C: /f /r /x

# Check SMART status via PowerShell
Get-PhysicalDisk | Select-Object FriendlyName, OperationalStatus, HealthStatus, Size

If HealthStatus returns Warning or Unhealthy, replace the drive immediately.


Step 8: Perform a System Restore or In-Place Upgrade

System Restore (if a restore point exists):

  1. Press Win + R → type rstrui.exe → Enter.
  2. Select a restore point dated before the BSODs began.
  3. Click Finish and allow the system to restore.

In-place upgrade repair install (last resort): Download the Windows 11 ISO from Microsoft, mount it, and run setup.exe. Choose Keep personal files and apps. This reinstalls Windows without data loss and fixes deep system corruption.


Step 9: Check for Overclocking and Thermal Issues

Overclocking CPU or RAM beyond stable limits causes memory corruption BSODs. Enter BIOS and load Optimized Defaults to reset all overclocks. Also use HWiNFO64 or Core Temp to monitor CPU and GPU temperatures — sustained temps above 90°C (CPU) or 85°C (GPU) under load indicate thermal throttling that can trigger instability and BSODs.

Clean dust from heatsinks and fans, reapply thermal paste on the CPU if the system is over 3 years old.

Frequently Asked Questions

powershell
# ============================================================
# Windows 11 BSOD Diagnostic & Fix Script
# Run in an elevated PowerShell (Run as Administrator)
# ============================================================

# --- 1. Display last 10 BugCheck (BSOD) events from Event Log ---
Write-Host "=== Recent BSOD Events (Event ID 1001) ==="  -ForegroundColor Cyan
Get-WinEvent -LogName System | Where-Object { $_.Id -eq 1001 -and $_.ProviderName -eq 'Microsoft-Windows-WER-SystemErrorReporting' } | Select-Object -First 10 TimeCreated, Message | Format-List

# --- 2. List minidump files with timestamps ---
Write-Host "`n=== Minidump Files ==="  -ForegroundColor Cyan
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 (System File Checker) ==="  -ForegroundColor Cyan
Start-Process -FilePath "sfc.exe" -ArgumentList "/scannow" -Wait -NoNewWindow

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

# --- 5. Check for driver errors in Device Manager ---
Write-Host "`n=== Devices with Driver Errors ==="  -ForegroundColor Cyan
Get-WmiObject Win32_PnPEntity | Where-Object { $_.ConfigManagerErrorCode -ne 0 } | Select-Object Name, DeviceID, ConfigManagerErrorCode | Format-Table -AutoSize

# --- 6. List 10 most recent Windows Updates ---
Write-Host "`n=== 10 Most Recent Windows Updates ==="  -ForegroundColor Cyan
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 10 HotFixID, Description, InstalledOn | Format-Table -AutoSize

# --- 7. Schedule CHKDSK on next reboot ---
Write-Host "`n=== Scheduling CHKDSK on C: ==="  -ForegroundColor Cyan
echo Y | chkdsk C: /f /r

# --- 8. Check physical disk health ---
Write-Host "`n=== Physical Disk Health ==="  -ForegroundColor Cyan
Get-PhysicalDisk | Select-Object FriendlyName, MediaType, OperationalStatus, HealthStatus, @{N='SizeGB';E={[math]::Round($_.Size/1GB,1)}} | Format-Table -AutoSize

# --- 9. Launch Windows Memory Diagnostic (interactive) ---
Write-Host "`n=== Launching Windows Memory Diagnostic ==="  -ForegroundColor Yellow
Write-Host "Select 'Restart now and check for problems' in the dialog."
Start-Process mdsched.exe

# --- 10. Optional: Uninstall a specific KB update ---
# Uncomment and replace KB number before running
# $kb = "KB5034765"
# Write-Host "`n=== Uninstalling $kb ==="  -ForegroundColor Red
# wusa /uninstall /kb:$kb.Replace('KB','') /quiet /norestart

Write-Host "`n=== Diagnostic Complete. Review output above and reboot. ==="  -ForegroundColor Green
E

Error Medic Editorial

Error Medic Editorial is a team of senior DevOps engineers, SREs, and Windows systems administrators with over a decade of experience diagnosing and resolving operating system failures, BSOD stop errors, and enterprise infrastructure incidents. Our guides are based on real-world troubleshooting, official Microsoft documentation, and community-verified solutions tested on production systems.

Sources

Related Articles in Windows 11 Bsod

Explore More windows Guides