The KERNEL_DATA_INPAGE_ERROR is a Windows stop error or Blue Screen of Death (BSOD) identified by bug check:

0x0000007A

Microsoft defines this bug check as a condition where Windows was unable to read a requested page of kernel data from the paging file into memory.

In practical troubleshooting, this error deserves special attention because it can indicate a problem with the computer's SSD, NVMe drive, hard disk, storage connection, RAM, storage controller, file system, or paging system.

A single occurrence does not automatically mean the SSD or hard disk is failing. However, if KERNEL_DATA_INPAGE_ERROR appears repeatedly—especially together with disk errors, freezing, slow file access, corrupted files, or SMART warnings—you should treat the storage device as a possible failure and back up important data immediately.

What Does KERNEL_DATA_INPAGE_ERROR Mean?

Windows continuously moves information between physical RAM and storage. Part of this process involves the Windows paging file, normally:

pagefile.sys

When Windows needs kernel data that is not currently available in physical memory, it may need to retrieve that data from storage.

KERNEL_DATA_INPAGE_ERROR occurs when Windows requests kernel data but cannot successfully read the required information into memory.

Microsoft specifically describes bug check 0x7A as indicating that the requested page of kernel data from the paging file could not be read into memory.

Therefore, the underlying issue often involves the path:

Storage device → Storage controller/connection → Windows storage subsystem → Paging file → RAM

A problem anywhere along this path can potentially contribute to the crash.

Common Symptoms

A computer experiencing KERNEL_DATA_INPAGE_ERROR may show:

• Blue or black Windows stop-error screen
• Stop code: KERNEL_DATA_INPAGE_ERROR
• Bug check: 0x0000007A
• Random system freezing
• Unexpected restart
• Applications suddenly becoming unresponsive
• Extremely slow disk activity
• Windows taking unusually long to boot
• Files becoming inaccessible
• Disk-related Event Viewer errors
• SSD/HDD disappearing temporarily
• Clicking or unusual noises from an HDD
• Windows corruption after repeated crashes
• BSOD during heavy disk activity
• BSOD while opening large applications or files

On newer Windows 11 versions, the appearance of the stop-error screen can differ from the traditional blue screen, but the stop code remains important for diagnosis.

Most Common Causes of KERNEL_DATA_INPAGE_ERROR

1. Failing SSD, NVMe SSD or Hard Disk

Storage failure is one of the most important possibilities to investigate.

Possible problems include:

• NAND degradation on an SSD
• HDD bad sectors
• SSD controller failure
• NVMe errors
• Read failures
• Internal drive firmware problems
• Uncorrectable storage errors
• Intermittently disconnecting drives

If Windows cannot retrieve paging information from the storage device, it may generate the 0x7A bug check.

2. Bad Sectors or Unreadable Disk Areas

Microsoft identifies specific status codes associated with bad blocks.

For example:

0xC000009C – STATUS_DEVICE_DATA_ERROR

and

0xC000016A – STATUS_DISK_OPERATION_FAILED

can indicate bad blocks/sectors on the disk.

Bad sectors are particularly concerning on older mechanical hard drives.

An SSD handles defective flash differently internally, but repeated read errors or SMART warnings on an SSD should still be investigated seriously.

3. Loose or Defective SATA Cable

On desktop computers using SATA SSDs or HDDs, the problem may not actually be the disk.

Possible causes include:

• Loose SATA data cable
• Damaged SATA cable
• Poor motherboard SATA connector
• Loose SATA power connector
• Faulty power supply connector

Microsoft associates status 0xC000009D (STATUS_DEVICE_NOT_CONNECTED) with situations including defective or loose cabling or cases where the storage controller cannot see the disk.

Try another known-good SATA cable and, where appropriate, another motherboard SATA port.

4. Defective RAM

Faulty RAM can also cause KERNEL_DATA_INPAGE_ERROR.

Possible memory problems include:

• Defective RAM module
• Unstable XMP/EXPO profile
• Incorrect memory timings
• RAM overclocking
• Poor DIMM contact
• Faulty motherboard memory slot
• Mixed incompatible memory modules

