Why does Windows 11 BSOD after a Windows Update?

Windows 11 cumulative updates occasionally ship with driver incompatibilities or kernel regressions that trigger BSODs. This is well-documented on Microsoft's known issues page and Reddit communities. The immediate fix is to uninstall the offending KB update via Settings → Windows Update → Update History → Uninstall Updates. After uninstalling, pause updates for 1–2 weeks until Microsoft releases a patched version. If you cannot boot, access WinRE by force-shutting down 3 times and use DISM from the recovery command prompt to remove the package.

What causes the MEMORY_MANAGEMENT BSOD in Windows 11?

The MEMORY_MANAGEMENT stop code (0x0000001A) indicates a serious fault in Windows' memory management subsystem. The most common causes are: (1) Defective RAM modules or incompatible RAM running at unsupported XMP/EXPO speeds, (2) outdated or corrupt chipset/storage drivers, (3) overclocking instability, and (4) Windows system file corruption. Start by running Windows Memory Diagnostic (mdsched.exe) and MemTest86. If RAM passes, run SFC /scannow and DISM /RestoreHealth. Also try resetting RAM to JEDEC standard speeds in BIOS by disabling XMP/EXPO.

How do I fix the PFN_LIST_CORRUPT BSOD on Windows 11?

PFN_LIST_CORRUPT (0x0000004E) means the Page Frame Number database, which tracks physical memory pages, has become corrupted. This is almost always a hardware memory issue. Steps: (1) Run MemTest86 for at least 2 full passes. (2) Test with one RAM stick at a time, trying each stick in different slots. (3) Check your RAM is on your motherboard's QVL (Qualified Vendor List). (4) Disable XMP/EXPO in BIOS and run at stock speeds. (5) Update motherboard firmware (BIOS/UEFI). (6) Run SFC and DISM to rule out software corruption. If the error persists, the RAM likely needs to be replaced.

How do I fix KERNEL_SECURITY_CHECK_FAILURE on Windows 11?

KERNEL_SECURITY_CHECK_FAILURE (0x00000139) occurs when a driver or application violates kernel security rules, often caused by: (1) Outdated or incompatible drivers — especially GPU, antivirus kernel drivers, or VPN drivers. (2) Memory corruption. (3) Overclocking. Fix steps: Boot into Safe Mode and check if the error stops — if it does, a third-party driver is the cause. Use WinDbg or WhoCrashed to identify the faulting .sys file from the minidump at C:\Windows\Minidump\. Uninstall or roll back that driver. Also run SFC /scannow and check if any third-party antivirus or kernel-level software (anti-cheat programs, VPN drivers) was recently updated.

How do I read BSOD logs in Windows 11?

Windows 11 saves crash information in two places: (1) Minidump files at C:\Windows\Minidump\ — these are the most detailed and can be opened with WinDbg (type !analyze -v) or analyzed automatically with the free WhoCrashed tool. (2) Event Viewer — press Win + X, open Event Viewer, go to Windows Logs → System, and look for Event ID 1001 (BugCheck) or Event ID 41 (Kernel-Power). The BugCheck event shows the stop code in hexadecimal (e.g., 0x0000001a = MEMORY_MANAGEMENT). Always read the minidump first, as it identifies the exact driver or module that caused the crash.

Windows 11 BSOD: Complete Fix Guide for 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, and KERNEL_SECURITY_CHECK_FAILURE. Step-by-step diagnosis and repair guide.

Last updated: March 1, 2026

Last verified: March 1, 2026

2,086 words

Key Takeaways

