Blue Tint Monitor & Blue Screen of Death (BSOD): Complete Troubleshooting Guide
Fix blue tint monitor issues and Blue Screen of Death (BSOD) errors on Windows. Step-by-step solutions for stop codes, driver failures, and display problems.
- A blue tint on your monitor is usually caused by incorrect color calibration, a failing GPU driver, a bad cable connection, or hardware damage to the display panel.
- Blue Screen of Death (BSOD) errors are triggered by driver conflicts (ntoskrnl.exe, nvlddmkm.sys, dxgkrnl.sys), corrupt system files, faulty RAM, overheating hardware, or Windows update failures.
- Most BSOD stop codes (0xc000021a, CRITICAL_PROCESS_DIED, KERNEL_SECURITY_CHECK_FAILURE, MEMORY_MANAGEMENT, SYSTEM_SERVICE_EXCEPTION) can be resolved by updating or rolling back drivers, running SFC and DISM scans, checking RAM with MemTest86, and reviewing crash dumps in Event Viewer or BlueScreenView.
| Method | When to Use | Time | Risk |
|---|---|---|---|
| Update / Roll Back GPU Driver | After new driver install causes BSOD or blue tint (nvlddmkm.sys, amdkmdag.sys, dxgkrnl.sys) | 5-15 min | Low |
| SFC /scannow + DISM | Corrupt Windows system files suspected (ntoskrnl.exe, ntfs.sys, fltmgr.sys) | 15-30 min | Low |
| MemTest86 RAM Test | MEMORY_MANAGEMENT, BAD_POOL_CALLER, PFN_LIST_CORRUPT stop codes | 60-120 min | None |
| Windows Startup Repair / Recovery | PC won't boot, CRITICAL_PROCESS_DIED, INACCESSIBLE_BOOT_DEVICE, 0xc000021a | 10-20 min | Low-Medium |
| Monitor Color Calibration / Cable Swap | Blue tint on screen only, no BSOD, no OS errors | 5-10 min | None |
| Driver Verifier (verifier.exe) | Identifying which driver causes random BSODs | Ongoing | Medium (may trigger more BSODs) |
| Reinstall / Reset Windows | All other fixes exhausted, persistent BSODs | 60-180 min | High (data risk) |
Understanding Blue Tint Monitor vs. Blue Screen of Death
These are two distinct but often confused problems. A blue tint monitor means your display has an unwanted blue color cast — the screen looks bluish even when showing white or neutral content. A Blue Screen of Death (BSOD) is a Windows system crash that forces a full stop, displaying a blue screen with a stop code such as KERNEL_SECURITY_CHECK_FAILURE, CRITICAL_PROCESS_DIED, MEMORY_MANAGEMENT, or SYSTEM_SERVICE_EXCEPTION.
Both can sometimes occur together if a GPU driver failure causes both display color problems and system crashes.
Part 1: Fix Blue Tint on Monitor
Step 1: Check Physical Connections
A loose, damaged, or low-quality cable between your PC and monitor is the most common cause of a blue tint.
- Unplug and firmly reseat the HDMI, DisplayPort, DVI, or VGA cable on both ends.
- Try a different cable of the same type.
- Try a different port on your GPU.
- If the blue tint disappears on a different cable or port, the original cable or port is faulty.
Step 2: Calibrate Monitor Color Settings
Via Windows Display Settings:
- Right-click the desktop → Display settings → Advanced display → Display adapter properties.
- Go to the Color Management tab → Color Management → Advanced → Calibrate display.
- Follow the on-screen wizard to correct the color balance.
Via Monitor OSD (On-Screen Display):
- Press the physical buttons on your monitor.
- Navigate to Color Temperature or Color Settings.
- Set color temperature to 6500K (standard) or switch from Cool to Warm or Custom.
- Reduce the Blue channel gain manually if your monitor supports RGB gain sliders.
Via GPU Control Panel:
- NVIDIA: Right-click desktop → NVIDIA Control Panel → Display → Adjust desktop color settings → Set Color temperature to 6500K or manually lower the blue channel.
- AMD: Right-click desktop → AMD Software (Adrenalin) → Display → Color → Adjust Custom Color sliders.
Step 3: Update or Reinstall GPU Drivers
A corrupt or outdated GPU driver can cause blue tint and display rendering errors.
- Download DDU (Display Driver Uninstaller) from guru3d.com.
- Boot into Safe Mode (press F8 or Shift + Restart → Troubleshoot → Advanced → Startup Settings).
- Run DDU and select Clean and restart.
- After restart, download the latest driver from NVIDIA or AMD and install.
Step 4: Check for Hardware Failure
If the blue tint persists across all cables, ports, and software settings:
- Test the monitor on a different computer. If blue tint still appears, the monitor panel or backlight is failing — contact the manufacturer.
- Test your GPU on a different monitor. If blue tint follows the GPU, the GPU may have a failing video output circuit.
Part 2: Fix Blue Screen of Death (BSOD)
Step 1: Identify the Stop Code
When Windows crashes, it displays a stop code on the blue screen. Common stop codes and their typical causes include:
| Stop Code | Common Cause |
|---|---|
CRITICAL_PROCESS_DIED (0x000000EF) |
Corrupt system files, bad Windows update, malware |
KERNEL_SECURITY_CHECK_FAILURE (0x00000139) |
RAM errors, driver incompatibility, corrupt system files |
MEMORY_MANAGEMENT (0x0000001A) |
Faulty RAM, corrupt page file, driver bug |
SYSTEM_SERVICE_EXCEPTION (0x0000003B) |
Driver conflict (win32k.sys, ntfs.sys, nvlddmkm.sys) |
INACCESSIBLE_BOOT_DEVICE (0x0000007B) |
Storage driver missing, SSD/HDD failure, BitLocker issue |
0xc000021a |
Winlogon or CSRSS process crashed, corrupt system DLLs |
DRIVER_IRQL_NOT_LESS_OR_EQUAL (0x000000D1) |
Buggy driver accessing invalid memory address |
DPC_WATCHDOG_VIOLATION (0x00000133) |
SSD firmware, outdated chipset/storage driver |
PFN_LIST_CORRUPT (0x0000004E) |
Faulty RAM or failing hard drive |
VIDEO_TDR_FAILURE (nvlddmkm.sys / dxgkrnl.sys) |
GPU driver crash, overheating GPU, failing graphics card |
If your PC reboots too fast to read the code, disable automatic restart:
- Right-click This PC → Properties → Advanced system settings → Startup and Recovery → Settings → Uncheck Automatically restart.
Step 2: Read the Crash Dump with BlueScreenView or Event Viewer
Using BlueScreenView (nirsoft.net):
- Download and run BlueScreenView (bluescreenview.exe).
- It automatically loads minidump files from
C:\Windows\Minidump\. - Look at the Caused By Driver column — this identifies the specific .sys file responsible.
Using Event Viewer:
- Press
Win + R→ typeeventvwr.msc→ Enter. - Navigate to Windows Logs → System.
- Filter for Critical and Error events around the time of the crash.
- Look for source BugCheck for BSOD details.
Step 3: Run System File Checker and DISM
Corrupt Windows system files cause a large proportion of BSODs. Run these commands in an elevated Command Prompt (Run as Administrator):
sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth
Restart after completion and monitor for BSODs.
Step 4: Update or Roll Back Drivers
Driver-related BSODs are among the most common. If a BSOD started after a Windows Update or driver update:
- Press
Win + X→ Device Manager. - Right-click the problematic device (especially Display adapters, Network adapters, Storage controllers) → Properties → Driver tab → Roll Back Driver.
For GPU crashes (nvlddmkm.sys, dxgkrnl.sys, amdkmdag.sys, atikmpag.sys), use DDU in Safe Mode as described in Part 1, Step 3.
For ntoskrnl.exe BSODs, the issue is often not ntoskrnl itself but a third-party driver calling it. Use BlueScreenView to find the actual culprit.
Step 5: Test RAM with MemTest86
For stop codes like MEMORY_MANAGEMENT, BAD_POOL_CALLER, KERNEL_SECURITY_CHECK_FAILURE, or PFN_LIST_CORRUPT:
- Download MemTest86 from memtest86.com and create a bootable USB.
- Boot from the USB and run at least 2 full passes.
- Any errors = faulty RAM. Try running with one stick at a time to identify the bad module.
- Also try reseating RAM sticks (remove and firmly re-insert).
Quick Windows Memory Diagnostic:
- Press
Win + R→ typemdsched.exe→ Restart now and check for problems.
Step 6: Fix Boot-Related BSODs (0xc000021a, INACCESSIBLE_BOOT_DEVICE)
If your PC shows 0xc000021a or INACCESSIBLE_BOOT_DEVICE and won't boot:
- Boot from a Windows 10/11 installation USB.
- Select Repair your computer → Troubleshoot → Advanced options → Startup Repair.
- If Startup Repair fails, choose Command Prompt and run:
bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd
- For
0xc000021aspecifically, also run:
bcdedit /set {default} safeboot minimal
Boot into Safe Mode, run SFC, then remove the safeboot flag:
bcdedit /deletevalue {default} safeboot
Step 7: Check for Overheating
GPU or CPU overheating causes sudden BSODs especially during gaming (VIDEO_TDR_FAILURE, nvlddmkm.sys, dxgmms2.sys).
- Download HWMonitor or HWiNFO64 and monitor temperatures under load.
- GPU should stay below 85°C; CPU below 90°C under load.
- Clean dust from heatsinks and fans. Reapply thermal paste if temperatures are extreme.
- Underclock GPU slightly using MSI Afterburner if temperatures are borderline.
Step 8: Use Driver Verifier to Isolate Faulty Drivers
If you're getting random BSODs and can't identify the driver:
- Press
Win + R→ typeverifier→ Enter. - Select Create standard settings → Next.
- Select Automatically select all drivers installed on this computer → Finish → Restart.
- Driver Verifier will intentionally crash the system when a problematic driver is detected, showing the exact driver name in the BSOD.
- After identifying the driver, disable Driver Verifier:
verifier /resetin an elevated command prompt.
Warning: Driver Verifier increases BSOD frequency intentionally. Only use on a system that can afford temporary instability.
Step 9: Perform a Clean Boot
Third-party software (antivirus like McAfee mfehidk.sys, Kaspersky, Sophos; VPN drivers like sgravpn.sys, nordvpn) can cause BSODs.
- Press
Win + R→ typemsconfig→ Services tab. - Check Hide all Microsoft services → Disable all.
- Go to Startup tab → Open Task Manager → Disable all startup items.
- Restart and test. If no BSOD occurs, re-enable services in batches to isolate the culprit.
Step 10: Windows Reset as Last Resort
If all else fails:
- Go to Settings → System → Recovery → Reset this PC.
- Choose Keep my files first. If BSODs continue after reset, choose Remove everything.
- This reinstalls Windows while optionally preserving personal files.
Frequently Asked Questions
# ============================================================
# BSOD & Blue Tint Diagnostic and Fix Commands
# Run all commands in an elevated Command Prompt (Run as Admin)
# ============================================================
# --- 1. Check for corrupt system files ---
sfc /scannow
# --- 2. Repair Windows image with DISM ---
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
# --- 3. Check disk for errors (replace C: with your drive letter) ---
chkdsk C: /f /r /x
# --- 4. View recent BSOD stop codes from Windows event log ---
wevtutil qe System /q:"*[System[Provider[@Name='Microsoft-Windows-WER-SystemErrorReporting']]]" /c:10 /f:text
# --- 5. List recent minidump files ---
dir C:\Windows\Minidump\ /o-d
# --- 6. Fix boot records (run from Windows Recovery Command Prompt) ---
bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd
# --- 7. Force boot to Safe Mode (useful for 0xc000021a fix) ---
bcdedit /set {default} safeboot minimal
# To undo after fixing (run in Safe Mode):
bcdedit /deletevalue {default} safeboot
# --- 8. Disable automatic restart on BSOD (via registry) ---
reg add "HKLM\SYSTEM\CurrentControlSet\Control\CrashControl" /v AutoReboot /t REG_DWORD /d 0 /f
# --- 9. Enable kernel memory dump for better crash analysis ---
reg add "HKLM\SYSTEM\CurrentControlSet\Control\CrashControl" /v CrashDumpEnabled /t REG_DWORD /d 2 /f
# --- 10. Reset Driver Verifier (if it was enabled and causing issues) ---
verifier /reset
# --- 11. Run Windows Memory Diagnostic ---
mdsched.exe
# --- 12. Check GPU temperature and driver info (PowerShell) ---
powershell -Command "Get-WmiObject Win32_VideoController | Select-Object Name, DriverVersion, Status"
# --- 13. List all installed drivers (to find third-party culprits) ---
driverquery /v /fo csv > C:\drivers_list.csv
# --- 14. Uninstall a specific Windows Update (replace KB_NUMBER) ---
wusa /uninstall /kb:KB_NUMBER /quiet /norestart
# --- 15. Check for and repair BCD errors ---
bcdedit /enum all
# --- 16. Monitor color calibration reset (PowerShell) ---
powershell -Command "Remove-ItemProperty -Path 'HKCU:\Software\Microsoft\Windows NT\CurrentVersion\ICM' -Name 'Calibration Data' -ErrorAction SilentlyContinue"
# --- 17. Disable Night Light (blue tint from software filter) ---
powershell -Command "Set-ItemProperty -Path 'HKCU:\Software\Microsoft\Windows\CurrentVersion\CloudStore\Store\DefaultAccount\Current\default$windows.data.bluelightreduction.bluelightreductionstate\windows.data.bluelightreduction.bluelightreductionstate' -Name 'Data' -Type Binary -Value ([byte[]](0x43,0x42,0x01,0x00,0x0A,0x02,0x01,0x00,0x00,0x00,0x00,0x00))"
# ============================================================
# NOTES:
# - For nvlddmkm.sys / GPU BSOD: boot to Safe Mode, run DDU,
# then reinstall drivers from nvidia.com or amd.com
# - For 0xc000021a: use Startup Repair from Windows USB first
# - For RAM issues: boot MemTest86 from USB (2+ passes)
# ============================================================Error Medic Editorial
The Error Medic Editorial team consists of senior DevOps engineers, SREs, and Windows system administrators with 10+ years of experience diagnosing hardware failures, driver conflicts, and OS-level crashes. Our guides are tested on real hardware across Windows 10 and Windows 11 environments before publication.
Sources
- https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-code-reference2
- https://learn.microsoft.com/en-us/windows-hardware/drivers/devtest/driver-verifier
- https://support.microsoft.com/en-us/windows/troubleshoot-blue-screen-errors-5c62a79a-27d7-7c28-b0eb-f6292e653a07
- https://www.nirsoft.net/utils/blue_screen_view.html
- https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/reading-bug-check-callback-data
- https://stackoverflow.com/questions/tagged/bsod