Blue Tint Screen & Blue Screen of Death on Windows 10: Complete Fix Guide (All Stop Codes)

Understanding Blue Tint Screen vs. Blue Screen of Death on Windows 10

Windows 10 users frequently confuse two distinct issues. The blue tint screen is a display color problem — your desktop still works but everything appears with a blue/cool hue. The Blue Screen of Death (BSOD), also called a stop code screen, is a critical system crash that displays a sad face and an error code like CRITICAL_PROCESS_DIED or MEMORY_MANAGEMENT. This guide covers both.

Part 1: Fixing a Blue Tint Screen on Windows 10

A blue tint on your Windows 10 display (without a system crash) is almost always software-related.

Step 1: Disable Night Light and Check Color Temperature

Go to Settings → System → Display → Night light settings. Turn Night Light off. If the tint disappears, you're done — adjust the color temperature to a warmer value if you still want eye protection.

Step 2: Reset Color Profile

1. Open Control Panel → Color Management (search colorcpl in Run).
2. Select your display under the Devices tab.
3. Check Use my settings for this device.
4. Remove any custom ICC profiles and click Set as Default Profile on sRGB IEC61966-2.1.

Step 3: Update or Reinstall Display Driver

A corrupt or outdated GPU driver is the second most common cause of a persistent blue tint.

1. Press Win + X → Device Manager.
2. Expand Display adapters, right-click your GPU, choose Update driver → Search automatically.
3. If the tint appeared after a driver update, choose Roll Back Driver instead.
4. For NVIDIA users experiencing nvlddmkm.sys issues, use DDU (Display Driver Uninstaller) in Safe Mode before reinstalling the latest driver from nvidia.com.
5. For AMD users with atikmdag.sys or amdkmdag.sys errors, use the AMD Cleanup Utility before reinstalling.

Part 2: Diagnosing Any Windows 10 BSOD Stop Code

When a stop code appears, Windows writes a minidump file to C:\Windows\Minidump\. Always start diagnosis here.

Step 1: Read the Stop Code

Note the exact error string on the blue screen, for example:

• CRITICAL_PROCESS_DIED (0x000000EF)
• MEMORY_MANAGEMENT (0x0000001A)
• KERNEL_SECURITY_CHECK_FAILURE (0x00000139)
• SYSTEM_SERVICE_EXCEPTION (0x0000003B)
• PFN_LIST_CORRUPT (0x0000004E)
• INACCESSIBLE_BOOT_DEVICE (0x0000007B)
• 0xC000021A / STATUS_SYSTEM_PROCESS_TERMINATED
• 0xC0000225 (Boot configuration data missing)
• APC_INDEX_MISMATCH (0x00000001)
• DRIVER_IRQL_NOT_LESS_OR_EQUAL (0x000000D1)
• BAD_POOL_HEADER / BAD_POOL_CALLER

Also note the faulting driver listed, e.g. ntoskrnl.exe, ndis.sys, tcpip.sys, nvlddmkm.sys, dxgmms2.sys, fltmgr.sys, classpnp.sys.

Step 2: Analyze Minidumps with BlueScreenView

Download BlueScreenView (NirSoft) — free, no install required. It reads .dmp files and shows the faulting driver highlighted in red. This is the fastest way to determine whether the problem is a driver, Windows component, or hardware.

Step 3: Check Event Viewer

Run eventvwr.msc → Windows Logs → System. Filter for Critical and Error events at the timestamp of each crash. Look for source BugCheck, Kernel-Power (Event ID 41 — unexpected shutdown), or specific driver names.

Part 3: Step-by-Step Fixes by Stop Code Category

Fix 1: System File Corruption (CRITICAL_PROCESS_DIED, ntoskrnl.exe, SYSTEM_SERVICE_EXCEPTION)

Boot normally or into Safe Mode (F8 or Shift+Restart → Troubleshoot → Advanced Options → Startup Settings → Safe Mode with Command Prompt).

Run the commands in the code_block section of this article. SFC repairs protected Windows files. DISM restores the Windows image component store. These two commands fix the majority of stop codes caused by Windows Update corruption.