Root Cause 1: Faulty or incompatible RAM is the leading cause of MEMORY_MANAGEMENT and PFN_LIST_CORRUPT BSODs — run Windows Memory Diagnostic or MemTest86 to confirm.
Root Cause 2: Corrupt or outdated drivers (especially GPU, NIC, and storage drivers) trigger KERNEL_SECURITY_CHECK_FAILURE and general BSODs, particularly after a Windows 11 update.
Root Cause 3: Recent Windows 11 cumulative updates (e.g., KB5034765, KB5035853) have introduced BSOD regressions — uninstalling the offending update via DISM or Settings is often an immediate fix.
Root Cause 4: Corrupted system files or a damaged Windows image can cause repeated startup BSODs — SFC /scannow and DISM /RestoreHealth resolve the majority of these cases.
Quick Fix Summary: Boot into Safe Mode, read the minidump log with WinDbg or WhoCrashed, identify the faulting module, then target the fix (driver rollback, RAM replacement, update uninstall, or SFC/DISM repair).

Windows 11 BSOD Fix Approaches Compared
Method	When to Use	Time	Risk
Read BSOD Minidump (WinDbg / WhoCrashed)	First step — always; identifies the exact faulting module	5–15 min	None
Uninstall Recent Windows Update (DISM/Settings)	BSOD started after a cumulative update (e.g., KB5034765)	10–20 min	Low
Roll Back or Reinstall Driver	Minidump points to a driver file (e.g., nvlddmkm.sys, iaStorA.sys)	15–30 min	Low
Run Windows Memory Diagnostic / MemTest86	MEMORY_MANAGEMENT or PFN_LIST_CORRUPT stop codes	30 min – 8 hr	None
SFC /scannow + DISM /RestoreHealth	Corrupt system files, BSOD on startup, no clear driver cause	20–40 min	Very Low
Check Disk (CHKDSK)	Storage-related BSODs (NTFS_FILE_SYSTEM, BAD_POOL_HEADER)	15–60 min	Low
Reset / Repair Windows 11 Install	All other methods failed; repeated BSODs on startup	60–120 min	Medium (keeps files)
Replace RAM / SSD Hardware	Memory diagnostic confirms hardware failure	30–60 min	Low (hardware swap)

Understanding Windows 11 BSOD Errors

A Blue Screen of Death (BSOD) in Windows 11 is a kernel-level stop error that halts the system to prevent data corruption or hardware damage. The screen displays a stop code such as:

MEMORY_MANAGEMENT (0x0000001A)
PFN_LIST_CORRUPT (0x0000004E)
KERNEL_SECURITY_CHECK_FAILURE (0x00000139)
SYSTEM_SERVICE_EXCEPTION (0x0000003B)
IRQL_NOT_LESS_OR_EQUAL (0x0000000A)
CRITICAL_PROCESS_DIED (0x000000EF)
PAGE_FAULT_IN_NONPAGED_AREA (0x00000050)

Windows 11 writes a minidump file to C:\Windows\Minidump\ every time a BSOD occurs. This file is the single most important artifact for diagnosing the root cause.

Step 1: Collect the BSOD Log (Minidump)

Before making any changes, read the crash dump to identify the faulting module.

Option A — WhoCrashed (GUI, easiest):

Download WhoCrashed Free from resplendence.com.
Run it and click Analyze.
The report will show the faulting driver, e.g.: nvlddmkm.sys (NVIDIA), iaStorA.sys (Intel RST), ntoskrnl.exe (kernel itself).

Option B — WinDbg (Microsoft, authoritative):

Install WinDbg from the Microsoft Store or Windows SDK.
Open the latest .dmp file from C:\Windows\Minidump\.
In the command window, type: !analyze -v
Look for the MODULE_NAME and IMAGE_NAME fields.

Option C — Event Viewer:

Press Win + X → Event Viewer.
Navigate to Windows Logs → System.
Filter by Critical events around the time of the crash.
Look for Event ID 41 (Kernel-Power unexpected shutdown) or 1001 (BugCheck).

Step 2: Boot into Safe Mode (If BSOD Occurs on Startup)

If Windows 11 BSODs before reaching the desktop:

