KERNEL_DATA_INPAGE_ERROR is a Windows Blue Screen of Death (BSOD) with the bug-check value:

0x0000007A

Microsoft defines bug check 0x7A as a condition where Windows could not read a requested page of kernel data from the paging file into memory.

In simpler terms, Windows needed critical data that should have been available from the storage subsystem, but the data could not be successfully read into RAM.

This makes KERNEL_DATA_INPAGE_ERROR particularly important because it can indicate problems involving:

• SSD, HDD or NVMe storage
• Bad sectors or failing storage media
• SATA/storage cables
• Storage controllers
• RAM
• Windows paging file
• Storage or chipset drivers
• File-system corruption
• Windows system-file corruption
• BIOS/UEFI or storage firmware
• Motherboard/storage-controller hardware

Unlike some BSOD errors that are primarily caused by software, repeated 0x7A crashes should make storage and RAM diagnostics a priority. Microsoft specifically lists defective storage hardware and failing RAM among common causes.

Common Symptoms

A computer affected by KERNEL_DATA_INPAGE_ERROR may show one or more of these symptoms:

• Sudden blue screen while Windows is running
• Stop code KERNEL_DATA_INPAGE_ERROR
• Error 0x0000007A
• Random restart
• Windows freezing before the BSOD
• Applications becoming unresponsive
• Very high disk activity
• Slow file access
• Windows taking unusually long to boot
• Clicking/noise from a mechanical HDD
• SSD or NVMe intermittently disappearing
• Disk-related errors in Event Viewer
• BSOD while copying large files
• BSOD while gaming or under heavy load
• Crashes shortly after startup
• Automatic disk checking during startup

If the problem occurs repeatedly, back up important data as soon as possible because a deteriorating storage device is one possible cause.

Understanding the 0x7A Error

The KERNEL_DATA_INPAGE_ERROR bug check contains four parameters. For advanced troubleshooting, Parameter 2 is especially useful because it normally contains an I/O error status code that can provide clues about the underlying failure.

Some important status codes documented by Microsoft include:

0xC000009A – STATUS_INSUFFICIENT_RESOURCES

Windows did not have sufficient non-paged pool resources.

This is different from the disk-related status codes and may require investigating memory/resource exhaustion.

0xC000009C – STATUS_DEVICE_DATA_ERROR

This commonly indicates a storage media problem such as a bad block or bad sector.

If this code appears repeatedly, check the SSD/HDD immediately.

0xC000009D – STATUS_DEVICE_NOT_CONNECTED

Windows could not properly communicate with the storage device.

Possible causes include:

• Loose SATA cable
• Defective SATA cable
• Storage controller problem
• Intermittently disconnected drive
• Failing SSD/HDD

0xC000016A – STATUS_DISK_OPERATION_FAILED

This can indicate that Windows could not read the required data because of bad blocks/sectors on the disk.

0xC0000185 – STATUS_IO_DEVICE_ERROR

This indicates an I/O communication problem.

On modern systems, investigate:

• Storage device
• Storage controller
• Cables/connectors
• Controller drivers
• Motherboard
• External storage connections, where applicable

0xC000000E – STATUS_NO_SUCH_DEVICE

Windows can no longer access the expected device.

Possible causes include:

• Storage hardware failure
• Incorrect storage configuration
• Loose connection
• Controller problem
• Drive intermittently disappearing

Microsoft specifically recommends checking the drive connections and running the diagnostic utility supplied by the drive manufacturer for this condition.

Major Causes of KERNEL_DATA_INPAGE_ERROR

1. Failing SSD, HDD or NVMe Drive

A deteriorating system drive is one of the first possibilities to investigate.

Windows uses the storage device continuously, including for the paging file. If the drive cannot reliably return requested data, Windows may trigger bug check 0x7A.

Warning signs include:

