Blue Tint Monitor & Blue Screen of Death (BSOD): Complete Troubleshooting Guide for Windows
Fix blue tint monitor issues and Blue Screen of Death (BSOD) errors on Windows. Step-by-step diagnostics, stop codes, and proven fixes for every BSOD type.
- Blue tint on a monitor is usually caused by incorrect color temperature settings, a failing display cable, outdated GPU drivers, or Windows night-light/blue-light filter being misconfigured.
- Blue Screen of Death (BSOD) errors are triggered by driver conflicts, faulty RAM, corrupted system files, overheating hardware, or incompatible Windows updates — each stop code points to a specific root cause.
- Quick fix summary: update or roll back GPU/driver, run 'sfc /scannow' and DISM, check RAM with Windows Memory Diagnostic, inspect Event Viewer crash logs with BlueScreenView, and verify monitor cable and display color settings.
| Method | When to Use | Time | Risk |
|---|---|---|---|
| Update/Roll Back GPU Driver | After driver install causes BSOD or blue tint (nvlddmkm.sys, amdkmdag.sys, atikmpag.sys) | 5–15 min | Low |
| SFC & DISM System File Repair | Corrupted OS files causing stop codes (ntoskrnl.exe, ntfs.sys, fltmgr.sys) | 15–30 min | Low |
| Windows Memory Diagnostic / MemTest86 | BSOD stop codes: MEMORY_MANAGEMENT, BAD_POOL_CALLER, PFN_LIST_CORRUPT | 1–8 hrs | None |
| Check Event Viewer + BlueScreenView | Identifying exact crash driver or module from minidump files | 5–10 min | None |
| Boot into Safe Mode & Uninstall Suspect Driver | BSOD on every boot, can't reach desktop | 10–20 min | Low |
| Adjust Monitor Color Temperature / ICC Profile | Blue tint on display not related to crashes | 2–5 min | None |
| Replace Display Cable (HDMI/DP/VGA) | Physical blue tint, flickering, or color distortion on monitor | 5–10 min | None |
| System Restore / Rollback Windows Update | BSOD started after a Windows Update (0xc000021a, CRITICAL_PROCESS_DIED) | 10–30 min | Medium |
| Reset/Reinstall Windows | All other fixes failed, persistent stop codes | 1–3 hrs | High |
Understanding Blue Tint Monitor vs. Blue Screen of Death
These two issues are frequently searched together but have different causes. A blue tint on your monitor is a display calibration or hardware problem — your screen looks washed in blue but Windows still runs. A Blue Screen of Death (BSOD) is a critical Windows kernel crash that halts the OS entirely, showing a stop code like MEMORY_MANAGEMENT, KERNEL_SECURITY_CHECK_FAILURE, CRITICAL_PROCESS_DIED, or SYSTEM_SERVICE_EXCEPTION.
Both can stem from GPU driver problems, which is why they're often diagnosed together.
Part 1: Fixing a Blue Tint on Your Monitor
Step 1: Check Windows Color & Display Settings
- Right-click the desktop → Display settings → Advanced display settings.
- Click Display adapter properties → Color Management tab → Color Management... → ensure no incorrect ICC profile is applied.
- Open Night Light settings:
Settings > System > Display > Night light. Turn it off — a misconfigured night light set to a cold hue can cause a blue cast. - In the Intel Graphics Command Center, AMD Radeon Software, or NVIDIA Control Panel, reset Color Temperature to 6500K (neutral/standard).
Step 2: Check Monitor OSD (On-Screen Display) Settings
Press your monitor's physical menu button and navigate to Color Temperature or Picture Mode. Reset to Standard or sRGB. Many monitors ship with Cool mode enabled, which drastically increases the blue channel.
Step 3: Check the Display Cable
A damaged or poorly seated HDMI, DisplayPort, DVI, or VGA cable can cause color channel bleed, producing a blue tint. Try:
- Reseating both ends of the cable.
- Swapping to a different cable or port.
- Testing the monitor on a different PC to isolate the issue.
Step 4: Update GPU Drivers
Outdated or corrupted display drivers cause both blue tinting and BSODs.
- NVIDIA: Download from nvidia.com/drivers. Perform a Clean Install.
- AMD: Download from amd.com/support. Use DDU (Display Driver Uninstaller) in Safe Mode before reinstalling.
- Intel: Use Intel Driver & Support Assistant at intel.com/DSA.
Part 2: Diagnosing Blue Screen of Death (BSOD) Errors
Step 1: Read the Stop Code
When Windows crashes, it displays a stop code on the blue screen. Note it exactly. Common stop codes include:
| Stop Code | Common Cause |
|---|---|
MEMORY_MANAGEMENT (0x0000001A) |
RAM errors, driver bugs |
KERNEL_SECURITY_CHECK_FAILURE (0x00000139) |
Corrupted memory, driver stack |
CRITICAL_PROCESS_DIED (0x000000EF) |
Critical Windows process terminated |
SYSTEM_SERVICE_EXCEPTION (0x0000003B) |
Driver or system call fault |
DRIVER_IRQL_NOT_LESS_OR_EQUAL (0x000000D1) |
Driver accessing wrong memory |
INACCESSIBLE_BOOT_DEVICE (0x0000007B) |
Storage controller driver mismatch |
PAGE_FAULT_IN_NONPAGED_AREA (0x00000050) |
RAM or paging file issue |
DPC_WATCHDOG_VIOLATION (0x00000133) |
Driver timeout, SSD firmware bug |
VIDEO_TDR_FAILURE |
GPU driver failure (nvlddmkm.sys, atikmpag.sys) |
NTFS_FILE_SYSTEM |
Disk corruption |
BAD_POOL_CALLER |
Memory pool corruption |
PFN_LIST_CORRUPT |
Physical memory table corruption |
APC_INDEX_MISMATCH |
Driver synchronization error |
WDF_VIOLATION |
Windows Driver Framework violation |
0xC000021A |
Winlogon or CSRSS subsystem failure |
The stop code is your primary clue. Windows also shows a QR code linking to https://www.windows.com/stopcode for online help.
Step 2: Analyze Minidump Files with BlueScreenView
Windows saves crash data to C:\Windows\Minidump\. Use NirSoft BlueScreenView (free, portable) to read these:
- Download BlueScreenView from nirsoft.net.
- Open it — it auto-loads all minidumps.
- Look at the Caused By Driver column. This is the specific
.sysor.exefile responsible. - Common offenders:
ntoskrnl.exe,nvlddmkm.sys,amdkmdag.sys,atikmpag.sys,netio.sys,dxgkrnl.sys,dxgmms2.sys,win32kfull.sys,fltmgr.sys.
Step 3: Check Event Viewer
- Press
Win + R, typeeventvwr.msc, press Enter. - Navigate to Windows Logs → System.
- Filter by Critical and Error events around the crash time.
- Look for Event ID 41 (unexpected shutdown) and Event ID 1001 (BugCheck) — these contain the exact bugcheck code and crash parameters.
Step 4: Run SFC and DISM
Corrupted system files are a leading cause of stop codes like CRITICAL_PROCESS_DIED, SYSTEM_SERVICE_EXCEPTION, and 0xC000021A.
Open Command Prompt as Administrator and run:
sfc /scannow
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
Reboot after each scan completes.
Step 5: Check RAM
Memory errors cause MEMORY_MANAGEMENT, BAD_POOL_CALLER, PFN_LIST_CORRUPT, and PAGE_FAULT_IN_NONPAGED_AREA.
- Press
Win + R, typemdsched.exe→ Restart now and check for problems. - For deeper testing, boot from a MemTest86 USB (pass at least 2 full cycles).
- If you have multiple RAM sticks, test them one at a time to identify a bad module.
Step 6: Update or Roll Back Drivers
If BlueScreenView identifies a specific .sys file, act on it:
- GPU drivers (
nvlddmkm.sys,amdkmdag.sys,atikmpag.sys,dxgkrnl.sys): Uninstall via DDU in Safe Mode, then install the latest stable version. - Network drivers (
netio.sys,ndis.sys,netwtw10.sys): Update via Device Manager → Network Adapters. - Audio drivers (
portcls.sys,hdaudbus.sys): Update via Device Manager → Sound controllers. - McAfee/Kaspersky/Bitdefender (
mfehidk.sys,klflt.sys): Temporarily uninstall security software to test if it's causing the crash.
Step 7: Fix 0xC000021A (Winlogon Failure)
This stop code means a critical user-mode subsystem (winlogon.exe or csrss.exe) terminated unexpectedly. It's common after Windows updates.
- Boot from Windows installation media.
- Choose Repair your computer → Troubleshoot → Advanced options → Startup Repair.
- If that fails, use Command Prompt from recovery and run:
sfc /scannow /offbootdir=C:\ /offwindir=C:\Windowsbcdedit /set {default} safeboot minimal(to force Safe Mode boot)
- Uninstall the problematic update:
Settings → Update & Security → View Update History → Uninstall Updates.
Step 8: Fix INACCESSIBLE_BOOT_DEVICE (0x0000007B)
- Boot from Windows installation media → Command Prompt.
- Run
bootrec /fixmbrandbootrec /fixbootandbootrec /rebuildbcd. - Check that SATA controller mode (AHCI vs. IDE) in BIOS matches the Windows driver installed.
- If after a Windows update, boot into recovery and roll back the update.
Step 9: Check for Overheating
Thermal throttling and overheating cause random BSODs, especially during gaming or heavy loads.
- Use HWiNFO64 or Core Temp to monitor CPU/GPU temperatures.
- CPU should stay below 90°C under load; GPU below 85°C.
- Clean dust from heatsinks and fans. Reapply thermal paste on CPUs older than 3–4 years.
- Check for
machine_check_exception(0x00000124) — this is almost always hardware-level thermal or voltage failure.
Step 10: Last Resort — System Restore or Reset
If all else fails:
- System Restore:
Control Panel → Recovery → Open System Restore→ choose a restore point before BSODs started. - Reset This PC:
Settings → Update & Security → Recovery → Reset this PC→ Keep my files (or Remove everything for a clean slate). - Clean Windows Install: Download Windows 10/11 ISO from Microsoft, create a bootable USB with the Media Creation Tool, and perform a fresh installation.
Frequently Asked Questions
:: ============================================================
:: BSOD & Blue Tint Monitor - Full Diagnostic & Fix Script
:: Run as Administrator in Command Prompt or PowerShell
:: ============================================================
:: --- 1. System File Checker (repairs corrupted Windows files) ---
sfc /scannow
:: --- 2. DISM - Repair Windows Image ---
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
:: --- 3. Check and repair disk errors on C: drive ---
chkdsk C: /f /r /x
:: (Will schedule on next reboot if drive is in use)
:: --- 4. View recent BSOD stop codes via PowerShell ---
powershell -Command "Get-EventLog -LogName System -EntryType Error | Where-Object {$_.EventID -eq 41 -or $_.EventID -eq 1001} | Select-Object -First 20 TimeGenerated, Message | Format-List"
:: --- 5. List minidump files for BlueScreenView analysis ---
dir C:\Windows\Minidump\ /o-d
:: --- 6. Check currently loaded drivers (look for suspicious 3rd-party .sys files) ---
driverquery /v /fo list | findstr /i "Module Name Driver Type"
:: --- 7. Run Windows Memory Diagnostic ---
mdsched.exe
:: (Opens GUI - choose "Restart now and check for problems")
:: --- 8. Check Windows Update history for recent installs ---
powershell -Command "Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 10"
:: --- 9. Uninstall a problematic Windows Update by KB number ---
:: Replace KBxxxxxxx with the actual KB from step 8
:: wusa /uninstall /kb:KBxxxxxxx /quiet /norestart
:: --- 10. Reset network stack (fixes BSOD from netio.sys, ndis.sys) ---
netsh winsock reset
netsh int ip reset
ipconfig /flushdns
:: --- 11. Force generate a kernel dump for analysis (Advanced) ---
:: This writes a kernel memory dump to C:\Windows\MEMORY.DMP
notmyfault.exe /crash
:: (Requires SysInternals NotMyFault tool from Microsoft)
:: --- 12. Check GPU driver version via WMIC ---
wmic path win32_videocontroller get name, driverversion, status
:: --- 13. Monitor color calibration reset via PowerShell ---
powershell -Command "& { Add-Type -AssemblyName System.Windows.Forms; [System.Windows.Forms.Screen]::PrimaryScreen }"
:: Open Color Calibration tool manually:
calibrate.exe
:: --- 14. Enable verbose BSOD logging for future crashes ---
reg add "HKLM\SYSTEM\CurrentControlSet\Control\CrashControl" /v CrashDumpEnabled /t REG_DWORD /d 2 /f
reg add "HKLM\SYSTEM\CurrentControlSet\Control\CrashControl" /v AutoReboot /t REG_DWORD /d 0 /f
:: (Sets minidump mode and disables auto-reboot so you can read the stop code)
:: --- 15. Boot into Safe Mode if BSOD prevents normal login ---
bcdedit /set {default} safeboot minimal
:: To revert after troubleshooting:
:: bcdedit /deletevalue {default} safebootError Medic Editorial
The Error Medic Editorial team is composed of senior DevOps engineers, Windows SREs, and system administrators with 10+ years of experience diagnosing Windows kernel crashes, hardware failures, and display issues across enterprise and consumer environments. Our guides are based on real-world troubleshooting, official Microsoft documentation, and analysis of thousands of BSOD minidump files.
Sources
- https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-code-reference2
- https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/analyzing-a-kernel-mode-dump-file
- https://support.microsoft.com/en-us/windows/fix-blue-screen-errors-in-windows-7a80ae44-f6bc-3cc0-5f24-a95d3cf0ed4a
- https://www.nirsoft.net/utils/blue_screen_view.html
- https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/dpc-watchdog-violation
- https://learn.microsoft.com/en-us/windows/client-management/stop-error-zero-xc000021a