What does stop code 0xC000021A mean and how do I fix it?

Stop code 0xC000021A (also written as 0x0000021A or c00021a) means Windows critical system processes Winlogon.exe or CSRSS.exe terminated unexpectedly. This most commonly happens after a Windows Update or driver change. Fix: Boot into WinRE → Startup Repair. If that fails, open Command Prompt in WinRE and run: sfc /scannow then DISM /Online /Cleanup-Image /RestoreHealth. You can also use System Restore to revert to a pre-update state. On Windows 10/11, try: dism /image:C:\ /cleanup-image /restorehealth from WinRE.

My monitor has a blue tint — is this a hardware or software problem?

It can be either. Start with software: reset your color profile in Display Settings to sRGB, disable Night Light, and reinstall your GPU driver using DDU. If the blue tint appears even at the BIOS/UEFI screen (before Windows loads), the problem is hardware — likely a failing monitor panel, backlight, or display cable. Try a different HDMI/DisplayPort cable. If the tint only appears in Windows, it's a driver or color profile issue. Samsung monitors and LG TVs showing a blue tint often just need the color temperature reset to 6500K in the OSD menu.

What causes MEMORY_MANAGEMENT blue screen and how do I fix it?

MEMORY_MANAGEMENT (stop code 0x0000001A) is caused by failing RAM, a corrupt page file, or faulty drivers accessing memory incorrectly. Steps to fix: (1) Run Windows Memory Diagnostic (mdsched.exe) or MemTest86 to check RAM. (2) Reseat RAM sticks — remove and reinsert them. (3) If you have multiple sticks, test with one at a time to isolate the bad module. (4) Run sfc /scannow to fix corrupted system files. (5) Disable XMP/EXPO memory overclocking in BIOS. (6) Update or roll back your GPU driver, as ntoskrnl.exe combined with memory_management often points to a driver memory leak.

How do I fix VIDEO_TDR_FAILURE (nvlddmkm.sys, dxgkrnl.sys, or atikmpag.sys)?

VIDEO_TDR_FAILURE means the GPU driver stopped responding and failed to recover within the timeout period. Fix: (1) Boot into Safe Mode. (2) Use Display Driver Uninstaller (DDU) to completely remove the GPU driver. (3) Download the latest driver from NVIDIA or AMD website and install fresh. (4) If it still crashes, check GPU temperatures under load — overheating causes TDR failures. (5) Reseat the GPU in the PCIe slot and check power connectors. (6) For laptops with dxgmms2.sys or dxgkrnl.sys errors, also update the Intel integrated graphics driver from the manufacturer's site.

How do I use BlueScreenView to diagnose which driver is causing BSOD?

BlueScreenView (free from NirSoft at nirsoft.net/utils/blue_screen_view.html) reads Windows minidump files from C:\Windows\Minidump. After installing and opening it, each row shows a crash event. Click a crash to see the drivers loaded at the time — the driver highlighted in pink/red is typically the one that caused the crash. Note the filename (e.g., nvlddmkm.sys, ntoskrnl.exe, netio.sys) and then update, roll back, or remove that driver. If ntoskrnl.exe is the only listed driver with no third-party drivers highlighted, the issue is usually RAM or the Windows kernel itself.

Blue Tint Monitor & Blue Screen of Death (BSOD): Complete Troubleshooting Guide for Windows

Fix blue tint monitor issues and Windows BSOD stop codes (memory management, kernel security, ntoskrnl.exe, dxgkrnl.sys) with step-by-step commands and proven s

Last updated: March 1, 2026

Last verified: March 1, 2026

2,313 words

Key Takeaways

Blue tint on monitor is usually caused by incorrect color temperature settings, a faulty display cable, bad GPU driver, or hardware color profile misconfiguration — fixable in minutes via display settings or driver reinstall.
Windows BSOD stop codes (0xc000021a, memory_management, kernel_security_check_failure, system_service_exception, critical_process_died, ntoskrnl.exe, dxgkrnl.sys, nvlddmkm.sys, and others) are most commonly triggered by corrupt/incompatible drivers, failing RAM, overheating, or a recent Windows Update.
Quick fix sequence: (1) boot into Safe Mode, (2) run Windows Memory Diagnostic and sfc /scannow, (3) roll back or update the offending driver identified in Event Viewer or BlueScreenView, (4) run CHKDSK on the system drive, (5) use Startup Repair if the machine won't boot.

