Blue screen with this error code: KERNEL_DATA_INPAGE_ERROR, STOP: 0x0000007A

A quick summarization of the suggestions given in this thread:

Meghmala:

The error code KERNEL_DATA_INPAGE_ERROR STOP: 0x0000007A states that the requested page of kernel data from the paging file could not be read into memory. It appears that there are some issues with the hard disk.

Use check disk command for any errors on hard disk -

Warning: Microsoft does not recommend interrupting the CHKDSK process. Microsoft does not guarantee the integrity of the disk if the CHKDSK program is interrupted. For safety you can back up your data before using the check disk command.

Use the check disk commands as follows:

 1. Click Start.

 2. In search window type 'cmd' and ENTER. Right click and select 'Run as administrator'.

 3. <removed>

 4. Type CHKDSK C: /F /R and press ENTER to repair corrupt sectors, if there are any.

NOTE: The root drive has to be C: and the command may schedule a task at the system startup, if it does, then press Y to schedule a task and restart the computer to perform chkdsk.

Once chkdsk completes, boot to the desktop and then check.

You may refer to the below mentioned link for more details -

http://msdn.microsoft.com/en-us/library/ms793989.aspx

SpiritX MS MVP has a lot, but the one that stands out for the topic:

Check to see if this Hotfix applies to your system.

You receive various Stop error messages in Windows 7 or in Windows Server 2008 R2 when you try

to resume a computer that has a large SATA hard disk.

http://support.microsoft.com/kb/977178

To use BlueScreenView, MyEventViewer, and other methods to troubleshoot BlueScreens see this

thread - top 3 replies.

http://social.answers.microsoft.com/Forums/en-US/w7repair/thread/c675b7b8-795f-474d-a1c4-6b77b3fcd990

BCCode: 7A    0x0000007A

Cause

Frequently, you can determine the cause of the KERNEL_DATA_INPAGE_ERROR bug check from the error status (Parameter 2). Some common status codes include the following:

• 0xC000009A, or STATUS_INSUFFICIENT_RESOURCES, indicates a lack of nonpaged pool resources.
• 0xC000009C, or STATUS_DEVICE_DATA_ERROR, typically indicates bad blocks (sectors) on the hard disk.
• 0xC000009D, or STATUS_DEVICE_NOT_CONNECTED, indicates defective or loose cabling, termination, or that the controller does not see the hard disk.
• 0xC000016A, or STATUS_DISK_OPERATION_FAILED, indicates bad blocks (sectors) on the hard disk.
• 0xC0000185, or STATUS_IO_DEVICE_ERROR, indicates improper termination or defective cabling on SCSI devices or that two devices are trying to use the same IRQ.

These status codes are the most common ones that have specific causes. For more information about other possible status codes that can be returned, see theNtstatus.h file in the Microsoft Windows Driver Kit (WDK).

Another common cause of this error message is defective hardware or failing RAM.

A virus infection can also cause this bug check.

Resolution

Resolving a bad block problem: An I/O status code of 0xC000009C or 0xC000016A typically indicates that the data could not be read from the disk because of a bad block (sector). If you can restart the computer after the error, Autochk runs automatically and attempts to map the bad sector to prevent it from being used anymore.

If Autochk does not scan the hard disk for errors, you can manually start the disk scanner. RunChkdsk /f /r on the system partition. You must restart the computer before the disk scan begins. If you cannot start the computer because of the error, use the Recovery Console and runChkdsk /r.

Warning   If your system partition is formatted with the FAT file system, the long file names that the Windows operating system uses might be damaged if you use Scandisk or another MS-DOS-based hard disk tool to verify the integrity of your hard disk from MS-DOS. Always use the version of Chkdsk that matches your version of Windows.

Resolving a defective hardware problem: If the I/O status is C0000185 and the paging file is on an SCSI disk, check the disk cabling and SCSI termination for problems.

Resolving a failing RAM problem: Run the hardware diagnostics that the system manufacturer supplies, especially the memory scanner. For more information about these procedures, see the owner's manual for your computer.

