Microsoft Stop Code (Blue Screen of Death): Complete Troubleshooting Guide for All BSOD Errors

Understanding Microsoft Stop Codes

A Microsoft stop code — commonly known as a Blue Screen of Death (BSOD) or, in newer Windows versions, a Blue Screen with a QR code — indicates that Windows has encountered a critical error it cannot safely recover from. The system halts to prevent further damage. On Windows 10 and 11, the screen displays a sad face emoji, a brief description, a stop code string (e.g., MEMORY_MANAGEMENT), and a QR code you can scan for Microsoft's support page at https://www.microsoft.com/stopcode or https://windows.microsoft.com/stopcode.

On Microsoft Surface devices (including Surface Pro), BSODs can also be caused by firmware bugs, thermal throttling, or driver conflicts unique to Surface hardware.

Most Common Microsoft Stop Codes and Their Causes

1. 0xc000021a / 0xc00021a / Stop Code 21a Full error: STOP: c000021a {Fatal System Error}. This occurs when the Windows Session Manager (smss.exe) or Client/Server Runtime (csrss.exe) fails. Common triggers: corrupted Windows update, bad third-party software, or registry damage.

2. IRQL_NOT_LESS_OR_EQUAL / DRIVER_IRQL_NOT_LESS_OR_EQUAL A driver attempted to access pageable memory at a process IRQL that was too high. Usually caused by a faulty, outdated, or incompatible device driver.

3. MEMORY_MANAGEMENT Indicates a serious memory subsystem error. Causes include faulty RAM sticks, corrupted virtual memory, or a failing hard drive.

4. BAD_POOL_CALLER A kernel-mode process made an invalid pool allocation request. Often caused by buggy drivers or corrupted system files.

5. KERNEL_SECURITY_CHECK_FAILURE A kernel data structure integrity check failed. Commonly triggered by incompatible drivers, malware, or RAM errors.

6. INACCESSIBLE_BOOT_DEVICE Windows cannot access the boot partition during startup. Causes include corrupted boot sector, missing storage drivers, or failed Windows update.

7. DRIVER_POWER_STATE_FAILURE A driver did not complete a power-state transition in time. Often occurs after sleep/hibernate cycles and is usually driver-related.

Step 1: Capture the Stop Code and Crash Dump

Before fixing anything, identify the exact stop code. If Windows reboots too fast:

1. Go to Settings > System > About > Advanced system settings > Startup and Recovery > Settings.
2. Uncheck Automatically restart so the BSOD stays visible.
3. Note the stop code displayed on the blue screen.

Alternatively, read crash dumps using Event Viewer or WinDbg:

• Open Event Viewer > Windows Logs > System and filter for Critical errors.
• Use WinDbg or the free WhoCrashed tool to analyze minidump files located at C:\Windows\Minidump\.

Step 2: Boot into Safe Mode or WinRE

If Windows won't start normally, access the Windows Recovery Environment (WinRE):

• Force-shutdown your PC 3 times during boot to trigger Automatic Repair mode.
• From Automatic Repair, choose Advanced options > Troubleshoot > Advanced options > Startup Settings > Restart, then press 4 for Safe Mode.

On Microsoft Surface or Surface Pro:

• Hold Volume Down + Power for 15 seconds to force shutdown, then boot normally into WinRE after two failed starts.

Step 3: Run System File Checker and DISM

From an elevated Command Prompt (run as Administrator):

sfc /scannow
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

Restart after completion and check if the stop code recurs.

Step 4: Check and Repair the Disk

Run CHKDSK to detect and repair disk errors:

chkdsk C: /f /r /x

You will be prompted to schedule this for the next restart. Type Y and restart. This is especially important for INACCESSIBLE_BOOT_DEVICE errors.

Step 5: Test Your RAM

For MEMORY_MANAGEMENT or BAD_POOL_CALLER stop codes:

1. Press Win + R, type mdsched.exe, and press Enter.
2. Choose Restart now and check for problems.
3. Windows will run two full passes of memory tests.

For more thorough testing, use MemTest86 (bootable from USB) for extended overnight testing.

Step 6: Update or Roll Back Drivers

For IRQL_NOT_LESS_OR_EQUAL, DRIVER_IRQL_NOT_LESS_OR_EQUAL, or DRIVER_POWER_STATE_FAILURE:

1. Open Device Manager (devmgmt.msc).
2. Look for devices with yellow warning icons.
3. Right-click the suspect device > Update driver or Roll back driver.

To identify the specific faulty driver from a minidump, use WinDbg:

!analyze -v

This will output the name of the offending .sys file.

For Microsoft Surface devices, always get drivers from the official Microsoft Surface Update or through Windows Update rather than third-party sources.

Step 7: Fix 0xc000021a Specifically

This stop code often requires WinRE. Boot into WinRE and open Command Prompt:

bcdedit /set {default} safeboot minimal

Restart into Safe Mode, then:

net stop wuauserv
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
net start wuauserv
sfc /scannow

If the issue followed a Windows Update, use System Restore:

• WinRE > Advanced options > System Restore > pick a restore point before the update.

Step 8: Address Microsoft Teams Blue Screen

If the BSOD occurs specifically when Microsoft Teams is running, this is often caused by a conflict between Teams' hardware acceleration and a display or audio driver:

1. Open Teams > Settings > General > Disable GPU hardware acceleration.
2. Update your graphics driver from the manufacturer's website (NVIDIA, AMD, or Intel).
3. Reinstall Teams using the Teams bootstrapper rather than the store version.

Step 9: Microsoft Update Blue Screen Recovery

If a Windows Update caused the BSOD:

1. Boot into WinRE > Troubleshoot > Advanced options > Uninstall Updates.
2. Choose Uninstall latest quality update or Uninstall latest feature update.
3. After unbooting, pause Windows Updates temporarily while you investigate the problematic update KB article.

Step 10: Last Resort — Reset or Reinstall Windows

If all above steps fail:

1. Go to Settings > System > Recovery > Reset this PC.
2. Choose Keep my files for a non-destructive reset, or Remove everything for a full clean reinstall.

For a clean install on Surface devices, download the Surface Recovery Image from the Microsoft website and flash it via USB.

Microsoft Green Screen of Death (GSOD)

Windows Insider Preview builds display a Green Screen of Death instead of blue. It functions identically to a BSOD — same stop codes, same troubleshooting steps. The green color simply identifies it as occurring on an Insider/preview build of Windows.

Using the Microsoft QR Code on BSOD

Modern Windows 10/11 BSODs display a QR code. Scanning it takes you to https://www.microsoft.com/stopcode (also accessible as https://windows.microsoft.com/stopcode, https://microsoft.com/stopcode, or https://www.microsoft stopcode). This page redirects to Microsoft's official BSOD support documentation and is a good starting reference point.