BSOD & Blue Tint Fix Approaches Compared
Method	When to Use	Time	Risk
Update/Roll Back GPU Driver (DDU)	Blue tint, nvlddmkm.sys, dxgkrnl.sys, dxgmms2.sys, video TDR failure BSODs	15–30 min	Low
sfc /scannow + DISM	ntoskrnl.exe, system_service_exception, critical_process_died, corrupt system files	20–40 min	Low
Windows Memory Diagnostic / MemTest86	memory_management, bad_pool_header, pfn_list_corrupt, RAM-related BSODs	30 min – 8 hrs	None
CHKDSK /f /r	NTFS file system stop code, inaccessible boot device, rdr_file_system	30–120 min	Low
Driver Verifier	Identify unknown driver causing intermittent BSOD	Variable	Medium — may loop BSOD
Startup Repair / WinRE	PC won't boot, 0xc000021a, critical_process_died on boot, automatic repair loop	10–30 min	Low
Clean Windows Re-install	Persistent BSODs after all other fixes, boot loop, corrupt registry	60–120 min	Medium — backup data first
Monitor Color Profile Reset	Blue tint on monitor, bluish screen, monitor too blue	2–5 min	None

Understanding the Error

Two distinct problems share the "blue screen" label:

Blue tint on monitor — The display has an unwanted blue color cast, making whites look blue and images look cold. This is a display calibration or hardware issue, not a Windows crash.
Blue Screen of Death (BSOD) — Windows halts completely and displays a blue stop-code screen. Common stop codes include MEMORY_MANAGEMENT (0x0000001A), KERNEL_SECURITY_CHECK_FAILURE (0x00000139), SYSTEM_SERVICE_EXCEPTION (0x0000003B), CRITICAL_PROCESS_DIED (0x000000EF), INACCESSIBLE_BOOT_DEVICE (0x0000007B), 0xC000021A, NTFS_FILE_SYSTEM, DPC_WATCHDOG_VIOLATION, VIDEO_TDR_FAILURE, and dozens more.

Both issues are addressed in this guide.

Part 1: Fix Blue Tint on Monitor

Step 1 — Check Monitor Color Temperature & Color Profile

Right-click the desktop → Display settings → Advanced display → Display adapter properties.
Click the Color Management tab → Color Management... → select your monitor → ensure the color profile is set to sRGB or the manufacturer default.
Open Settings → System → Display → Night light — ensure Night Light is off or not permanently stuck on a warm/cool setting. If it is on but inverted (blue rather than warm), toggle it off.
On the monitor's OSD (on-screen display) hardware buttons, navigate to Picture → Color Temperature and set it to 6500K (Normal/Standard). Avoid "Cool" or "Blueish" presets.

Step 2 — Update or Reinstall GPU Driver (Blue Tint)

A corrupt or misconfigured GPU driver can force the display into an incorrect color mode.

Download Display Driver Uninstaller (DDU) from Wagnardsoft.
Boot into Safe Mode: press Win + R, type msconfig, go to Boot tab, check Safe boot → Minimal, reboot.
Run DDU, choose your GPU vendor (NVIDIA/AMD/Intel), click Clean and restart.
Boot normally and install the latest driver from nvidia.com or amd.com/en/support.

Step 3 — Check Physical Cable and Monitor Hardware

Reseat the HDMI/DisplayPort/VGA cable on both ends.
Try a different cable. HDMI cables can fail and cause color degradation.
Test the monitor on a different PC, or connect your PC to a different monitor, to isolate whether the problem is the monitor or the GPU.
If the blue tint persists on a different PC with the same monitor, the monitor panel or backlight is failing — contact manufacturer support.

Part 2: Fix Blue Screen of Death (BSOD)

Step 1 — Identify the Stop Code