Microsoft also identifies failing RAM as a possible cause of bug check 0x7A.

5. Corrupted Paging File

The Windows paging file may become corrupted because of:

• Improper shutdown
• Disk corruption
• Storage errors
• File-system problems
• Unexpected power failure

Since KERNEL_DATA_INPAGE_ERROR directly concerns reading kernel information associated with paging, pagefile and underlying storage problems should be investigated.

6. Storage Controller or Driver Problems

Storage communication passes through controllers and drivers such as:

• SATA/AHCI controller
• NVMe controller
• RAID controller
• Intel Rapid Storage Technology
• AMD storage/chipset components
• OEM storage drivers

A faulty, incompatible or unstable driver can interfere with storage I/O.

This possibility becomes particularly relevant if the BSOD started immediately after:

• Windows Update
• BIOS update
• Storage-driver update
• SSD replacement
• Cloning Windows to another disk
• Changing SATA/AHCI/RAID configuration

7. File-System Corruption

NTFS or other file-system corruption may interfere with Windows reading required information.

Possible causes include:

• Sudden power loss
• Forced shutdowns
• Storage failure
• System crashes
• Improper disk cloning
• Bad sectors

Important 0x7A Status Codes

The second bug-check parameter can be particularly useful when analyzing a KERNEL_DATA_INPAGE_ERROR memory dump.

Some important codes documented by Microsoft include:

These codes can substantially narrow the investigation.

How to Fix KERNEL_DATA_INPAGE_ERROR

Step 1: Back Up Important Data First

If KERNEL_DATA_INPAGE_ERROR occurs repeatedly, do not begin with aggressive repair operations on an obviously failing drive before protecting important data.

Back up:

• Documents
• Desktop files
• Photos
• Accounting data
• Email archives
• Browser data
• Application databases
• Tally/BUSY/company data
• Project files
• Any other critical information

If the SSD/HDD is making unusual noises, repeatedly disappearing, reporting SMART failure, or becoming extremely slow, prioritize data recovery or cloning rather than repeatedly stressing the drive.

Step 2: Check SSD/HDD Health

Check the health information reported by the drive.

Look for indications such as:

• Critical Warning
• Media/Data Integrity Errors
• Uncorrectable errors
• Reallocated sectors
• Pending sectors
• Read errors
• Interface/CRC errors
• Abnormal temperature
• SMART warning
• Very low remaining SSD life

For an NVMe SSD, manufacturer diagnostic software can often provide additional NVMe health information.

Examples include tools supplied by SSD or computer manufacturers.

If the manufacturer reports a critical drive-health failure, replacing the storage device is generally safer than trying to "repair Windows" indefinitely.

Step 3: Run CHKDSK

Open Command Prompt as Administrator.

A basic online NTFS scan can be started with:

chkdsk C: /scan

For file-system repair:

chkdsk C: /f

For a deeper scan that also locates bad sectors and attempts to recover readable information:

chkdsk C: /f /r

If C: is currently in use, Windows may ask whether you want the volume checked during the next restart.

Press:

Y

and restart the computer.

Microsoft documents that /f fixes disk errors, while /r locates bad sectors and attempts to recover readable information; /r also includes the functionality of /f.

Important SSD Note

Do not repeatedly run full /r scans on an SSD as routine maintenance.

Microsoft notes that occasional use is not a significant concern, but repeated full-surface scans can unnecessarily add write/erase activity.

Use a deep scan when troubleshooting justifies it rather than running it frequently without reason.

Step 4: Repair Windows System Files

Corrupted Windows components may contribute to instability.

Open Command Prompt as Administrator and run:

DISM.exe /Online /Cleanup-Image /RestoreHealth

Wait for the process to complete.

Then run:

sfc /scannow

Microsoft recommends DISM followed by System File Checker when repairing corrupted Windows components and system files.

Restart Windows after completion.

Step 5: Test the RAM

Search Windows for:

Windows Memory Diagnostic

Select:

Restart now and check for problems

Allow the test to complete.

For intermittent errors, a longer manufacturer or dedicated bootable memory diagnostic may provide more comprehensive testing.

