Blue Screen of Death (BSOD): What It Means and How to Fix It

Your computer was working fine. Then, without warning, the screen went solid blue, displayed a sad face and a cryptic error code, and restarted itself. Welcome to the Blue Screen of Death -- the most alarming error in Windows, and one of the most misunderstood.

A BSOD doesn't necessarily mean your computer is dying. In many cases, it's a software problem that can be fixed without replacing anything. This guide walks you through what the blue screen actually means, how to read the error information it gives you, and how to systematically fix the most common causes.

What a Blue Screen of Death Actually Is

A BSOD is a kernel-level crash. It means something went so wrong that Windows couldn't safely continue running. Rather than risk corrupting your files or damaging hardware, Windows halts everything and restarts.

Think of it like a circuit breaker tripping in your house. The breaker isn't the problem -- it's protecting you from the problem. The blue screen is Windows protecting itself from whatever caused the crash.

On Windows 10 and 11, the BSOD shows a sad face emoticon, a brief message ("Your PC ran into a problem"), a percentage counter as it collects crash data, and a stop code at the bottom. That stop code is the single most important piece of information for diagnosing the issue.

Important: Before the screen disappears, take a photo of it with your phone. The stop code and any file name mentioned (like ntfs.sys or nvlddmkm.sys) are critical for diagnosis. If you miss it, you can find the information later in Event Viewer under Windows Logs → System, looking for "BugCheck" entries.

Reading the QR Code and Error Information

Modern BSODs include a QR code that links to a Microsoft support page. Scanning it with your phone can be useful, but it usually leads to a generic troubleshooting page rather than a specific fix for your stop code.

More useful is the stop code itself, displayed in all caps at the bottom of the screen. Windows also sometimes shows a "What failed" line with the name of a specific driver or system file. That filename is your strongest lead. For example:

nvlddmkm.sys -- NVIDIA graphics driver
atikmdag.sys -- AMD graphics driver
ntfs.sys -- Windows file system driver (often points to disk problems)
tcpip.sys -- Network stack (network driver or VPN issue)
win32kfull.sys -- Windows display subsystem

If a third-party driver file is named, you've likely found your culprit. If it's a core Windows system file, the problem is deeper -- corrupted system files, bad RAM, or failing storage.

The 5 Most Common BSOD Stop Codes

1. IRQL_NOT_LESS_OR_EQUAL

This is the most frequent BSOD stop code. It means a driver or system process tried to access memory it wasn't allowed to touch. The cause is almost always a faulty or outdated driver -- particularly network adapters, Bluetooth, or USB device drivers. Overclocked RAM running at unstable timings can also trigger it.

2. CRITICAL_PROCESS_DIED

A process that Windows depends on to run crashed unexpectedly. This can be caused by corrupted system files, a bad Windows update, malware, or a failing hard drive. It's one of the more serious codes because it can indicate multiple overlapping problems.

3. SYSTEM_SERVICE_EXCEPTION

A system service encountered an error it couldn't handle. Usually caused by incompatible drivers, but antivirus software is a surprisingly common trigger -- especially third-party antivirus that hooks deep into the kernel. If this started after installing a new antivirus or security tool, that's your first suspect.

4. KERNEL_DATA_INPAGE_ERROR

Windows tried to read data from the page file (virtual memory on your disk) and couldn't retrieve it. This almost always points to a hardware problem -- either a failing hard drive, a bad SSD, or faulty RAM. If you see this code, back up your data immediately before doing anything else.

Warning: KERNEL_DATA_INPAGE_ERROR combined with clicking sounds from your hard drive is a strong indicator of imminent drive failure. Stop using the computer and back up your critical files to an external drive or cloud storage right away.

5. PAGE_FAULT_IN_NONPAGED_AREA

Windows tried to access a piece of memory that should have been available (non-paged = always in RAM, never swapped to disk) but wasn't there. Bad RAM is the most common cause, followed by corrupt drivers and disk errors. If it happens after adding new RAM sticks, one of them may be defective.

