How to Fix the Blue Screen of Death on Windows

The Blue Screen of Death, or BSOD, is Windows telling you that something went so wrong it had to shut everything down to prevent damage. The screen shows a stop code, a frowning face, and sometimes a percentage as it collects crash data. It is alarming, but in most cases the underlying problem is fixable once you know what the stop code means and where to look.

What the stop code tells you

Every BSOD displays a stop code at the bottom of the screen. This code is the single most useful piece of information for diagnosing the crash. The most common ones and what they usually mean:

• IRQL_NOT_LESS_OR_EQUAL — a driver tried to access memory it should not have. Almost always a driver problem, most often a recently installed or updated driver
• CRITICAL_PROCESS_DIED — a system process that Windows depends on stopped unexpectedly. Can be caused by corrupted system files, a failing drive, or malware
• SYSTEM_SERVICE_EXCEPTION — a system service caused an error, typically a driver or antivirus conflict
• KERNEL_DATA_INPAGE_ERROR — Windows could not read data from the disk into memory. This is often a sign of a failing hard drive or SSD, or a problem with RAM
• PAGE_FAULT_IN_NONPAGED_AREA — the system tried to access memory that does not exist. Usually points to faulty RAM or a driver bug
• WHEA_UNCORRECTABLE_ERROR — a hardware error detected by the Windows Hardware Error Architecture. Common with overheating CPUs, unstable overclocks, or failing hardware
• DPC_WATCHDOG_VIOLATION — a driver took too long to complete an operation. Frequently caused by storage drivers, especially after switching from a SATA drive to NVMe without updating the storage controller driver
• DRIVER_IRQL_NOT_LESS_OR_EQUAL — similar to IRQL_NOT_LESS_OR_EQUAL but specifically names the offending driver file. The filename shown on the BSOD screen tells you exactly which driver to update or roll back

If you missed the stop code because the computer restarted too quickly, you can find it in Event Viewer. Open Event Viewer, expand Windows Logs, click System, and look for a Critical event with source BugCheck around the time of the crash. The parameters listed are the stop code.

First steps after a blue screen

If the computer restarts normally after the BSOD and you can get to the desktop, start here:

Check for Windows updates

Open Settings, then Windows Update, then Check for updates. Microsoft regularly releases patches that fix known BSOD-causing bugs in Windows itself. Install all pending updates and restart.

Check recently installed software and drivers

Think about what changed before the BSODs started. A new program, a driver update, a Windows update, or a new piece of hardware are the most common triggers. If you can pinpoint when the crashes began, you can often pinpoint the cause.

To check recent driver changes: open Device Manager, right-click the device you suspect, click Properties, then the Driver tab. If the driver date is recent and matches when the crashes started, click Roll Back Driver to return to the previous version.

Run System File Checker

Corrupted Windows system files can cause unpredictable BSODs. Open Command Prompt as administrator and run:

sfc /scannow

This scans all protected system files and replaces corrupted ones from a cached copy. If it reports that it found and fixed files, restart and see if the BSODs stop. If SFC reports corruption it cannot fix, run DISM first:

DISM /Online /Cleanup-Image /RestoreHealth

Then run sfc /scannow again.

Hardware-related blue screens

If the stop code points to hardware (WHEA_UNCORRECTABLE_ERROR, KERNEL_DATA_INPAGE_ERROR, PAGE_FAULT_IN_NONPAGED_AREA), or if the crashes happen during heavy workloads like gaming, video editing, or file transfers, the problem may be physical.

Test your RAM

Bad RAM is one of the most common and most frustrating causes of BSODs because the symptoms are random and inconsistent. Windows has a built-in memory test:

1. Press Windows + R, type mdsched.exe, and press Enter
2. Choose Restart now and check for problems
3. The computer will restart and run a memory test before Windows loads. This takes 10 to 20 minutes
4. After the test, Windows will boot normally and show the results in a notification