If multiple RAM modules are installed and the computer continues crashing, a technician can also test modules individually.

Also Check

If XMP/EXPO or memory overclocking is enabled, temporarily return memory settings to manufacturer/default settings.

If the BSOD disappears, memory instability rather than Windows itself may have been responsible.

Step 6: Check SATA and Power Connections

This step mainly applies to SATA HDDs and SATA SSDs.

Shut the PC down completely and disconnect power before opening the computer.

Check:

SATA Data Cable

SSD/HDD → Motherboard

and:

SATA Power Cable

Power Supply → SSD/HDD

If possible:

1. Reconnect both cables.
2. Replace the SATA data cable.
3. Try another motherboard SATA port.
4. Check the power connector.
5. Inspect connectors for damage.

This is particularly important if the dump reports:

0xC000009D

or other device-disconnection/I/O errors.

Step 7: Check Windows Event Viewer

Press:

Win + R

Enter:

eventvwr.msc

Navigate to:

Windows Logs → System

Examine events immediately before the BSOD.

Pay special attention to storage-related sources such as:

• Disk
• Ntfs
• storahci
• stornvme
• volmgr
• WHEA-Logger

Repeated storage errors immediately before every crash are valuable diagnostic evidence.

Do not diagnose the drive from a single Event ID alone. Correlate the events with SMART/drive diagnostics, dump information and the timing of the crashes.

Step 8: Check the Windows Page File

Normally Windows should manage the paging file automatically.

Open:

System Properties → Advanced → Performance Settings → Advanced → Virtual Memory

For most systems, enable:

Automatically manage paging file size for all drives

Restart the computer after making changes.

Avoid disabling the page file merely as an attempted solution to KERNEL_DATA_INPAGE_ERROR. Windows and applications may depend on virtual memory, and disabling it can introduce additional problems.

Step 9: Update Storage and Chipset Drivers

Check for appropriate drivers for:

• Motherboard chipset
• SATA/AHCI controller
• NVMe controller
• RAID controller
• Intel RST, if applicable
• AMD chipset/storage components

For branded laptops and desktops, use drivers intended for the exact system model where possible.

Avoid installing random "driver updater" utilities simply because a BSOD occurred.

Step 10: Check SSD Firmware and BIOS/UEFI

Firmware problems can sometimes contribute to storage instability.

Check the computer or storage manufacturer's support resources for:

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

Before updating firmware, ensure that important data is backed up and follow the manufacturer's instructions carefully.

Step 11: Undo Recent Hardware Changes

If the error started after installing:

• New RAM
• New SSD
• NVMe drive
• Additional hard disk
• PCIe storage controller
• New motherboard
• New SATA cable

temporarily reverse or verify the change.

Microsoft's general BSOD troubleshooting guidance recommends removing newly added hardware when crashes begin after a hardware change.

Step 12: Try Safe Mode

If Windows repeatedly crashes during normal startup, try Safe Mode.

Safe Mode loads a reduced set of drivers and services.

If the computer remains stable in Safe Mode but crashes during normal operation, investigate:

• Third-party drivers
• Storage software
• Security software
• Recently installed applications
• Startup services
• Recent driver updates

However, Safe Mode stability does not conclusively prove that the storage hardware is healthy.

Step 13: Analyze the Memory Dump

For repeated KERNEL_DATA_INPAGE_ERROR crashes, dump analysis can provide much stronger evidence than repeatedly trying generic fixes.

Windows crash dumps may be stored in:

C:\Windows\Minidump

or:

C:\Windows\MEMORY.DMP

Advanced technicians can analyze them using Microsoft WinDbg.

For bug check 0x7A, pay particular attention to the bug-check parameters and especially the I/O status/error status, because Microsoft documents several status values that directly indicate likely storage, connection or resource problems.

If Windows Does Not Boot

If KERNEL_DATA_INPAGE_ERROR prevents normal startup, access the Windows Recovery Environment (WinRE).

Depending on the system, you may be able to reach:

Troubleshoot → Advanced options

Available recovery options can include:

• Startup Repair
• Startup Settings
• System Restore
• Uninstall Updates
• Command Prompt

