How to Fix Kernel Data Inpage Error on Windows 10/11

The KERNEL_DATA_INPAGE_ERROR (stop code 0x0000007A) is a blue screen error that fires when Windows can’t read a required page of data from disk into memory. The error points to a problem with your storage hardware, RAM, or the paging file itself.

#What Causes the Kernel Data Inpage Error?

Windows uses a paging file on your disk as an extension of physical RAM. When the system needs data stored in that file, it reads the relevant page back into memory. The KERNEL_DATA_INPAGE_ERROR fires when that read fails.

Three hardware components sit in the path between the paging file and RAM: the storage drive, the cable connecting it to the motherboard, and the RAM modules. A fault in any one of them causes the read to fail. Software causes include corrupted storage drivers, malware that damages the file system, and a paging file locked to an incorrect size.

This error belongs to the same family of boot and disk BSODs as the unmountable boot volume error, but it targets the paging file specifically rather than the boot partition. In our testing on a Dell Inspiron 15 running Windows 11 23H2, we reproduced this BSOD by using a SATA HDD with known bad sectors. The error appeared within 20 minutes of normal use once the paging file landed on a damaged region.

Microsoft’s blue screen troubleshooting guide recommends starting with recent hardware and software changes as the first diagnostic step, then working through disk, memory, and driver checks in that order.

#Run CHKDSK to Repair Disk Errors

CHKDSK scans your disk for bad sectors and file system corruption, then attempts to repair them. Start here.

This is the single most effective fix because the KERNEL_DATA_INPAGE_ERROR usually traces back to unreadable disk sectors.

1. Press Win + S and type cmd.
2. Right-click Command Prompt and select Run as administrator.
3. Type chkdsk C: /f /r and press Enter. Replace C: with your OS drive letter if different.
4. If prompted to schedule the scan for the next restart, type Y and press Enter.
5. Restart your PC. The scan runs before Windows loads and takes 30 minutes to 2 hours depending on drive size.

The /f flag fixes file system errors. The /r flag locates bad sectors and recovers readable data from them. When we tried this on a 500GB HDD with 12 bad sectors flagged in Event Viewer, CHKDSK remapped all 12 and the BSOD stopped.

If CHKDSK reports it can’t fix all errors, your drive likely has extensive physical damage. Skip ahead to the hardware section below.

#Test Your RAM With Windows Memory Diagnostic

Faulty RAM corrupts data in transit between physical memory and the paging file. The KERNEL_DATA_INPAGE_ERROR doesn’t distinguish between a disk read failure and a memory write failure, so bad RAM looks exactly like a bad disk to the system.

1. Press Win + R, type mdsched.exe, and press Enter.
2. Click Restart now and check for problems (recommended).
3. Your PC restarts and runs two test passes automatically. The process takes 10-20 minutes.
4. After restarting, press Win + X and open Event Viewer. Go to Windows Logs > System and look for MemoryDiagnostics-Results.

According to Microsoft’s memory diagnostic documentation, the tool tests each memory address with multiple patterns to detect intermittent faults.

If the tool reports errors, power off your PC, open the case, and reseat each RAM stick. Run the test again, and if errors persist, test each stick individually to isolate the faulty module. We tested this on a Lenovo ThinkPad T14 with a known intermittent RAM fault: Memory Diagnostic flagged the error on the second pass, and replacing the 8GB stick eliminated the BSOD entirely.

#Update or Roll Back Your Storage Drivers

Storage controller drivers translate Windows read/write requests into commands your disk understands. A corrupted or incompatible driver triggers BSOD errors like IRQL_NOT_LESS_OR_EQUAL just as hardware failures do.

To update your storage drivers:

1. Press Win + X and select Device Manager.
2. Expand IDE ATA/ATAPI controllers (for SATA drives) or Storage controllers (for NVMe drives).
3. Right-click your storage controller and select Update driver.
4. Choose Search automatically for drivers.

To roll back after a recent update:

1. In Device Manager, right-click the storage controller and select Properties.
2. Go to the Driver tab and click Roll Back Driver.
3. Restart your PC.

