How to Fix KERNEL_DATA_INPAGE_ERROR BSOD (0x0000007A)
What error 0x0000007A means
Windows does not keep everything in RAM at once. When memory gets full, it moves pages of data out to a paging file on your drive, and reads them back in when they are needed again. KERNEL_DATA_INPAGE_ERROR (stop code 0x0000007A) fires when one of those reads fails: the kernel asked the disk for a page of its own data, and the page never arrived intact. The blue screen is Windows stopping before it can run on corrupted or missing kernel data.
That failure points in two directions at once, which is why this error confuses people. The page lives on disk, so a bad sector, a failing drive, a loose SATA cable, or a broken storage driver can all block the read. But the page lands in RAM, so a defective memory stick can corrupt it on arrival and produce the same stop code. Corrupted system files and a paging file that is too small or badly configured can also trigger it. The fix order below respects that reality: protect your data first, check the disk, then check the memory and the software around both.
One warning worth taking seriously: unlike a purely software blue screen, this one is frequently the first symptom of a drive that is starting to die. Treat the backup in step 1 as non-negotiable, not optional. If the drive is the cause, every day you run without a backup is a gamble with your files.
Common causes
- Bad sectors in the paging file: damaged areas of the disk corrupt exactly the pages Windows needs to read back into memory.
- A failing hard drive or SSD: a drive whose controller or media is deteriorating cannot reliably return the data the kernel asks for.
- Loose or damaged drive cables: a SATA cable that is not seated properly, or an NVMe drive that has worked loose, drops reads intermittently.
- Faulty RAM: a defective memory stick corrupts pages as they are read in, so the kernel sees a failed page even when the disk is fine.
- Bad storage drivers or a misconfigured paging file: outdated controller drivers and a paging file that is too small, fragmented, or on damaged sectors both block clean page reads.
How to fix error 0x0000007A — step by step
Work through these fixes in order. The backup comes first for a reason: if the drive is failing, the repairs themselves are the riskiest thing you will do to it.
- Back up your files before anything else. If Windows still boots, even briefly, copy your important files to an external drive or cloud storage right away, before running any repair that writes to the disk. This blue screen often points at a drive that is starting to fail, and every extra boot or scan is another chance for it to get worse. If the PC will not stay on long enough to copy files, boot into Safe Mode instead: interrupt the boot three times in a row to reach Recovery, then go to Troubleshoot > Advanced options > Startup Settings > Restart, and press 4 for Safe Mode. Do not skip this step — a backup turns a possible drive failure from a disaster into an inconvenience.
- Run CHKDSK to find and repair bad sectors. Open an admin Terminal by right-clicking Start and choosing Terminal (Admin), then run
chkdsk C: /f /rand type Y when prompted. Restart the PC so the check can run before Windows loads, and let it finish completely — on a large drive this can take an hour or more. CHKDSK finds bad sectors, tries to recover the data on them, and marks them so Windows stops using them. If it reports bad sectors and the crashes stop, the drive bought you some time, but keep the backup current: bad sectors tend to spread, and a drive that has started developing them should be treated as living on borrowed time. - Test your RAM with Windows Memory Diagnostic. Press Win + R, type
mdsched.exe, and choose Restart now and check for problems. Let the test run to completion without skipping it, since a partial test can miss a bad memory cell. If it reports any error, a RAM stick is defective and should be replaced — faulty RAM corrupts the pages Windows is trying to read in, which produces exactly this stop code. If you have more than one stick, test them one at a time afterwards to find the bad one: power off, unplug the PC, leave a single stick installed in the slot your motherboard manual recommends, and boot with each stick alone. The stick that crashes on its own is the one to replace. - Repair system files with SFC and DISM. Open an admin Terminal (right-click Start > Terminal (Admin)). Run
sfc /scannowfirst and let it finish — it repairs protected Windows files, including the storage and memory components involved in paging. Then runDISM /Online /Cleanup-Image /RestoreHealth, which repairs the component store that SFC draws on. If SFC reported corruption it could not fix, run it once more after DISM completes. Restart the PC and use it normally for a day or two: if the crashes were caused by corrupted system files rather than hardware, they should now be gone. - Update storage drivers and reset the paging file to automatic. Press Win + X and open Device Manager, then expand Storage controllers and Disk drives. Right-click each storage controller, choose Update driver, and then Search automatically for drivers — but also check your motherboard or PC maker's support page for the latest chipset and storage controller drivers, since the manufacturer's versions are newer and more reliable than the generic ones Windows Update offers. Next, fix the paging file: press Win + R, type
sysdm.cpl, go to the Advanced tab, click Settings under Performance, open the Advanced tab there, and click Change under Virtual memory. Tick Automatically manage paging file size for all drives, click Set, then OK, and restart. A paging file that is too small, fragmented, or sitting on damaged sectors is a direct trigger for this error. - Check the drive connection and the drive's health, then replace it if it is failing. If the software steps have not fixed it, the problem is very likely hardware. On a desktop, power off, unplug the PC, and reseat the drive: unplug the SATA data and power cables (or remove and refit an NVMe drive), check for bent pins or a damaged cable, and try a different SATA cable and port if you have one. Then check the drive's health: open an admin Terminal and run
wmic diskdrive get status— a result other than OK means the drive is reporting failure. If CHKDSK keeps finding new bad sectors, the drive status is not OK, or the crashes continue after reseating, replace the drive and restore from the backup you made in step 1. Continuing to use a failing drive risks losing data that no repair can recover.
Did this fix it? Quick checklist
- Important files backed up to an external drive or cloud storage
- CHKDSK completed with no new bad sectors appearing on repeat scans
- Windows Memory Diagnostic completed with zero errors
- SFC and DISM completed without unrepairable corruption, and the paging file is set to automatic
If crashes continue after all six steps, the drive is the prime suspect even if it still seems to work: replace it before it fails outright, and restore from your backup. A clean Windows install on a new drive that still crashes points instead at RAM, the motherboard storage controller, or cabling — work through those one at a time rather than reinstalling repeatedly on the same suspect hardware.
Frequently asked questions
What does KERNEL_DATA_INPAGE_ERROR (0x0000007A) mean?
It means Windows tried to read a page of kernel data from the paging file on disk into memory, and the read failed. The usual reasons are bad sectors in the paging file, a failing hard drive or SSD, a loose or damaged drive cable, faulty RAM, a bad storage controller driver, or corrupted system files. The name is literal: a page of data that should have come in from disk did not arrive.
Does 0x0000007A always mean my hard drive is dying?
No, but a dying drive is the most common cause, so it should be ruled out first. Faulty RAM, a loose SATA cable, a bad storage driver, and a misconfigured paging file all produce the same blue screen. That is why the fix order starts with a backup and a CHKDSK scan, then tests RAM and drivers before concluding the drive itself has to be replaced.
Can faulty RAM cause KERNEL_DATA_INPAGE_ERROR?
Yes. When Windows reads a page into memory, a defective RAM cell can corrupt it on arrival, and the kernel reports the failed page read as 0x0000007A. Running Windows Memory Diagnostic (mdsched.exe) catches most bad sticks, and testing one stick at a time finds the exact one to replace if you have several installed.
Will CHKDSK delete my files?
CHKDSK does not delete healthy files, but it can make files stored on bad sectors unreadable, because the data on a physically damaged sector may already be gone. That is why the first step is to back up your files before running it. The risk of running CHKDSK is far smaller than the risk of continuing to use a drive with bad sectors without a backup.
What should I do if 0x0000007A keeps coming back after all the fixes?
Treat the drive as failing: replace it and restore from your backup, even if it still mostly works. A drive that keeps developing bad sectors will only get worse, and the next crash could take your files with it. If a brand-new drive and a clean Windows install still produce the error, the fault is likely in the RAM, the motherboard storage controller, or the cabling — test the RAM one stick at a time and try a different SATA port or cable.