Fix 2: Driver-Related BSODs (nvlddmkm.sys, ndis.sys, dxgmms2.sys, atikmdag.sys, fltmgr.sys)

1. Boot into Safe Mode with Networking.
2. Uninstall the problematic driver via Device Manager.
3. Delete residual driver files if needed.
4. Download the latest driver directly from the manufacturer's website.
5. For network-related drivers (ndis.sys, tcpip.sys, netio.sys): run netsh winsock reset and netsh int ip reset.

Fix 3: Memory/RAM Faults (MEMORY_MANAGEMENT, PFN_LIST_CORRUPT, BAD_POOL_HEADER, BAD_POOL_CALLER)

1. Run Windows Memory Diagnostic: press Win + R, type mdsched.exe, choose restart and check.
2. For thorough testing, boot from a MemTest86 USB (memtest86.com) and run at least 2 full passes.
3. If errors are found: reseat RAM sticks, test one stick at a time, replace faulty module.
4. Also check virtual memory: System Properties → Advanced → Performance Settings → Advanced → Virtual Memory — set to system-managed.

Fix 4: Storage/Boot Faults (INACCESSIBLE_BOOT_DEVICE, NTFS_FILE_SYSTEM, 0xC000021A, 0xC0000225)

1. Boot from Windows 10 installation media.
2. Choose Repair your computer → Troubleshoot → Advanced Options → Startup Repair first.
3. If Startup Repair fails, open Command Prompt and run the disk and BCD repair commands from the code block below.
4. For 0xC0000225 (missing BCD): rebuild the Boot Configuration Data with bootrec /rebuildbcd.
5. For INACCESSIBLE_BOOT_DEVICE after a Windows Update: roll back the update from WinRE → Uninstall Updates.

Fix 5: Third-Party Software / Antivirus BSODs (KERNEL_SECURITY_CHECK_FAILURE, WDF_VIOLATION, aswvmm.sys, mfeepmpk.sys)

Security software hooks deep into the kernel. If your BSOD appeared after installing Kaspersky, McAfee, or Avast:

1. Boot into Safe Mode.
2. Use the vendor's dedicated removal tool (e.g., Kaspersky KAVRemover, McAfee Consumer Product Removal Tool).
3. For WDF_VIOLATION on HP laptops: check for HP-specific driver updates via HP Support Assistant.
4. For VMware or BlueStacks BSODs: update the virtualization application or disable Hyper-V (bcdedit /set hypervisorlaunchtype off).

Fix 6: Blank Blue Screen / Blue Screen During Windows 10 Installation

• Blank/plain blue screen during install: disconnect all external USB devices except keyboard and mouse. Disable Secure Boot in BIOS. Disable Fast Boot.
• KERNEL_SECURITY_CHECK_FAILURE during install: the installation media may be corrupt — recreate the USB with the Media Creation Tool. Also check RAM.
• Blue screen after login: boot into Safe Mode and run SFC/DISM, or create a new user account to test for profile corruption.

Fix 7: Persistent Blue Screen Loop — Last Resorts

1. System Restore: WinRE → Troubleshoot → Advanced Options → System Restore. Choose a restore point before the BSODs started.
2. Reset this PC (Keep my files): WinRE → Troubleshoot → Reset this PC.
3. Clean reinstall: Back up data, boot from installation media, format the system partition, and reinstall Windows 10.

Preventing Future BSODs

• Keep Windows Update current but pause updates for 7 days after major releases to avoid day-one driver conflicts.
• Use Driver Verifier (verifier.exe) only in a test environment — it can force BSODs to identify a buggy driver but should not be left enabled.
• Monitor temperatures with HWiNFO64 — thermal throttling and overheating GPUs/CPUs trigger CLOCK_WATCHDOG_TIMEOUT and WHEA_UNCORRECTABLE_ERROR.
• Replace SSDs/HDDs showing reallocated sector counts in CrystalDiskInfo before they cause boot-time stop codes.
• Avoid mixing RAM kits with different timings — PFN_LIST_CORRUPT is frequently traced to mismatched DIMMs.