• SMART warnings
• Increasing bad/reallocated sectors on applicable drives
• File corruption
• Slow disk access
• Disk disappearing from BIOS/Windows
• Frequent disk-related Event Viewer errors
• Repeated CHKDSK repairs
• Random read/write errors

Do not rely solely on the fact that Windows still boots. A failing drive can remain partially operational for some time.

2. Bad Sectors or Unreadable Disk Blocks

Microsoft specifically associates status codes 0xC000009C and 0xC000016A with bad blocks/sectors.

Mechanical hard drives are particularly susceptible to physical sector deterioration, although SSDs can also develop unreadable areas or other flash/controller problems.

Repeated bad-block errors should be treated as a potential hardware problem rather than repeatedly “repairing” the disk indefinitely.

3. Loose or Defective SATA Cable

For SATA SSDs and HDDs, do not overlook the data cable.

A defective or poorly seated SATA cable can interrupt communication between the motherboard and storage device.

For desktop computers:

1. Shut down Windows.
2. Disconnect AC power.
3. Reseat the SATA data cable.
4. Reseat the SATA power connector.
5. If possible, replace the SATA cable.
6. Try another motherboard SATA port.

For NVMe SSDs, reseat the module if you are qualified to service the system and doing so does not conflict with warranty/service requirements.

4. Faulty RAM

Microsoft also lists failing RAM as a common cause of KERNEL_DATA_INPAGE_ERROR.

Memory corruption can make a storage-related crash appear more complicated than it actually is.

RAM problems may also produce other BSODs such as:

• MEMORY_MANAGEMENT
• PAGE_FAULT_IN_NONPAGED_AREA
• IRQL_NOT_LESS_OR_EQUAL
• SYSTEM_SERVICE_EXCEPTION
• KERNEL_SECURITY_CHECK_FAILURE

If several unrelated BSOD codes occur randomly, RAM becomes an important suspect.

5. Paging File Problems

Windows virtual memory uses a paging file, normally:

C:\pagefile.sys

Because KERNEL_DATA_INPAGE_ERROR specifically concerns kernel data that could not be read from the paging file into memory, paging-file and underlying storage problems deserve attention.

In most cases, Windows should be allowed to manage the paging-file size automatically.

To check:

Settings → System → About → Advanced system settings → Performance → Settings → Advanced → Virtual memory

Normally select:

Automatically manage paging file size for all drives

or use:

System managed size

Avoid disabling the paging file as a general BSOD troubleshooting measure.

6. Storage Controller or Driver Problems

Storage drivers form the communication layer between Windows and storage hardware.

Problems may involve:

• Standard SATA AHCI Controller
• Intel storage/RST components
• AMD chipset/storage components
• NVMe controller drivers
• RAID controller drivers
• OEM storage drivers

A problem may appear after:

• Driver installation
• Windows update
• BIOS update
• Storage-mode change
• SSD replacement
• System cloning

Check:

Device Manager → Storage controllers

and:

Device Manager → IDE ATA/ATAPI controllers

depending on the hardware.

Use drivers supplied by Windows Update or the PC/motherboard/storage-controller manufacturer where appropriate.

Do not randomly change BIOS storage mode between AHCI/RAID/IDE on an existing Windows installation. Doing so can make Windows unbootable.

7. Corrupted Windows System Files

Damaged Windows components may contribute to system instability.

Microsoft recommends using DISM followed by System File Checker when repairing Windows component and system-file corruption.

Open Command Prompt or Terminal as Administrator and run:

DISM.exe /Online /Cleanup-Image /RestoreHealth

After DISM completes successfully, run:

sfc /scannow

Restart the computer afterward.

8. BIOS/UEFI or SSD Firmware Problems

Firmware can occasionally contribute to storage instability.

Check your:

• Computer manufacturer's support page
• Motherboard manufacturer's support page
• SSD manufacturer's management utility

Look for applicable updates for:

• BIOS/UEFI
• Chipset
• Storage controller
• SSD/NVMe firmware

