How to Fix BSOD Blue Screen of Death Crashes

Published 2026-10-16 · LuxuriousComputers Repair

Your computer crashes to a blue screen, shows an error code, and restarts. It might happen during gaming, while working, or even sitting idle. Blue screen crashes (BSODs) happen when Windows encounters a critical error that it cannot recover from — a bad driver, failing hardware, corrupted system files, or unstable overclocks. The stop code displayed on the blue screen is the key to finding the cause.

Find the stop code

Every BSOD shows a stop code near the bottom of the screen. Common examples include IRQL_NOT_LESS_OR_EQUAL, PAGE_FAULT_IN_NONPAGED_AREA, SYSTEM_SERVICE_EXCEPTION, and WHEA_UNCORRECTABLE_ERROR. If the computer restarts too quickly to read it:

• Disable automatic restart: Right-click This PC, Properties, Advanced System Settings, Startup and Recovery Settings. Uncheck Automatically Restart. The next BSOD will stay on screen until you manually restart
• Event Viewer: Open Event Viewer, Windows Logs, System. Filter for Critical events with source BugCheck. Each entry contains the stop code and the associated driver or module
• Reliability Monitor: Search for Reliability Monitor in the Start menu. It shows a timeline of system crashes with dates and details, making it easy to correlate crashes with software installations or updates

Driver-caused blue screens

Drivers are responsible for the majority of BSODs. A buggy, outdated, or incompatible driver running at the kernel level can crash the entire system:

Graphics drivers

The most common BSOD source. Stop codes that frequently point to graphics drivers include VIDEO_TDR_FAILURE, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (with nvlddmkm.sys or atikmpag.sys), and DPC_WATCHDOG_VIOLATION:

• Download the latest driver directly from NVIDIA GeForce Experience, AMD Radeon Software, or Intel's support site — not through Windows Update, which often has older versions
• If BSODs started after a driver update, roll back: Device Manager, Display Adapters, right-click your GPU, Properties, Driver, Roll Back Driver
• For persistent graphics driver crashes, use DDU (Display Driver Uninstaller) in Safe Mode to completely remove the driver, then install fresh

Network and Wi-Fi drivers

Stop codes mentioning ndis.sys, tcpip.sys, or a network adapter name point to network drivers. Update from the laptop or motherboard manufacturer's support page.

Recently installed hardware

If BSODs started after connecting new hardware (USB devices, printers, Bluetooth adapters, capture cards), that device's driver is the likely cause. Disconnect the device and see if BSODs stop. If they do, check for an updated driver from the device manufacturer.

RAM problems

Faulty RAM causes random BSODs with varying stop codes because the errors appear in different parts of memory each time. Common RAM-related stop codes include MEMORY_MANAGEMENT, KERNEL_DATA_INPAGE_ERROR, and PAGE_FAULT_IN_NONPAGED_AREA:

Test RAM

1. Search for Windows Memory Diagnostic in the Start menu
2. Select Restart now and check for problems
3. The test runs before Windows loads and reports results after the next boot
4. For more thorough testing, create a MemTest86 bootable USB and run it overnight. Quick passes miss intermittent errors that only appear after extended testing

XMP and memory overclocking

If you enabled XMP (Intel) or DOCP (AMD) in the BIOS to run RAM at its rated speed, the overclock may be unstable with your specific hardware:

• Enter BIOS and disable XMP/DOCP. Test at default RAM speed for several days
• If BSODs stop, the memory overclock was unstable. Try a less aggressive XMP profile if available, or manually set a slightly lower frequency than the rated speed
• RAM rated for a specific speed is not always stable at that speed on every motherboard — compatibility varies

Storage drive failures

A failing SSD or hard drive causes BSODs when Windows cannot read critical data. KERNEL_DATA_INPAGE_ERROR and NTFS_FILE_SYSTEM are common stop codes for storage problems:

• Check SMART data: Download CrystalDiskInfo. If the drive shows Caution or Bad, it is failing. Key metrics to check: Reallocated Sectors Count, Current Pending Sectors, and UltraDMA CRC Error Count
• Run chkdsk: Open Command Prompt as Administrator, run chkdsk C: /f /r. This scans and repairs file system errors and checks the physical drive surface
• Hard drive sounds: If a hard drive makes clicking, grinding, or repetitive ticking sounds, back up data immediately. These sounds indicate imminent mechanical failure

System file repair

Corrupted Windows system files cause unpredictable BSODs because critical system components malfunction:

1. Open Command Prompt as Administrator
2. Run: sfc /scannow — scans protected system files and repairs corruption from a cached copy
3. If SFC finds unrepairable corruption: DISM /Online /Cleanup-Image /RestoreHealth — repairs the image SFC uses as its source
4. Run sfc /scannow again after DISM completes
5. Restart and monitor

Overheating

Excessive heat causes electronic components to malfunction, leading to BSODs. WHEA_UNCORRECTABLE_ERROR is a common heat-related stop code:

• Monitor temperatures with HWMonitor or Core Temp. CPU temperatures above 90 degrees Celsius during normal use indicate a cooling problem
• Clean dust from the CPU heatsink, case fans, and exhaust vents. A heavily dusted heatsink can raise temperatures by 20 to 30 degrees
• Check that all fans are spinning. A stopped CPU fan causes rapid overheating
• On laptops, blocked exhaust vents (from using it on a bed or couch) are a common cause

Power supply issues (desktop)

An unstable or failing power supply causes random BSODs, especially under load:

• BSODs that happen specifically during gaming, rendering, or other high-load tasks suggest the power supply cannot deliver stable power under demand
• A power supply near end-of-life may deliver unstable voltage. Test with a known-good power supply or a PSU tester
• If you recently added a new graphics card or other components, the power supply may not have enough wattage for the increased load

BIOS update

Motherboard BIOS updates fix stability issues, improve hardware compatibility, and address bugs that can cause BSODs:

• Check your motherboard manufacturer's website for the latest BIOS version
• Read the changelog — if it mentions stability fixes for your hardware type, the update may fix your BSODs
• Follow the manufacturer's BIOS update instructions carefully. Use a stable power source during the update

Windows update

Both missing updates and problematic updates can cause BSODs:

• Install all pending updates: Settings, Windows Update, Check for Updates
• If BSODs started after a specific Windows update, check if an uninstall option is available: Settings, Windows Update, Update History, Uninstall Updates
• Microsoft releases out-of-band patches for updates that cause widespread BSODs — check again for updates if one was recently installed

Clean boot

A clean boot isolates whether a third-party service or program is causing the crashes:

1. Press Windows+R, type msconfig, press Enter
2. Services tab: check Hide All Microsoft Services, then click Disable All
3. Startup tab: click Open Task Manager, disable all startup items
4. Restart. If BSODs stop, re-enable services in groups to find the culprit

Safe Mode

If BSODs are too frequent to troubleshoot normally:

1. Hold Shift and click Restart from the login screen
2. Troubleshoot, Advanced Options, Startup Settings, Restart
3. Press 4 for Safe Mode. Safe Mode loads only essential drivers
4. If stable in Safe Mode, the problem is a non-essential driver or third-party software

BSOD diagnosis in Columbus or Delaware

If your computer keeps blue screening and the troubleshooting above did not identify the cause, LuxuriousComputers can analyze crash dump files, test RAM, storage drives, and the power supply, identify the specific driver or component responsible, and fix the root cause of the blue screen crashes.