What does the CRITICAL_PROCESS_DIED stop code mean on Windows 10?

CRITICAL_PROCESS_DIED (0x000000EF) means a core Windows process — such as csrss.exe, winlogon.exe, or smss.exe — terminated unexpectedly. This is commonly caused by corrupted system files, failing hardware, or malware. Fix it by running 'sfc /scannow' and 'DISM /Online /Cleanup-Image /RestoreHealth' from an elevated Command Prompt, checking for malware with Windows Defender, and testing RAM with Windows Memory Diagnostic.

How do I fix KERNEL_SECURITY_CHECK_FAILURE on Windows 10?

KERNEL_SECURITY_CHECK_FAILURE (0x00000139) typically indicates memory corruption or a driver violating security policies. Steps: (1) Boot into Safe Mode. (2) Run 'sfc /scannow'. (3) Update or roll back recently installed drivers — especially GPU and network drivers. (4) Run MemTest86 to rule out bad RAM. (5) If installing Windows 10 from USB, try re-downloading the ISO and verifying the hash, as a corrupted installer file commonly triggers this stop code during setup.

Why do I get a blue screen with stop code 0xC000021A on Windows 10?

Stop code 0xC000021A means the Windows subsystem (csrss.exe or winlogon.exe) failed during session initialization — most often triggered by corrupted system files, a bad Windows Update, or mismatched DLL versions. Boot into WinRE (press F8 or force 3 shutdowns), go to Troubleshoot > Advanced Options > Startup Repair. If that fails, run 'chkdsk C: /f /r' and 'sfc /scannow' from the WinRE Command Prompt. As a last resort, uninstall recent updates from WinRE.

How can I stop the blue screen loop on Windows 10 after an update?

When Windows 10 is stuck in a BSOD loop after an update: (1) Force 3 consecutive shutdowns to boot into WinRE. (2) Go to Troubleshoot > Advanced Options > Uninstall Updates and remove the latest cumulative update. (3) If that is unavailable, use 'Startup Repair.' (4) From WinRE Command Prompt run: 'DISM /Image:C:\ /Cleanup-Image /RestoreHealth' and 'sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows'. (5) If Windows cannot recover, use the Media Creation Tool to perform an in-place upgrade repair without losing files.

What causes nvlddmkm.sys or atikmdag.sys blue screens on Windows 10 and how do I fix them?

These are NVIDIA and AMD GPU driver files respectively. They cause VIDEO_TDR_FAILURE when the GPU driver stops responding and cannot recover. Root causes include overheating GPU, outdated/corrupted drivers, overclocking, or DirectX compatibility issues. Fix: (1) Download Display Driver Uninstaller (DDU) from wagnardsoft.com. (2) Boot into Safe Mode. (3) Run DDU to completely remove GPU drivers. (4) Reinstall the latest stable driver from NVIDIA.com or AMD.com. (5) Check GPU temperatures using HWInfo64 — if above 90°C under load, clean the heatsink or reapply thermal paste.

Blue Tint Screen Windows 10: Fix Every Blue Screen of Death (BSOD) Stop Code

Fix blue tint screen & BSOD on Windows 10. Step-by-step guide covering stop codes, kernel failures, memory errors, driver issues & recovery commands.

Last updated: March 1, 2026

Last verified: March 1, 2026

2,335 words

Key Takeaways

A blue tint or full Blue Screen of Death (BSOD) on Windows 10 is most commonly caused by faulty or outdated drivers (e.g., nvlddmkm.sys, ntoskrnl.exe, ndis.sys), corrupted system files, bad RAM, or a failed Windows Update.
Stop codes such as CRITICAL_PROCESS_DIED, KERNEL_SECURITY_CHECK_FAILURE, MEMORY_MANAGEMENT, PFN_LIST_CORRUPT, SYSTEM_SERVICE_EXCEPTION, IRQL_NOT_LESS_OR_EQUAL, and 0xC000021A each point to a specific subsystem failure that narrows the diagnostic path.
Quick fix summary: Boot into Safe Mode, run 'sfc /scannow' and 'DISM /Online /Cleanup-Image /RestoreHealth', update or roll back drivers, check RAM with Windows Memory Diagnostic, and use BlueScreenView to identify the crashing module before attempting a system restore or clean install.

