Blue Screen of Death (BSOD) in Windows 7: Complete Fix Guide for Stop Errors, Driver Crashes & Memory Dumps

Understanding Windows 7 Blue Screen Errors

A Blue Screen of Death (BSOD) in Windows 7 occurs when the kernel encounters a fatal error from which it cannot recover. The screen displays a stop code (e.g., STOP: 0x0000000A), the name of a faulting driver or module (e.g., atikmpag.sys), and a memory dump is written to C:\Windows\Minidump. Understanding which stop code and module appear is the foundation of any effective fix.

Common Stop Codes and Their Root Causes

0x0000000A – IRQL_NOT_LESS_OR_EQUAL A kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. Common culprits: network drivers (ndis.sys, netio.sys), USB drivers (iusb3xhc.sys).

0x00000F4 / STOP 0x000000F4 – CRITICAL_OBJECT_TERMINATION A critical system process (such as csrss.exe, winlogon.exe, or a storage process) terminated unexpectedly. Commonly caused by a failing hard drive, corrupt system partition, or iaStorA/iastor.sys driver issues.

0x0000007B – INACCESSIBLE_BOOT_DEVICE Windows cannot access the system partition at boot. Triggered by SATA controller mode changes (IDE vs AHCI), corrupt NTFS volume (766f6c756d652e63 3f1 relates to a volume bitmap corruption), or missing storage drivers.

BAD_POOL_HEADER / BAD_POOL_CALLER Memory pool corruption — often caused by faulty RAM, a buggy driver writing outside its allocated pool, or malware.

PFN_LIST_CORRUPT Page Frame Number list corruption — almost always faulty RAM or a driver corrupting memory structures.

APC_INDEX_MISMATCH A thread's APC disable count is wrong, usually caused by a file system filter driver (fltmgr.sys) or antivirus kernel component.

GPU-Related BSODs (atikmpag.sys, atikmdag.sys, ati2dvag.dll, nvlddmkm.sys, dxgkrnl.sys, dxgmms1.sys, igdkmd32.sys) The GPU driver or DirectX kernel subsystem crashed, either due to a driver bug, overheating GPU, corrupt driver installation, or hardware failure.

BUGCODE_USB_DRIVER A USB driver (often iusb3xhc.sys for USB 3.0) caused a violation. Update the Intel USB 3.0 xHCI driver or roll back to an older version.

SYSTEM_SERVICE_EXCEPTION A system service violated memory access rules. Can be caused by ntoskrnl.exe, ntkrnlpa.exe (PAE kernel), ntkrnlmp.exe (multiprocessor kernel), or third-party drivers.

CRITICAL_PROCESS_DIED A critical system process has died. While more common in Windows 10, this can appear in Windows 7 when core OS processes fail.

Step 1: Capture the Crash Information

Before fixing anything, record the exact stop code and module name from the blue screen. If the system reboots too fast:

1. Right-click Computer > Properties > Advanced system settings.
2. Under Startup and Recovery, click Settings.
3. Uncheck Automatically restart so the BSOD stays on screen.
4. Change Write debugging information to Small memory dump (256 KB).
5. Note the dump location: %SystemRoot%\Minidump.

Step 2: Boot Into Safe Mode

If you cannot boot normally (blue screen on startup):

1. Press F8 repeatedly during POST until the Advanced Boot Options menu appears.
2. Select Safe Mode with Networking (needed for driver downloads).
3. If F8 does not work, boot from the Windows 7 installation DVD and select Repair your computer > Startup Repair.

For 0x0000007B (INACCESSIBLE_BOOT_DEVICE) specifically: Enter BIOS/UEFI and check if the SATA mode changed from AHCI to IDE (or vice versa). Changing it back often resolves this immediately.

Step 3: Run System File Checker and CHKDSK

Open an elevated Command Prompt (Run as Administrator) and run:

sfc /scannow

This repairs corrupt Windows system files including ntoskrnl.exe, ntkrnlpa.exe, classpnp.sys, fltmgr.sys, and ntfs.sys. If SFC reports it cannot fix files, run DISM (if available on Windows 7 with SP1):

Dism /Online /Cleanup-Image /RestoreHealth

For disk errors causing 0x00000F4, NTFS.sys BSODs, or stop 0x000000F4:

chkdsk C: /f /r

Type Y to schedule on next reboot, then restart. This scan checks for bad sectors and file system corruption. Allow 30-120 minutes.

Step 4: Fix GPU Driver BSODs (atikmpag.sys / atikmdag.sys / nvlddmkm.sys)

