How to Fix Blue Screen of Death (BSOD)

The Blue Screen of Death is Windows telling you something went critically wrong at the system level. Unlike application crashes where a single program stops working, a BSOD means the entire operating system encountered a condition it cannot recover from. The computer restarts, work is lost, and the user submits an urgent ticket.

BSODs are alarming but they are rarely random. Every blue screen includes a stop code that identifies the category of failure. Once you know the stop code, the troubleshooting path narrows significantly. This guide covers the most common stop codes, what causes them, and exactly how to fix each one.

Common Causes of Blue Screen Errors

• Faulty or incompatible device drivers
• Defective RAM modules
• Corrupted system files
• Overheating hardware
• Failing hard drive or SSD
• Recently installed software or updates
• Hardware conflicts from new peripherals

Step 1: Note the Stop Code

When a BSOD occurs, Windows displays a stop code at the bottom of the blue screen. Common codes include IRQL_NOT_LESS_OR_EQUAL, DRIVER_IRQL_NOT_LESS_OR_EQUAL, PAGE_FAULT_IN_NONPAGED_AREA, SYSTEM_SERVICE_EXCEPTION, CRITICAL_PROCESS_DIED, and KERNEL_DATA_INPAGE_ERROR. Write down or photograph the stop code - it is your primary diagnostic tool.

If you missed the stop code, open Event Viewer (search "Event Viewer" in the Start menu), go to Windows Logs, then System, and look for Critical-level events with source "BugCheck." The event details include the stop code and any associated driver or file that triggered the crash. You can also check Settings, then System, then About, then "Advanced system settings," then Startup and Recovery to ensure Windows is configured to write a dump file for future crashes.

Step 2: Check for Recently Installed Drivers

The single most common cause of BSODs is a driver problem - a recently updated driver that is incompatible, corrupted during installation, or conflicts with another driver. This is especially common after Windows Update pushes a new driver automatically.

If the BSOD started after a driver update, roll back the driver. Open Device Manager, find the device whose driver was recently updated (often the graphics card, network adapter, or chipset), right-click it, select Properties, go to the Driver tab, and click "Roll Back Driver." If the rollback option is grayed out, the previous driver was not saved. In that case, download the previous version from the manufacturer's website and install it manually.

The stop codes IRQL_NOT_LESS_OR_EQUAL and DRIVER_IRQL_NOT_LESS_OR_EQUAL almost always point to driver issues. If the blue screen mentions a specific .sys file (like nvlddmkm.sys for NVIDIA or atikmdag.sys for AMD), that tells you exactly which driver is causing the crash.

Step 3: Run Windows Memory Diagnostics

Faulty RAM causes BSODs that seem random because they depend on which memory address the system happens to use. The stop codes PAGE_FAULT_IN_NONPAGED_AREA and KERNEL_DATA_INPAGE_ERROR frequently indicate memory problems.

Search for "Windows Memory Diagnostic" in the Start menu and run it. The tool will schedule a memory test on the next restart. Let it run the standard test - it takes 10-20 minutes. If it reports errors, you have confirmed a hardware problem. The failing RAM module needs to be identified and replaced.

For a more thorough test, download and run MemTest86 from a USB boot drive. It runs outside Windows and tests memory more exhaustively. Let it run for at least two full passes. Any errors mean the RAM is defective. If the computer has multiple RAM sticks, remove one at a time and test each individually to identify which module is bad.

Step 4: Run System File Checker

Corrupted Windows system files can cause BSODs, especially CRITICAL_PROCESS_DIED and SYSTEM_SERVICE_EXCEPTION. The System File Checker tool scans protected system files and replaces corrupted ones from a cached copy.

Open an elevated Command Prompt and run these commands in order:

1. DISM /Online /Cleanup-Image /RestoreHealth - this repairs the Windows component store first, which SFC needs as its source for clean files. This takes 5-15 minutes and requires an internet connection.
2. sfc /scannow - this scans all protected system files and replaces any that are corrupted or modified. It takes 10-20 minutes. Do not interrupt it.

If SFC reports that it found and repaired corrupt files, restart the computer and monitor for further BSODs. If it reports files it could not repair, the corruption may be too extensive for in-place repair. A repair install of Windows (keeping files and applications) is the next option before a full reinstall.

Step 5: Check the Hard Drive or SSD

A failing storage drive causes BSODs because the operating system cannot read or write critical data. KERNEL_DATA_INPAGE_ERROR and UNEXPECTED_STORE_EXCEPTION often point to storage issues.

Open an elevated Command Prompt and run "chkdsk C: /f /r." This will schedule a disk check on the next restart since the system drive cannot be checked while Windows is running. Restart and let the check complete - it can take 30-60 minutes on large drives. CHKDSK will find and attempt to repair filesystem errors and mark bad sectors.

For SSDs, check the drive's health using the manufacturer's tool (Samsung Magician, Crucial Storage Executive, Western Digital Dashboard). These tools report the drive's remaining life percentage and any warning indicators. An SSD reporting less than 10% remaining life or any "Warning" or "Critical" health status should be replaced promptly - data loss is imminent.

Step 6: Uninstall Recent Updates or Software

If BSODs started after a Windows Update, uninstall the recent update. Go to Settings, then Windows Update, then Update History, then "Uninstall updates." Find the update installed around the time the BSODs started and uninstall it. You can then pause updates temporarily while waiting for Microsoft to release a fix.

Similarly, if you recently installed new software (especially system-level tools like antivirus, VPN clients, disk encryption, or virtualization software), uninstall it to test. These tools install kernel-level drivers that can conflict with existing system drivers and cause BSODs.

Step 7: Check for Overheating

Overheating causes BSODs because the CPU or GPU reaches a temperature where it either throttles too aggressively for the system to function or triggers a thermal emergency shutdown. These BSODs tend to happen under load - during heavy work, gaming, or compilation tasks - and rarely at idle.

Install HWMonitor or Core Temp and check temperatures during normal use and under load. CPU temperatures above 95 degrees Celsius under load indicate a cooling problem. Clean dust from fans and heatsinks with compressed air. For laptops, ensure the vents are not blocked. For desktops, check that all case fans are running and that the CPU fan is properly seated.

Step 8: Boot Into Safe Mode for Persistent BSODs

If the computer crashes too frequently to complete any of the above steps, boot into Safe Mode. Safe Mode loads Windows with only essential drivers and services, which eliminates most driver-related BSOD causes.

To enter Safe Mode, interrupt the boot process three times (turn on, wait for the Windows logo, hold the power button to force off, repeat). On the fourth boot, Windows enters the recovery environment. Select Troubleshoot, then Advanced Options, then Startup Settings, then Restart. Press 4 or F4 for Safe Mode, or 5 or F5 for Safe Mode with Networking.

Once in Safe Mode, run the diagnostic steps above. If the computer is stable in Safe Mode, the problem is almost certainly a third-party driver or service. Use Device Manager to roll back or uninstall recently changed drivers, and use msconfig to disable third-party startup services one at a time to identify the culprit.

When to Escalate to IT Support

Escalate to IT support if:

1. BSODs occur in Safe Mode - this strongly indicates a hardware failure (RAM, CPU, motherboard, or storage)
2. Memory Diagnostic or MemTest86 reports errors - RAM replacement requires hardware access
3. The drive health tool reports warnings or critical status - drive replacement and data migration need to happen before data loss
4. The same BSOD occurs across multiple machines in the office - this suggests a bad update, a group policy change, or a network driver issue deployed organization-wide
5. You cannot identify the failing driver or component after completing the steps above - the crash dump files need analysis with Windows Debugging Tools (WinDbg), which requires specialized knowledge