Important: Never interrupt a BIOS or SSD firmware update. Back up important data first and follow the manufacturer's instructions exactly.

Complete KERNEL_DATA_INPAGE_ERROR Troubleshooting Procedure

Step 1 – Back Up Important Data First

If Windows still starts, copy important files before performing extensive troubleshooting.

Prioritize:

• Documents
• Desktop
• Email archives
• Accounting data
• Business databases
• Browser data
• Application databases
• Photos
• Project files

If you suspect physical disk failure, avoid unnecessary stress tests until critical data is safely backed up.

Step 2 – Check the Exact BSOD Information

Record:

• Stop code
• Bug-check parameters
• “What failed” filename, if shown
• Date and time
• What the computer was doing
• Whether the error occurs under heavy disk activity

A photograph of the BSOD can be useful.

For advanced diagnosis, inspect the Windows crash dump with WinDbg and pay particular attention to the second parameter of bug check 0x7A.

Step 3 – Check Windows Event Viewer

Press:

Win + R

Enter:

eventvwr.msc

Check:

Windows Logs → System

Look around the exact time of the crash.

Pay attention to errors involving:

• Disk
• Ntfs
• storahci
• stornvme
• iaStor
• storage controllers
• WHEA
• unexpected device removal

Repeated storage-related errors immediately before a 0x7A BSOD can provide an important diagnostic clue.

Step 4 – Check Disk Health

Check the health of the system SSD/HDD using the manufacturer's diagnostic utility where available.

Depending on the drive manufacturer, diagnostics may provide:

• SMART information
• Temperature
• Remaining SSD life
• Firmware version
• Diagnostic scan
• Drive-health status

A simple SMART status of “Good” should not be treated as absolute proof that the drive is healthy. Intermittent controller, cable and NAND/media problems may require deeper diagnostics.

Step 5 – Run CHKDSK

Microsoft recommends CHKDSK for disk-related 0x7A conditions, including the bad-block status codes.

Open Command Prompt as Administrator.

Start with:

chkdsk C: /f

For a more extensive check when bad sectors/read failures are suspected:

chkdsk C: /f /r

Windows may display:

Chkdsk cannot run because the volume is in use by another process. Would you like to schedule this volume to be checked the next time the system restarts?

Type:

Y

Restart the computer.

Important

/r performs a considerably more extensive operation. On large or unhealthy disks it may take a long time.

If the drive is showing obvious signs of physical failure, securing important data should take priority over repeatedly running intensive repair scans.

Step 6 – Repair Windows Using DISM and SFC

Run:

DISM.exe /Online /Cleanup-Image /RestoreHealth

Wait for completion.

Then:

sfc /scannow

Microsoft recommends running DISM before SFC because DISM can repair the Windows component source used by System File Checker.

Possible SFC results include:

Windows Resource Protection did not find any integrity violations.

No protected system-file corruption was detected.

Windows Resource Protection found corrupt files and successfully repaired them.

Restart and monitor the computer.

Windows Resource Protection found corrupt files but was unable to fix some of them.

Additional Windows component repair or offline repair may be required.

Step 7 – Test RAM

Press:

Win + R

Enter:

mdsched.exe

Select:

Restart now and check for problems

Windows Memory Diagnostic will restart the computer and test RAM.

For intermittent problems, the computer manufacturer's hardware diagnostics or a more extensive memory diagnostic may be appropriate.

If multiple RAM modules are installed and hardware troubleshooting is necessary, a technician may test modules individually to isolate a defective DIMM or slot.

Step 8 – Inspect Storage Connections

For SATA drives:

• Reseat SATA data cable
• Reseat SATA power cable
• Replace SATA cable
• Test another SATA port where appropriate
• Inspect connectors for damage

For NVMe drives:

• Verify the drive is securely installed
• Check for excessive temperature
• Inspect the M.2 slot where appropriate
• Check SSD firmware
• Check BIOS compatibility

