How to Fix a Windows Blue Screen of Death (BSOD)

Few things are more jarring than watching your screen suddenly turn blue, fill with cryptic text, and force your computer to restart. Known as the Blue Screen of Death (BSOD), this error is Windows’ way of protecting your system when it encounters a problem so serious that it can’t continue running safely. While it can feel alarming, a BSOD is rarely catastrophic — it’s usually Windows stopping itself before a deeper issue (like data corruption or hardware damage) can occur.

BSODs can be triggered by a wide range of issues: faulty or outdated drivers, incompatible hardware, corrupted system files, malware, overheating components, or even a failing hard drive. Each crash typically displays a “stop code” (such as MEMORY_MANAGEMENT, CRITICAL_PROCESS_DIED, or IRQL_NOT_LESS_OR_EQUAL), which acts as a clue to help narrow down the cause. Modern versions of Windows (10 and 11) also display a QR code you can scan for more information, though it usually just links to a generic support page.

The good news is that most BSOD issues can be resolved without professional help or a full system reinstall. This guide walks through four proven methods to diagnose and fix a Blue Screen of Death, starting with the simplest fixes and moving toward more advanced troubleshooting. By the end, you’ll have a clear action plan for getting your PC back to stable, everyday use.

Method 1: Identify the Stop Code and Recent Changes

Before applying any fix, it helps to gather information. Every BSOD displays a stop code — a short identifier like 0x0000007B or a name like DRIVER_IRQL_NOT_LESS_OR_EQUAL. This code is your single most useful diagnostic clue, since different codes point to different root causes (memory issues, driver conflicts, disk errors, and so on).

Steps to identify the cause:

1. Write down the stop code shown on the blue screen, or check it later in Windows’ Reliability Monitor (search “Reliability Monitor” in the Start menu) or Event Viewer (Windows Logs > System, look for “Critical” events around the crash time).
2. Think about recent changes. Did you install new hardware, update a driver, install new software, or apply a Windows update shortly before the crash started? BSODs are frequently triggered by something that changed recently, so this timeline is often the fastest path to a fix.
3. Search the exact stop code alongside “Windows 10” or “Windows 11” to see if it’s a known issue tied to a specific driver or piece of hardware.
4. Check for a minidump file. Windows automatically saves crash logs in C:\Windows\Minidump. Tools like the free BlueScreenView (by NirSoft) can read these files and show you exactly which driver or process caused the crash — often the single most efficient way to pinpoint a fix.

If you recently installed a new update, driver, or software, the fix might be as simple as rolling that back. If nothing has changed recently, the issue is more likely tied to failing hardware or a deeper corruption, and you’ll want to move on to the following methods.

Method 2: Update or Roll Back Drivers

Outdated, corrupted, or incompatible drivers are one of the most common causes of BSODs — especially graphics drivers, network adapter drivers, and drivers for peripherals like printers or external storage.

To update drivers:

1. Open Device Manager (right-click the Start button and select it).
2. Look for devices with a yellow warning triangle, which indicates a driver problem.
3. Right-click the device and choose Update driver > Search automatically for drivers.
4. For graphics cards specifically, it’s often better to download the latest driver directly from the manufacturer’s website (NVIDIA, AMD, or Intel) rather than relying solely on Windows Update, since manufacturer drivers tend to be more current and better optimized.

To roll back a driver (useful if the BSOD started right after an update):

1. In Device Manager, right-click the relevant device and select Properties.
2. Go to the Driver tab.
3. Click Roll Back Driver if the option is available. If it’s grayed out, no previous version is stored, and you’ll need to manually reinstall an older driver from the manufacturer’s site.

If you identified a specific driver from the minidump analysis in Method 1, prioritize updating or rolling back that driver first — it will save considerable trial and error.

Method 3: Run System File and Disk Checks

Corrupted system files or a failing hard drive can both trigger BSODs, and Windows includes built-in tools to detect and repair both issues.

Run System File Checker (SFC):

1. Search for “Command Prompt,” right-click it, and select Run as administrator.
2. Type sfc /scannow and press Enter.
3. Let the scan complete — it checks all protected system files and automatically repairs corrupted ones it finds.

Run DISM (Deployment Image Servicing and Management):

If SFC reports errors it can’t fix, DISM can repair the underlying Windows image that SFC relies on:

