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
    2010-07-27T19:48:28+00:00

    Hi,

    As far as I can determine the HotFix is one-of which has to be specially applied though you

    might check with Microsoft Support direct.

    Microsoft - Contact Support

    http://support.microsoft.com/contactus/?ws=support#tab0

    Microsoft International

    http://support.microsoft.com/common/international.aspx

    Rob Brown - MS MVP - Windows Desktop Experience : Bicycle - Mark Twain said it right.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2010-07-27T19:15:28+00:00

    re-seating is also great advice.  But just for academic purposes I think I'll try one thing at a time in an attempt to zero in on the true cause.

    The hotfix also looks like a potential fix if the driver update doesnt do it.  Just curious though, is the hotfix code not already rolled into the normal updates or is it a one-off fix?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2010-07-27T18:59:04+00:00

    Hi,

    Low level chipset drivers could cause this issue so hopefully the installation of newer ones

    will solve it. Even reseating the SATA cable might help.

    Rob Brown - MS MVP - Windows Desktop Experience : Bicycle - Mark Twain said it right.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2010-07-27T17:50:28+00:00

    I may be onto it. Although I updated the chipset using the latest Intel driver it didnt look like the new driver got installed.  I installed it again and this time it does look like its installed.  I would think the chipset driver could definitely cause this error.   Anyhow, this is an intermittent problem in that it only happens randomly on wake from sleep. I'll have to wait and see.  I would say I may be able to report back in a week as to whether this was the fix. I've performed a few of your suggestions like the scans (clean) and looking at drivers.  I'd rather not do more at this point to see if this was actually the root cause.

    Thanks for your help so far.   The next thing, if the problem still exists, is to replace the sata cable.

    Was this answer helpful?

    0 comments