KERNEL_DATA_INPAGE_ERROR, the blue screen, explained and fixed
This stop code (0x0000007A) means a page of kernel data that Windows needed could not be read from the paging file on disk into memory. Unlike most blue screens, software is rarely the story here: the read itself failed. A failing drive is the prime suspect, followed by a loose or damaged storage connection, then faulty RAM. Treat this one as a hardware warning until proven otherwise.
The fix, in order
- Back up your important files before troubleshooting. If the drive is failing, every hour of testing is borrowed time. Copy what matters to another drive or the cloud first, then diagnose.
- Read the second parameter if you can see the crash details. In the dump details, common status values tell the story: 0xC000009C means bad blocks on the disk, 0xC000016A is also disk-related, and 0xC000000E means the device disappeared mid-read, pointing at the cable, port, or drive electronics.
- Run a disk check. From an admin Command Prompt:
chkdsk /f /r and let it run at the next restart. Also open the drive maker’s health tool and read the SMART status; reallocated or pending sectors confirm a failing drive.
- Reseat the storage connection. On a desktop, power off and reseat the SATA data and power cables or the NVMe drive, and try a different cable and port. On a laptop, reseating is harder, skip to the health checks and consider a repair shop if the drive is not user-accessible.
- Test the RAM. Run Windows Memory Diagnostic. Memory that fails cannot reliably hold pages read from disk and can imitate a disk fault, so it stays on the list even though the drive leads it.
- Confirm the paging file is system-managed. Settings → System → About → Advanced system settings → Performance Settings → Advanced → Virtual memory: “Automatically manage paging file size” should be on. A disabled or undersized page file on a nearly full drive can starve this read.
A drive that produces this code plus clicking, grinding, or disappearing from the BIOS is done. Stop stress-testing it, get the data off, and replace it. Tools like chkdsk /r are diagnostics, not repairs, for a mechanically failing disk.
If it still happens
If the drive’s SMART status is clean, cables are reseated, and memory passes, run the file repairs (DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow) and check for storage controller driver and BIOS updates. If the error follows the drive to another machine, the question is answered: replace the drive.
Common questions
Is KERNEL_DATA_INPAGE_ERROR always a dead drive? Not always, but the drive is guilty until proven innocent. The remaining causes, in order, are a loose or failing cable or port, bad RAM, and a page file problem on a full disk. The SMART health report and a backup-first approach keep you safe either way.
chkdsk says the drive is fine. What now? chkdsk checks the file system more than the hardware. Read the raw SMART data with the manufacturer’s tool, reseat or swap the cable, and test the RAM. Intermittent cable and controller faults pass chkdsk cleanly while still failing reads.
Related errors