The Windows memory test catches obvious failures but misses subtle ones. For a more thorough test, download MemTest86 (free), create a bootable USB drive, and let it run for at least 4 passes. Any errors mean the RAM stick needs replacing.

If you have multiple RAM sticks, you can isolate the bad one by testing with one stick at a time. Remove all but one, run the test, swap to the next stick, repeat.

Check your hard drive or SSD health

A failing storage drive can cause BSODs when Windows tries to read corrupted data or cannot access the drive fast enough. Open Command Prompt as administrator and run:

wmic diskdrive get status

If it returns anything other than OK, the drive may be failing. For more detail, install CrystalDiskInfo (free). Look at the Health Status indicator. Caution or Bad means the drive should be replaced before it fails completely.

For a deeper scan, run chkdsk C: /f /r from an elevated Command Prompt. This will schedule a scan on the next restart. It checks for file system errors and attempts to recover data from bad sectors.

Check temperatures

An overheating CPU will either throttle itself (slowing down to reduce heat) or trigger a BSOD, typically WHEA_UNCORRECTABLE_ERROR. Install HWMonitor or Core Temp and watch the CPU temperature under load. A CPU consistently hitting 90 degrees Celsius or higher under normal use needs attention, usually dust cleaning, thermal paste replacement, or a better cooler.

Driver-related blue screens

Drivers are the number one cause of BSODs. A driver is a piece of software that lets Windows communicate with a hardware component, and a buggy driver can crash the entire system.

Identify the problem driver

Some BSODs name the driver file directly on the crash screen (like nvlddmkm.sys for NVIDIA graphics or Realtek.sys for audio). If yours did, you know exactly which driver to target.

If it did not name a file, use a free tool called BlueScreenView from NirSoft. It reads the crash dump files Windows saves and shows which driver was involved in each crash. Look at the Caused By Driver column.

Update or roll back the driver

If the problem driver is identified:

• GPU drivers (NVIDIA, AMD, Intel): download the latest stable driver directly from the manufacturer's website, not through Windows Update. For NVIDIA, choose Studio or Game Ready drivers. If the crash started after a GPU driver update, use Display Driver Uninstaller (DDU) in Safe Mode to completely remove the driver, then install an older stable version
• Audio, network, chipset drivers: go to your laptop or motherboard manufacturer's support page and download the driver for your specific model
• USB or Bluetooth drivers: these are less commonly the cause, but if Device Manager shows a warning icon on any device, right-click it and update or reinstall the driver

If BSODs happen before you can reach the desktop

When the computer blue screens during or immediately after booting, you cannot run diagnostic tools normally. Windows should automatically enter the Recovery Environment after two or three failed boot attempts. From there:

1. Choose Troubleshoot, then Advanced options
2. Try Startup Repair first. It attempts to fix common boot problems automatically
3. If Startup Repair does not help, go back to Advanced options and open Safe Mode (under Startup Settings). Safe Mode loads Windows with minimal drivers. If the computer is stable in Safe Mode, the problem is a third-party driver or program
4. In Safe Mode, uninstall recently added programs, roll back recently updated drivers, or run sfc /scannow
5. If the BSOD happens even in Safe Mode, the problem is likely hardware (RAM, drive, motherboard) or deep system corruption that may need a Windows reinstall

When a clean install is the answer

If you have tried driver updates, memory tests, disk checks, and system file repair and the BSODs continue, a clean reinstall of Windows eliminates any software cause. If the BSODs persist on a fresh Windows installation, the problem is definitively hardware and the affected component needs to be identified and replaced.

Before reinstalling, back up your files. A clean install wipes the system drive. Use an external drive or cloud storage to save documents, photos, and anything else you cannot redownload.

Blue screen repair in Marion

LuxuriousComputers in Marion diagnoses and fixes blue screen crashes on Windows desktops and laptops. We read the crash dumps, test the RAM and storage, check for driver conflicts, and identify whether the problem is software or hardware. If a component is failing, we replace it. If the system needs a clean install, we back up your data first.