KERNEL_DATA_INPAGE_ERROR (0x7A): Causes and Fixes

KERNEL_DATA_INPAGE_ERROR (0x0000007A)

Stop code 0x0000007A, also written 0x7A. Here is what it means, what usually causes it, and the safest order to work through fixes on Windows 11 and Windows 10.

In short

Windows could not read a page of kernel data back from disk into memory.

What KERNEL_DATA_INPAGE_ERROR means

Windows sometimes moves memory pages to the paging file on disk and reads them back later. This stop means a requested page could not be read back. A failing drive, a bad cable or controller connection and memory errors are the typical explanations.

Common causes

A failing drive or bad sectors in the paging file area
A loose or damaged data cable, or an unreliable controller connection
Faulty RAM
Malware or file system corruption, less often

How to fix KERNEL_DATA_INPAGE_ERROR

Work through these in order and test after each one. Stopping as soon as the crashes stop tells you which change mattered.

Check the health of the drive. Read the SMART data with the drive maker's tool or CrystalDiskInfo and look for reallocated or pending sectors, media errors and a low remaining-life figure. Back up important files first if the drive reports any warning.
Check the cable and port. Power off and unplug the PC, then reseat the SATA or M.2 connection. Try another SATA cable or port, because a bad cable is a cheap thing to rule out.
Scan the volume. Open Terminal (Admin) and run chkdsk C: /scan. Back up first if SMART data shows warnings.
Test the memory. Run Windows Memory Diagnostic (search for it in Start) for a quick check, then MemTest86 for several passes if the crashes continue. Any error points to a faulty stick or slot, or to memory settings the hardware cannot run reliably.
Repair Windows system files. Open Terminal (Admin) and run sfc /scannow. If it reports damage it could not repair, run DISM /Online /Cleanup-Image /RestoreHealth, restart, and run sfc /scannow once more.

When to stop and protect your data

If the drive reports reallocated or pending sectors, copy your data off immediately and replace the drive.

Not sure this is your code?

The stop code appears as text on the blue screen. If the PC restarted before you could read it, open Event Viewer, then Windows Logs, then System, and look for a BugCheck event with ID 1001. You can also search all stop codes.

Related guides

Other storage and file system errors

Frequently asked questions

What does KERNEL_DATA_INPAGE_ERROR mean?

Windows could not read a page of kernel data back from disk into memory. Windows sometimes moves memory pages to the paging file on disk and reads them back later. This stop means a requested page could not be read back. A failing drive, a bad cable or controller connection and memory errors are the typical explanations.

What usually causes KERNEL_DATA_INPAGE_ERROR?

Typical causes: A failing drive or bad sectors in the paging file area; A loose or damaged data cable, or an unreliable controller connection; Faulty RAM; Malware or file system corruption, less often.

How do I fix KERNEL_DATA_INPAGE_ERROR (0x0000007A)?

A sensible order is: 1) Check the health of the drive; 2) Check the cable and port; 3) Scan the volume; 4) Test the memory. If the drive reports reallocated or pending sectors, copy your data off immediately and replace the drive.

Use this guidance carefully

A stop code can have several causes, and these steps are general guidance rather than a diagnosis of your PC. If your data matters, back it up before repairs. If the problem continues, a hardware technician can test the parts.

See our testing methodology·Read our editorial policy