Why is my Windows 11 PC getting a BSOD on startup every time it boots?

A BSOD on startup is usually caused by corrupt system files, a failed Windows Update, a bad driver loading at boot, or a failing storage drive. Boot into Safe Mode by holding Shift at the login screen and clicking Restart > Troubleshoot > Advanced Options > Startup Settings. From Safe Mode, run 'sfc /scannow' and 'DISM /Online /Cleanup-Image /RestoreHealth', roll back the latest Windows Update, and check disk health with 'chkdsk C: /r /f'. If you cannot reach Safe Mode, boot from a Windows 11 USB and use Startup Repair.

How do I read a BSOD log in Windows 11 to find out what caused the crash?

Windows 11 stores crash minidumps at C:\Windows\Minidump\ and writes events to the System log. Open Event Viewer (eventvwr.msc), go to Windows Logs > System, and filter for Event ID 1001 (BugCheck) to see the stop code. For a detailed driver-level analysis, install WinDbg from the Microsoft Store, open the .dmp file, and run '!analyze -v'. This command identifies the exact driver or module that caused the crash in the MODULE_NAME and IMAGE_NAME fields.

Windows 11 keeps getting a BSOD after a Windows Update — how do I fix it?

Go to Settings > Windows Update > Update History > Uninstall Updates and remove the most recently installed Cumulative Update. You can also open an elevated PowerShell and run 'DISM /online /get-packages /format:table' to list all installed packages, then remove the problematic KB using 'DISM /online /remove-package /packagename: '. After uninstalling, pause Windows Updates and check the Microsoft support forums or Windows health dashboard (status.windows.com) to confirm whether a fix has been issued.

What causes MEMORY_MANAGEMENT and PFN_LIST_CORRUPT BSODs in Windows 11?

Both MEMORY_MANAGEMENT (0x0000001A) and PFN_LIST_CORRUPT (0x0000004E) stop codes almost exclusively indicate faulty RAM, incorrect RAM voltage or timing settings (XMP/EXPO profiles), or mismatched memory modules. Start by reseating your RAM sticks and testing one module at a time. Run Windows Memory Diagnostic (mdsched.exe) for a quick test, or MemTest86 from a bootable USB for comprehensive testing. If you use XMP in BIOS, try disabling it and running at stock JEDEC speeds. Rarely, these errors can also stem from a failing storage controller.

How do I fix KERNEL_SECURITY_CHECK_FAILURE BSOD in Windows 11?

KERNEL_SECURITY_CHECK_FAILURE (0x00000139) means a driver violated kernel data structure integrity checks. Boot into Safe Mode and use WinDbg to analyze the latest minidump with '!analyze -v' to find the offending driver name. Common culprits include outdated GPU drivers, antivirus kernel components, and network drivers. Uninstall or roll back the identified driver via Device Manager. For GPU drivers, use Display Driver Uninstaller (DDU) in Safe Mode for a clean removal. Also run 'sfc /scannow' to rule out corrupt system files. If the error persists, enable Driver Verifier ('verifier /standard /all') to isolate the specific driver.

Windows 11 BSOD (Blue Screen of Death): Fix 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 with step-by-step commands and log analysis.

Last updated: March 1, 2026

Last verified: March 1, 2026

2,211 words

Key Takeaways

Root cause 1: Faulty or incompatible RAM is the leading trigger for MEMORY_MANAGEMENT and PFN_LIST_CORRUPT BSODs — run Windows Memory Diagnostic or MemTest86 immediately.
Root cause 2: Corrupt or outdated drivers (especially GPU, NIC, and storage drivers) cause KERNEL_SECURITY_CHECK_FAILURE and post-update BSODs on Windows 11.
Root cause 3: Damaged system files, botched Windows Update patches, or disk errors can destabilize the kernel and cause BSODs on startup or after login.
Quick fix summary: Boot into Safe Mode, read the BSOD stop code from Event Viewer or WinDbg, roll back the most recent driver or Windows Update, run SFC /scannow and DISM, test RAM, and check disk health with chkdsk.

Fix Approaches Compared
Method	When to Use	Time	Risk
Roll back Windows Update (Settings > Windows Update > Update History)	BSOD started immediately after a Windows Update patch	5–10 min	Low
Roll back device driver (Device Manager)	BSOD after GPU, NIC, or storage driver update	5–15 min	Low
SFC /scannow + DISM /RestoreHealth	Corrupt system files suspected; BSOD on startup or random crashes	20–45 min	Very Low
Windows Memory Diagnostic / MemTest86	MEMORY_MANAGEMENT or PFN_LIST_CORRUPT stop codes	30 min – 8 hrs	None
chkdsk /r /f	BSOD with disk-related stop codes or failing SSD/HDD	30 min – 2 hrs	Low
Clean boot / disable third-party services	BSOD caused by conflicting software or antivirus	15–30 min	Low
WinDbg crash dump analysis	Stop code unclear; need root-cause driver/module name	15–30 min	None
Windows 11 Startup Repair / Reset	System unbootable; all other fixes failed	30–90 min	Medium (data loss possible on Reset)