1. In the same administrator Command Prompt, type DISM /Online /Cleanup-Image /RestoreHealth and press Enter.
2. This process can take 10–20 minutes and requires an internet connection.
3. Once complete, run sfc /scannow again to confirm the repair worked.

Check your disk for errors:

1. In the administrator Command Prompt, type chkdsk C: /f /r and press Enter.
2. You’ll likely be prompted to schedule the scan for the next restart — type Y and restart your computer.
3. The scan checks for and attempts to repair bad sectors and file system errors, which are common culprits behind BSODs related to storage.

Check memory (RAM) for errors:

1. Search for “Windows Memory Diagnostic” and open it.
2. Choose Restart now and check for problems.
3. Your PC will restart and run a memory test before booting back into Windows, flagging any faulty RAM modules.

Method 4: Use System Restore or Reset Windows

If the previous methods haven’t resolved the issue, it’s time to consider a more comprehensive reset.

System Restore rolls your computer’s system files and settings back to a previous point in time, without affecting personal files:

1. Search for “Create a restore point” and open System Properties.
2. Click System Restore.
3. Choose a restore point from before the BSODs started (ideally right before a suspicious update or installation).
4. Follow the prompts to complete the restoration and restart your PC.

If BSODs prevent you from booting normally, you’ll need to access the Windows Recovery Environment:

1. Force a shutdown three times in a row during boot-up to trigger Automatic Repair, or boot from a Windows installation USB and select Repair your computer.
2. Navigate to Troubleshoot > Advanced options > System Restore (or Startup Repair to let Windows attempt an automatic fix).

Reset This PC (a more drastic step):

1. Go to Settings > System > Recovery.
2. Under “Reset this PC,” choose Reset PC.
3. Select Keep my files to preserve personal documents while reinstalling Windows system files, or Remove everything for a completely clean slate if you suspect deep corruption or malware.

This method should generally be considered a last resort after driver updates, file repairs, and restore points have failed to resolve the problem, since it involves more time and, in the case of a full reset, the loss of installed applications.

Conclusion

A Blue Screen of Death can be unsettling, but it’s rarely a sign that your computer is beyond saving. By working through these four methods — identifying the stop code and recent changes, updating or rolling back drivers, running system file and disk checks, and using System Restore or a full reset as a last resort — you can resolve the vast majority of BSOD issues without professional repair.

The key is to work systematically: start with the least invasive fixes and only escalate if the problem persists. Keeping track of the specific stop code and any patterns (does it happen during gaming, right after waking from sleep, or randomly?) will make each step faster and more targeted. And once your system is stable again, keeping drivers updated and running periodic disk and memory checks can help prevent future crashes before they start.

Frequently Asked Questions

1. Is a Blue Screen of Death dangerous to my computer or files?

Generally, no. The BSOD is actually a protective mechanism — Windows detects a critical error and stops itself to prevent further damage, such as file system corruption. In most cases, your files remain safe. However, frequent BSODs can occasionally indicate a failing hard drive, in which case there’s a risk of data loss if the drive fails completely. If crashes are frequent, back up important files as a precaution while you troubleshoot.

2. Why does my computer keep getting the same BSOD error repeatedly?

A recurring identical stop code usually points to a consistent underlying cause — most often a specific driver, a piece of failing hardware, or a corrupted system file that hasn’t been fully repaired. Repeated crashes with the same code are actually helpful for troubleshooting, since they let you rule out random causes (like overheating) and focus on the software or hardware component directly tied to that code.

3. Can overheating cause a Blue Screen of Death?

Yes. Overheating is a common but often overlooked cause of BSODs, particularly under heavy use like gaming or video editing. When components like the CPU or GPU exceed safe temperatures, Windows may crash to prevent hardware damage. If your BSODs happen mainly during demanding tasks, check that fans and vents are free of dust, ensure proper airflow, and consider monitoring temperatures with a tool like HWMonitor or Core Temp.

4. Should I take my computer to a professional if none of these methods work?

If you’ve worked through driver updates, system file repairs, disk and memory checks, and a System Restore without success, it’s a reasonable point to consult a professional — especially if you suspect failing hardware like a dying hard drive or faulty RAM that needs physical replacement. A technician can run more advanced diagnostics on individual components (like a dedicated hardware stress test) that go beyond what’s practical to do without specialized tools.