Driver Issues: The #1 Cause of Blue Screens

If we had to pick a single cause for the majority of BSODs we see, it's driver problems. Drivers are the software layer between Windows and your hardware. When a driver has a bug, accesses memory incorrectly, or conflicts with another driver, the result is often a blue screen.

The most problematic drivers, in our experience:

Graphics drivers (NVIDIA/AMD) -- These are large, complex, and updated frequently. A bad update or a driver version mismatched with your GPU model can cause constant BSODs.
Network and Wi-Fi drivers -- Especially Realtek and Intel wireless adapters. Generic Windows Update drivers sometimes conflict with manufacturer-specific ones.
USB and Bluetooth drivers -- Particularly when you plug in new peripherals that install their own driver stack.
Virtualization and security software -- Hyper-V, VMware, VPN clients, and some antivirus programs install kernel-level drivers that can conflict.

How to fix driver-related BSODs:

Open Device Manager (right-click Start → Device Manager)
Look for any device with a yellow warning triangle
If you identified the crashing driver file from the BSOD, right-click the matching device → Update driver → Search automatically
If updating doesn't help, try Roll Back Driver to the previous version
For GPU drivers specifically: use DDU (Display Driver Uninstaller) to completely remove the driver, then install a clean copy from the manufacturer's website

How to Use Safe Mode for BSOD Troubleshooting

If your computer blue-screens during startup and you can't reach the desktop, you need Safe Mode. Safe Mode loads Windows with only essential drivers, which bypasses most driver-related BSODs.

Getting into Safe Mode when you can't boot normally:

Force-restart your computer 3 times in a row (hold the power button during boot). This triggers Windows Recovery Environment.
Select Troubleshoot → Advanced options → Startup Settings → Restart
Press 4 for Safe Mode or 5 for Safe Mode with Networking (choose 5 if you might need to download drivers)

Once in Safe Mode, you can uninstall recently installed drivers, run diagnostics, or roll back a Windows update that may have caused the problem.

Pro tip: If the BSODs started after a specific event -- installing new hardware, updating a driver, running Windows Update -- focus there first. The timeline is your best diagnostic tool.

Running SFC and DISM to Repair System Files

Corrupted Windows system files are a common BSOD cause that's easy to fix. Windows includes two built-in repair tools that should be your first stop.

Step 1: System File Checker (SFC)

Open Command Prompt as Administrator (search "cmd," right-click, Run as administrator) and run:

sfc /scannow

This scans every protected system file and replaces corrupted ones from a cached copy. It takes 10-20 minutes. If it reports "Windows Resource Protection found corrupt files and successfully repaired them," the problem may be solved. Restart and test.