Fix Approaches Compared
Method	When to Use	Time	Risk
SFC + DISM System File Repair	Corrupted system files, BSOD after update, ntoskrnl.exe errors	15-40 min	Low
Driver Rollback / Update	BSOD after driver install, nvlddmkm.sys, atikmdag.sys, ndis.sys errors	10-30 min	Low-Medium
Windows Memory Diagnostic / MemTest86	MEMORY_MANAGEMENT, PFN_LIST_CORRUPT, BAD_POOL_HEADER stop codes	30 min - 8 hrs	Low
Safe Mode Boot + Clean Boot	BSOD on startup, CRITICAL_PROCESS_DIED, SYSTEM_SERVICE_EXCEPTION	5-15 min	Low
BlueScreenView / Event Viewer Analysis	Identifying exact crashing driver or module after any BSOD	5-15 min	None
System Restore	BSOD started after a specific update or software install	20-45 min	Medium
Startup Repair (WinRE)	PC stuck in BSOD boot loop, 0xC000021A, INACCESSIBLE_BOOT_DEVICE	20-60 min	Low-Medium
Chkdsk Disk Repair	NTFS.sys BSOD, disk read errors, UNMOUNTABLE_BOOT_VOLUME	20-120 min	Low-Medium
Windows 10 Reset / Reinstall	All other methods failed, persistent blue screen loop	2-4 hrs	High (data loss risk)

Understanding the Blue Screen of Death on Windows 10

A Blue Screen of Death (BSOD), also called a stop error or blue tint screen, occurs when Windows 10 encounters a fatal error it cannot safely recover from. The system halts to prevent data corruption, writes a memory dump, and displays a stop code. Since Windows 10, Microsoft added a QR code and a plain-English description, but the underlying stop codes remain the same as earlier NT versions.

When users report a 'blue tint screen,' they may be describing one of two things: (1) the classic BSOD with a blue background and stop code, or (2) a display driver glitch causing the entire screen to take on a blue hue without a crash. This guide covers both scenarios comprehensively.

The reference URL https://www.windows.com/stopcode (also logged as https://www.microsoft.com/en-us/safety/pc-security/windows-stop-codes) is shown on every Windows 10 BSOD screen and links to Microsoft's official stop code documentation.

Step 1: Record the Stop Code and Crashing Module

Before attempting any fix, note the exact stop code and file name displayed on the blue screen. Common examples include:

CRITICAL_PROCESS_DIED (0x000000EF)
KERNEL_SECURITY_CHECK_FAILURE (0x00000139)
SYSTEM_SERVICE_EXCEPTION (0x0000003B)
MEMORY_MANAGEMENT (0x0000001A)
PFN_LIST_CORRUPT (0x0000004E)
IRQL_NOT_LESS_OR_EQUAL (0x0000000A)
APC_INDEX_MISMATCH (0x00000001)
BAD_POOL_CALLER / BAD_POOL_HEADER
INACCESSIBLE_BOOT_DEVICE
UNMOUNTABLE_BOOT_VOLUME
0xC000021A / 0xC0000225 (boot-time failures)
0xC00007B (application subsystem failure)
VIDEO_TDR_FAILURE (nvlddmkm.sys, atikmdag.sys, dxgkrnl.sys)
WDF_VIOLATION
CLOCK_WATCHDOG_TIMEOUT
DRIVER_POWER_STATE_FAILURE

If the BSOD is too brief to read, use BlueScreenView (free tool from NirSoft) or Windows Event Viewer after booting normally or into Safe Mode.

Step 2: Boot into Safe Mode

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

Force shutdown by holding the power button. Repeat 3 times — Windows will automatically enter Windows Recovery Environment (WinRE).
Navigate to Troubleshoot > Advanced Options > Startup Settings > Restart.
Press F4 for Safe Mode or F5 for Safe Mode with Networking.

In Safe Mode, only essential drivers load, which isolates third-party driver conflicts.

Step 3: Analyze Crash Dumps with BlueScreenView or Event Viewer

BlueScreenView reads minidump files from C:\Windows\Minidump\ and shows you exactly which driver caused the crash.

Download from: https://www.nirsoft.net/utils/blue_screen_view.html
Sort by 'Crash Time' — the highlighted driver in red is the offending module.

Event Viewer approach:

Press Win + R, type eventvwr.msc, press Enter.
Go to Windows Logs > System.
Filter for Error and Critical events around the crash timestamp.
Look for source BugCheck or WheaLogger.

