KERNEL_DATA_INPAGE_ERROR is Windows stop code 0x0000007A (0x7A). Microsoft's reference says it indicates "that the requested page of kernel data from the paging file couldn't be read into memory." Of the codes on this site, it is the one where Microsoft's page speaks most directly to disks, cables and RAM.
The key to reading it is parameter 2, the error status. Microsoft names six common status codes, and each points to a different kind of problem.
This page is built from the Microsoft Learn article "Bug Check 0x7A: KERNEL_DATA_INPAGE_ERROR" and, where noted, Microsoft's general page on analysing blue screen data, both read on 13 October 2026 and checked against the Microsoft Docs source files. Microsoft marks the 0x7A page as written for programmers and directs customers to https://www.windows.com/stopcode. Anything taken from the general page rather than the 0x7A page is labelled as such.
What do the parameters say?
The four parameters have three possible meanings, depending on the first parameter. As printed in Microsoft's reference:
| When | Parameter 1 | Parameter 2 | Parameter 3 | Parameter 4 |
|---|---|---|---|---|
| First parameter is 1, 2 or 3 and third is 0 | The lock type that was held (1, 2 or 3) | The error status (usually an I/O status code) | If lock type is 1: the current process; if 2 or 3: 0 | The virtual address that couldn't be paged into memory |
| First parameter is 3 or 4 and third is not 0 | The lock type that was held (3 or 4) | The error status (typically an I/O status code) | Address of the InPageSupport structure | The faulting address |
| Otherwise | Address of the page table entry (PTE) | The error status (usually an I/O status code) | The PTE contents | The faulting address |
In all three layouts, parameter 2 is the error status, an NTSTATUS value. That is the figure to copy from the System Log.
What do the six status codes mean?
Microsoft says you can frequently determine the cause from the error status in parameter 2, and lists the most common ones:
| Status code | Name | What Microsoft says it indicates |
|---|---|---|
| 0xC000009A | STATUS_INSUFFICIENT_RESOURCES | A lack of non-paged pool resources |
| 0xC000009C | STATUS_DEVICE_DATA_ERROR | Typically bad blocks (sectors) on the hard disk |
| 0xC000009D | STATUS_DEVICE_NOT_CONNECTED | Defective or loose cabling, termination, or that the controller doesn't see the hard disk |
| 0xC000016A | STATUS_DISK_OPERATION_FAILED | Bad blocks (sectors) on the hard disk |
| 0xC0000185 | STATUS_IO_DEVICE_ERROR | Improper termination or defective cabling on SCSI devices, or two devices trying to use the same IRQ |
| 0xC000000E | STATUS_NO_SUCH_DEVICE | A hardware failure or an incorrect drive configuration; with older PATA (IDE) drives, an incorrect master/subordinate configuration |
Microsoft adds that these are the most common ones with specific causes and points to the Ntstatus.h file in the Windows Driver Kit for others. Two further common causes are named without a status code: defective storage hardware or failing RAM, and a virus infection.
What does Microsoft say to do about each cause?
The Resolution section gives a separate paragraph for each, which is rare among bug check pages.
| Cause | What Microsoft says to do |
|---|---|
| Bad block (0xC000009C or 0xC000016A) | If you can restart, Autochk runs automatically and tries to map the bad sector. If it doesn't, run Chkdsk /f /r on the system partition and restart before the scan begins. If the computer won't start, use the Recovery Console and run Chkdsk /r |
| Failing RAM | Run the hardware diagnostics the manufacturer supplies, especially the memory scanner |
| Defective hardware (0xC0000185 with an older SCSI disk) | Check the disk cabling and the SCSI termination |
| Virus infection | Scan with up-to-date commercial virus-scanning software that examines the Master Boot Record |
Notice that two of the four paragraphs are about older hardware: SCSI disks and PATA drives. The page was written for a long line of Windows versions, and the status-code table keeps those entries. If you use an SSD or NVMe drive, the bad-block and memory advice still applies as written, while the SCSI and PATA lines will not.
What else does Microsoft list?
A closing group of checks applies to any 0x7A. Check the System Event Viewer for error messages, in particular those right before the bug check. Make sure the latest Windows updates are installed. Locate and run any diagnostic software for the PC, because a crack, a scratched trace or a defective component on the motherboard can cause this bug check. For PCs with card slots, check that adapter cards are properly seated, and clean the contacts with an ink eraser or an electrical contact treatment.
The page also lists KERNEL_STACK_INPAGE_ERROR (0x77) as a related bug check in its See also section.
What Microsoft tells non-programmers to do
For people who cannot use a debugger, the Resolution section is already written in plain steps. In Microsoft's order:
- Read parameter 2 (the error status) and match it to the table above.
- For a bad block, let Autochk run after restart or run Chkdsk /f /r on the system partition; use the Recovery Console with Chkdsk /r if the computer won't start.
- For failing RAM, run the manufacturer's hardware diagnostics, especially the memory scanner.
- For defective hardware with an older SCSI disk, check cabling and termination.
- For a virus, scan with up-to-date software that examines the Master Boot Record.
- Check Event Viewer, install the latest Windows updates, run PC diagnostics, and reseat and clean adapter cards.
Microsoft does not rank these. The status code in parameter 2 is what tells you which one to start with.
Checklist before changing anything
- The four parameters, especially parameter 2, from the System Log
- Whether the disk reports bad sectors or the system partition passes Chkdsk
- Result of the manufacturer's memory scanner
- Cables, connectors and adapter cards seated and clean (where the hardware has them)
- Whether the latest Windows updates are installed
How to work through a 0x7A blue screen
- Copy parameter 2 and match it to the status-code table
- Run Chkdsk on the system partition if it points to bad blocks
- Run the manufacturer's memory scanner
- Check cables, cards and a virus scan, then install Windows updates
Registry edits and paid tools. Microsoft's page does not mention them, so neither does this one.
What if the status code is not one of the six?
Microsoft calls the six listed values "the most common ones that have specific causes", which leaves the rest open. For other status codes returned by a specific version of Windows, the page points to the Ntstatus.h file in the Windows Driver Kit. It also links, as a third party and not as its own documentation, to an OSR document that maps NTSTATUS values to Win32 error codes. Both are lookups, not fixes: they tell you what the number in parameter 2 is called, and the cause still has to come from the name. A status code that is not in the six has no Microsoft-stated cause on this page, so this page does not supply one either.
Every stop code covered here is listed in our Windows blue screen stop code index.
Sources and how to check
- Microsoft Learn, "Bug Check 0x7A: KERNEL_DATA_INPAGE_ERROR" — https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x7a--kernel-data-inpage-error. Source file in the MicrosoftDocs/windows-driver-docs repository.
- Microsoft Learn, "Analyze bug check (stop code error) data" — https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/blue-screen-data (general guide).
- Bug check code reference, Microsoft Learn: https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-code-reference2
- Troubleshoot blue screen errors (for regular users): https://www.windows.com/stopcode
- Licence and credit: Microsoft Learn documentation is published under CC BY 4.0. This page selects, rewords and reorders it, adds a plain-language reading, and is not endorsed by Microsoft. The original is linked above.
- Checked as of 13 October 2026.
Questions readers ask about KERNEL_DATA_INPAGE_ERROR Blue Screen 0x7A
What is stop code 0x7A?
It is KERNEL_DATA_INPAGE_ERROR (0x0000007A). Microsoft says the requested page of kernel data from the paging file couldn't be read into memory.
What does STATUS_DEVICE_DATA_ERROR (0xC000009C) point to?
Microsoft says it typically indicates bad blocks (sectors) on the hard disk.
How does Microsoft say to check for bad blocks?
Let Autochk run after a restart, or run Chkdsk /f /r on the system partition; if the computer won't start, use the Recovery Console and Chkdsk /r.
Can failing RAM cause 0x7A?
Yes. Microsoft names failing RAM and defective storage hardware as common causes and says to run the manufacturer's diagnostics, especially the memory scanner.
Can a virus cause it?
Microsoft says a virus infection can cause this bug check and to scan with software that examines the Master Boot Record.