This is the most common category of Windows 7 BSODs, especially on AMD and NVIDIA systems.

For AMD (atikmpag.sys, atikmdag.sys, ati2dvag.dll, blue screen atikmpag sys windows 7 64 bit fix):

1. Boot into Safe Mode.
2. Download Display Driver Uninstaller (DDU) from Wagnardsoft.
3. Run DDU in Safe Mode, select Clean and restart.
4. Download the latest stable Catalyst driver (or the version prior to when BSODs started) from AMD's support site.
5. Install with a clean installation option.

Alternatively, manually replace atikmpag.sys:

• Rename C:\Windows\System32\drivers\atikmpag.sys to atikmpag.sys.bak.
• Copy a known-good version from your driver installation folder.

For NVIDIA (nvlddmkm.sys, dxgkrnl.sys, dxgmms1.sys):

1. Boot into Safe Mode.
2. Run DDU to fully remove NVIDIA drivers.
3. Install a clean driver from NVIDIA's official site.
4. If the error persists, check GPU temperature with GPU-Z or HWMonitor — throttle or replace if overheating.

For Intel integrated graphics (igdkmd32.sys):

• Download the latest Intel HD Graphics driver from Intel's download center.
• Ensure Windows Update has not installed a generic driver over the OEM driver.

Step 5: Fix Memory-Related BSODs (BAD_POOL_HEADER, PFN_LIST_CORRUPT, 0x0000000A)

1. Run Windows Memory Diagnostic: Start > Search > "Windows Memory Diagnostic" > Restart now and check for problems.
2. For thorough testing, boot from MemTest86 USB/CD and run at least 2 full passes (8+ hours recommended).
3. If errors are found, reseat RAM sticks, try each stick individually, and replace faulty modules.
4. Check for overclocking: reset RAM to XMP profile or stock speeds in BIOS.

Step 6: Analyze Minidump Files with WinDbg

If the BSOD is intermittent and you cannot identify the cause:

1. Install Windows SDK and open WinDbg.
2. Set symbol path: .sympath srv*C:\symbols*https://msdl.microsoft.com/download/symbols
3. Open the minidump: File > Open Crash Dump > browse to C:\Windows\Minidump\*.dmp.
4. Run: !analyze -v
5. Look for the Probably caused by line — this names the faulting module (e.g., atikmpag.sys, iastor.sys, nvlddmkm.sys).

Step 7: Fix Specific Stop Codes

BUGCODE_USB_DRIVER / iusb3xhc.sys: Update Intel USB 3.0 eXtensible Host Controller driver from Intel's download center, or disable USB 3.0 in BIOS temporarily.

ndis.sys / netio.sys (network BSODs): Update your NIC driver. If using a VPN or packet filter software, uninstall it temporarily to isolate.

iastor.sys / iaStor.sys: Update Intel Rapid Storage Technology (RST) driver from Intel. If on a laptop, check the OEM support page for a compatible version.

classpnp.sys (blue screen on startup): This often means a failing storage device. Run chkdsk, check SMART data with CrystalDiskInfo, and check BIOS to ensure the drive is recognized.

fltmgr.sys / APC_INDEX_MISMATCH: Disable or uninstall third-party antivirus or file system filter drivers. Boot into Safe Mode and use Autoruns to identify kernel-mode filter drivers.

crash dump windows 7 blue screen fix (memory dump): Ensure the page file is on the system drive. Go to System Properties > Advanced > Performance Settings > Advanced > Virtual Memory. Set it to system managed.

Step 8: Last Resort — Startup Repair and Repair Install

If BSODs persist after all the above:

1. Boot from Windows 7 installation media.
2. Select Repair your computer > Startup Repair — this automatically fixes boot sector, BCD, and some system file issues.
3. If that fails, use Command Prompt from recovery and run:

   bootrec /fixmbr
   bootrec /fixboot
   bootrec /rebuildbcd
   

4. As a final step before reinstalling, perform an in-place upgrade (repair install) by booting from the Windows 7 DVD, clicking Install Now, and selecting Upgrade — this replaces system files without deleting personal data.

Step 9: Hardware Checks

• Check GPU temperature: Use HWMonitor during load. AMD cards above 95°C and NVIDIA above 90°C are dangerously hot.
• Check hard drive SMART: Use CrystalDiskInfo. Any "Caution" or "Bad" status on reallocated sectors or pending sectors indicates a failing drive.
• Reseat hardware: Power off, remove and firmly reseat RAM, GPU, and storage cables.
• Test with minimal hardware: Remove non-essential PCIe cards, extra RAM sticks, and external USB devices to isolate the failing component.