Step 4: Run System File Checker and DISM

Corrupted system files are responsible for a large percentage of BSODs — especially after a bad Windows Update. Run the following commands from an elevated Command Prompt:

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

After DISM completes, run sfc /scannow again to repair any remaining files. Restart and test.

Step 5: Update, Roll Back, or Uninstall Problem Drivers

Drivers are the #1 cause of BSODs. Key offenders and their fixes:

Driver File	Stop Code / Symptom	Fix
`nvlddmkm.sys`	VIDEO_TDR_FAILURE	Update/clean-install NVIDIA drivers using DDU
`atikmdag.sys` / `amdkmdag.sys`	VIDEO_TDR_FAILURE	DDU clean uninstall, then reinstall AMD drivers
`ntoskrnl.exe`	SYSTEM_SERVICE_EXCEPTION, MEMORY_MANAGEMENT	Run SFC, check RAM
`ndis.sys`	SYSTEM_SERVICE_EXCEPTION	Update network adapter drivers
`netio.sys`	SYSTEM_SERVICE_EXCEPTION	Update network drivers, disable VPN software
`fltmgr.sys`	SYSTEM_SERVICE_EXCEPTION	Check antivirus filter drivers, uninstall/update AV
`dxgkrnl.sys` / `dxgmms2.sys`	VIDEO_TDR_FAILURE	Update GPU drivers, check GPU temperature
`tcpip.sys`	SYSTEM_SERVICE_EXCEPTION	Update network drivers, disable offload features
`classpnp.sys`	Stuck during boot	Boot to Safe Mode, run chkdsk

To roll back a driver:

Press Win + X > Device Manager.
Right-click the device > Properties > Driver tab > Roll Back Driver.

To use Display Driver Uninstaller (DDU): Boot to Safe Mode, run DDU, select your GPU brand, click 'Clean and restart.' Reinstall the latest stable driver from NVIDIA/AMD website.

Step 6: Check RAM with Windows Memory Diagnostic

Faulty RAM causes MEMORY_MANAGEMENT, PFN_LIST_CORRUPT, BAD_POOL_HEADER, and IRQL_NOT_LESS_OR_EQUAL errors.

Press Win + R, type mdsched.exe, press Enter.
Choose Restart now and check for problems.
For more thorough testing, use MemTest86 (bootable USB) and run at least 2 full passes.

If errors are found, reseat your RAM sticks. Try booting with one stick at a time to isolate a faulty module.

Step 7: Check Disk Health with CHKDSK

Disk errors trigger NTFS_FILE_SYSTEM, INACCESSIBLE_BOOT_DEVICE, UNMOUNTABLE_BOOT_VOLUME, and 0xC000021A stop codes.

chkdsk C: /f /r /x

This requires a restart to run before Windows loads. Also check S.M.A.R.T. data using CrystalDiskInfo (free) to detect failing drives.

Step 8: Uninstall Recent Windows Updates

If BSODs started after a cumulative update:

Go to Settings > Update & Security > Windows Update > View Update History > Uninstall Updates.
Sort by date, right-click the most recent update, select Uninstall.
Alternatively, from WinRE: Troubleshoot > Advanced Options > Uninstall Updates.

Step 9: Use System Restore

If restore points exist:

Press Win + R, type rstrui.exe.
Select a restore point from before the BSOD started.
Or from WinRE: Troubleshoot > Advanced Options > System Restore.

Step 10: Fix Blue Tint Without a BSOD (Display Driver Glitch)

If your screen has a blue tint but Windows is responsive:

Right-click Desktop > Display Settings > Color calibration — recalibrate colors.
Device Manager > Display Adapters > Roll back or update GPU driver.
Check Night Light: Settings > System > Display > Night light settings — ensure it's not set to a high warm level that might appear bluish on some monitors.
Check monitor cable — a loose or damaged HDMI/DisplayPort cable can cause color channel tinting.
If using an AMD GPU: Open AMD Radeon Software > Display > check for color temperature or hue adjustments.
If using NVIDIA: NVIDIA Control Panel > Adjust desktop color settings — reset to defaults.

Step 11: Last Resort — Windows 10 Reset or Reinstall

If all else fails:

Settings > Update & Security > Recovery > Reset this PC.
Choose Keep my files (soft reset) or Remove everything (clean install).
For a completely clean install, use the Windows 10 Media Creation Tool to create a bootable USB.

