- Software and digital services
- Operating system
KERNEL_DATA_INPAGE_ERROR
KERNEL_DATA_INPAGE_ERROR (0x7A) on Windows: kernel data unreadable
Risk level
High
Professional inspection is recommended.
Urgency
High
Quick answer
Windows stopped because it could not read kernel data back into memory from the paging file. Back up your files as soon as possible and let the automatic disk check finish when you restart.
Safety first
Stop and check this first
- This code can come from a drive with damaged sectors: every start and every repair attempt can make it worse. Copy your data before running long checks or resetting Windows.
- If the recovery options ask for the BitLocker recovery key, do not try random keys: look for it only in your Microsoft account (aka.ms/myrecoverykey), your work or school account, a printout or the USB drive where you saved it. Microsoft support cannot retrieve it.
Safe checks you can perform
- Immediate backup
- Disk check at restart
- Event Viewer and antivirus scan
Leave these tasks to a qualified professional
- Do not attempt this professional task: Read parameter 2 and test the drive
- Do not attempt this professional task: Maker's memory diagnostic
- Do not attempt this professional task: Internal connection check
What a technician must be able to justify
Technician visit
These are the steps they must carry out and show you. Tick them as they work: if steps are skipped, do not accept a part swap.
These are not instructions for opening or handling the equipment yourself. They are the checks that should support a technical conclusion.
Read parameter 2 and test the drive
What they doThe technician reads the parameter 2 status code from the dump and, depending on its value, runs the drive maker's diagnostic or checks cables and controller.
They must show youthe status code and the drive diagnostic report.
In writingwhether the drive passed and, if replaced, the part reference and reason.
Maker's memory diagnostic
What they doThey run the PC maker's hardware diagnostics, especially its memory test.
They must show youthe memory test result.
In writingwhich module failed, if any, and what was replaced.
Internal connection check
What they doWith the case open, they check that expansion cards are properly seated and drive cables are firm.
They must show youphotos of the connections checked.
In writingwhat they found and corrected.
Before accepting a part or repair
Nothing has been shown yet. Do not accept a part swap based on the code alone.
Follow these steps
Note: Follow the documented order. An error code identifies the affected system, but it does not prove by itself which part has failed.
Immediate backup
- Who:
- you.
- How:
- if Windows starts, copy your documents and photos now to a USB drive, another disk or OneDrive, most important first.
- Result that matters:
- having your data off the suspect drive.
- If the copy finishes:
- you can carry on checking without risking your data.
- If the copy stops with read errors:
- do not keep trying; take the PC to a technician.
- Evidence to keep:
- list of folders copied and errors shown.
Evidence: Troubleshooting Windows unexpected restarts and stop code errors · Bug Check 0x7A KERNEL_DATA_INPAGE_ERROR
Disk check at restart
- Who:
- you.
- How:
- restart and let Windows run Autochk without interrupting it; if it does not run by itself, from a Command Prompt as administrator run chkdsk /f /r on the system partition and restart.
- Result that matters:
- whether the check finds and isolates bad sectors.
- If it finds bad sectors:
- the drive is damaged; a technician should assess it with the maker's diagnostic.
- If it finds nothing:
- check memory and viruses.
- Evidence to keep:
- photo or screenshot of the check summary.
chkdsk /r can take hours; do not run it without a backup and do not turn the PC off while it works.
Evidence: Bug Check 0x7A KERNEL_DATA_INPAGE_ERROR
Event Viewer and antivirus scan
- Who:
- you.
- How:
- in Event Viewer, Windows Logs, System, look for disk errors just before the crash; then scan the PC with an up-to-date antivirus that also checks the Master Boot Record (MBR), such as Microsoft Safety Scanner.
- Result that matters:
- whether there are earlier disk errors or an infection.
- If there are disk errors:
- they strengthen the suspicion on storage.
- If the scan finds malware:
- remove it and watch whether the crash returns.
- Evidence to keep:
- screenshot of the events and the scan result.
Evidence: Stop code error or bug check troubleshooting (IT professionals) · Bug Check 0x7A KERNEL_DATA_INPAGE_ERROR
Still not solved
If the error persists, stop here. See what the technician must do and show you.
Where this code applies
A code is meaningful only inside the right product and version context.
Primary scope
- System
- Software and digital services
- Brand
- Microsoft Windows
- Product type
- Operating system
Known code variants
- 0x0000007A
- 0x7A
- KERNEL DATA INPAGE ERROR
- STOP 0x0000007A
- stop code KERNEL_DATA_INPAGE_ERROR
What it means
Microsoft defines bug check 0x0000007A as a page of kernel data from the paging file that could not be read into memory. Parameter 2 is a status code that points to the cause: 0xC000009C or 0xC000016A usually mean bad sectors, 0xC000009D a loose cable or a controller that does not see the disk, 0xC000000E a hardware fault or drive configuration problem, 0xC000009A a lack of nonpaged pool. Microsoft adds defective storage, failing RAM or a virus. Without that parameter, the code alone is not enough to blame a part.
Warnings and stop conditions
- Higheditorial warning
This code can come from a drive with damaged sectors: every start and every repair attempt can make it worse. Copy your data before running long checks or resetting Windows.
Evidence: Bug Check 0x7A KERNEL_DATA_INPAGE_ERROR
- Highsource verified
If the recovery options ask for the BitLocker recovery key, do not try random keys: look for it only in your Microsoft account (aka.ms/myrecoverykey), your work or school account, a printout or the USB drive where you saved it. Microsoft support cannot retrieve it.
Evidence: Find your BitLocker recovery key
Symptoms and causes
Probable causes · in order
- Bad sectors on the driveCommon
You can tell from status 0xC000009C or 0xC000016A in parameter 2 and because the disk check finds damaged sectors.
Evidence: Bug Check 0x7A KERNEL_DATA_INPAGE_ERROR
- Cable or controller losing the drivePossible
Status 0xC000009D means defective or loose cabling, or the controller not seeing the disk; a technician checks it.
Evidence: Bug Check 0x7A KERNEL_DATA_INPAGE_ERROR
- Failing RAMPossible
Microsoft lists it as a common cause; it is confirmed with the PC maker's memory diagnostic.
Evidence: Bug Check 0x7A KERNEL_DATA_INPAGE_ERROR
- Virus infectionLess common
Microsoft says a virus can also cause this code; it is ruled out with an up-to-date antivirus scan.
Evidence: Bug Check 0x7A KERNEL_DATA_INPAGE_ERROR
Virtual technician
Does KERNEL_DATA_INPAGE_ERROR still appear after these checks?
Answer a few questions to narrow down the likely cause and the safest next action. Guidance only - it never replaces a professional.
Sources and technical references
- 1
Troubleshooting Windows unexpected restarts and stop code errors
Microsoft · 2026 · official_doc
- 2
Bug Check 0x7A KERNEL_DATA_INPAGE_ERROR
Microsoft · 2026 · official_doc
- 3
Find your BitLocker recovery key
Microsoft · 2026 · official_doc
Was this entry useful?