On laptops, internal hardware servicing should only be performed when appropriate for the device and warranty conditions.

Step 9 – Check SSD/NVMe Temperature

NVMe drives can become extremely hot under sustained workloads.

Excessive temperature may cause:

• Throttling
• Performance drops
• Controller instability
• Temporary drive disappearance in severe cases

Check whether:

• M.2 heatsink is installed correctly
• Thermal pad makes proper contact
• Airflow is adequate
• SSD temperature becomes excessive under load

Step 10 – Update Windows

Microsoft's general BSOD guidance recommends keeping Windows updated as part of troubleshooting stop errors.

Go to:

Settings → Windows Update → Check for updates

Install appropriate updates and restart.

If the BSOD began immediately after a particular driver or update, however, investigate that change rather than blindly updating every component.

Step 11 – Update Chipset and Storage Drivers

Visit the support site for your:

• Dell
• HP
• Lenovo
• ASUS
• Acer
• MSI
• Motherboard manufacturer

Install applicable:

• Chipset drivers
• Storage drivers
• Intel/AMD platform drivers
• NVMe-related updates
• BIOS/UEFI updates

For branded computers, OEM-tested drivers are often preferable when diagnosing hardware-specific problems.

Step 12 – Check BIOS Storage Configuration

Enter BIOS/UEFI and verify that the system drive is consistently detected.

Check:

• SSD/HDD detection
• NVMe detection
• SATA controller
• RAID configuration
• Boot device

Do not arbitrarily change AHCI/RAID configuration.

Changing storage-controller mode without preparing Windows can itself cause boot failure.

Step 13 – Temporarily Remove Newly Installed Hardware

Microsoft recommends considering newly added hardware when troubleshooting BSODs.

If the error began after installing:

• RAM
• SSD
• HDD
• PCIe expansion card
• Storage controller
• External storage device

temporarily remove or reverse the recent hardware change where practical and test again.

Step 14 – Boot Windows in Safe Mode

If normal Windows operation repeatedly crashes, test Safe Mode.

Safe Mode loads a reduced set of drivers and services.

If KERNEL_DATA_INPAGE_ERROR does not occur in Safe Mode, investigate:

• Recently installed drivers
• Third-party storage utilities
• Antivirus/security software
• Backup software
• Disk encryption software
• Hardware-monitoring utilities

However, absence of the BSOD in Safe Mode does not automatically prove the storage hardware is healthy because Safe Mode may generate a different workload.

Step 15 – Check Reliability Monitor

Press:

Win + R

Enter:

perfmon /rel

Reliability Monitor provides a timeline showing:

• Windows failures
• Application crashes
• Hardware errors
• Driver installations
• Windows updates

Look for changes immediately before KERNEL_DATA_INPAGE_ERROR began.

Advanced Diagnosis Using Crash Dumps

Windows normally creates crash-dump information after a BSOD.

Check:

C:\Windows\Minidump

and:

C:\Windows\MEMORY.DMP

Advanced administrators can analyze these files with Microsoft WinDbg.

For bug check 0x7A, the second parameter is especially important because Microsoft documents it as normally containing the relevant error status.

This can help distinguish among:

• Bad storage blocks
• Device disconnection
• I/O failure
• Resource shortage
• Hardware/configuration problems

Should You Replace the SSD or HDD?

Consider replacing the drive when several independent signs point toward hardware deterioration, for example:

• Manufacturer diagnostic fails
• SMART reports a critical condition
• Repeated unreadable sectors
• Repeated 0xC000009C errors
• Repeated 0xC000016A errors
• Disk repeatedly disappears
• Increasing file corruption
• Windows installation repeatedly becomes corrupted
• I/O errors continue after replacing cables
• Another known-good drive works correctly

Do not continue trusting an important business system to a drive that repeatedly produces confirmed hardware errors.