Check that all the adapter cards in the computer are properly seated. Use an ink eraser or an electrical contact treatment, available at electronics supply stores, to ensure adapter card contacts are clean.

Check the System Log in Event Viewer for additional error messages that might help identify the device that is causing the error. You can also disable memory caching of the BIOS to try to resolve this error.

Make sure that the latest Windows Service Pack is installed.

If the preceding steps do not resolve the error, take the system motherboard to a repair facility for diagnostic testing. A crack, a scratched trace, or a defective component on the motherboard can cause this error.

Resolving a virus infection: Check your computer for viruses by using any up-to-date, commercial virus scanning software that examines the Master Boot Record of the hard disk. All Windows file systems can be infected by viruses.

BCCode: 7A    0x0000007A  <-- read thishttp://www.faultwire.com/solutions-fatal\_error/KERNEL-DATA-INPAGE-ERROR-0x0000007A-\*1137.html?order=date

Check the System maker (or motherboard maker for custom systems) for BIOS and low leve

chipset drivers. Intel Downloads for your motherboard for those and if there are any others

they will be there. Good idea to check manually at any specific device maker's sites such as

video/display drivers.

Andre.Ziegler:

You can try this hotfix:

http://support.microsoft.com/kb/977178

You receive various Stop error messages in Windows 7 or in Windows Server 2008 R2 when you try to resume a computer that has a large SATA hard disk

Mike Burr:

If you run into this issue again, I wrote a post that may be of help,http://mikemstech.blogspot.com/2011/12/troubleshooting-0x0000007a.html

Axel Skough:

In my case the cause was finally located to defective system files in the Windows 7, most probably from the original system delivery from vendor (delivered on a special, hidden, RECOVERY partition on the HDD, no DVD). It took long time to locate the problem source and also a considerable amount of time to repair the matter as I didn't had any source DVD with the operating system.

Hardware checkout software did not showed up any problems with hardware - everything was signalled to be fine.

  Finally, I got a tip to execute the "SFC /SCANNOW" command (System File Checker, executed from command prompt in extended mode) and this dissolved the defective system files. Such problems should normally be self repairing, but this did not worked because also the protected system backup copy, stored in the WinSXS directory, was found to be defective, too. Therefore, a true source DVD was required to get the system repaired (no download available on the Internet for this problem).

 Indeed, the practical effect of the defective system files was invisible and nothing showed up until the system crashed 0x7A (sometimes 0x9F) at different memory addresses - all unlike and therefore unuseable to reproduce nor diagnose from. Sometimes (very seldom) a WinDump file could be created, but I was unsuccessful to locate any useable information from it.

The problem was caused in the kernel and found to be random overwrite of kernel memory, sometimes affecting hardware access control blocks which finally caused system fail.

 But this is a special cause, it is not necessarily the same thing in your case. You can make some computer and system file scans to see if you can find out something similar, but anyhow, otherwise I would propose you to follow the hint given by Rob Brown and open a new case in this question. 

Hopefully, the matter can be solved, I found these matters hard to diagnose and very time-consuming. Myself, I spent about six months on this including long delivery times for source DVD and support involved, both from Microsoft and from the original computer vendor.

Hope this helps!

It might be worth your time looking over the thread in case I missed out on any other suggestions or tips that might help resolve your issue.  If none of the above helps, like SpiritX MS MVP stated over various times, Blue Screens are usually a complex ordeal and are best to be served one thread at a time.  That being said, it is probably best for you to create your own thread.

Be sure to include all necessary information that will help with diagnosing your particular issue, including but not limited to: PC make & model, PC specifications, OS type, a description of what led to the problem you are facing, what steps you have taken in trying to resolve the issue, etc. .  The more specific and detailed you can be, the better it will help with providing you valuable suggestions for troubleshooting your conundrum.    ^_^

I am going ahead and locking this thread.  Thanks to all of those who helped out with their suggestions!