The Problem

KERNEL_DATA_INPAGE_ERROR (stop code 0x0000007A) means Windows asked for a page of kernel data that had been moved out to disk, and the read failed. Something between memory and the platter — the drive, its cable, its controller, its driver, or the page file itself — did not return the data.

This is one of the few stop codes that tells you why if you look closely. The blue screen prints four parameters, and the second one is a status code that names the failure category. Reading it turns an hour of guessing into a five-minute diagnosis, so Step 1 is where the value is.

Windows also failing to boot, or hanging on the spinning dots? Same underlying drive problem — see fix Windows 11 stuck on the loading screen.

Symptoms

Blue screen reading KERNEL_DATA_INPAGE_ERROR, often when opening a large file or launching an app.
Clicking or grinding from a mechanical drive shortly before the crash.
Windows freezes for several seconds at a time, then recovers or crashes.
File Explorer reports files as corrupt or unreadable between crashes.
Boot times have crept up from seconds to a minute or more.

Step 1: Read the Status Code on the Blue Screen

Photograph the blue screen, including the parameter line beginning 0x0000007A.
The second parameter is the status code. Match it below:

| Status | What it means | |---|---| | 0xC000009C | Bad sectors — the drive has physically failing areas | | 0xC000009D | Loose or faulty cable, or a drive that is failing to respond | | 0xC000016A | A bad block was found and could not be read | | 0xC0000185 | Cabling or termination fault on the storage bus | | 0xC000000E | The drive was not found at all |

If you cannot catch the screen, open Windows + R → eventvwr.msc → Windows Logs → System, and filter by source BugCheck — the parameters are recorded there.
Full method: how to use Event Viewer to find why your PC crashed.

Anything in the 0xC00000xx family above points at the storage device, not at Windows. Back up now, before troubleshooting further.

Step 2: Back Up Before You Do Anything Else

This stop code is one of the most reliable early warnings of drive failure there is. Running repair tools on a dying disk can be the thing that finishes it off.

Copy irreplaceable files to an external drive or cloud storage first — documents, photos, anything you have not got a second copy of.
Do not defragment, do not run a long chkdsk pass, and do not image the drive until the important files are off it.
Set this up properly afterwards: set up automatic backups and back up your PC with Windows Backup and File History.

Step 3: Reseat the Cables and Connections

Shut down, unplug the PC at the wall, and hold the power button for five seconds.
On a desktop, unplug and reconnect both ends of the SATA data cable, and the SATA power lead. Swap in a different SATA cable if you have one — they fail more often than people expect.
For an M.2 NVMe drive, loosen the retaining screw, reseat the drive fully, and retighten. Check the standoff is in the right hole for the drive's length.
Plug the drive into a different SATA port on the motherboard.
On a laptop, if the drive is accessible, reseat it in its connector.

Step 4: Check the Drive's Own Health Report

Right-click Start → Terminal (Admin) and run:
```
wmic diskdrive get model,status
```
Anything other than OK is conclusive — replace the drive.
Read the full SMART attributes with CrystalDiskInfo. Watch Reallocated Sectors Count, Current Pending Sector Count, and Uncorrectable Sector Count — any non-zero value on a mechanical drive means it is degrading.
On an SSD, check Percentage Used and Available Spare.
Detail: check SSD and hard drive health.
Update the SSD firmware from the maker's toolbox — Samsung Magician, Crucial Storage Executive, WD Dashboard, Kingston SSD Manager.

Step 5: Scan the File System for Bad Sectors

Only after Step 2. On a large mechanical drive this can take several hours.

In Terminal (Admin):
```
chkdsk C: /f /r
```
Press Y to schedule it for the next restart, then reboot and let it run to completion without interrupting.
/r locates bad sectors and recovers readable information; /f fixes file system errors.
If chkdsk reports and remaps a growing number of bad sectors across repeated runs, the drive is failing — replace it rather than repairing it again.

Step 6: Rebuild the Page File

A damaged page file produces this exact error even on a healthy drive.

Windows + R → sysdm.cpl → Advanced tab → Performance → Settings → Advanced → Change.
Untick Automatically manage paging file size for all drives.
Select the system drive, choose No paging file, click Set, and reboot.
Return to the same screen, choose System managed size, click Set, and reboot again. Windows builds a fresh page file.
Never leave the page file disabled permanently — Windows needs it even with plenty of RAM.

Step 7: Repair Windows and Update Storage Drivers

In Terminal (Admin):
```
sfc /scannow
```

Then:

DISM /Online /Cleanup-Image /RestoreHealth

Reboot and repeat sfc /scannow. Full guide: how to run SFC and DISM.
Install the chipset and storage controller drivers (Intel RST, AMD NVMe) from your motherboard or laptop vendor's support page, not from a generic updater. See how to update outdated drivers.
Update the motherboard BIOS — NVMe compatibility fixes ship in firmware.

Step 8: Rule Out Memory

Memory faults corrupt data on its way to and from the disk, which surfaces as an inpage error.

Windows + R → mdsched.exe → Restart now and check for problems, pressing F1 to set Extended.
Follow with MemTest86 from USB for four passes or more.
Disable XMP / EXPO and retest at stock speed: how to enter BIOS or UEFI.
Related: check and upgrade your RAM and fix PFN_LIST_CORRUPT.

What Not to Do

Don't run chkdsk repeatedly on a clicking drive. Every pass is more stress on a mechanism that is already failing. Recover your files instead: how to recover deleted files in Windows.
Don't reinstall Windows onto the same suspect drive. The install will likely fail partway, or crash again within days.
Don't disable the page file as a workaround. It hides the symptom and causes new problems.
Don't ignore a single occurrence. This code rarely appears once on healthy hardware.

Still Not Working?

If SMART is clean, memory tests fine, cables are new, and the crashes continue, the storage controller on the motherboard is the remaining suspect. Try the drive in another machine, or another drive in this one, to separate the two. If the drive is confirmed failing, replace it and start fresh: how to choose an SSD for your PC and how to clone an HDD to an SSD.

How to Fix KERNEL_DATA_INPAGE_ERROR in Windows 11