Force-shutdown the PC 3 times during boot to trigger Windows Recovery Environment (WinRE).
Go to Troubleshoot → Advanced Options → Startup Settings → Restart.
Press F4 to boot into Safe Mode (or F5 for Safe Mode with Networking).

Alternatively, from an installation USB:

bcdedit /set {default} safeboot minimal

To exit Safe Mode later:

bcdedit /deletevalue {default} safeboot

Step 3: Fix BSOD After Windows 11 Update

If the BSOD started after installing a cumulative update:

Via Settings:

Settings → Windows Update → Update History → Uninstall Updates.
Sort by date and uninstall the most recent KB package.

Via Command Line (DISM):

dism /online /get-packages /format:table
dism /online /remove-package /packagename:Package_for_RollupFix~...

Via WinRE Command Prompt:

dism /image:C:\ /get-packages
dism /image:C:\ /remove-package /packagename:<KB_NAME>

After the rollback, pause updates in Settings to prevent the same update from reinstalling.

Step 4: Roll Back or Reinstall Drivers

If the minidump points to a driver file:

Roll back via Device Manager:

Press Win + X → Device Manager.
Find the device associated with the faulting driver (e.g., Display Adapters for nvlddmkm.sys).
Right-click → Properties → Driver → Roll Back Driver.

Clean driver reinstall (GPU example):

Download Display Driver Uninstaller (DDU) from Wagnardsoft.
Boot into Safe Mode.
Run DDU and select Clean and Restart.
After reboot, install the latest stable driver from the GPU vendor site.

For Intel RST / storage drivers causing iaStorA.sys crashes:

pnputil /remove-device /deviceid "PCI\VEN_8086..."

Then reinstall from the Intel driver support site.

Step 5: Repair System Files (SFC + DISM)

Run these commands in an elevated Command Prompt or PowerShell:

# Step 1: Repair Windows image
DISM /Online /Cleanup-Image /RestoreHealth

# Step 2: Scan and repair system files
sfc /scannow

# Step 3: Review SFC results
findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log | more

If SFC reports it could not repair files, run DISM first, then SFC again.

Step 6: Diagnose RAM (MEMORY_MANAGEMENT / PFN_LIST_CORRUPT)

Windows Memory Diagnostic (built-in):

Press Win + R → type mdsched.exe → Restart now and check for problems.
Review results after reboot in Event Viewer → Windows Logs → System → search for MemoryDiagnostics-Results.

MemTest86 (comprehensive, bootable):

Download MemTest86 from memtest86.com.
Flash to USB with Rufus.
Boot from USB and run at least 2 full passes (8+ passes recommended for conclusive results).
Any errors = faulty RAM. Try removing one stick at a time to isolate the bad module.

Test RAM slots with a single stick:

Remove all but one RAM stick.
Boot and observe stability.
Rotate through sticks and slots to identify the faulty component.

Step 7: Check Disk Health (Storage-Related BSODs)

# Check and repair disk (schedule for next reboot if C: is in use)
chkdsk C: /f /r /x

# View SMART data via PowerShell
Get-PhysicalDisk | Get-StorageReliabilityCounter | Select-Object DeviceId, Wear, ReadErrorsTotal, WriteErrorsTotal

# Or use wmic for quick SMART status
wmic diskdrive get model,status

If the disk reports Pred Fail or CHKDSK finds bad sectors, back up data immediately and replace the drive.

Step 8: Reset or Repair Windows 11 Install

If all else fails and BSODs persist on startup:

Option A — Startup Repair (WinRE):

Boot from WinRE → Troubleshoot → Advanced Options → Startup Repair.

Option B — Reset This PC (keeps files):

Settings → System → Recovery → Reset this PC → Keep my files.

Option C — In-place upgrade repair (ISO):

Download the Windows 11 ISO from Microsoft.
Mount it and run setup.exe.
Choose Upgrade this PC now and select Keep personal files and apps.

This method reinstalls Windows system files without touching user data or applications and resolves even deeply corrupted system states.