From recovery Command Prompt, you can investigate the Windows partition and run an appropriate CHKDSK operation.

Remember that the Windows partition's drive letter may be different inside the recovery environment.

HDD vs SSD: What Should You Suspect?

Mechanical HDD

On an HDD, KERNEL_DATA_INPAGE_ERROR combined with any of the following is especially concerning:

• Clicking noises
• Bad sectors
• Extremely slow reads
• SMART warnings
• Reallocated/pending sectors
• Disk Event Viewer errors
• File corruption

Back up the data and consider replacing the drive.

SATA SSD

Investigate:

• SMART/health information
• SATA data cable
• SATA power cable
• SSD firmware
• Controller errors
• Remaining SSD health
• File-system errors

NVMe SSD

Investigate:

• NVMe health information
• Firmware
• Temperature
• Motherboard BIOS
• Chipset drivers
• M.2 seating
• PCIe/storage errors
• Manufacturer diagnostics

Should You Replace the SSD/HDD?

Do not replace a drive based only on one BSOD.

Replacement becomes much more justified when multiple indicators agree, such as:

KERNEL_DATA_INPAGE_ERROR + SMART failure + repeated I/O errors + manufacturer diagnostic failure

or:

0x7A + bad sectors + file corruption + repeated crashes

At that point, continuing to repair Windows without addressing the underlying drive may waste time and put data at risk.

Recommended Troubleshooting Order

For a system that is otherwise bootable, a practical order is:

1. Back up important data

↓

2. Check SSD/HDD health and manufacturer diagnostics

↓

3. Review Event Viewer for storage errors

↓

4. Check physical SATA/power connections where applicable

↓

5. Run CHKDSK as appropriate

↓

6. Run DISM and SFC

↓

7. Test RAM

↓

8. Check storage/chipset drivers

↓

9. Check BIOS and SSD firmware

↓

10. Analyze crash dumps if the problem continues

This approach helps avoid spending hours repairing Windows when the actual problem is a failing storage device.

What Not to Do

Avoid these common troubleshooting mistakes.

Do not immediately format Windows

Reinstalling Windows will not repair a physically failing SSD, HDD, RAM module or SATA cable.

Do not ignore repeated SMART warnings

A failing drive should be treated as a data-protection issue.

Do not repeatedly run repair scans on a severely failing disk

If the drive contains important data and is physically deteriorating, prioritize backup/recovery.

Do not randomly change AHCI/RAID settings in BIOS

Changing storage mode without understanding the current Windows configuration can make Windows unbootable.

Do not install random driver-updater programs

Use Windows Update or drivers from the computer, motherboard, chipset or storage manufacturer.

Frequently Asked Questions (FAQ)

1. What is KERNEL_DATA_INPAGE_ERROR?

KERNEL_DATA_INPAGE_ERROR is Windows bug check 0x0000007A. It means Windows could not read a requested page of kernel data from the paging file into memory.

2. Is KERNEL_DATA_INPAGE_ERROR a hardware problem?

It can be. Common possibilities include storage hardware, RAM, cabling, storage controllers and other hardware issues. Software, driver and file-system problems should also be investigated.

3. Does KERNEL_DATA_INPAGE_ERROR mean my SSD is failing?

Not necessarily. One occurrence is insufficient to conclude that an SSD is defective. Repeated crashes combined with SMART errors, manufacturer diagnostic failures or storage I/O errors make drive failure much more likely.

4. Can a bad HDD cause KERNEL_DATA_INPAGE_ERROR?

Yes. Microsoft specifically identifies bad disk blocks as a possible explanation for status codes such as 0xC000009C and 0xC000016A.

5. Can bad RAM cause error 0x7A?

Yes. Microsoft lists failing RAM as another possible cause.

6. Can a SATA cable cause this BSOD?

Yes. Loose or defective storage cabling can produce device-connection or I/O failures and should be checked on SATA-based systems.

7. What does 0xC000009C mean?

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

8. What does 0xC000009D mean?

It is STATUS_DEVICE_NOT_CONNECTED. Microsoft notes possible defective/loose cabling or a situation where the controller cannot see the storage device.