What If CHKDSK Finds Bad Sectors?

Finding bad sectors does not necessarily mean CHKDSK has permanently “fixed” the hardware.

CHKDSK can identify filesystem problems and attempt to prevent Windows from using known problematic areas, but it cannot physically repair damaged storage media.

If new bad sectors continue appearing, replace the storage device.

What If the SSD Health Shows 100%?

A reported health percentage is useful but is not a complete diagnosis.

A drive can still experience problems involving:

• Controller
• Firmware
• PCIe connection
• SATA cable
• Power delivery
• Motherboard slot
• Intermittent communication errors

Therefore, investigate the complete storage path.

Recommended Troubleshooting Order

For most systems, use this sequence:

1. Back up important data.
2. Record the BSOD and error parameters.
3. Check Event Viewer.
4. Check SSD/HDD/NVMe health.
5. Run manufacturer diagnostics.
6. Check storage cables/connections.
7. Run CHKDSK when appropriate.
8. Run DISM.
9. Run SFC.
10. Test RAM.
11. Update appropriate chipset/storage drivers.
12. Check SSD firmware.
13. Check BIOS/UEFI updates.
14. Analyze the crash dump if the problem continues.
15. Substitute known-good storage/RAM hardware if diagnostics remain inconclusive.

This approach helps avoid reinstalling Windows when the actual problem is failing hardware.

Common Mistakes to Avoid

Mistake 1: Immediately Reinstalling Windows

A fresh Windows installation will not repair a physically failing SSD, HDD, RAM module or storage controller.

Diagnose the hardware first when evidence points toward I/O failure.

Mistake 2: Assuming CHKDSK Repairs Physical Damage

CHKDSK repairs filesystem structures and handles problematic disk areas logically. It cannot physically restore damaged storage media.

Mistake 3: Ignoring the SATA Cable

A low-cost SATA cable can produce symptoms that resemble an expensive SSD/HDD failure.

Mistake 4: Disabling the Page File

Because the error mentions paging, users sometimes disable virtual memory.

This is generally not a recommended solution.

Mistake 5: Ignoring Intermittent Errors

A system that crashes only once every few days can still have a deteriorating drive, cable, controller or RAM module.

Mistake 6: Repeatedly Stressing a Suspected Failing Drive

If important files are not backed up, secure the data before running repeated intensive scans.

Frequently Asked Questions (FAQ)

1. What does KERNEL_DATA_INPAGE_ERROR mean?

It means Windows was unable to read required kernel data from the paging file into memory. Its bug-check value is 0x0000007A.

2. Is KERNEL_DATA_INPAGE_ERROR serious?

It can be. A single crash may result from a temporary problem, but repeated 0x7A crashes can indicate storage, RAM, cabling or controller problems.

3. Can a failing SSD cause KERNEL_DATA_INPAGE_ERROR?

Yes. Defective storage hardware is one of the causes specifically identified by Microsoft.

4. Can a hard drive with bad sectors cause error 0x7A?

Yes. Microsoft associates status codes 0xC000009C and 0xC000016A with bad blocks/sectors.

5. Can RAM cause KERNEL_DATA_INPAGE_ERROR?

Yes. Microsoft also identifies failing RAM as a common cause.

6. Can a SATA cable cause this BSOD?

Yes. A loose or defective storage connection can cause device communication failures. Microsoft specifically associates certain 0x7A status conditions with defective or loose cabling.

7. What does 0xC000009C mean?

It is STATUS_DEVICE_DATA_ERROR and commonly indicates bad blocks/sectors on the storage device in the context of bug check 0x7A.

8. What does 0xC000009D mean?

It is STATUS_DEVICE_NOT_CONNECTED, indicating that the controller cannot properly communicate with the storage device or that a connection/hardware problem exists.

9. What does 0xC000016A mean?

It is STATUS_DISK_OPERATION_FAILED and can indicate bad disk blocks/sectors.

