Fix KERNEL_DATA_INPAGE_ERROR on Windows 10/11 (Exact Commands)

The fast answer. KERNEL_DATA_INPAGE_ERROR (stop code 0x0000007A) means Windows tried to read a page of kernel data from the paging file on disk back into memory and the read failed. Treat it as a storage problem first: a failing drive, bad sectors, or a loose cable. Failing RAM is the next most likely cause. Back up your files while the PC still runs, check the drive's health, then repair bad sectors from an admin Command Prompt:

chkdsk C: /f /r

On the system drive, type Y to schedule the scan and restart. If the drive reports as unhealthy or chkdsk finds bad sectors, plan to replace it. No command repairs a dying disk.

Why this happens

Bad sectors or a failing drive — the most common cause. Status codes 0xC000009C and 0xC000016A in the error point to bad blocks on the disk.
Loose or bad cabling or connection — 0xC000009D means the controller can't see the disk. A worn SATA cable, a loose power connector, or a badly seated NVMe drive can cause it.
Failing RAM — bad memory can corrupt data as it moves between disk and memory.
Storage driver or firmware problems — an outdated storage controller driver or SSD firmware.
Malware — Microsoft lists virus infection as a less common cause.

Step-by-step fix

Step 1 — Read the error status code

The second parameter of the bug check is an I/O status code, and it usually tells you which part failed. If Windows boots, open Event Viewer → Windows Logs → System and find the BugCheck entry (Event ID 1001) for the crash. Its message shows 0x0000007a followed by four parameters, and the second one is the status code:

0xC000009C or 0xC000016A — bad sectors on the disk.
0xC000009D — loose or bad cabling, or the controller can't see the disk.
0xC0000185 — I/O device error, often cabling.
0xC000000E — hardware failure or incorrect drive configuration.
0xC000009A — insufficient resources (non-paged pool), not a disk fault.

Step 2 — Check drive health before stressing it

In an admin PowerShell, check what Windows reports for each disk:

Get-PhysicalDisk

Look at the HealthStatus and OperationalStatus columns. Anything other than Healthy / OK means you should back up and replace the drive. For a firmer verdict, run the drive maker's diagnostic tool. A "Healthy" result doesn't fully clear the drive, but a warning is reliable bad news.

Step 3 — Reseat cables and connections

Shut down and unplug the PC. On a desktop, reseat the SATA data and power cables at both ends, or swap in a known-good SATA cable and port. For an NVMe SSD, reseat it in its M.2 slot. Microsoft also recommends making sure all adapter cards are properly seated. This is the main fix for 0xC000009D and 0xC0000185.

Step 4 — Repair bad sectors with chkdsk

From an admin Command Prompt in Windows, run:

chkdsk C: /f /r

Because the system drive is in use, chkdsk asks to run at the next restart. Type Y and reboot. If Windows won't stay up long enough, enter Windows Recovery (WinRE): force three failed boots to trigger Automatic Repair, or boot a Windows install USB and choose Repair your computer. Then go to Troubleshoot → Advanced options → Command Prompt and run the same command. The Windows drive letter can differ in WinRE, so confirm it with dir C:\ first. /r reads every sector and takes a long time on large drives.

Step 5 — Test the RAM

Run the built-in Windows Memory Diagnostic (press Win+R):

mdsched.exe

Choose Restart now and check for problems. Results appear after Windows restarts. For a deeper test, boot MemTest86 from a USB stick and run several passes. If you have more than one memory stick, test them one at a time.

Step 6 — Scan for malware and repair system files

Run a full scan with an up-to-date antivirus. With Microsoft Defender, also run Windows Security → Virus & threat protection → Scan options → Microsoft Defender Offline scan. Then repair system files from an admin Command Prompt:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

These repair software damage only. They won't fix a bad disk or bad RAM.

Step 7 — Update Windows, storage drivers, and SSD firmware

Install the latest Windows updates. Then get current chipset and storage controller drivers from your PC or motherboard maker's support page. If you have an SSD, check the drive maker's tool for a firmware update. Back up first, and never cut power during a firmware update.

Data safety: This stop code very often means the drive holding Windows is failing. Copy your important files off it now, while it still runs, before you run chkdsk /r or any long diagnostic. A full sector-by-sector read can push a weak drive over the edge. If the drive clicks, disappears, or freezes repeatedly, stop scanning it. Image it to a known-good external disk, or take it to a professional data recovery service, and never run repairs on the only copy of irreplaceable data.

GRAM tip: KERNEL_DATA_INPAGE_ERROR usually leaves Windows bootable between crashes, so GRAM applies directly. Plug in GRAM — a free portable repair toolkit that runs from a USB inside Windows — to check SMART disk health, analyze the crash dumps, and pull the disk and BugCheck history from the event logs. Then let its AI agent help you work out whether the drive, a cable, or the RAM is to blame.

Download GRAM free See AI pricing →

FAQ

Can I fix this without a second working computer?

Yes. Most of these steps run inside Windows, which usually still boots between crashes. If it won't reach the desktop, Windows Recovery (WinRE) lives on the broken PC itself — force three failed boots to trigger Automatic Repair, or boot from any Windows install USB — and you can run chkdsk from its Command Prompt. You'd only need another PC to create a MemTest86 USB or install USB, or to receive your backed-up files. (GRAM runs inside Windows rather than from boot media — use it once the machine boots to check disk health and confirm the root cause.)

Does KERNEL_DATA_INPAGE_ERROR mean my drive is dying?

Often, but not always. Microsoft lists defective storage hardware and failing RAM as the common causes, and loose cabling is behind some cases. Check the status code first. Bad-sector codes (0xC000009C, 0xC000016A) plus a non-Healthy drive status mean you should back up and replace the drive.

Will chkdsk /r erase my files?

No, it doesn't wipe the drive. It repairs the file system and marks bad sectors so they aren't used again. Files stored on unreadable sectors may be lost or moved to FOUND.000 folders. On a failing drive, the long read can make things worse, so copy important files off first.

Will sfc or DISM fix this error?

Rarely. They repair Windows system files, but this stop code is almost always a disk, cable, or memory problem. Run them after the hardware checks to rule out software damage. Don't expect them to cure a failing drive.