A sudden system freeze culminating in a Blue Screen of Death (BSOD) displaying Stop Code: KERNEL_DATA_INPAGE_ERROR (bugcheck 0x0000007A) halts work in Windows 11. In Windows NT virtual memory architecture, the operating system paging mechanism swaps idle kernel memory blocks out to physical disk storage (the pagefile.sys) and reads them back into physical RAM when demanded by active processes (“in-paging”). When the Windows kernel attempts to read a requested kernel page from disk into physical memory, but the underlying storage controller, SSD NAND flash, SATA/NVMe bus, or filesystem fails to return the data, bugcheck 0x0000007A is triggered. This guide explains how to decipher status codes, test storage drive health, and fix error 0x0000007A in Windows 11.
What Causes KERNEL_DATA_INPAGE_ERROR?
Bugcheck 0x0000007A is fundamentally an input/output (I/O) communication breakdown between the disk and RAM:
- Physical Bad Sectors on Storage Drive (SSD/HDD): Corrupted NAND flash blocks or magnetic sectors residing directly within the storage boundaries of
pagefile.sys. - Faulty SATA Cable or Loose NVMe M.2 Slot Connection: Loose physical cable connections or oxidized M.2 PCIe contacts introducing signal noise during high-throughput I/O.
- Outdated Storage Controller Firmware / AHCI Driver: Incompatible NVMe controller drivers (such as Intel RST or standard NVM Express drivers) timing out during sleep-wake transitions.
- Filesystem Structural Damage: Corrupted Master File Table (MFT) records or damaged NTFS metadata preventing the operating system from reading virtual memory blocks.
- Defective Physical RAM (Memory): Faulty DRAM memory chips unable to receive in-paged data packets from the disk controller.
Method 1: Decipher Bugcheck Parameter 2 (I/O Status Code)
Bugcheck 0x0000007A includes an I/O status code (Parameter 2) that reveals the exact hardware reason for the read failure:
0xC000009C(STATUS_DEVICE_DATA_ERROR): Storage drive has physical bad sectors or dying NAND flash cells.0xC000009D(STATUS_DEVICE_NOT_CONNECTED): The storage drive physically disconnected or lost power during I/O (loose NVMe/SATA connection).0xC0000185(STATUS_IO_DEVICE_ERROR): Cable impedance fault, faulty SATA cable, or hardware communication termination.0xC000000E(STATUS_NO_SUCH_DEVICE): Storage device disappeared from the PCIe/SATA bus.
Method 2: Run CHKDSK to Remap Bad Disk Sectors
The Check Disk utility evaluates file system integrity and marks unreadable bad sectors so the operating system avoids them.
- Press Win + S, type
cmd, right-click Command Prompt, and select Run as administrator. - Execute the comprehensive disk repair command:
chkdsk C: /f /r /x - Command Prompt will inform you that the drive cannot be locked because it is in use, prompting: “Would you like to schedule this volume to be checked the next time the system restarts? (Y/N)”.
- Type
Yand press Enter. - Restart your computer. Windows will perform a thorough sector scan and recovery during startup before loading the desktop.
Method 3: Reseat NVMe M.2 SSD or Replace SATA Cables
Hardware disconnects (status code 0xC000009D or 0xC0000185) point to physical connection degradation.
- Shut down your desktop PC or laptop and disconnect the power adapter.
- Open the computer casing:
- For NVMe M.2 SSDs: Remove the mounting screw, gently slide the M.2 SSD out of its PCIe slot, clean the gold contact pins with a dry lint-free cloth, and firmly reseat the drive back into the slot.
- For 2.5-inch SATA SSDs/HDDs: Replace the SATA data cable with a brand-new, shielded SATA III 6 Gbps cable and connect to an alternative SATA motherboard port.
- Reassemble and power on the computer.
Method 4: Recreate the Windows Paging File (pagefile.sys)
Deleting the current paging file and generating a fresh allocation eliminates corrupt virtual memory sectors.
- Press Win + R, type
sysdm.cpl, and press Enter. - Select the Advanced tab.
- Under Performance, click Settings… > select the Advanced tab > click Change… under Virtual memory.
- Uncheck Automatically manage paging file size for all drives.
- Select your primary drive (C:), choose No paging file, and click Set. Confirm the prompt.
- Restart your PC. Windows will boot without a paging file, purging the old disk blocks.
- After reboot, return to Virtual Memory settings, re-check Automatically manage paging file size for all drives, and click OK. Windows creates a fresh, healthy
pagefile.sys.
Method 5: Check SMART Drive Health via CrystalDiskInfo
Evaluating drive telemetry confirms whether the underlying drive requires urgent warranty replacement.
- Download the open-source diagnostic utility CrystalDiskInfo.
- Launch the utility and review the overall Health Status:
- Good (Blue): Storage drive NAND and sectors are healthy.
- Caution (Yellow): Reallocated sectors or uncorrectable sector counts detected; back up your data immediately and replace the drive.
- Bad (Red): Imminent drive failure.
KERNEL_DATA_INPAGE_ERROR Diagnostic Matrix
| Status Hex Code | Hardware Interpretation | Required Action |
|---|---|---|
0xC000009C |
Physical bad sectors on storage drive | Run chkdsk C: /f /r; monitor SMART drive health |
0xC000009D |
Storage drive dropped offline / lost connection | Reseat NVMe M.2 drive or replace SATA data cable |
0xC0000185 |
SATA/PCIe bus communication error | Update motherboard chipset and NVMe controller drivers |
0xC000000E |
Boot device unavailable during I/O | Rebuild EFI bootloader; check BIOS boot priority |
Frequently Asked Questions
Does KERNEL_DATA_INPAGE_ERROR mean my SSD is dying?
In many cases, yes. While a loose cable or corrupted filesystem can trigger the error, code 0x0000007A is the primary blue screen symptom of an SSD or hard drive developing unreadable NAND flash blocks. Back up your critical files immediately when this error appears.
Can RAM failure trigger KERNEL_DATA_INPAGE_ERROR?
Yes. If physical RAM fails to receive data being paged in from the disk, the memory controller generates a page fault. Run Windows Memory Diagnostic (mdsched.exe) to verify RAM integrity alongside disk checks.