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

Anonymous
2009-12-20T20:35:50+00:00

I get this blue screen error:

   KERNEL_DATA_INPAGE_ERROR

   STOP: 0x0000007A

whenever I resume from hibernation or restart after shut down. I did a clean install of windows 7 couple of months back and have been seeing this problem for last month or so.

Sometimes I also see the following error while resuming from hibernation:

   Boot Device Not Found

   Please install an operating system on your hard disk

   Hard Disk (3F0)

And when I click on Hard Disk Test from System Diagnostics, I see this:

   "Hard Disk Test"  Hard disk not exist

I have no idea whether all these errors are related and caused by the same issue. Also, I hear a kind of clicking noise coming from my laptop and the computer starts slowing down eventually resulting in the blue screen.

All my drivers are up to date and windows is also up to date (installed everything on Windows Update).

Windows for home | Previous Windows versions | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2009-12-21T18:30:43+00:00

Hi djrules,

Welcome to Microsoft Answers.

****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. Type at the command prompt CHKDSK /P and press ENTER to scan the disk.

 4. Then 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

Hope this helps. Let us know the results.

Thanks,

Meghmala – Microsoft Support

Visit our Microsoft Answers Feedback Forum and let us know what you think

Was this answer helpful?

400+ people found this answer helpful.
0 comments

65 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2012-03-03T17:15:17+00:00

    Thank you Andre ziegler

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

    helped me to solve my problem: Bluescreen after standby / hybernate with large 2 Terrabyte Seagate barracuda , Windows 7 X64

    No Bluescreen any more,

    Great!

    Thank you, man!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2012-01-14T19:26:03+00:00

    be sure there is a space between K and /P

    Was this answer helpful?

    0 comments
  3. Anonymous
    2011-12-23T07:58:34+00:00

    Now my variant of the STOP ERROR 0x7A has been resolved, but it took time.

    The cause was simply the builtin service "Windows Search".

    What happens is that this service makes indexing of files to make search more effective, this action is transparent to the end user but obviously involves actions in the kernel

    One has to note that mail files also are being indexed and in this case one of the mail files was physically defective (a number of internal file blocks were accidentally destroyed durin a copy operation over network).

    I use the Microsoft Office Outlook 2010 and thus the mail file was a .pst one.

    What happens is that the Microsoft Indexer enters proteckted kernel mode and due to the defective data it writes in an uncontrolled way in the protected kernel causing trouble on several sensitive points including device control blocks. My indications were most commonly STOP 0x7A, but STOP 0xF4 was also raised and no dump data were normally written as the primary local HDD was found to be unavailable.

    The solution is simply to mark the critical files as unavailable for being indexed.

    Of course other actions can be performed as for example stop the "Windows Search" service, remove or repair the critical files etc. The essential thing is that the critical file should not be indexed anymore.

    That's all. But hard to diagnose.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2011-12-08T07:51:25+00:00

    Hi,

    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

    Was this answer helpful?

    0 comments