KERNEL_DATA_INPAGE_ERROR
Windows
Critical severity
Kernel Data Inpage Error — Blue Screen Fix
Windows could not read a page of kernel data from the paging file — usually failing storage, a loose SATA/NVMe connection or bad RAM.
Last reviewed 2026-08-29 by the Tech Issue Guide team.
Symptoms
- Blue screen reading KERNEL_DATA_INPAGE_ERROR, sometimes with a stop code like 0x0000007A.
- Clicking or buzzing noises from a mechanical drive before the crash.
- Long freezes, then a crash, when opening large files.
What causes KERNEL_DATA_INPAGE_ERROR
- A failing hard drive or SSD, or bad sectors in the paging file area.
- A loose or faulty SATA/NVMe/power cable or drive seating.
- Defective RAM corrupting data on its way to or from disk.
- Aggressive antivirus or disk-filter drivers interfering with paging I/O.
How to fix it — 3 steps
- Run chkdsk with full repair on the system drive (command below) and reseat the drive’s data and power connections.
- Test memory with Windows Memory Diagnostic (mdsched) or, better, MemTest86 for a full pass overnight.
- Check the drive’s SMART health with the vendor tool or CrystalDiskInfo; if reallocated or pending sectors are rising, back up immediately and replace the disk.
Terminal / CLI command
chkdsk /f /r C:Elevated Command Prompt. It will schedule for the next restart — type Y and reboot. The /r pass can take hours on a large drive.
How to confirm the fix: chkdsk completes with no bad sectors, memory tests pass, and the system runs without recurrence for several days.
Prevent it from coming back
Back up regularly, replace drives proactively once SMART warnings appear, and keep the PC on a surge-protected supply.
Frequently asked questions
Is my data safe?
Treat this error as a warning that storage may be failing. Back up important files first, then troubleshoot.
chkdsk is stuck at 10% or 27% — is it frozen?
The /r pass slows dramatically over weak sectors. Leave it running for several hours before assuming it is stuck.