The stop code is printed on the blue screen itself, for example:

Your PC ran into a problem and needs to restart.
Stop code: MEMORY_MANAGEMENT

If the PC reboots too fast to read it:

Open Event Viewer → Windows Logs → System → filter by Critical or search for BugCheck (Event ID 1001).
Or use BlueScreenView (free tool from NirSoft): it reads minidump files from C:\Windows\Minidump and shows the exact stop code, faulting driver, and memory address.

Common stop code → likely cause mapping:

Stop Code	Likely Cause
`MEMORY_MANAGEMENT (0x1A)`	Failing RAM, corrupt page file, ntoskrnl.exe
`KERNEL_SECURITY_CHECK_FAILURE (0x139)`	Corrupt driver, overclocking, RAM issue
`SYSTEM_SERVICE_EXCEPTION (0x3B)`	Corrupt or incompatible driver (nvlddmkm.sys, dxgkrnl.sys, win32kfull.sys, netio.sys)
`CRITICAL_PROCESS_DIED (0xEF)`	Windows system process crashed, corrupt OS files
`0xC000021A`	Winlogon or CSRSS process failure, often after Windows Update
`INACCESSIBLE_BOOT_DEVICE (0x7B)`	Storage driver missing, drive failure, BIOS SATA mode changed
`VIDEO_TDR_FAILURE`	GPU driver crash (nvlddmkm.sys, dxgkrnl.sys, atikmpag.sys, amdkmdag.sys)
`DPC_WATCHDOG_VIOLATION`	SSD/NVMe driver, fast startup conflict
`BAD_POOL_HEADER / BAD_POOL_CALLER`	Memory corruption, antivirus driver conflict
`NTFS_FILE_SYSTEM`	Drive corruption, failing HDD/SSD
`DRIVER_IRQL_NOT_LESS_OR_EQUAL (0x0A)`	Faulty network/GPU driver
`APC_INDEX_MISMATCH`	Driver using incorrect kernel functions