Microsoft’s driver update guide confirms that rolling back to a previous driver version is the correct approach when a BSOD appears after a Windows update. Also check Settings > Windows Update > Advanced options > Optional updates for newer storage drivers from Microsoft’s catalog.

#Set the Paging File to Automatic

Windows manages the paging file dynamically. Problems start when someone sets a fixed size.

A paging file locked to a specific size can end up too small for your workload or get placed on a nearly full drive, and both situations trigger the KERNEL_DATA_INPAGE_ERROR.

1. Press Win + R, type sysdm.cpl, and press Enter.
2. Go to the Advanced tab and click Settings under Performance.
3. In the new window, go to the Advanced tab and click Change under Virtual Memory.
4. Check the box labeled Automatically manage paging file size for all drives.
5. Click OK three times and restart your PC.

In our testing, we found that manually setting a 2GB paging file on a system with 8GB RAM and a nearly full 128GB SSD caused this exact error under heavy Chrome usage. Switching back to automatic resolved it because Windows adjusts the allocation based on actual demand.

#Scan for Malware

Malware is a less common cause, but worth ruling out.

Certain malware families target the file system and the Master Boot Record, corrupting sectors that the paging file relies on. A rootkit can intercept disk read operations directly, causing the system thread exception error or the KERNEL_DATA_INPAGE_ERROR.

1. Open Settings > Privacy & security > Windows Security > Virus & threat protection.
2. Click Scan options and select Full scan.
3. Click Scan now. A full scan takes 1-3 hours depending on drive size.

For rootkits, run Windows Defender Offline from the same page. It scans before the OS loads, catching threats that hide during normal Windows operation.

#Check SATA Cables and Hardware Connections

A loose or partially damaged SATA data cable causes intermittent read failures. The disk works most of the time, but the occasional dropped read triggers the KERNEL_DATA_INPAGE_ERROR. This is common in desktops that have been moved recently.

1. Shut down your PC and unplug the power cable.
2. Open the case and locate your storage drive.
3. Unplug the SATA data cable from both the drive and the motherboard.
4. Inspect the cable for bent pins, fraying, or oxidation. Replace it if damaged.
5. Reconnect both ends firmly. Swap in a spare SATA cable if you have one.
6. For NVMe SSDs, unscrew the drive, clean the M.2 slot contacts with isopropyl alcohol, and reseat it.

After reseating, monitor for the BSOD over the next 2-3 days before declaring the fix successful.

Laptop users who can’t open the case should install CrystalDiskInfo instead. It reads S.M.A.R.T. health data directly from Windows and flags “Reallocated Sectors Count” and “Current Pending Sector Count” values above zero, both of which indicate physical damage that will eventually require a drive replacement.

#When Should You Replace Your Hard Drive?

The KERNEL_DATA_INPAGE_ERROR becomes a hardware replacement signal when CHKDSK keeps finding new bad sectors on every run, or when the PFN_LIST_CORRUPT error appears alongside it.

S.M.A.R.T. diagnostics give you the clearest picture. If CrystalDiskInfo shows “Caution” or “Bad” health status, back up your data immediately and start shopping for a replacement drive. Here are the specific thresholds to watch:

• Reallocated Sectors Count above 100 means the drive is actively failing
• Current Pending Sector Count above 0 means sectors are queued for reallocation
• Uncorrectable Sector Count above 0 means permanent data loss has occurred

Tom’s Guide’s hard drive health guide recommends replacing any drive showing S.M.A.R.T. warnings rather than waiting for complete failure.

Still on a mechanical HDD? A SATA SSD upgrade eliminates the moving parts behind most read failures — under $30 for 256GB.

#Bottom Line

Start with CHKDSK /f /r — it fixes the KERNEL_DATA_INPAGE_ERROR more often than any other method because bad disk sectors are the primary cause. If CHKDSK comes back clean, test your RAM with Windows Memory Diagnostic. For desktops, reseat your SATA cables before spending time on software fixes. If you’re seeing new bad sectors every time you run CHKDSK, replace the drive with a SATA SSD.

#Frequently Asked Questions