Frequently Asked Questions

powershell

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

# --- 1. List recent minidump files ---
Write-Host "=== Recent Minidump Files ==="
Get-ChildItem -Path "$env:SystemRoot\Minidump" -Filter "*.dmp" -ErrorAction SilentlyContinue |
    Sort-Object LastWriteTime -Descending |
    Select-Object Name, LastWriteTime, @{N='SizeMB';E={[math]::Round($_.Length/1MB,2)}} |
    Format-Table -AutoSize

# --- 2. Read last BSOD stop code from Event Log ---
Write-Host "`n=== Last BugCheck Event (Event ID 1001) ==="
Get-WinEvent -FilterHashtable @{LogName='System'; Id=1001} -MaxEvents 5 -ErrorAction SilentlyContinue |
    Select-Object TimeCreated, Message |
    Format-List

# --- 3. Check for kernel-power unexpected shutdown (Event ID 41) ---
Write-Host "`n=== Kernel-Power Critical Events (Event ID 41) ==="
Get-WinEvent -FilterHashtable @{LogName='System'; Level=1; Id=41} -MaxEvents 5 -ErrorAction SilentlyContinue |
    Select-Object TimeCreated, Message |
    Format-List

# --- 4. Run DISM to repair Windows image ---
Write-Host "`n=== Running DISM RestoreHealth ==="
Start-Process -FilePath "dism.exe" -ArgumentList "/Online /Cleanup-Image /RestoreHealth" -Wait -NoNewWindow

# --- 5. Run SFC scan ---
Write-Host "`n=== Running SFC Scannow ==="
Start-Process -FilePath "sfc.exe" -ArgumentList "/scannow" -Wait -NoNewWindow

# --- 6. Show SFC results from CBS log ---
Write-Host "`n=== SFC Results (last 20 lines) ==="
$cbsLog = "$env:SystemRoot\Logs\CBS\CBS.log"
if (Test-Path $cbsLog) {
    Get-Content $cbsLog | Select-String "\[SR\]" | Select-Object -Last 20
} else {
    Write-Host "CBS.log not found."
}

# --- 7. Check disk SMART status ---
Write-Host "`n=== Physical Disk SMART Status ==="
Get-PhysicalDisk | Get-StorageReliabilityCounter |
    Select-Object DeviceId, Wear, ReadErrorsTotal, WriteErrorsTotal, Temperature |
    Format-Table -AutoSize

# --- 8. List recently installed Windows Updates ---
Write-Host "`n=== Recent Windows Updates (last 10) ==="
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 10 |
    Select-Object HotFixID, InstalledOn, Description |
    Format-Table -AutoSize

# --- 9. List recently installed drivers ---
Write-Host "`n=== Recently Modified Drivers (last 7 days) ==="
Get-ChildItem -Path "$env:SystemRoot\System32\drivers" -Filter "*.sys" |
    Where-Object { $_.LastWriteTime -gt (Get-Date).AddDays(-7) } |
    Select-Object Name, LastWriteTime |
    Format-Table -AutoSize

# --- 10. Schedule CHKDSK on next reboot ---
# Uncomment the line below to schedule a disk check:
# Start-Process -FilePath "chkdsk.exe" -ArgumentList "C: /f /r /x" -Verb RunAs

Write-Host "`n=== Diagnostic Complete ==="
Write-Host "Review the output above and the minidump files with WinDbg or WhoCrashed for root cause analysis."
Write-Host "WinDbg command: !analyze -v"
Write-Host "WhoCrashed download: https://www.resplendence.com/whocrashed"

Error Medic Editorial

The Error Medic Editorial team is composed of senior DevOps engineers, SREs, and Windows systems administrators with 10+ years of experience diagnosing kernel-level failures, managing enterprise Windows fleets, and writing incident post-mortems. Every troubleshooting guide is tested against real crash dumps and verified against Microsoft's official documentation 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.