Step 2: DISM (if SFC can't fix everything)

Sometimes the cached copy SFC uses is itself corrupted. DISM pulls fresh copies from Windows Update. Run these three commands in order:

DISM /Online /Cleanup-Image /CheckHealth

DISM /Online /Cleanup-Image /ScanHealth

DISM /Online /Cleanup-Image /RestoreHealth

The RestoreHealth command can take 15-30 minutes and requires an internet connection. After it completes, run sfc /scannow again to verify the repair.

Checking RAM with Windows Memory Diagnostic

Bad RAM causes some of the most frustrating BSODs because the errors appear random -- different stop codes, different times, no obvious trigger. If you're getting blue screens that seem to have no pattern, RAM should be your prime suspect.

Built-in test:

Press Win + R, type mdsched.exe, and press Enter
Choose "Restart now and check for problems"
Your computer will reboot and run a memory test (this takes 10-30 minutes depending on how much RAM you have)
Results appear after you log back in -- check them in Event Viewer → Windows Logs → System, source "MemoryDiagnostics-Results"

The Windows tool does a basic scan. For a more thorough test, download MemTest86 and run it from a USB drive overnight. It tests more aggressively and catches errors the Windows tool misses.

If RAM errors are found: If you have multiple RAM sticks, remove one at a time and test to identify which stick is faulty. A single bad stick can cause constant instability even though the other sticks are fine.

Checking Disk Health

A failing storage drive can cause BSODs, especially KERNEL_DATA_INPAGE_ERROR and CRITICAL_PROCESS_DIED. Both HDDs and SSDs can fail, though they fail differently -- HDDs develop bad sectors and mechanical wear; SSDs lose write endurance and can fail suddenly.

Check disk health:

Open Command Prompt as Administrator and run: chkdsk C: /f /r -- this schedules a disk check on next restart. The /r flag locates bad sectors and recovers readable data.
For a quicker overview, run: wmic diskdrive get status -- if it reports anything other than "OK," your drive may be failing.
For SSDs, check the manufacturer's tool (Samsung Magician, Crucial Storage Executive, Western Digital Dashboard) to view remaining drive life percentage.

If your drive has bad sectors or is reporting poor health, back up your data first before attempting any repairs. A failing drive can go from "working with errors" to "completely dead" without warning.

Recent Windows Update Problems

Windows updates occasionally introduce BSODs, especially cumulative updates that include driver changes. This is more common than people realize -- Microsoft pushes driver updates through Windows Update, and sometimes those generic drivers conflict with your specific hardware configuration.

If BSODs started after a Windows update:

Go to Settings → Windows Update → Update History
Note the date and KB number of recent updates
Click Uninstall updates and remove the most recent one
If the BSODs stop, you can pause that specific update until Microsoft releases a fix

You can also use System Restore to roll your computer back to a point before the problematic update. Open Start, search "Create a restore point," click System Restore, and select a restore point from before the BSODs started.

When a BSOD Means Hardware Failure

Not every BSOD is a software problem. Here are signs that hardware is failing:

BSODs with different stop codes every time -- Random, varying errors strongly suggest bad RAM or a failing motherboard.
BSODs under heavy load only (gaming, video editing) -- Could be an overheating GPU, failing power supply that can't deliver enough power, or an unstable CPU overclock.
BSODs immediately after POST (before Windows even loads fully) -- Failing storage drive or critical hardware component.
BSODs accompanied by physical symptoms -- Clicking hard drive, burning smell, screen artifacts, USB ports not working. These need immediate attention.
BSODs that persist through a clean Windows install -- If you wipe the drive, install fresh Windows, and still get blue screens, the problem is definitely hardware.

Common hardware culprits in order of likelihood: RAM, storage drive, GPU, power supply, motherboard. CPU failure is rare but does happen, usually after overheating damage.

Quick test: If you suspect hardware, run Windows Memory Diagnostic for RAM, check SMART data for your drive, and monitor temperatures with a tool like HWiNFO. If your CPU is hitting 90C+ or your GPU is above 95C under load, overheating is your problem.

The Systematic BSOD Troubleshooting Checklist

When a customer comes to us with blue screen issues, here's the order we work through:

Identify the stop code and any named driver file -- Check Event Viewer if you didn't capture the screen
Check the timeline -- What changed before the BSODs started? New hardware, driver update, Windows update, new software?
Boot into Safe Mode -- If BSODs don't occur in Safe Mode, it's almost certainly a driver or software issue
Update or roll back the suspected driver -- Especially GPU, network, and Bluetooth drivers
Run SFC and DISM -- Repair any corrupted system files
Test RAM -- Run Windows Memory Diagnostic or MemTest86
Check disk health -- Run chkdsk and check SMART status
Uninstall recent Windows updates if the timeline matches
Check temperatures -- Rule out thermal throttling and overheating
If nothing works -- Consider a clean Windows install. If BSODs persist after that, it's hardware.

Most BSODs we encounter are resolved by steps 3-5. Driver problems and corrupted system files account for roughly 70% of all blue screen cases we handle. RAM and disk issues cover another 20%. True motherboard or CPU failures are the remaining 10%.