Understanding Windows 11 BSOD Errors

A Blue Screen of Death (BSOD) in Windows 11 is a kernel-level stop error that halts the OS to prevent hardware or data damage. Unlike Windows 10, Windows 11's BSOD screen shows a QR code and a simplified message, but the underlying stop codes remain the same. The most common stop codes users encounter are:

MEMORY_MANAGEMENT (0x0000001A) — RAM corruption or bad memory pages
PFN_LIST_CORRUPT (0x0000004E) — Page Frame Number list is corrupted, almost always a RAM issue
KERNEL_SECURITY_CHECK_FAILURE (0x00000139) — A driver violated kernel security checks
SYSTEM_SERVICE_EXCEPTION (0x0000003B) — A system service threw an unhandled exception
IRQL_NOT_LESS_OR_EQUAL (0x0000000A) — A driver accessed memory at an incorrect IRQL
CRITICAL_PROCESS_DIED (0x000000EF) — A critical Windows process terminated unexpectedly

Step 1: Collect the BSOD Stop Code and Crash Dump

Before fixing anything, identify exactly which stop code triggered the BSOD. Windows 11 writes a minidump to C:\Windows\Minidump\ after each crash.

Method A — Event Viewer:

Press Win + R, type eventvwr.msc, and press Enter.
Navigate to Windows Logs > System.
Filter by Event ID 41 (Kernel-Power) and Event ID 1001 (BugCheck).
The BugCheck event contains the stop code in hexadecimal (e.g., 0x0000001A).

Method B — WinDbg (most reliable): Install WinDbg from the Microsoft Store or the Windows SDK. Open a crash dump:

windbg -z C:\Windows\Minidump\<filename>.dmp

Then run:

!analyze -v

Look for the FAILURE_BUCKET_ID and MODULE_NAME fields — these pinpoint the offending driver or module.

Method C — PowerShell one-liner:

Get-WinEvent -LogName System | Where-Object {$_.Id -eq 1001} | Select-Object -First 10 | Format-List TimeCreated, Message

Step 2: Fix BSOD After Windows 11 Update

If the BSOD started immediately after installing a Windows Update, roll back the patch:

Boot into Safe Mode: Hold Shift while clicking Restart > Troubleshoot > Advanced Options > Startup Settings > Enable Safe Mode.
Go to Settings > Windows Update > Update History > Uninstall Updates.
Identify the most recently installed Cumulative Update (KB number) and click Uninstall.
Alternatively, use DISM from an elevated PowerShell:

dism /online /get-packages /format:table
dism /online /remove-package /packagename:<PackageName>

After rolling back, pause Windows Updates (Settings > Windows Update > Advanced Options > Pause Updates) until Microsoft releases a fix.

Step 3: Fix Driver-Related BSODs (KERNEL_SECURITY_CHECK_FAILURE)

The stop code KERNEL_SECURITY_CHECK_FAILURE (0x00000139) almost always points to a misbehaving driver. Common culprits are GPU drivers (NVIDIA/AMD), network adapter drivers, and antivirus kernel components.

Boot into Safe Mode with Networking.
Open Device Manager (devmgmt.msc).
Right-click the suspected device > Properties > Driver > Roll Back Driver.
If rollback is unavailable, uninstall the driver and reboot — Windows will install a generic driver.
For GPU drivers, use DDU (Display Driver Uninstaller) in Safe Mode for a clean removal before reinstalling the last known good driver version.
Use Driver Verifier to identify a misbehaving driver:

verifier /standard /all

Reboot. When the BSOD occurs, WinDbg will now show the exact faulty driver. After identifying it, disable Driver Verifier:

verifier /reset

Step 4: Fix MEMORY_MANAGEMENT and PFN_LIST_CORRUPT BSODs

These stop codes are almost exclusively RAM-related. Follow this sequence:

Reseat RAM: Power off, remove RAM sticks, clean gold contacts with an eraser, and reinsert firmly. If you have dual-channel kits, try one stick at a time.
Run Windows Memory Diagnostic: Press Win + R, type mdsched.exe. Choose "Restart now and check for problems." Review results in Event Viewer under Windows Logs > System, filtering for source MemoryDiagnostics-Results.
Run MemTest86 for comprehensive testing: Download from memtest86.com, create a bootable USB, and run for at least two full passes (ideally 8+ passes overnight).
Check XMP/EXPO profiles: If RAM is overclocked via XMP in BIOS, disable it and run at stock JEDEC speeds to test stability.
Check virtual memory settings: Right-click This PC > Properties > Advanced System Settings > Performance Settings > Advanced > Virtual Memory. Set to "System managed size" and remove any custom values.

Step 5: Repair System Files with SFC and DISM

Corrupt Windows system files cause random BSODs, especially on startup. Run these commands from an elevated Command Prompt or PowerShell:

# Step 1: DISM repairs the Windows image before SFC runs
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

# Step 2: SFC scans and repairs protected system files
sfc /scannow

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