9. What does 0xC000016A mean?

It is STATUS_DISK_OPERATION_FAILED, which can indicate bad blocks on the disk.

10. What does 0xC0000185 mean?

It is STATUS_IO_DEVICE_ERROR. It points the investigation toward an I/O communication or hardware-related problem.

11. Should I run CHKDSK /f /r?

It can be appropriate when investigating disk errors. /f repairs file-system errors, while /r locates bad sectors and attempts to recover readable information.

Back up important data first if you suspect physical drive failure.

12. Is CHKDSK /r safe for SSDs?

Occasional diagnostic use is generally acceptable, but Microsoft notes that repeatedly performing full-surface scans on SSDs can unnecessarily add write/erase activity.

13. Will SFC fix KERNEL_DATA_INPAGE_ERROR?

SFC can repair corrupted protected Windows system files, but it cannot repair physically defective RAM or storage hardware.

14. Should I run DISM before SFC?

Microsoft's current repair procedure uses:

DISM.exe /Online /Cleanup-Image /RestoreHealth

followed by:

sfc /scannow

15. Can an NVMe SSD cause KERNEL_DATA_INPAGE_ERROR?

Yes. NVMe drives are storage devices and failures involving the drive, firmware, controller, motherboard connection or storage path can potentially lead to paging-related I/O failures.

16. Can overheating cause this error?

Storage or system instability caused by excessive temperatures can contribute to crashes. Check SSD/NVMe and overall system temperatures if the crashes happen under sustained load.

17. Can Windows Update cause KERNEL_DATA_INPAGE_ERROR?

A driver or software change can sometimes expose or introduce instability, but do not automatically blame Windows Update. Check storage health and the crash's status code first.

18. Why does the error happen only occasionally?

Intermittent failures can occur because of unstable RAM, marginal storage sectors, loose connections, thermal problems or intermittent storage-controller errors.

19. Should I reinstall Windows?

Usually not as the first troubleshooting step. First verify storage health, RAM, connections, file system and drivers. Reinstalling Windows cannot fix physically defective hardware.

20. When should I replace the drive?

Strong reasons include manufacturer diagnostic failure, critical SMART warnings, repeated uncorrectable errors, repeated bad-sector problems, frequent I/O errors, or persistent 0x7A crashes clearly linked to the storage device.

Conclusion

KERNEL_DATA_INPAGE_ERROR (0x0000007A) should not be treated as just another random Windows blue screen. It specifically indicates that Windows was unable to read required kernel data from the paging file into memory.

The most important areas to investigate are SSD/HDD/NVMe health, storage I/O errors, bad sectors, SATA connections, RAM, storage drivers, file-system integrity and the paging environment.

If the error occurs repeatedly, protect the user's data first. Then diagnose the storage subsystem before spending significant time on Windows repairs.

A particularly useful rule for technicians is:

One 0x7A crash = investigate.

Repeated 0x7A crashes + disk/I/O errors = prioritize storage diagnostics and backup.

0x7A + SMART/diagnostic failure = strongly consider drive replacement.

Microsoft's official technical reference for this stop code is available at Microsoft Learn – Bug Check 0x7A KERNEL_DATA_INPAGE_ERROR.

#Tags: #KERNEL_DATA_INPAGE_ERROR #KernelDataInpageError #0x0000007A #0x7A #BSOD #BlueScreen #WindowsBSOD #Windows11 #Windows10 #WindowsError #StopCode #WindowsTroubleshooting #BSODFix #WindowsRepair #SSD #SSDHealth #SSDFailure #NVMe #NVMeSSD #NVMeError #HardDisk #HDD #HardDriveFailure #BadSectors #DiskError #DiskFailure #StorageError #StorageTroubleshooting #DiskIOError #PageFile #PagingFile #VirtualMemory #RAM #RAMError #MemoryError #WindowsMemoryDiagnostic #CHKDSK #CHKDSKRepair #SFC #SFCScannow #DISM #SystemFileChecker #EventViewer #SMART #SMARTStatus #SATA #SATACable #StorageDriver #WindowsRecovery #ComputerRepair