Blue Tint Monitor & Blue Screen of Death (BSOD): Complete Troubleshooting Guide for Windows
Fix blue tint monitor issues and Windows BSOD stop codes (0xc000021a, memory management, kernel security check failure) with step-by-step commands and proven so
- Blue tint on monitor is usually caused by incorrect color calibration, a faulty display cable, or misconfigured GPU color settings — fixable without hardware replacement in most cases.
- Windows Blue Screen of Death (BSOD) stop codes like MEMORY_MANAGEMENT, KERNEL_SECURITY_CHECK_FAILURE, CRITICAL_PROCESS_DIED, and SYSTEM_SERVICE_EXCEPTION are most commonly caused by corrupt or incompatible drivers, failing RAM, overheating, or a recent Windows Update.
- Use the Windows built-in tools (Event Viewer, Memory Diagnostic, SFC, DISM, and BlueScreenView) to identify the exact failing driver or module before attempting fixes — never reinstall Windows without diagnosing first.
- For stop code 0xc000021a after a Windows Update, roll back the update or use Startup Repair from a bootable USB to restore boot integrity.
- Driver-related BSODs (nvlddmkm.sys, dxgkrnl.sys, dxgmms2.sys, amdkmdag.sys, ntoskrnl.exe) require a clean driver reinstall using DDU (Display Driver Uninstaller) in Safe Mode.
| Method | When to Use | Time | Risk |
|---|---|---|---|
| Run SFC /scannow + DISM | Corrupt system files, stop code 0xc000021a, CRITICAL_PROCESS_DIED | 10–20 min | Low |
| Windows Memory Diagnostic / MemTest86 | MEMORY_MANAGEMENT, BAD_POOL_CALLER, PFN_LIST_CORRUPT stop codes | 30 min – 8 hrs | None |
| Clean Driver Reinstall via DDU | nvlddmkm.sys, dxgkrnl.sys, amdkmdag.sys, VIDEO_TDR_FAILURE BSODs | 20–40 min | Low |
| Uninstall Recent Windows Update | BSOD after update, stop code 0xc000021a, KERNEL_SECURITY_CHECK_FAILURE | 5–15 min | Low |
| Boot into Safe Mode + Event Viewer | Identify exact crashing driver or process | 5–10 min | None |
| Monitor Color Calibration Reset | Blue tint monitor, bluish screen display, monitor too blue | 2–5 min | None |
| Replace Display Cable (HDMI/DP) | Persistent blue tint on specific monitor not fixed by software | 5–10 min | None |
| Startup Repair / Bootrec commands | BSOD on boot, INACCESSIBLE_BOOT_DEVICE, unmountable boot volume | 15–30 min | Medium |
| Reset or Reinstall Windows | All else fails; multiple unresolvable stop codes | 1–3 hrs | High — back up data first |
Understanding the Issues: Blue Tint Monitor vs. Blue Screen of Death
These two problems share the word "blue" but are entirely different in nature. A blue tint on a monitor is a display output problem — your screen shows an unwanted blue cast over all content. A Blue Screen of Death (BSOD) is a Windows kernel-level crash that forces the system to halt to prevent data corruption. This guide covers both comprehensively.
Part 1: Fixing a Blue Tint Monitor
What Causes a Blue Tint?
A blue tint on your computer monitor or laptop screen typically has one of these causes:
- Incorrect RGB color balance or color temperature settings in Windows or the GPU control panel
- A damaged or loosely connected display cable (HDMI, DisplayPort, VGA, or LVDS ribbon)
- A misconfigured blue light filter (Windows Night Light set too high)
- A failing monitor backlight or display panel
- Incorrect ICC color profile applied to the display
Step 1: Disable Windows Night Light and Blue Light Filters
Windows 10/11 includes a built-in blue light filter called Night Light. If it is stuck on or misconfigured, the screen will appear bluish or orange.
- Press Windows + I to open Settings.
- Navigate to System > Display.
- Find Night Light and toggle it Off.
- Click Night Light Settings and set the color temperature slider to neutral.
If you use a third-party blue light filter (f.lux, Windows bluelight filter app), disable it temporarily to rule it out.
Step 2: Reset GPU Color Settings
For NVIDIA:
- Right-click the desktop and open NVIDIA Control Panel.
- Navigate to Display > Adjust Desktop Color Settings.
- Ensure Digital Vibrance, Hue, and Brightness are at default values.
- Under Output Color Format, select RGB and Output Dynamic Range: Full.
For AMD:
- Open AMD Radeon Software.
- Go to Display tab.
- Scroll to Color and reset all sliders to default.
For Intel Integrated Graphics:
- Right-click the desktop > Intel Graphics Settings.
- Navigate to Color and click Restore Defaults.
Step 3: Run Windows Color Calibration
- Press Windows + R, type
dccw, and press Enter. - Follow the on-screen wizard to calibrate gamma, brightness, contrast, and color balance.
- Adjust the RGB sliders until whites appear neutral (not blue-tinted).
Step 4: Check and Reseat Display Cables
If the blue tint persists after software fixes:
- Power off the monitor and PC.
- Disconnect and firmly reseat the HDMI, DisplayPort, or VGA cable on both ends.
- Try a different cable entirely — HDMI cables can develop internal wire breaks that cause color channel imbalance.
- Test the monitor on a different computer to determine if the issue is the monitor itself or the PC.
Step 5: Update or Rollback Monitor ICC Profile
- Press Windows + R, type
colorcpl, press Enter. - Select your monitor under Devices.
- Click Add and choose sRGB IEC61966-2.1 as a test profile.
- Set it as default and check if the tint improves.
Part 2: Diagnosing Windows Blue Screen of Death (BSOD)
Reading the Stop Code
Every BSOD displays a stop code (e.g., MEMORY_MANAGEMENT, KERNEL_SECURITY_CHECK_FAILURE, CRITICAL_PROCESS_DIED). The QR code on modern Windows BSODs points to https://www.windows.com/stopcode which provides a lookup tool. The stop code is the most important piece of information — always record it before rebooting.
Common stop codes and their primary causes:
| Stop Code | Primary Cause |
|---|---|
MEMORY_MANAGEMENT (0x0000001A) |
Faulty RAM, corrupt drivers |
KERNEL_SECURITY_CHECK_FAILURE (0x00000139) |
Corrupt drivers, RAM errors, malware |
CRITICAL_PROCESS_DIED (0x000000EF) |
Corrupt system files, failing drive |
SYSTEM_SERVICE_EXCEPTION (0x0000003B) |
Driver conflict, especially GPU drivers |
IRQL_NOT_LESS_OR_EQUAL (0x0000000A) |
Incompatible driver accessing restricted memory |
VIDEO_TDR_FAILURE (0x00000116) |
GPU driver crash (nvlddmkm.sys, dxgkrnl.sys, amdkmdag.sys) |
INACCESSIBLE_BOOT_DEVICE (0x0000007B) |
Boot drive failure, SATA mode change, corrupt BCD |
BAD_POOL_CALLER |
Driver allocating memory incorrectly |
PFN_LIST_CORRUPT |
RAM failure or driver corruption |
0xc000021a |
Critical Windows session process (winlogon/csrss) failure |
DPC_WATCHDOG_VIOLATION |
Driver not completing within time limit, SSD firmware |
APC_INDEX_MISMATCH |
Driver mismatch, often after Windows Update |
WDF_VIOLATION |
Windows Driver Framework rule violation |
NTFS_FILE_SYSTEM |
File system corruption on NTFS volume |
DRIVER_POWER_STATE_FAILURE |
Driver failing to handle sleep/wake transitions |
Step 1: Collect Crash Dump Information
Windows saves minidump files at C:\Windows\Minidump. Use BlueScreenView (by NirSoft) to analyze them without a debugger.
- Download BlueScreenView from
https://www.nirsoft.net/utils/blue_screen_view.html. - Open the application — it auto-loads all minidump files.
- Look at the Caused By Driver column — this identifies the exact .sys file responsible.
- Cross-reference the driver filename with the known causes table above.
Step 2: Check Event Viewer
- Press Windows + X, select Event Viewer.
- Navigate to Windows Logs > System.
- Filter for Critical and Error events around the time of the crash.
- Look for sources like
BugCheck,EventLog, or the specific driver name.
Step 3: Repair System Files (SFC and DISM)
Open Command Prompt as Administrator and run the following (see code_block section for the full script):
sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth
SFC scans and repairs corrupted Windows system files. DISM repairs the Windows image used by SFC. Always run DISM first if SFC fails repeatedly.
Step 4: Test RAM
For any MEMORY_MANAGEMENT, BAD_POOL_CALLER, PFN_LIST_CORRUPT, or KERNEL_SECURITY_CHECK_FAILURE errors:
- Press Windows + R, type
mdsched.exe, press Enter. - Choose Restart now and check for problems.
- For thorough testing, boot from a MemTest86 USB drive and run at least 2 complete passes.
- If errors are found, reseat RAM sticks, test one stick at a time, or replace faulty modules.
Step 5: Fix Driver-Related BSODs (GPU/Network/Audio)
For stop codes pointing to nvlddmkm.sys, dxgkrnl.sys, dxgmms2.sys, amdkmdag.sys, atikmpag.sys, netio.sys, ndis.sys:
- Boot into Safe Mode (press F8 or Shift+Restart > Troubleshoot > Advanced Options > Startup Settings).
- Download Display Driver Uninstaller (DDU) from
https://www.guru3d.com/files-details/display-driver-uninstaller-download.html. - Run DDU in Safe Mode to completely remove GPU drivers.
- Reboot normally and install the latest stable driver from NVIDIA, AMD, or Intel's official site.
- For network drivers (netio.sys, ndis.sys), open Device Manager, right-click the network adapter, and select Update Driver or Uninstall Device then reinstall.
Step 6: Fix Stop Code 0xc000021a
This error indicates that either winlogon.exe or csrss.exe (critical Windows session processes) has failed. It commonly appears after a Windows Update.
Boot from Windows installation media (USB):
- Select Repair your computer > Troubleshoot > Advanced Options > Startup Repair.
- If Startup Repair fails, open Command Prompt from Advanced Options and run:
bootrec /fixmbr
bootrec /fixboot
bootrec /rebuildbcd
sfc /scannow
Roll back the problematic update:
- Boot to Troubleshoot > Advanced Options > Uninstall Updates.
- Select Uninstall latest quality update or feature update.
Step 7: Fix INACCESSIBLE_BOOT_DEVICE (0x0000007B)
- Check BIOS/UEFI: ensure the SATA controller mode hasn't changed from AHCI to IDE (or vice versa).
- Boot from Windows USB, open Command Prompt, and run
chkdsk C: /f /r. - Verify the boot drive is detected in BIOS.
- Run
bootrec /rebuildbcdto repair the boot configuration.
Step 8: Check for Overheating
Overheating causes random BSODs with various stop codes. Use HWiNFO64 or Core Temp to monitor temperatures.
- CPU should stay below 90°C under load (ideally below 80°C).
- GPU should stay below 85°C.
- Clean dust from vents and heatsinks; reapply thermal paste if the system is over 3 years old.
Step 9: When to Reset or Reinstall Windows
If SFC, DISM, memory tests, and driver reinstalls all fail to resolve recurring BSODs:
- Back up your data to an external drive.
- Go to Settings > System > Recovery > Reset this PC.
- Choose Keep my files for a repair reset, or Remove everything for a clean install.
- Alternatively, perform a clean install using a Windows 11 or Windows 10 bootable USB from Microsoft's official site.
Frequently Asked Questions
# ============================================================
# BSOD & Blue Tint Monitor - Windows Diagnostic & Fix Script
# Run PowerShell as Administrator
# ============================================================
# --- STEP 1: Check recent BSOD events from Event Log ---
Write-Host "[1] Recent BSOD Events (last 30 days)" -ForegroundColor Cyan
Get-WinEvent -FilterHashtable @{
LogName = 'System'
Id = 41 # Kernel-Power unexpected shutdown
StartTime = (Get-Date).AddDays(-30)
} -ErrorAction SilentlyContinue | Select-Object TimeCreated, Message | Format-List
# --- STEP 2: List minidump files ---
Write-Host "`n[2] Minidump Files Found:" -ForegroundColor Cyan
$dumpPath = "C:\Windows\Minidump"
if (Test-Path $dumpPath) {
Get-ChildItem -Path $dumpPath -Filter "*.dmp" | Sort-Object LastWriteTime -Descending | Select-Object Name, LastWriteTime, @{N='SizeMB';E={[math]::Round($_.Length/1MB,2)}}
} else {
Write-Host "No minidump directory found. Ensure small memory dumps are enabled." -ForegroundColor Yellow
}
# --- STEP 3: Enable small memory dumps if not already set ---
Write-Host "`n[3] Ensuring Small Memory Dumps are Enabled..." -ForegroundColor Cyan
$regPath = "HKLM:\SYSTEM\CurrentControlSet\Control\CrashControl"
Set-ItemProperty -Path $regPath -Name "CrashDumpEnabled" -Value 3 # 3 = Small memory dump
Set-ItemProperty -Path $regPath -Name "MinidumpDir" -Value "%SystemRoot%\Minidump"
Set-ItemProperty -Path $regPath -Name "AutoReboot" -Value 1
Write-Host "Small memory dumps enabled at $dumpPath" -ForegroundColor Green
# --- STEP 4: Run System File Checker ---
Write-Host "`n[4] Running SFC (System File Checker)..." -ForegroundColor Cyan
Write-Host "This may take 5-15 minutes. Do not close this window."
sfc /scannow
# --- STEP 5: Run DISM to repair Windows image ---
Write-Host "`n[5] Running DISM to restore Windows health image..." -ForegroundColor Cyan
DISM /Online /Cleanup-Image /RestoreHealth
# --- STEP 6: Check disk health ---
Write-Host "`n[6] Checking disk for errors on C: drive..." -ForegroundColor Cyan
Write-Host "Note: A full scan will be scheduled on next reboot if volume is in use."
cmd /c "echo Y | chkdsk C: /f /r /x"
# --- STEP 7: Scan for driver issues ---
Write-Host "`n[7] Listing recently installed drivers (last 30 days)..." -ForegroundColor Cyan
Get-WinEvent -FilterHashtable @{LogName='System'; ProviderName='Microsoft-Windows-DriverFrameworks-UserMode'; StartTime=(Get-Date).AddDays(-30)} -ErrorAction SilentlyContinue | Select-Object -First 20 TimeCreated, Message | Format-List
# --- STEP 8: List installed drivers sorted by date ---
Write-Host "`n[8] Recently Modified Drivers:" -ForegroundColor Cyan
Get-WindowsDriver -Online -ErrorAction SilentlyContinue | Sort-Object Date -Descending | Select-Object -First 20 OriginalFileName, ProviderName, Date, Version | Format-Table -AutoSize
# --- STEP 9: Check RAM slots and memory info ---
Write-Host "`n[9] RAM Information:" -ForegroundColor Cyan
Get-CimInstance -ClassName Win32_PhysicalMemory | Select-Object BankLabel, DeviceLocator, Capacity, Speed, Manufacturer | Format-Table -AutoSize
# --- STEP 10: GPU Driver Info ---
Write-Host "`n[10] GPU / Display Adapter Information:" -ForegroundColor Cyan
Get-CimInstance -ClassName Win32_VideoController | Select-Object Name, DriverVersion, DriverDate, VideoProcessor | Format-Table -AutoSize
# --- STEP 11: Monitor color profile fix (blue tint) ---
Write-Host "`n[11] Opening Color Management for Monitor Blue Tint Fix..." -ForegroundColor Cyan
Start-Process "colorcpl.exe"
Write-Host "In Color Management: Select your monitor > Add > choose 'sRGB IEC61966-2.1' > Set as Default Profile"
# --- STEP 12: Disable Night Light via registry (blue tint quick fix) ---
Write-Host "`n[12] Disabling Windows Night Light (if enabled)..." -ForegroundColor Cyan
$nightLightReg = "HKCU:\Software\Microsoft\Windows\CurrentVersion\CloudStore\Store\DefaultAccount\Current\default`$windows.data.bluelightreduction.bluelightreductionstate\windows.data.bluelightreduction.bluelightreductionstate"
if (Test-Path $nightLightReg) {
# Reset to disable Night Light
Remove-Item -Path $nightLightReg -Force -ErrorAction SilentlyContinue
Write-Host "Night Light registry entry cleared. Log out and back in to apply." -ForegroundColor Green
} else {
Write-Host "Night Light registry key not found or already disabled." -ForegroundColor Yellow
}
# --- Launch Windows Memory Diagnostic ---
Write-Host "`n[13] To run RAM test now, execute:" -ForegroundColor Cyan
Write-Host " mdsched.exe" -ForegroundColor White
Write-Host "Or for offline testing, download MemTest86 from https://www.memtest86.com/"
# --- STEP 14: List recent Windows Updates ---
Write-Host "`n[14] Recent Windows Updates (last 15 days):" -ForegroundColor Cyan
Get-HotFix | Where-Object {$_.InstalledOn -ge (Get-Date).AddDays(-15)} | Sort-Object InstalledOn -Descending | Select-Object HotFixID, Description, InstalledOn | Format-Table -AutoSize
Write-Host "`n=== Diagnostics Complete ===" -ForegroundColor Green
Write-Host "Review output above. For BSOD analysis, also run NirSoft BlueScreenView on your minidump files."
Write-Host "Download: https://www.nirsoft.net/utils/blue_screen_view.html"Error Medic Editorial
The Error Medic Editorial team consists of senior Windows engineers, SREs, and system administrators with 10+ years of experience diagnosing hardware failures, BSOD crash dumps, and display issues across enterprise and consumer environments. Our guides are built from real diagnostic data, Microsoft WinDbg analysis, and field-tested remediation steps.
Sources
- https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-code-reference2
- https://support.microsoft.com/en-us/windows/windows-stop-codes-bsod-3b9cb23c-5e04-4e74-bf56-0df16e0b9a84
- https://www.nirsoft.net/utils/blue_screen_view.html
- https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x1a--memory-management
- https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0xef--critical-process-died
- https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x139--kernel-security-check-failure
- https://www.guru3d.com/files-details/display-driver-uninstaller-download.html
- https://www.memtest86.com/