Windows 7 BSOD (Blue Screen of Death): Complete Fix & Repair Guide

Understanding the Windows 7 BSOD

A Blue Screen of Death (BSOD) in Windows 7 indicates a fatal system error from which the operating system cannot safely recover. The screen displays a stop code — also called a bug check code — in the format 0x000000XX along with a descriptive name such as IRQL_NOT_LESS_OR_EQUAL, PAGE_FAULT_IN_NONPAGED_AREA, KERNEL_DATA_INPAGE_ERROR, or DRIVER_IRQL_NOT_LESS_OR_EQUAL.

The full crash information, including the faulting module, is written to a minidump file at *C:\Windows\Minidump* and optionally to a full memory dump at C:\Windows\MEMORY.DMP. Analyzing these files is the definitive way to trace the root cause.

Step 1: Document the Stop Code

When the BSOD appears, write down:

• The stop code (e.g., 0x0000007E)
• The descriptive name (e.g., SYSTEM_THREAD_EXCEPTION_NOT_HANDLED)
• Any .sys file named on screen (e.g., ntfs.sys, nvlddmkm.sys, atikmpag.sys)

If the system reboots too quickly, disable automatic restart:

1. Right-click Computer > Properties
2. Click Advanced system settings
3. Under Startup and Recovery, click Settings
4. Uncheck Automatically restart under System failure
5. Click OK

Step 2: Boot into Safe Mode

If Windows 7 won't boot normally, press F8 repeatedly during startup to access the Advanced Boot Options menu. Select Safe Mode with Networking to retain internet access for downloading fixes.

In Safe Mode, only essential Microsoft drivers load, which isolates third-party driver conflicts.

Step 3: Run System File Checker (SFC)

Corrupted Windows system files frequently cause BSODs. Open an elevated Command Prompt (Run as Administrator) and execute:

sfc /scannow

This scans all protected system files and replaces corrupted versions with a cached copy. Allow it to complete fully — do not interrupt. If SFC reports it cannot fix some files, run DISM next:

DISM /Online /Cleanup-Image /RestoreHealth

Note: DISM requires internet connectivity or a mounted Windows 7 ISO as a source.

Step 4: Check the Hard Drive with CHKDSK

Disk errors and bad sectors are a common BSOD cause, particularly for stop codes like 0x00000024 (NTFS_FILE_SYSTEM) and 0x0000007A (KERNEL_DATA_INPAGE_ERROR). Run:

chkdsk C: /f /r

Because the C: drive is in use, Windows will schedule the scan for the next reboot. Type Y when prompted and restart. CHKDSK will run before Windows loads and fix found errors.

Step 5: Analyze Minidump Files

Download and install Windows Debugging Tools (WinDbg) from Microsoft. Open WinDbg and:

1. Go to File > Symbol File Path and enter:

   srv*C:\Symbols*https://msdl.microsoft.com/download/symbols
   

2. Go to File > Open Crash Dump and browse to a file in *C:\Windows\Minidump*
3. In the command window, type:

   !analyze -v
   

WinDbg will output the exact faulting driver, the call stack, and a probable cause. Look for lines like:

Probable cause: DRIVER_FAULT
Faulting module: nvlddmkm.sys (NVIDIA display driver)

This tells you exactly which driver or component to target.

Step 6: Update or Roll Back Drivers

If a specific driver is implicated:

To roll back a driver:

1. Open Device Manager (devmgmt.msc)
2. Right-click the device > Properties > Driver tab
3. Click Roll Back Driver

To update a driver:

1. Visit the hardware manufacturer's website (NVIDIA, AMD, Intel, Realtek, etc.)
2. Download the latest Windows 7-compatible driver
3. Install and reboot

Common problematic drivers in Windows 7 BSODs:

• nvlddmkm.sys — NVIDIA GPU driver
• atikmpag.sys / atikmdag.sys — AMD/ATI GPU driver
• tcpip.sys — TCP/IP network stack
• ntfs.sys — NTFS file system driver
• classpnp.sys — Storage class driver

Step 7: Run Windows Memory Diagnostic

Faulty RAM causes unpredictable BSODs with varying stop codes. Run the built-in tool:

1. Click Start > search Windows Memory Diagnostic
2. Choose Restart now and check for problems
3. After the test completes, Windows boots and displays results

Alternatively, download MemTest86 and run it overnight from a USB drive for more thorough testing. Any errors indicate RAM must be replaced.

Step 8: Check Temperatures and Hardware

Overheating causes thermal-protection BSODs. Download HWMonitor or SpeedFan to check:

• CPU temperature (normal idle: below 50°C; under load: below 85°C)
• GPU temperature (normal idle: below 60°C; under load: below 90°C)
• Hard drive temperature (should stay below 55°C)

If temperatures are high: clean dust from vents and fans, reapply thermal paste on the CPU, and ensure case airflow is adequate.

Step 9: Use System Restore

If the BSOD started recently after a software or driver change, System Restore can revert to a known good state:

1. Boot into Safe Mode
2. Click Start > All Programs > Accessories > System Tools > System Restore
3. Select a restore point dated before the BSOD started
4. Click Next and Finish

System Restore does not affect personal files but will remove programs and drivers installed after the chosen restore point.

Step 10: Run Startup Repair (if Windows Won't Boot)

1. Insert your Windows 7 installation DVD or bootable USB
2. Boot from the media (press F12 or DEL for boot menu)
3. Select Repair your computer
4. Choose Startup Repair
5. Follow the prompts — this automatically fixes common boot-time issues including corrupted BCD (Boot Configuration Data)

If Startup Repair fails, use the Recovery Console and run:

bootrec /fixmbr
bootrec /fixboot
bootrec /rebuildbcd

When to Reinstall Windows 7

If all the above steps fail and hardware tests pass (RAM, hard drive, thermals are all confirmed good), a clean reinstall is the final option. Back up all personal data first using a live USB Linux environment if Windows won't boot. Use your Windows 7 product key to reinstall from official media.