Windows BSOD KERNEL_DATA_INPAGE_ERROR (0x0000007A) — Disk Read Failure
Criticalbsod
Overview
KERNEL_DATA_INPAGE_ERROR occurs when Windows cannot read kernel data from the paging file due to disk errors, bad sectors, or failing storage hardware.
Key Details
- Stop code 0x0000007A — kernel requested data from the page file but the read failed
- Parameter 2 contains the I/O status code identifying the type of failure
- Common I/O status: 0xC000009C = bad disk block, 0xC000009D = device failure, 0xC000016A = disk hardware error
- Strongly indicates physical disk problems — bad sectors, failing read heads, or cable issues
- Can also be caused by faulty RAM where data was paged out incorrectly
Common Causes
- Hard drive or SSD developing bad sectors
- Failing SATA cable or loose connection
- Corrupted paging file (pagefile.sys) on a damaged disk region
- RAM failure causing corrupted data to be written to the page file
- Disk controller or driver malfunction
Steps
- 1Run chkdsk C: /f /r from elevated Command Prompt to scan and repair disk errors
- 2Check disk health in CrystalDiskInfo — replace drive if SMART shows warnings
- 3Run Windows Memory Diagnostic to rule out RAM issues
- 4Disable, delete, and recreate the page file: System > Advanced > Performance Settings > Virtual Memory
- 5Replace SATA cable and try a different SATA port on the motherboard
Tags
windowsbsodkernel-data-inpagedisk-errorbad-sectors
More in Bsod
windows-0000000A-irql-not-less-or-equalWindows Error 0x0000000A — IRQL NOT LESS OR EQUAL
Criticalwindows-00000050-page-fault-in-nonpaged-areaWindows Error 0x00000050 — PAGE FAULT IN NONPAGED AREA
Criticalwindows-0000007E-system-thread-exception-not-handledWindows Error 0x0000007E — SYSTEM THREAD EXCEPTION NOT HANDLED
Criticalwindows-0000007A-kernel-data-inpage-errorWindows Error 0x0000007A — KERNEL DATA INPAGE ERROR
Criticalwindows-000000EF-critical-process-diedWindows Error 0x000000EF — CRITICAL PROCESS DIED
Criticalwindows-00000133-dpc-watchdog-violationWindows Error 0x00000133 — DPC WATCHDOG VIOLATION
CriticalFrequently Asked Questions
Very likely. This BSOD specifically indicates disk read failures. Check SMART status immediately and back up your data.