Always back up important data before resetting.

Frequently Asked Questions

bash

# =============================================================
# Windows 10 Blue Screen Diagnostic & Repair Commands
# Run all commands from an ELEVATED Command Prompt or PowerShell
# =============================================================

# --- STEP 1: Check System Files ---
sfc /scannow

# --- STEP 2: DISM System Image Repair ---
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

# Run SFC again after DISM completes
sfc /scannow

# --- STEP 3: Check Disk for Errors (C: drive) ---
# Schedule chkdsk for next reboot
chkdsk C: /f /r /x

# --- STEP 4: Verify Disk Health via WMIC ---
wmic diskdrive get status

# --- STEP 5: Launch Windows Memory Diagnostic ---
mdsched.exe

# --- STEP 6: View Last 10 Critical/Error Events (PowerShell) ---
Get-WinEvent -LogName System -MaxEvents 100 | Where-Object {$_.LevelDisplayName -eq 'Critical' -or $_.LevelDisplayName -eq 'Error'} | Select-Object TimeCreated, Id, Message | Format-List

# --- STEP 7: Find the Last BSOD Stop Code via Event Viewer ---
Get-WinEvent -LogName System | Where-Object {$_.Id -eq 1001} | Select-Object -First 5 | Format-List

# --- STEP 8: List All Installed Drivers (sorted by date) ---
driverquery /v /fo csv | ConvertFrom-Csv | Sort-Object 'Link Date' -Descending | Select-Object -First 20 | Format-Table 'Display Name','Start Mode','State','Link Date'

# --- STEP 9: List Recently Installed Windows Updates ---
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 10

# --- STEP 10: Uninstall a Specific Update by KB Number ---
# Replace KB1234567 with the actual KB number
wusa /uninstall /kb:1234567 /quiet /norestart

# --- STEP 11: Disable Automatic Restart on BSOD (for reading stop code) ---
reg add "HKLM\SYSTEM\CurrentControlSet\Control\CrashControl" /v AutoReboot /t REG_DWORD /d 0 /f

# --- STEP 12: Enable Complete Memory Dump for Better Analysis ---
reg add "HKLM\SYSTEM\CurrentControlSet\Control\CrashControl" /v CrashDumpEnabled /t REG_DWORD /d 1 /f

# --- STEP 13: Check Driver Verifier (catch rogue drivers) ---
# CAUTION: Only enable this for targeted testing — can cause more BSODs
# Enable for all third-party drivers:
verifier /standard /all
# To disable Driver Verifier:
verifier /reset

# --- STEP 14: Offline SFC from WinRE Command Prompt ---
# (Use when Windows won't boot normally)
# Find Windows partition letter first:
diskpart
# Inside diskpart:
#   list vol
#   exit
# Then run offline SFC (replace D: with your Windows drive letter):
sfc /scannow /offbootdir=D:\ /offwindir=D:\Windows

# --- STEP 15: Offline DISM from WinRE ---
DISM /Image:D:\ /Cleanup-Image /RestoreHealth

# --- STEP 16: Check Network Driver (ndis.sys / netio.sys issues) ---
netsh winsock reset
netsh int ip reset
ipconfig /flushdns

# --- STEP 17: Reset BCD if INACCESSIBLE_BOOT_DEVICE or 0xC0000225 ---
# Run from WinRE Command Prompt:
bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd

# --- STEP 18: Export Minidump List (PowerShell) ---
Get-ChildItem -Path 'C:\Windows\Minidump' -Filter '*.dmp' | Sort-Object LastWriteTime -Descending | Select-Object Name, LastWriteTime, Length

# --- STEP 19: Check GPU Temperature (PowerShell + WMIC) ---
wmic path win32_videocontroller get name,driverversion,status

# --- STEP 20: Check for Corrupted Startup ---
bcdedit /enum all

Error Medic Editorial

The Error Medic Editorial team is composed of senior DevOps engineers, SREs, and Windows systems administrators with a combined 30+ years of experience diagnosing crash dumps, debugging kernel stop codes, and building resilient infrastructure. We specialize in translating complex low-level Windows internals into actionable, human-readable troubleshooting guides. Our guides are tested against real hardware configurations and verified against Microsoft's official documentation and community-sourced crash analysis data.

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.