How to Fix the Blue Screen of Death (BSOD)

The Blue Screen of Death (BSOD) is a Windows stop error that halts the system and displays a stop code, and the most common cause is a faulty or incompatible device driver. Other frequent causes include defective RAM, corrupt system files, failing storage, overheating, a recent Windows update, and malware. This article explains what a BSOD is, how to read the stop code and identify the failing driver, and the step-by-step fixes that resolve most crashes.

Each fix names the exact Windows tool to use, including Windows Event Viewer, BlueScreenView, the Windows Memory Diagnostic, SFC, and DISM. The fixes are ordered from the most common and least disruptive to hardware checks and recovery options such as Safe Mode and System Restore.

Apply the fixes in order and test stability after each one, because a single driver or hardware fault usually accounts for the crash. A reference table at the end lists the most common stop codes and their meanings.

What Causes a Blue Screen of Death?

A Blue Screen of Death is caused by an error in kernel-mode code that Windows cannot recover from safely, so the operating system stops to protect data and hardware. The causes below are ranked from most to least common.

• Faulty or incompatible device drivers. A driver that accesses memory incorrectly or fails a system check is the leading cause of stop errors.
• Defective or unstable RAM. Bad memory cells corrupt data in transit and trigger codes such as MEMORY_MANAGEMENT and PAGE_FAULT_IN_NONPAGED_AREA.
• Corrupt system files. Damaged Windows components from a failed update or disk error cause crashes during boot or normal use.
• Failing storage drives. Bad sectors and a failing SSD or hard drive cause read errors that the kernel cannot resolve.
• Overheating hardware. A CPU or GPU above its thermal limit produces calculation errors that surface as stop codes.
• A recent Windows update or driver update. An incompatible patch can destabilize the system immediately after installation.
• Malware. Rootkits and other malware that modify kernel components cause integrity-check failures and crashes.

How to Read the BSOD Stop Code

Reading the stop code is the first step, because the code names the type of fault and points to the correct fix. Modern Windows shows a short stop-code name and a QR code on the blue screen.

1. Record the stop-code name shown on the screen, such as DRIVER_POWER_STATE_FAILURE or IRQL_NOT_LESS_OR_EQUAL.
2. Note any file name listed under “What failed,” because a name ending in .sys identifies a driver.
3. Scan the QR code with a phone to open the Microsoft support page for that stop code.
4. If the screen clears too fast, read the code from Event Viewer or a minidump after restart.

The stop code and the failing file together narrow the cause from hardware in general to a specific driver or component. A full reference of codes is covered in the guide to reading and fixing BSOD stop codes.

Find the Failing Driver with Event Viewer and Minidumps

Identifying the failing driver from the crash log converts a generic blue screen into a single device to update or remove. Windows writes a minidump file to C:\Windows\Minidump after each stop error.

1. Open Windows Event Viewer, expand Windows Logs, and select System.
2. Filter the log for Error and Critical events near the crash time.
3. Download BlueScreenView and point it at the Minidump folder to list each crash.
4. Read the “Caused By Driver” column in BlueScreenView to find the responsible .sys file.
5. For deeper analysis, open the minidump in WinDbg and run the !analyze -v command.

Match the named .sys file to a device in Device Manager. A graphics driver such as nvlddmkm.sys points to the GPU, while a network driver points to the Wi-Fi or Ethernet adapter.

Update or Roll Back Device Drivers

Updating a faulty driver, or rolling back a driver that began crashing after an update, resolves the largest share of blue screen errors. Graphics, storage, network, and chipset drivers cause most driver-related crashes.

1. Open Device Manager and expand Display adapters, Network adapters, and Storage controllers.
2. Right-click the suspect device, select Update driver, then Search automatically for drivers.
3. Download the newest driver from the device or PC maker if Windows reports none.
4. If crashes started after a driver update, open the device Properties, select the Driver tab, and click Roll Back Driver.
5. Restart and test stability for several hours after each change.

When the failing driver is unknown, the Driver Verifier tool stresses every third-party driver and forces a crash that names the offender in the next minidump.

Test the RAM with Windows Memory Diagnostic

Testing memory confirms or rules out defective RAM, a frequent cause of MEMORY_MANAGEMENT and PAGE_FAULT_IN_NONPAGED_AREA stop codes. Windows includes a built-in memory tester.

1. Type Windows Memory Diagnostic in Windows Search and open it.
2. Select Restart now and check for problems.
3. Allow the test to run through every pass before Windows reloads.
4. Read the result in Event Viewer under the MemoryDiagnostics-Results source.
5. Run MemTest86 from a USB drive for several passes to confirm an intermittent fault.