If SFC reports errors it cannot fix, you may need to run it from Windows Recovery Environment (WinRE) by booting from a Windows 11 USB installer and opening Command Prompt.

Step 6: Check Disk Health

A failing SSD or HDD can cause BSODs, especially on startup. Check and repair disk errors:

# Schedule chkdsk on next reboot (C: drive)
chkdsk C: /r /f

# Check NVMe/SSD health with PowerShell
Get-PhysicalDisk | Select-Object FriendlyName, MediaType, OperationalStatus, HealthStatus

# For detailed SMART data, use CrystalDiskInfo (GUI) or wmic
wmic diskdrive get model,status,size

If SMART reports reallocated sectors, pending sectors, or uncorrectable errors, back up data immediately and replace the drive.

Step 7: Perform a Clean Boot

Third-party software (antivirus, virtualization tools, overlay software) can inject kernel-mode drivers that cause BSODs:

Press Win + R, type msconfig, go to Services tab.
Check Hide all Microsoft services, then click Disable all.
Go to Startup tab > Open Task Manager, disable all startup items.
Reboot. If BSOD stops, re-enable services in batches to isolate the culprit.

Step 8: Use Windows 11 Startup Repair or Reset

If the system fails to boot and all else fails:

Boot from a Windows 11 USB installer.
Select Repair your computer > Troubleshoot > Advanced Options > Startup Repair.
If Startup Repair fails, use System Restore to revert to a pre-BSOD restore point.
As a last resort, choose Reset this PC with the Keep my files option to reinstall Windows while preserving personal data.

Frequently Asked Questions

powershell

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

# --- 1. Get last 10 BugCheck events (crash stop codes) ---
Write-Host "`n[1] Recent BugCheck Events (Stop Codes)" -ForegroundColor Cyan
Get-WinEvent -LogName System -ErrorAction SilentlyContinue |
    Where-Object { $_.Id -eq 1001 -and $_.ProviderName -eq 'Microsoft-Windows-WER-SystemErrorReporting' } |
    Select-Object -First 10 TimeCreated, Message |
    Format-List

# --- 2. List minidump files for WinDbg analysis ---
Write-Host "`n[2] Crash Minidump Files" -ForegroundColor Cyan
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

# --- 3. Check system file integrity ---
Write-Host "`n[3] Running DISM Health Check..." -ForegroundColor Cyan
DISM /Online /Cleanup-Image /CheckHealth

Write-Host "`n[4] Running DISM RestoreHealth (requires internet)..." -ForegroundColor Cyan
DISM /Online /Cleanup-Image /RestoreHealth

Write-Host "`n[5] Running SFC scan..." -ForegroundColor Cyan
sfc /scannow

# --- 4. Check disk health ---
Write-Host "`n[6] Physical Disk Health Status" -ForegroundColor Cyan
Get-PhysicalDisk | Select-Object FriendlyName, MediaType, Size, OperationalStatus, HealthStatus | Format-Table -AutoSize

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

# --- 6. List recently installed Windows Updates ---
Write-Host "`n[8] Recently Installed Windows Updates (last 30 days)" -ForegroundColor Cyan
Get-HotFix | Where-Object { $_.InstalledOn -gt (Get-Date).AddDays(-30) } |
    Sort-Object InstalledOn -Descending |
    Select-Object HotFixID, Description, InstalledOn |
    Format-Table -AutoSize

# --- 7. List third-party kernel drivers (common BSOD sources) ---
Write-Host "`n[9] Third-Party Kernel Drivers Loaded" -ForegroundColor Cyan
Get-WmiObject Win32_SystemDriver |
    Where-Object { $_.PathName -notlike "*\Windows\System32\drivers\*" -and $_.State -eq 'Running' } |
    Select-Object Name, DisplayName, PathName |
    Format-Table -AutoSize

# --- 8. Check RAM via Windows Memory Diagnostic (schedules on reboot) ---
Write-Host "`n[10] To run Memory Diagnostic, execute:" -ForegroundColor Yellow
Write-Host "    mdsched.exe" -ForegroundColor White
Write-Host "    (Choose 'Restart now and check for problems')" -ForegroundColor White

# --- 9. Check for Driver Verifier status ---
Write-Host "`n[11] Driver Verifier Status" -ForegroundColor Cyan
verifier /query

# --- 10. Export System Event Log for offline analysis ---
Write-Host "`n[12] Exporting System Event Log to Desktop..." -ForegroundColor Cyan
$exportPath = "$env:USERPROFILE\Desktop\SystemEvents_$(Get-Date -Format 'yyyyMMdd_HHmmss').evtx"
wevtutil epl System $exportPath
Write-Host "    Exported to: $exportPath" -ForegroundColor Green

Write-Host "`n[DONE] Diagnostic complete. Review output above and check $exportPath for full logs." -ForegroundColor Green
Write-Host "[TIP] Open minidumps with WinDbg and run '!analyze -v' for detailed crash analysis." -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-level failures, crash dumps, and system instability across enterprise and consumer Windows environments. Our guides are built from real-world incident responses, WinDbg analysis sessions, and community-validated fixes.

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.