Stop code 0x0000007A: KERNEL_DATA_INPAGE_ERROR
Updated
Cleared for publishing after the automated checks on .
What the code means
This bug check indicates that the requested page of kernel data from the paging file couldn't be read into memory. (Bug check 0x7A: KERNEL_DATA_INPAGE_ERROR)
Code facts for 0x0000007A
| Code as Windows shows it | 0x0000007A |
|---|---|
| Type | Stop code (bug check) |
| Symbolic name | KERNEL_DATA_INPAGE_ERROR |
| Hexadecimal, 8 digits | 0x0000007A |
| Decimal (unsigned) | 122 |
| Decimal (signed 32-bit) | 122 |
| Group | Stop codes |
Read with care
- A stop (bug check) code is not a Win32 or HRESULT code. Read as Win32 error 122 it would be ERROR_INSUFFICIENT_BUFFER, which is unrelated. (Bug check code reference, System Error Codes (0-499))
Code facts: Bug check 0x7A: KERNEL_DATA_INPAGE_ERROR (Microsoft Learn, CC BY 4.0), checked Nov 14, 2026.
Code facts: Bug check code reference (Microsoft Learn, CC BY 4.0), checked Nov 14, 2026.
Where this error shows up
This code shows up on a blue screen, after Windows stops and restarts.
Applies to
Stop-code support page: Windows 11 and Windows 10 (as listed at the top of the Microsoft page). Bug check page: Windows (reference for programmers, no version list).
These steps come from a Microsoft page written for advanced users.
Try these first
These steps carry no risk flag in the data. They keep the order of the full list below, which is not reordered. A step without a flag is not a promise that it is safe for your computer.
3 steps to try, in order
Steps are grouped by the Microsoft page they come from. The page lists only what those pages give; other causes of 0x0000007A are not covered. 1 step is flagged.
If this page and Microsoft's page differ, follow Microsoft's page.
Microsoft also gives general steps that cover this code: see the general steps in the stop codes group. Each block there says which codes its Microsoft page gives the steps for.
From: Bug check 0x7A: KERNEL_DATA_INPAGE_ERROR
Source: Bug check 0x7A: KERNEL_DATA_INPAGE_ERROR (Microsoft Learn), checked Nov 14, 2026. © Microsoft, licensed under CC BY 4.0. Steps shortened and reworded by PC Driver Update.
From Microsoft's bug check page, which says it is written for programmers. Only its basic, non-debugger troubleshooting lines are used.
Bad blocks on the disk
Changes disksStatus 0xC000009C or 0xC000016A usually means a bad block (sector). If you can restart the computer, Autochk runs automatically and tries to map out the bad sector.
If Autochk doesn't scan the disk, run Chkdsk /f /r on the system partition yourself; the scan starts after a restart.
Microsoft advises: Back up your personal files before you try these fixes. (Back up and restore with Windows Backup)
Failing RAM
Run the hardware diagnostics supplied by the system manufacturer, especially the memory scanner (see the computer's owner's manual).
Hardware diagnostics and adapter cards
Run any available diagnostic testing software for the PC. On PCs with card slots, check that all adapter cards are properly seated and their contacts are clean.
Stop and get help
If these steps do not fix the problem, or you are not sure about a step, stop and get help from Microsoft Support or from the maker of your PC. Stop at once if the data on this computer is at risk: back up your files first, or ask a professional before you go on.
Dates and review
| Automated checks | first check: ; fourth check: |
|---|---|
| Microsoft pages read |
|
| Review status | Cleared for publishing after the automated checks on . |