Reseat each memory module and test one stick at a time to isolate a single failing module. Confirm the modules match the board specification described in the guide to how RAM works.

Run SFC and DISM to Repair System Files

Repairing corrupt system files removes a common cause of crashes that occur during boot or with no driver named. SFC and DISM are built-in command-line tools.

1. Right-click Start and open Terminal or Command Prompt as administrator.
2. Run DISM /Online /Cleanup-Image /RestoreHealth and wait for it to finish.
3. Run sfc /scannow to scan and repair protected system files.
4. Restart the computer after both tools report completion.
5. Re-run sfc /scannow once more to confirm no further corruption remains.

Uninstall Recent Updates and Scan for Malware

Removing a recent update and scanning for malware fixes crashes that began right after a patch or infection. An incompatible quality update is a common trigger.

1. Open Settings, then Windows Update, then Update history, and select Uninstall updates.
2. Remove the most recent quality update installed before the crashes began.
3. Open Windows Security, select Virus and threat protection, and run a Full scan.
4. Run a Microsoft Defender Offline scan to catch rootkits that load before Windows.

Check Overheating and Disk Health

Checking temperatures and disk health rules out the hardware faults that cause random, load-dependent crashes. Heat and bad sectors both corrupt data in use.

• Monitor temperatures. Use HWiNFO to confirm the CPU and GPU stay below their thermal limits under load.
• Clear dust and check fans. Remove dust from the cooler and confirm every fan spins to stop thermal-related crashes.
• Check the disk. Run chkdsk /f /r on the system drive to find and repair bad sectors.
• Read SMART data. Use CrystalDiskInfo to confirm the drive health status is Good and reallocated sectors are not rising.

Use Safe Mode and System Restore

Safe Mode loads Windows with minimal drivers so fixes can be applied when the system crashes during normal startup, and System Restore reverses recent changes. Both are reached from the Windows Recovery Environment.

1. Force three failed boots to trigger the Windows Recovery Environment, or hold Shift and click Restart from the sign-in screen.
2. Select Troubleshoot, then Advanced options, then Startup Settings, and enable Safe Mode.
3. In Safe Mode, uninstall the suspect driver or update that caused the crash.
4. To undo recent changes, open Advanced options and select System Restore.
5. Choose a restore point dated before the crashes began and complete the restore.

Disconnect New Hardware and External Devices

Removing recently added hardware and unneeded peripherals isolates a device or its driver as the cause of crashes that began after an installation. New or faulty hardware introduces driver conflicts and electrical faults.

1. Shut down the computer and unplug all non-essential USB devices, leaving only the keyboard and mouse.
2. Remove any expansion card, drive, or RAM module added shortly before the crashes started.
3. Reseat the graphics card and memory modules in their slots to clear contact faults.
4. Restart and test stability with the minimal hardware set.
5. Reconnect one device at a time, testing after each, to find the component that returns the crash.

A failing power supply also causes random stop errors under load. Confirm the supply matches the system draw before replacing other components.

Disable Automatic Restart to Read the Stop Code

Turning off automatic restart keeps the blue screen on display long enough to record the stop code when the system reboots too fast to read it. The setting sits in System Properties.

1. Open System Properties, then Advanced system settings.
2. Under Startup and Recovery, click Settings.
3. Clear the “Automatically restart” checkbox.
4. Confirm a small memory dump is selected so minidumps are written.
5. Save changes so the next crash holds the stop code on screen.

With automatic restart disabled, the stop-code name and any failing .sys file stay visible until the screen is photographed or recorded.

Common BSOD Stop Codes and Their Meanings

Key Takeaways

• Read the stop code first. The stop-code name and any .sys file point directly to the cause.
• Suspect drivers before hardware. Updating or rolling back a driver fixes most blue screen errors.
• Test RAM and system files next. Windows Memory Diagnostic, SFC, and DISM cover the most common remaining causes.
• Use minidumps to find the offender. BlueScreenView and WinDbg name the failing driver from the crash file.
• Fall back to Safe Mode and System Restore. Both apply fixes when the system crashes during normal startup.

Last Thoughts on the Blue Screen of Death

A Blue Screen of Death is resolved by reading the stop code, identifying the failing component, and applying the matching fix in order. Driver updates, memory tests, and system-file repairs with SFC and DISM resolve most crashes without reinstalling Windows.

When a specific code appears, follow the targeted guides to fix DRIVER_POWER_STATE_FAILURE, fix KERNEL_SECURITY_CHECK_FAILURE, fix SYSTEM_SERVICE_EXCEPTION, and fix CRITICAL_PROCESS_DIED. When crashes follow restarts, the steps to stop a computer that keeps restarting apply, and a full index of related faults sits in the hub of common PC problems.