← Back to Blog

What Causes the Blue Screen of Death and How to Fix It

September 14, 2026 · LuxuriousComputers Repair, Marion OH

Your computer suddenly shows a blue screen with a sad face emoji, a stop code, and a message that it needs to restart. This is the Blue Screen of Death (BSOD) — Windows crashing because it encountered an error it cannot recover from. A BSOD means something went wrong at the system level: a driver failed, hardware malfunctioned, a critical system file was corrupted, or memory had an unrecoverable error. The stop code at the bottom of the blue screen tells you what category of failure occurred.

Common stop codes and what they mean

IRQL_NOT_LESS_OR_EQUAL

A driver or system process tried to access memory at an invalid address. This is almost always caused by a faulty or incompatible driver. It frequently appears after installing new hardware or updating drivers. The most common culprits are network adapter drivers, GPU drivers, and USB device drivers.

CRITICAL_PROCESS_DIED

A Windows system process that must be running at all times has stopped unexpectedly. This can be caused by corrupted system files, a failed Windows update, disk errors that corrupted system components, or malware that damaged critical files.

SYSTEM_SERVICE_EXCEPTION

A system service triggered an exception (an error it could not handle). Usually caused by a driver bug — the driver passed invalid data to a system function. GPU drivers and antivirus software are the most frequent sources of this error.

KERNEL_DATA_INPAGE_ERROR

Windows tried to read data from the page file (virtual memory on the disk) and the read failed. This points to a disk problem — bad sectors on the hard drive or SSD, a failing storage controller, or a loose SATA or NVMe connection. This stop code specifically indicates the storage subsystem could not deliver data the CPU was waiting for.

PAGE_FAULT_IN_NONPAGED_AREA

Windows requested data from RAM that should have been present but was not found. The most common cause is faulty RAM — a memory stick with defective cells that intermittently lose data. Can also be caused by a driver that corrupted the memory management tables.

WHEA_UNCORRECTABLE_ERROR

WHEA stands for Windows Hardware Error Architecture. This stop code means the hardware reported an error that the system could not correct. Common causes: CPU overheating (thermal throttling protection failed), unstable CPU overclock, failing RAM, or a power delivery problem on the motherboard. This is one of the more serious stop codes because it explicitly indicates hardware malfunction.

DPC_WATCHDOG_VIOLATION

A Deferred Procedure Call took too long to complete. In practical terms, a driver was doing something that took so long the system thought it was stuck. Storage drivers (especially after switching from IDE to AHCI mode or using generic Microsoft drivers instead of manufacturer NVMe drivers) and certain SSD firmware versions are common causes.

Software fixes

Update or roll back drivers

The majority of BSODs are caused by drivers. If the BSOD started after installing or updating a driver:

1. Boot into Safe Mode (restart, hold Shift while clicking Restart, navigate to Troubleshoot, Advanced Options, Startup Settings, restart, press 4 for Safe Mode)
2. Open Device Manager (right-click Start, Device Manager)
3. Find the recently updated device, right-click, Properties, Driver tab
4. Click Roll Back Driver to revert to the previous version

If you are not sure which driver caused the issue, update the most likely candidates: GPU driver (download the latest from the manufacturer and do a clean install using DDU in Safe Mode), chipset driver (from the motherboard manufacturer), and storage driver (from the SSD or motherboard manufacturer).

Run System File Checker

Corrupted Windows system files cause BSODs when the operating system tries to use a damaged file. Open Command Prompt as Administrator and run:

• sfc /scannow — Scans all protected system files and replaces corrupted ones from the Windows component store
• DISM /Online /Cleanup-Image /RestoreHealth — Repairs the component store itself (run this if SFC reports it found corruption but could not fix it)

After both commands complete, restart the computer and see if the BSOD recurs.

Check for Windows updates

Microsoft releases BSOD fixes through Windows Update, especially when a specific update caused widespread crashes. Check Settings, Windows Update for pending updates. Conversely, if the BSOD started right after an update, consider uninstalling the most recent update through Settings, Windows Update, Update History, Uninstall Updates.

Scan for malware

Malware that modifies system files, installs rootkit drivers, or corrupts the boot sector can cause BSODs. Run a full scan with Windows Defender (Windows Security, Virus and Threat Protection, Scan Options, Full Scan) and consider a second scan with Malwarebytes (free version) to catch threats that Windows Defender may miss.

Hardware diagnosis

Test RAM

Faulty RAM is one of the most common hardware causes of BSODs, and the symptoms are maddeningly random — different stop codes, different timing, no consistent pattern. Windows includes a memory test tool:

1. Type Windows Memory Diagnostic in the Start menu search
2. Select Restart now and check for problems
3. The computer restarts and runs a memory test. Results appear after login (check Windows Event Viewer, System log, source MemoryDiagnostics-Results if the notification disappears)

For a more thorough test, use MemTest86 (free) — create a bootable USB, boot from it, and run the test for at least 4 passes. MemTest86 tests memory more aggressively and catches errors that Windows Memory Diagnostic sometimes misses. Any errors found mean the RAM stick needs to be replaced.

Check disk health

Open Command Prompt as Administrator and run chkdsk C: /f /r (schedule it for the next restart). This scans the drive for file system errors and bad sectors. For SSDs, also check the drive's health using the manufacturer's tool (Samsung Magician, Crucial Storage Executive, Western Digital Dashboard) — SSDs track their own health metrics including remaining lifespan, error count, and temperature history.

Check temperatures

Overheating CPUs and GPUs can cause BSODs, especially under load. Download HWiNFO and monitor temperatures during normal use. CPU temperatures above 90 degrees Celsius under load or GPU temperatures above 95 degrees indicate a cooling problem — dust buildup, failed fans, or dried thermal paste.

Test with minimal hardware

If BSODs persist, simplify the system to isolate the cause. Remove all non-essential hardware — extra RAM sticks (leave one), USB devices, extra storage drives, PCIe cards. If the BSODs stop, add devices back one at a time until the problem returns. The last device added is the cause.

When BSODs happen repeatedly

A single BSOD can be a random fluke — cosmic ray, one-time driver hiccup, transient RAM error. Repeated BSODs with the same stop code point to a specific and consistent problem. Repeated BSODs with different stop codes suggest a foundational issue: RAM failure (causes errors in whatever process happens to use the bad memory addresses), an unstable overclock, or a failing power supply delivering inconsistent voltage.

BSOD help in Marion

If your computer keeps crashing with blue screen errors and you cannot identify the cause, LuxuriousComputers in Marion can run comprehensive hardware diagnostics — memory testing, drive health analysis, temperature monitoring, and driver analysis — to find the root cause and fix it before the underlying problem causes permanent data loss or component damage.

Related Articles