Blue Screen of Death in Windows 7: Complete Fix Guide (BSOD Stop Codes 0x0000000A, 0x000000F4, 0x0000007B & More)
Fix Windows 7 blue screen errors including 0x0000000A, 0x000000F4, atikmpag.sys, ntoskrnl.exe & more. Step-by-step BSOD troubleshooting guide with commands.
- Most Windows 7 BSODs are caused by faulty drivers (GPU, USB, storage), corrupt system files, bad RAM, or failing hardware — the stop code in the blue screen tells you exactly which component to investigate first.
- Common stop codes include: IRQL_NOT_LESS_OR_EQUAL (0x0000000A), PROCESS1_INITIALIZATION_FAILED (0x000000F4), INACCESSIBLE_BOOT_DEVICE (0x0000007B), BAD_POOL_HEADER, PFN_LIST_CORRUPT, APC_INDEX_MISMATCH, SYSTEM_SERVICE_EXCEPTION, and CRITICAL_PROCESS_DIED — each pointing to a specific subsystem failure.
- Quick fix path: Boot into Safe Mode → run 'sfc /scannow' and 'chkdsk /f /r' → update or roll back offending drivers → run Windows Memory Diagnostic → if nothing works, use Startup Repair from the Windows 7 installation DVD.
| Method | When to Use | Time | Risk |
|---|---|---|---|
| sfc /scannow (System File Checker) | Corrupt or missing Windows system files causing BSOD | 10-30 min | Low |
| chkdsk /f /r | BSOD on startup, NTFS.sys errors, disk corruption | 30-120 min | Low |
| Driver rollback or uninstall (Device Manager) | BSOD after driver update (GPU, USB, NIC drivers like atikmpag.sys, nvlddmkm.sys, ndis.sys) | 5-15 min | Low |
| Windows Memory Diagnostic / MemTest86 | PFN_LIST_CORRUPT, BAD_POOL_HEADER, random BSODs | 30-480 min | None |
| Startup Repair (from DVD/USB) | Blue screen on startup, boot loop, cannot enter Safe Mode | 15-45 min | Low |
| System Restore | BSOD started after a specific software or driver install | 15-30 min | Medium |
| Manual driver reinstall (ATI/AMD, NVIDIA, Intel) | atikmdag.sys, atikmpag.sys, nvlddmkm.sys, igdkmd32.sys BSODs | 10-30 min | Low |
| BIOS/UEFI settings reset or firmware update | iaStor.sys, iusb3xhc.sys, AHCI-related boot BSODs | 10-20 min | Medium |
| Clean Windows 7 reinstall | All other fixes failed, multiple corrupt components | 60-180 min | High (data loss) |
Understanding Windows 7 Blue Screen Errors
A Blue Screen of Death (BSOD) in Windows 7 occurs when the kernel encounters a fatal error it cannot recover from. The screen displays a stop code (e.g., *** STOP: 0x0000000A) and often names the offending driver or file (e.g., atikmpag.sys, ntoskrnl.exe). Understanding the stop code is your first diagnostic step.
Most Common Windows 7 Stop Codes and Their Causes
| Stop Code | Name | Typical Cause |
|---|---|---|
| 0x0000000A | IRQL_NOT_LESS_OR_EQUAL | Faulty driver accessing memory at wrong IRQL level |
| 0x000000F4 | CRITICAL_OBJECT_TERMINATION | Critical process (CSRSS, SMSS) terminated unexpectedly |
| 0x0000007B | INACCESSIBLE_BOOT_DEVICE | SATA mode change, corrupt boot sector, missing storage driver |
| 0x0000001E | KMODE_EXCEPTION_NOT_HANDLED | Driver or kernel code exception |
| 0x00000050 | PAGE_FAULT_IN_NONPAGED_AREA | Bad RAM or driver writing to wrong memory address |
| 0x0000003B | SYSTEM_SERVICE_EXCEPTION | System call failed, often GPU or network drivers |
| 0x00000019 | BAD_POOL_HEADER | Heap corruption, bad driver, or RAM fault |
| 0x000000FC | ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY | Driver bug or rootkit activity |
| 0x4E | PFN_LIST_CORRUPT | Corrupt page frame database, usually RAM or driver |
Step 1: Record the Exact Error Information
When the BSOD appears, note:
- The full STOP code (e.g., STOP: 0x000000F4)
- The symbolic name (e.g., CRITICAL_PROCESS_DIED)
- Any .sys or .dll file named on screen (e.g., atikmpag.sys, dxgkrnl.sys)
- The error parameters in parentheses
If the system reboots too fast to read it:
- Right-click My Computer → Properties → Advanced System Settings
- Under Startup and Recovery, click Settings
- Uncheck Automatically restart under System Failure
- Set Write debugging information to Small memory dump (256 KB)
Dump files are saved to C:\Windows\Minidump\. Analyze them with WinDbg.
Step 2: Boot Into Safe Mode
Press F8 during startup before the Windows logo appears. Select Safe Mode with Networking to access the internet for driver downloads.
If F8 doesn't work or the system blue screens immediately:
- Boot from your Windows 7 DVD
- Choose Repair your computer → Startup Repair
- Or access the command prompt from recovery options
Step 3: Run System File Checker and CHKDSK
Open an elevated command prompt (Run as Administrator):
sfc /scannow
This scans and repairs corrupt Windows system files. After it finishes, reboot and test. If errors are found but cannot be repaired, note the CBS.log file at C:\Windows\Logs\CBS\CBS.log.
For disk-related BSODs (NTFS.sys, classpnp.sys, 0x0000007B, 0x000000F4):
chkdsk C: /f /r
Type Y when asked to schedule on next reboot, then restart. This can take 1-2 hours on large drives.
Step 4: Address GPU Driver BSODs (atikmpag.sys, atikmdag.sys, nvlddmkm.sys, dxgkrnl.sys, dxgmms1.sys)
These are among the most common BSOD causes in Windows 7. The blue screen will display:
STOP: 0x00000116 VIDEO_TDR_FAILURE atikmpag.sysSTOP: 0x0000007E dxgkrnl.sysnvlddmkm.sys blue screen
For AMD/ATI drivers (atikmpag.sys, atikmdag.sys, ati2dvag.dll):
- Boot into Safe Mode
- Use DDU (Display Driver Uninstaller) to fully remove the driver
- Download the latest AMD driver for Windows 7 from amd.com
- Install fresh
Alternatively, roll back the driver:
- Device Manager → Display Adapters → Right-click GPU → Properties → Driver tab → Roll Back Driver
For NVIDIA (nvlddmkm.sys):
- Same process using DDU, then download from nvidia.com
Registry fix for atikmpag.sys (Windows 7 64-bit):
- Open regedit → Navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers - Create DWORD (32-bit) value named
TdrDelayand set it to8(decimal) - This increases the GPU timeout detection delay
Step 5: Fix USB and Storage Controller BSODs (iusb3xhc.sys, iaStor.sys, ataport.sys)
iusb3xhc.sys (USB 3.0 controller BSOD):
- Go to Device Manager → Universal Serial Bus controllers
- Right-click the Intel USB 3.0 controller → Update Driver Software
- Download Intel USB 3.0 eXtensible Host Controller Driver from Intel's website
- Alternatively, in BIOS/UEFI, disable xHCI mode and switch to EHCI
iaStor.sys (Intel AHCI driver BSOD):
- Often caused by BIOS SATA mode changing from IDE to AHCI (or vice versa) after Windows was installed
- Boot into Safe Mode and change the SATA mode back in BIOS
- Or pre-enable AHCI in registry before switching BIOS mode:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\msahci→ set Start to0HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iaStorV→ set Start to0
0x0000007B (INACCESSIBLE_BOOT_DEVICE) fix:
- Reset BIOS SATA settings to match original Windows install configuration
- Run Startup Repair from Windows 7 DVD
- Use bootrec commands:
bootrec /fixmbr,bootrec /fixboot,bootrec /rebuildbcd
Step 6: Fix Network Driver BSODs (ndis.sys, netio.sys, fltmgr.sys)
ndis.sys BSOD is typically caused by a corrupt or outdated NIC driver:
- Boot into Safe Mode with Networking
- Device Manager → Network Adapters → Roll back or update the driver
- If caused by a VPN or firewall software, uninstall it
fltmgr.sys (Filter Manager) BSODs are often caused by third-party security software or filesystem filter drivers:
- Uninstall antivirus software in Safe Mode
- Run
sfc /scannow - Check for recently installed file system filter drivers
Step 7: Diagnose RAM for BAD_POOL_HEADER and PFN_LIST_CORRUPT
- Press Windows Key + R → type
mdsched.exe→ Enter - Choose Restart now and check for problems
- Results appear after reboot in Event Viewer → Windows Logs → System
For thorough RAM testing, use MemTest86 (bootable USB) and run at least 2 full passes.
If RAM errors are found:
- Try each RAM stick individually
- Clean RAM contacts with an eraser
- Replace faulty RAM module
Step 8: Analyze Crash Dumps with WinDbg
Install Windows Debugging Tools (part of Windows SDK). Open WinDbg and run:
!analyze -v
This provides a detailed analysis of the crash dump, identifying the exact driver or function that caused the fault. Look for FAILURE_BUCKET_ID and IMAGE_NAME in the output.
Step 9: Use System Restore or Startup Repair
If BSODs started after a specific change:
- Boot from Windows 7 DVD → Repair your computer → System Restore
- Choose a restore point before the issue began
For persistent boot BSODs:
- Boot from DVD → Repair your computer → Startup Repair
- Let it run automatically; may require 2-3 attempts
Step 10: Nuclear Option — Repair Install or Clean Install
If nothing else works, perform a Windows 7 repair install (preserves files) or a clean install. Back up all data first using a Linux live USB if Windows won't boot normally.
Frequently Asked Questions
:: ============================================================
:: Windows 7 BSOD Diagnostic and Fix Commands
:: Run as Administrator (elevated command prompt)
:: ============================================================
:: --- 1. Disable automatic restart on BSOD so you can read the stop code ---
wmic recoveros set AutoReboot=False
:: --- 2. Scan and repair corrupt system files ---
sfc /scannow
:: --- 3. Check and repair disk errors (schedules on next reboot for C:) ---
chkdsk C: /f /r
:: --- 4. Run Startup Repair components manually (from Recovery CMD prompt) ---
bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd
:: --- 5. Run sfc offline (from Windows 7 DVD recovery command prompt) ---
:: Replace C: with your actual Windows drive letter if different
sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows
:: --- 6. Run DISM to repair Windows image (Windows 7 with KB2966583) ---
Dism /Online /Cleanup-Image /ScanHealth
Dism /Online /Cleanup-Image /RestoreHealth
:: --- 7. Enable AHCI in registry before changing BIOS SATA mode ---
reg add "HKLM\SYSTEM\CurrentControlSet\services\msahci" /v Start /t REG_DWORD /d 0 /f
reg add "HKLM\SYSTEM\CurrentControlSet\services\iaStorV" /v Start /t REG_DWORD /d 0 /f
:: --- 8. Add GPU TDR delay fix for atikmpag.sys / nvlddmkm.sys BSODs ---
reg add "HKLM\SYSTEM\CurrentControlSet\Control\GraphicsDrivers" /v TdrDelay /t REG_DWORD /d 8 /f
reg add "HKLM\SYSTEM\CurrentControlSet\Control\GraphicsDrivers" /v TdrDdiDelay /t REG_DWORD /d 8 /f
:: --- 9. Find and view recent minidump files (for WinDbg analysis) ---
dir C:\Windows\Minidump\ /od
:: --- 10. Open Windows Memory Diagnostic ---
mdsched.exe
:: --- 11. Open Driver Verifier (identifies faulty drivers causing BSOD) ---
verifier.exe
:: --- 12. View System event log for critical errors since last 7 days ---
wevtutil qe System /q:"*[System[TimeCreated[timediff(@SystemTime) <= 604800000] and (Level=1 or Level=2)]]" /f:text /rd:true /c:30
:: --- 13. Export crash dump details with PowerShell ---
powershell -Command "Get-EventLog -LogName Application -EntryType Error -Newest 20 | Format-List TimeGenerated, Source, Message"
:: --- 14. Disable Driver Verifier after testing (prevents boot loop) ---
verifier /reset
:: --- 15. Roll back a specific driver via command line (example: NIC driver) ---
:: First find the driver name using: driverquery /fo list | find "ndis"
:: Then use pnputil or devcon to manage drivers
pnputil /enum-drivers
:: --- 16. List all non-Microsoft drivers (third-party, often BSOD culprits) ---
driverquery /fo CSV /si | find /v "Microsoft"Error Medic Editorial
The Error Medic Editorial team consists of senior DevOps engineers, Windows systems administrators, and SRE professionals with a combined 40+ years of experience diagnosing kernel-level failures, BSOD stop codes, and system crashes across Windows desktop and server environments. Our guides are tested against real hardware scenarios and updated regularly to reflect the latest driver releases and Microsoft patches.
Sources
- https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-code-reference2
- https://support.microsoft.com/en-us/windows/resolving-stop-blue-screen-errors-in-windows-a9928e6c-f0d5-4f7b-b586-4d10ad9f4a36
- https://learn.microsoft.com/en-us/windows-hardware/drivers/devtest/driver-verifier
- https://superuser.com/questions/411830/windows-7-bsod-atikmpag-sys
- https://answers.microsoft.com/en-us/windows/forum/all/blue-screen-error-0x000000f4/2c1cbc72-4cb0-47bf-a839-6ddc9b1b8d2a
- https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/chkdsk
- https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/sfc