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

Understanding the Windows 11 Blue Screen of Death

A Blue Screen of Death (BSOD), officially called a Stop Error or Bug Check, occurs when Windows 11 encounters a fatal kernel-level fault it cannot safely recover from. The screen displays a QR code, a sad face emoji, a stop code string (e.g., CRITICAL_PROCESS_DIED), and a hex bug check code (e.g., 0x000000EF). Windows automatically writes a minidump file to C:\Windows\Minidump\ and a full memory dump to C:\Windows\MEMORY.DMP for post-mortem analysis.

Windows 11 22H2 introduced several regressions that elevated BSOD rates, particularly around Wi-Fi drivers (Intel AX series), certain AMD GPU driver builds, and the Windows Resilient File System (ReFS). If your BSODs began after upgrading to 22H2 or 23H2, driver compatibility and update conflicts are the first places to look.

Step 1: Capture the Stop Code and Minidump

Before fixing anything, record the exact stop code. If the machine reboots too fast to read it:

1. Go to Settings → System → About → Advanced system settings → Startup and Recovery → Settings.
2. Under "System failure," uncheck Automatically restart.
3. Set "Write debugging information" to Small memory dump (256 KB).

Now reproduce or wait for the next BSOD. The stop code appears in the format:

Your PC ran into a problem and needs to restart.
STOP CODE: MEMORY_MANAGEMENT
Failing module: ntoskrnl.exe

Common Windows 11 stop codes and their typical causes:

Step 2: Analyze the Minidump with WinDbg

Install WinDbg Preview from the Microsoft Store (free). Open a minidump:

1. Launch WinDbg → File → Open dump file → browse to C:\Windows\Minidump\<date>.dmp.
2. In the command window, type: !analyze -v
3. Look for the FAULTING_MODULE and IMAGE_NAME fields. These identify the exact driver or binary that caused the crash.

Example output:

BugCheck 1A, {41790, ffffb000a1234000, ...}
Probably caused by: nvlddmkm.sys (NVIDIA GPU driver)
FAILURE_BUCKET_ID: AV_nvlddmkm!...

This tells you immediately to target the NVIDIA driver.

Step 3: Repair System Files (SFC and DISM)

Open an elevated PowerShell or Command Prompt:

# Step 3a: Repair the Windows component store
DISM /Online /Cleanup-Image /RestoreHealth

# Step 3b: Scan and repair protected system files
sfc /scannow

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

If SFC reports Windows Resource Protection found corrupt files but was unable to fix some of them, boot from Windows 11 installation media and run SFC offline:

# From WinRE command prompt, identify your Windows drive letter (usually D: or C:)
sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows

Step 4: Update or Roll Back Drivers

Drivers are the #1 cause of Windows 11 BSODs. Focus on GPU, network, chipset, and storage drivers.

To roll back a driver:

1. Press Win + X → Device Manager.
2. Right-click the suspect device → Properties → Driver tab → Roll Back Driver.

To update drivers via PowerShell:

# Check for driver updates through Windows Update
Get-WindowsUpdate -Category Drivers -AcceptAll -Install

For GPU BSODs (VIDEO_TDR_FAILURE / nvlddmkm.sys / atikmpag.sys):

• Download Display Driver Uninstaller (DDU) from Wagnardsoft.
• Boot into Safe Mode.
• Run DDU to fully remove the current GPU driver.
• Install the latest stable driver (not beta) from NVIDIA.com or AMD.com.

Step 5: Test RAM with Windows Memory Diagnostic

# Launch Windows Memory Diagnostic (reboots system)
mdsched.exe

Choose Restart now and check for problems. For more thorough testing, use MemTest86 (bootable USB, 2+ passes). If errors are found:

• Reseat RAM sticks.
• Test each stick individually.
• Check RAM is on the motherboard's QVL (Qualified Vendor List) for your system.
• If XMP/EXPO profile is enabled in BIOS, try disabling it and running at stock speeds.

Step 6: Check Disk for File System Errors

# Schedule a disk check on the system drive (runs on next reboot)
chkdsk C: /r /f

# View SMART data for early drive failure warning
wmic diskdrive get model,status

# Using PowerShell for detailed SMART
Get-Disk | Get-StorageReliabilityCounter | Select-Object DeviceId, ReadErrorsTotal, Temperature, Wear

If chkdsk reports bad sectors or the drive status is not OK, back up data immediately and replace the drive.

Step 7: Uninstall a Problematic Windows Update

If BSODs began after a specific cumulative update (common with 22H2 patches):

# List recently installed updates
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 10

# Uninstall a specific update by KB number (example: KB5028185)
wusa /uninstall /kb:5028185 /quiet /norestart

# Or via Settings: Settings → Windows Update → Update history → Uninstall updates

Step 8: Check Event Viewer for Crash Context

# Get critical and error events from the last 24 hours
Get-WinEvent -FilterHashtable @{LogName='System'; Level=1,2; StartTime=(Get-Date).AddDays(-1)} |
  Select-Object TimeCreated, Id, Message | Format-List

# Look specifically for BugCheck events
Get-WinEvent -FilterHashtable @{LogName='System'; Id=1001} | Select-Object -First 5 | Format-List

Event ID 1001 (BugCheck) and Event ID 41 (Kernel-Power, unexpected shutdown) are the most relevant for BSOD analysis.

Step 9: Boot into Safe Mode for Isolation

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

1. Power on and force shutdown 3 times during boot to trigger Windows Recovery Environment (WinRE).
2. Navigate to Troubleshoot → Advanced options → Startup Settings → Restart.
3. Press 4 (Safe Mode) or 5 (Safe Mode with Networking).

In Safe Mode, only essential Microsoft drivers load. If BSODs stop in Safe Mode, a third-party driver or service is the culprit. Use msconfig to isolate it via selective startup.

Step 10: Last Resort — Reset or Reinstall Windows 11

If all steps above fail:

# Initiate a Reset This PC (keep personal files) from PowerShell
systemreset --factoryreset

# Or navigate to:
# Settings → System → Recovery → Reset this PC → Keep my files

For a clean reinstall, download the Windows 11 Installation Assistant or create bootable media using the Media Creation Tool from Microsoft's official site. Perform a full format of the system partition during setup.