KERNEL_DATA_INPAGE_ERROR (0x7A)

KERNEL_DATA_INPAGE_ERROR (0x7A) means Windows tried to read data from your storage drive into memory and the read failed. This is one of the most urgent BSODs because it usually indicates a dying drive.

What it means in plain English: Your SSD or hard drive couldn't deliver data that Windows needed. Think of it like a book with missing pages — Windows asked to read page 4,327 and the drive said 'I can't read that.' This is usually a hardware failure, and you should back up your data as soon as possible.

How to decode the error parameters: The BSOD or minidump shows parameter values. Parameter 2 is the NTSTATUS code that tells you exactly what went wrong: 0xC000009C = bad disk block (drive has physical damage), 0xC000009D = disk controller error (drive hardware failing), 0xC000016A = disk hardware error (drive is dying), 0xC0000185 = bad memory (RAM issue, not disk). If parameter 2 is 0xC0000185, this is actually a RAM problem — skip to memtest86.

The most common causes (in order)

1. Failing SSD or HDD. By far the most common cause. All drives have a limited lifespan. HDDs develop bad sectors over time. SSDs have write endurance limits. When the drive starts failing, read errors cause this BSOD.
2. Loose cable connection. SATA cables can work loose over time, especially if the PC was moved. A loose connection causes intermittent read failures. NVMe drives can also come partially unseated from the M.2 slot.
3. Corrupted pagefile. Windows uses the pagefile as overflow memory. If the pagefile lives on a damaged area of the drive, every time Windows swaps data through it, you get this error.
4. Faulty RAM (less common). If the NTSTATUS code is 0xC0000185, the data was corrupted in memory, not on disk.

How to fix it

1. Check drive health immediately. Download CrystalDiskInfo (free). Look at the overall status: 'Good' is fine, 'Caution' means failing, 'Bad' means replace now. Specifically check: Reallocated Sectors Count, Current Pending Sectors, and Uncorrectable Sector Count. Any non-zero value on these is a problem.
2. Back up your data. If CrystalDiskInfo shows anything other than 'Good', copy your important files to another drive or cloud storage right now. Failing drives can go from 'intermittent errors' to 'completely dead' overnight.
3. Run chkdsk. Open admin Command Prompt, run 'chkdsk C: /r /f'. Schedule it for next restart if prompted. This finds bad sectors and moves data away from them. It's a temporary fix — if the drive is failing, chkdsk buys time but doesn't fix the hardware.
4. Reseat cables and drives. Power off, unplug, open the case. Reseat SATA cables on both ends (drive and motherboard). For NVMe: unscrew the M.2 drive, remove it, reseat it firmly, rescrew. A poor connection causes exactly this BSOD.
5. Delete and recreate the pagefile. Right-click This PC > Properties > Advanced System Settings > Performance > Settings > Advanced > Virtual Memory > Change. Set to 'No paging file', restart, then set it back to 'System managed size' and restart again.
6. Run memtest86 if parameter 2 is 0xC0000185. If the error code points to memory, this is actually a RAM problem. Run memtest86 overnight to confirm.

Gaming-specific notes: If this only happens during gaming, the game might be hammering pagefile I/O (especially if you have less than 16GB RAM). Make sure the pagefile is on your fastest SSD, not an HDD. Increase pagefile size to 16-32GB if you only have 16GB RAM.