Fixing KERNEL_DATA_INPAGE_ERROR: A Deep Diagnostic Guide

The dreaded KERNEL_DATA_INPAGE_ERROR (Stop Code: 0x0000007A) is one of the most revealing Blue Screens of Death in Windows. Unlike generic crashes, it tells you exactly what failed at a structural level: the operating system tried to read a page of kernel data from virtual memory (the pagefile on your disk) into physical memory (RAM), but the read operation failed.

In this guide, we will walk through the hardware and system diagnostics necessary to trace the root cause, determine if your SSD/HDD is failing, check memory corruption, and fix the underlying connection issues.

---

1. Demystifying the Crash Parameters

When the crash occurs, the Blue Screen layout may list four parameters:

1. Parameter 1: The address of the pagefile page that couldn’t be read.
2. Parameter 2: The I/O status code (NTSTATUS) representing the exact transfer failure.
3. Parameter 3: The physical page number within RAM.
4. Parameter 4: The offset address.

Typically, the most critical parameter is Parameter 2 (the I/O status code). Keep an eye out for these common hex codes:

• 0xC000009C (STATUS_DEVICE_DATA_ERROR): Indicates bad blocks on the drive.
• 0xC000009D (STATUS_DEVICE_NOT_CONNECTED): Indicates loose SATA, M.2 cabling, or a drive controller that suddenly lost power.
• 0xC000016A (STATUS_DISK_OPERATION_FAILED): Bad sectors or controller hardware failures.
• 0xC0000185 (STATUS_IO_DEVICE_ERROR): Loose cables or duplicate SCSI IDs.

---

2. Check Drive SMART Attributes

Since a bad storage sector is the most frequent culprit, checking your drive’s Self-Monitoring, Analysis, and Reporting Technology (S.M.A.R.T.) metrics is the crucial first step.

You can inspect these values using a terminal utility or a GUI tool like CrystalDiskInfo:

# In PowerShell (Administrator), run this to get basic drive health status:
Get-PhysicalDisk | Select-Object DeviceId, FriendlyName, OperationalStatus, HealthStatus

If the status returns anything other than Healthy, check the following raw attributes:

• 05 (Reallocated Sectors Count): Shows the number of damaged sectors retired and replaced by spare sectors. A rising value means impending drive failure.
• BB (Reported Uncorrectable Errors): Hardware errors that could not be recovered by ECC (Error Correction Code).
• C7 (UltraDMA CRC Error Count): Points to connection cable interference or bad physical ports. If this is high on a SATA SSD, replace the SATA data cable.

---

3. Verify Memory and RAM Integrity

If the pagefile data was read off the disk but corrupted on its way into RAM, memory modules are the secondary suspect.

To test memory:

1. Press Windows Key + R, type mdsched.exe, and hit Enter.
2. Select Restart now and check for problems.
3. Upon reboot, the Windows Memory Diagnostic Tool will scan your RAM.

For a more rigorous test, download MemTest86 onto a USB drive and boot into it. Let it run for at least 4 full passes. If even a single error is reported, you have a faulty RAM module or an unstable memory overclock (XMP/EXPO profile).

---

4. Run CHKDSK and File Diagnostics

If the SMART status is healthy, Windows might simply have filesystem corruption in the pagefile sector. You can force Windows to search and repair filesystem errors:

1. Open PowerShell or Command Prompt as Administrator.
2. Run the check disk utility:

   chkdsk C: /f /r

   Note: Windows will ask to schedule the volume check on next reboot. Type Y and restart your PC.
3. After CHKDSK completes, run the System File Checker to repair missing system assets:

   sfc /scannow

---

Conclusion

If the KERNEL_DATA_INPAGE_ERROR persists and Parameter 2 shows 0xC000009D, turn off your PC, open the chassis, and reseat your drive connections. For M.2 NVMe SSDs, clean the contacts with isopropyl alcohol and secure it firmly in the slot. If bad sectors continue to multiply on SMART, clone the drive to a new SSD immediately to prevent data loss.