Step 2 — Boot Into Safe Mode (If PC Won't Start)

If the PC is stuck in a BSOD boot loop:

Force-shutdown by holding the power button 3 times in a row. Windows will enter WinRE (Windows Recovery Environment).
Go to Troubleshoot → Advanced options → Startup Settings → Restart → press 4 for Safe Mode.
Alternatively, boot from a Windows installation USB → Repair your computer → Troubleshoot → Advanced Options → Startup Repair or Command Prompt.

Step 3 — Run System File Checker and DISM

From an elevated Command Prompt (right-click Start → Windows Terminal (Admin)):

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

Wait for both to complete. If SFC reports corrupted files it could not fix, run DISM first and then SFC again.

Step 4 — Check RAM with Windows Memory Diagnostic

winmem

Or press Win + R, type mdsched.exe, choose Restart now and check for problems. If errors are found, reseat or replace the RAM module.

For extended testing, boot from a MemTest86 USB (free from memtest86.com) and run at least 2 full passes.

Step 5 — Fix Disk Corruption

chkdsk C: /f /r /x

Type Y to schedule on next reboot, then restart. On an SSD, also run:

powershell -Command "Optimize-Volume -DriveLetter C -ReTrim -Verbose"

Step 6 — Roll Back or Update the Faulting Driver

If BlueScreenView or Event Viewer points to a specific driver (e.g., nvlddmkm.sys, dxgkrnl.sys, atikmpag.sys, ntoskrnl.exe, netio.sys):

Open Device Manager → find the related device (Display adapters, Network adapters, etc.).
Right-click → Properties → Driver tab → Roll Back Driver (if a recent update caused the issue).
If Roll Back is greyed out, right-click → Update driver → Search automatically or manually install from manufacturer site.
For GPU drivers, always use DDU in Safe Mode before reinstalling (see Part 1, Step 2).

For 0xC000021A after Windows Update:

DISM /Image:C:\ /Get-Packages
DISM /Image:C:\ /Remove-Package /PackageName:<package_name>

Or use System Restore: WinRE → Troubleshoot → Advanced → System Restore → pick a restore point before the update.

Step 7 — Check for Overheating

BSODs during gaming (nvlddmkm.sys, dxgkrnl.sys, amdkmdag.sys) often indicate GPU/CPU overheating.

Download HWiNFO64 or MSI Afterburner to monitor temperatures.
GPU should stay below 85°C under load; CPU below 95°C.
Clean dust from vents, reapply thermal paste if needed (laptops older than 3–4 years).

Step 8 — Use Driver Verifier (Advanced)

If BSODs are intermittent and the faulting driver is unclear:

verifier /standard /all

Restart. Driver Verifier stresses all non-Microsoft drivers and will trigger a BSOD with the exact culprit if one exists. Disable after identifying the driver:

verifier /reset

Step 9 — Fix INACCESSIBLE_BOOT_DEVICE (0x7B)

From WinRE Command Prompt:

bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd

Also check BIOS: ensure SATA Mode matches the Windows installation (AHCI if installed as AHCI).

Step 10 — Last Resort: Reset / Reinstall Windows

If all else fails: Settings → System → Recovery → Reset this PC → Keep my files (or Remove everything for a clean install). Back up data first using a Live Linux USB or second drive.

Frequently Asked Questions

bash

# ============================================================
# BSOD & Blue Tint Diagnostic & Fix Script (Run as Administrator)
# Windows PowerShell / Command Prompt
# ============================================================

# --- 1. Check recent BSOD events in Event Viewer ---
Get-WinEvent -LogName System | Where-Object {$_.Id -eq 1001} | Select-Object -First 10 | Format-List TimeCreated, Message

# --- 2. Read latest minidump file location ---
Get-ChildItem C:\Windows\Minidump -ErrorAction SilentlyContinue | Sort-Object LastWriteTime -Descending | Select-Object -First 5

# --- 3. Run System File Checker ---
sfc /scannow

# --- 4. Run DISM to repair Windows image ---
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

# --- 5. Check disk for errors (schedule on reboot) ---
chkdsk C: /f /r /x

# --- 6. Run Windows Memory Diagnostic (schedules test on next reboot) ---
Start-Process mdsched.exe

# --- 7. List recently installed drivers (last 30 days) ---
Get-WinEvent -LogName System | Where-Object {$_.Id -eq 7045} | Select-Object -First 20 | Format-List TimeCreated, Message

# --- 8. List all third-party kernel drivers (non-Microsoft) ---
driverquery /fo csv /si | findstr /v "Microsoft"

# --- 9. Check GPU driver version ---
Get-WmiObject Win32_VideoController | Select-Object Name, DriverVersion, Status

# --- 10. Fix boot records (run from WinRE Command Prompt if PC won't boot) ---
# bootrec /fixmbr
# bootrec /fixboot
# bootrec /scanos
# bootrec /rebuildbcd

# --- 11. Roll back a specific Windows Update (replace KB number) ---
# wusa /uninstall /kb:5034441 /quiet /norestart

# --- 12. Reset color profile to fix blue tint on monitor ---
# Run in PowerShell to reset ICC profile for default monitor
Get-WmiObject -Namespace root\wmi -Class WmiMonitorID | Select-Object -First 1
# Then open: ms-settings:display to manually reset Night Light and color profile

# --- 13. Enable Driver Verifier to catch unknown BSOD culprit ---
# WARNING: May cause BSOD loop — disable after identifying driver
# verifier /standard /all
# To disable: verifier /reset

# --- 14. Export System info for further analysis ---
Get-ComputerInfo | Select-Object OsName, OsVersion, CsProcessors, CsPhyicallyInstalledMemory | Format-List
Get-WinEvent -LogName System -MaxEvents 50 | Where-Object {$_.LevelDisplayName -eq 'Critical'} | Format-Table TimeCreated, Message -AutoSize

Error Medic Editorial

The Error Medic Editorial team consists of senior DevOps engineers, SREs, and system administrators with 10+ years of hands-on experience diagnosing Windows kernel failures, BSOD stop codes, driver conflicts, and hardware display issues across enterprise and consumer environments. We specialize in translating cryptic error codes into actionable, step-by-step 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.