10. What does 0xC0000185 mean?

It is STATUS_IO_DEVICE_ERROR, indicating an I/O communication problem. Storage hardware, connections and controllers should be investigated.

11. What does 0xC000000E mean?

It is STATUS_NO_SUCH_DEVICE and can indicate hardware failure or an incorrect drive configuration.

12. Should I run CHKDSK?

Yes, when filesystem errors or bad sectors are suspected. Microsoft specifically recommends CHKDSK for relevant 0x7A disk-error conditions.

13. Should I use chkdsk /f or chkdsk /f /r?

/f repairs filesystem errors. /r additionally searches for unreadable sectors and attempts recovery of readable information. /r is considerably more intensive and should be used thoughtfully, especially if the drive may be physically failing.

14. Will SFC fix KERNEL_DATA_INPAGE_ERROR?

SFC can repair corrupted protected Windows system files, but it cannot repair defective RAM, a failing SSD/HDD or a bad cable.

15. Should DISM be run before SFC?

Yes. Microsoft's current repair procedure recommends running:

DISM.exe /Online /Cleanup-Image /RestoreHealth

before:

sfc /scannow

 

16. Can Windows Update cause KERNEL_DATA_INPAGE_ERROR?

A driver or system change can expose compatibility problems, but do not automatically assume Windows Update is responsible. Check storage health, drivers and the crash dump.

17. Can an NVMe SSD cause this error?

Yes. NVMe drives can experience controller, firmware, thermal, PCIe or media-related failures that interrupt storage reads.

18. Can overheating cause the error?

Potentially. Excessive SSD/NVMe or system temperature can contribute to hardware instability, although temperature alone should not be assumed to be the cause without evidence.

19. Will reinstalling Windows fix error 0x7A?

Only if the cause is software corruption. Reinstallation will not fix failing storage, bad RAM, a defective cable or motherboard/controller failure.

20. Should I back up my files immediately?

If the error repeats or storage-related errors are present, yes. Backing up important data should be one of the first actions because storage failure is a possible cause.

Final Conclusion

KERNEL_DATA_INPAGE_ERROR (0x0000007A) should be treated primarily as an error requiring careful investigation of the storage-to-memory data path.

The most important components to investigate are:

SSD/HDD/NVMe → cable/connector → storage controller → paging file → RAM

Microsoft's documentation confirms that common causes include bad disk blocks, storage-device communication problems, defective storage hardware and failing RAM.

For repeated crashes, the safest troubleshooting strategy is to back up important data first, inspect the 0x7A status code and Event Viewer, test storage health, check physical connections, run appropriate disk diagnostics, test RAM, repair Windows files with DISM/SFC, and analyze the crash dump if necessary.

Most importantly, do not repeatedly reinstall Windows until storage and RAM have been ruled out. If the underlying SSD, HDD, cable or RAM is failing, a Windows reinstall may temporarily appear successful while the BSOD eventually returns.

#tags

#KERNEL_DATA_INPAGE_ERROR #KernelDataInpageError #0x0000007A #0x7A #BSOD #BlueScreen #BlueScreenOfDeath #Windows11 #Windows10 #WindowsError #WindowsBSOD #WindowsTroubleshooting #BSODFix #WindowsRepair #KernelError #StopCode #WindowsStopCode #SSD #HDD #NVMe #SSDHealth #HardDriveFailure #SSDProblem #DiskError #DiskFailure #BadSectors #DiskHealth #StorageError #StorageTroubleshooting #IOError #WindowsMemory #RAM #RAMError #MemoryDiagnostic #WindowsMemoryDiagnostic #CHKDSK #SFC #DISM #SFCScannow #RestoreHealth #PageFile #VirtualMemory #WindowsRecovery #EventViewer #WinDbg #CrashDump #WindowsMinidump #StorageDriver #ComputerRepair #WindowsSupport