Kernel_Data_Inpage_Error Windows 11
On Windows 11, KERNEL_DATA_INPAGE_ERROR often points to storage or paging-file trouble. Ignoring it can mean repeated BSODs, file corruption, or a drive that fails before you back up data. This guide shows how to read the stop-code parameters, compare disk and memory symptoms, and narrow the cause before you start generic repairs.
What this stop code means
KERNEL_DATA_INPAGE_ERROR is Windows bug check 0x0000007A, and it means the requested page of kernel data from the paging file couldn’t be read into memory. The fastest first move is to back up anything important, then check the stop-code parameters before you run broad repairs. (Microsoft)
How to read the crash pattern
If the crash happens during game launches, large downloads, installs, or file copies, storage deserves priority. If it happens at random, after sleep, or on different apps with no disk-heavy activity, suspect RAM or storage hardware sooner. A one-off crash after a power cut is a different pattern from a repeat BSOD loop.
Say your PC blue-screens once after a long copy to an external SSD, then boots normally. That leans toward a read problem on the storage path. Suppose it blue-screens twice a day with different stop codes after a system change. That leans away from a single bad block and toward memory or hardware instability.
📊 KERNEL_DATA_INPAGE_ERROR bug check has value 0x0000007A. Source: Microsoft.
Likely causes, ranked
Most often, this stop code starts with storage hardware or connection trouble, then memory corruption, then other system issues. Use the parameter 2 status code to sort those branches before you spend time on generic fixes. That order saves time on Windows 11, especially when the machine keeps crashing after disk activity.
What to look for first
1. Storage hardware, cabling, or connection integrity. 2. RAM faults or unstable memory settings. 3. A virus infection. 4. Insufficient non-paged pool resources. 5. Incorrect drive configuration or hardware detection failure. Event Viewer and minidumps help separate those paths.
Storage hardware: what to check first?
If the status code points to the disk path, start with the drive and its connection before you run deeper repairs. Back up data first if the drive may be failing. On a desktop, check the SATA cable and power lead. On an SSD or NVMe drive, reseat the device and inspect the slot or adapter.
First steps for disk-related crashes
- Copy important files to another drive or cloud storage before repair.
- Open Event Viewer and check Windows Logs > System for disk, storahci, nvme, or controller errors before the crash.
- Run the manufacturer’s storage diagnostic utility on the SSD or hard drive.
- Open an elevated Command Prompt or Windows Terminal, then run
chkdsk /f /r. - Restart when prompted, because Autochk runs automatically after restart and attempts to map bad sectors.
Chkdsk /f /r is the right repair command for bad block problems. The /f switch fixes file-system errors, and /r checks for bad sectors and tries to recover readable data. If the system asks for a reboot, let it reboot before the scan begins.
When storage becomes the escalation point
If the drive utility reports bad blocks, uncorrectable errors, or repeated data errors, stop treating the issue as a simple software problem. Replace the drive or move the system image to known-good storage. A machine that crashes every time it touches the paging file is not a good candidate for endless repairs.
RAM or memory corruption: what to test?
If crashes repeat with different stop codes, or if the PC fails outside disk-heavy tasks, RAM or unstable memory settings move up the list. Start with the motherboard or system vendor’s memory diagnostic, then use extended testing if the error returns. Leave overclocking off until the system is stable.
Exact RAM checks to run
- Restore BIOS or UEFI memory settings to stock values.
- Turn off XMP or any manual memory overclock.
- Run Windows Memory Diagnostic for a quick screen.
- If the error repeats, run a MemTest86-style extended scan, and use an 8-pass run when available.
- If one stick fails, test each module separately in the same slot.
Memory corruption can look like storage trouble because the system only sees a failure while paging data in. That is why a single 0x7A does not always mean the disk is guilty. Repeated random crashes across apps, especially after a BIOS change or memory profile change, push RAM higher on the list.
Virus infection: what to check?
A virus infection can also cause this bug check. If the problem started after you noticed unusual system behavior, run a full scan with Windows Security, keep the built-in protection updated, and remove any detected threat before you retest the system. If the system still crashes, continue with storage and memory checks.
How to isolate security software
- Open Windows Security and run a full scan.
- Make sure protection updates are current.
- Test the machine during normal use and during a disk-heavy task.
- If the system stays stable, continue normal use and monitor for recurrence.
Security software can sit between Windows and the disk path, but antivirus removal is not the first assumption here. If a scan finds a threat, clean it and retest the PC before you move on to deeper hardware checks.
Driver and update fixes
Windows updates and driver problems sit lower than hardware on the triage list, but they matter when the crash follows a system change or happens with no storage errors. Install Windows updates first, then inspect Event Viewer and minidumps to identify the device involved.
Steps for software-side cleanup
- Open Settings > Windows Update and install the latest updates.
- Open Settings > Windows Update > Advanced options > Optional updates and install driver updates that apply.
- Open Event Viewer and review Windows Logs > System for the last errors before the crash.
- Check minidumps with a debugger or vendor support tool if the same device appears again.
- If a recent system change coincides with the crash, undo that change and retest.
In one support case, bugcheck 0x0000007A appeared with status 0xffffffffc000000e, and the reply pointed to driver removal plus DISM and SFC repairs. That does not make every 0x7A a driver fault. It does mean you should check driver evidence before assuming the disk is the only problem.
Kernel data triage table
The second bug-check parameter is the status code that tells you where to focus first. Use it to sort the crash before you run broad repairs. The table below maps the most useful 0x7A status codes to the most likely cause, the first test, and the next escalation step on Windows 11.
| Parameter 2 status code | Most likely cause | First test to run | Escalation action |
|---|---|---|---|
0xC000000E | Hardware failure or incorrect drive configuration | Check drive detection in BIOS or UEFI, then inspect Event Viewer for controller errors | Back up data, run the manufacturer storage diagnostic, and replace the drive if detection stays unstable |
0xC000009A | Lack of non-paged pool resources | Review memory usage and system load, then retest after a restart | If the issue repeats, look for a driver, service, or workload that is exhausting resources |
0xC000009C | Bad blocks on the hard disk | Run chkdsk /f /r after backing up | If bad blocks recur, move data off the drive and replace the storage device |
0xC000009D | Loose or defective cabling, or the controller does not see the hard disk | Reseat cables and reseat the drive or adapter | Swap the cable, port, or controller path; replace the drive if detection remains erratic |
0xC000016A | Bad blocks on the hard disk | Run chkdsk /f /r and let Autochk map bad sectors on reboot | If the scan finds recurring damage, treat the drive as failing and copy data off it |
0xC0000185 | Improper termination or defective cabling on SCSI devices | Check the cable, termination, and connection path | If the device is still unstable, replace the cable or the storage hardware |
Still not working?
If the crash keeps returning after storage checks, memory testing, updates, and system cleanup, stop and treat the problem as hardware until proven otherwise. Repeated 0x7A crashes during file access usually mean the drive path is unstable. If the machine still boots, collect Event Viewer entries and minidumps before the next reboot cycle.
What to do next
- Back up data immediately if you have not done so.
- Run the drive maker’s diagnostic again, especially if the disk is SSD, HDD, or NVMe.
- Test with one memory module at a time if RAM remains suspect.
- Repair Windows system files with
sfc /scannowandDISM /Online /Cleanup-Image /RestoreHealthif storage and RAM tests are clean. - Seek vendor support or replacement if the storage device still reports read errors or bad blocks.
Prevention: Keep Windows 11 updated, and do not ignore early disk warnings or repeated Event Viewer storage errors. If the machine starts blue-screening after a new drive or cable install, test that change first before you widen the repair path.
Frequently asked questions
What does kernel_data_inpage_error mean on Windows 11?
It means Windows could not bring a requested page of kernel data from the paging file into memory. Start with the 0x7A status code, then check the drive path, Event Viewer, and the storage manufacturer’s diagnostic utility. If the code repeats with different parameters, memory or storage hardware becomes more likely.
Is kernel_data_inpage_error caused by a bad hard drive?
Often, yes. Status codes such as 0xC000009C and 0xC000016A point to bad blocks on the hard disk, and 0xC000009D points to cabling or controller problems. If the crash happens during file copies or game loading, back up data first and run chkdsk /f /r.
Can a virus cause kernel_data_inpage_error?
Yes. A virus infection can trigger this bug check. Remove the threat with Windows Security, restart Windows 11, and test again under normal use. If the BSOD stops, keep protection updated and monitor the system for recurrence.
What do the 0x7a parameters mean in a kernel data inpage error?
Parameter 2 is the key clue because it carries the NTSTATUS code. Read 0xC000000E as a hardware failure or incorrect drive configuration, 0xC000009C and 0xC000016A as bad blocks, 0xC000009D as cabling or controller trouble, 0xC0000185 as a termination or cable issue on SCSI devices, and 0xC000009A as insufficient non-paged pool resources.
Should I run chkdsk or memtest for kernel_data_inpage_error?
Run chkdsk /f /r first if the status code points to disk damage or the crash follows file activity. Run a memory test if the crash repeats with different stop codes, happens at random, or survives a clean disk check. When both tests are clean, focus on hardware replacement or system changes.
What should I do if Windows 11 keeps blue screening with kernel_data_inpage_error?
Back up files, check the parameter 2 status code, and then work in order: storage diagnostics, cable or connection checks, memory testing, Windows Update, and system cleanup. If the drive reports bad blocks, move data off it quickly. If the same crash continues after those steps, stop basic repair and escalate to replacement or vendor support.
