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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2012-04-21T01:28:06+00:00

    Hi RayGo1975,

    BlueScreen issues are too complex to try to solve them for more than one user per

    thread so please start your own with the information we need to help us help you.

    How to ask a question

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

    We will definitely try to help.

    Hope this helps.

    Rob Brown - Microsoft MVP <- profile - Windows Expert - Consumer : Bicycle - Mark Twain said it right.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2012-04-21T09:33:23+00:00

    Hi RayGo1975,

    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! 

    Kind regards,

    Axel

    Was this answer helpful?

    0 comments
  3. Anonymous
    2012-04-23T05:06:40+00:00

    As I told Rob it seemed to be a bad driver for the SSD which gave the appearance of bad drive, also I had to update the firmware all seemed to fix the problem, Oh I forgot that the marvell driver for the mother board needed fixing.

    Thanks for your help Ray

    Was this answer helpful?

    0 comments
  4. Anonymous
    2012-05-11T16:31:02+00:00

    Hello, I did the process but at the end I didn't see any message, only the login page of my computer, what exactly means to "boot to the desktop and then check"?

    And what is the risk that I am having with my computer getting the KERNEL message?

    I also heard about another process in which I have to press "Fn" and then "Restart", but I also heard that it could be dangerous, could you explain to me how it works?

    Last question, should I reset my computer and install everything again?

    Thank you so much!!

    Was this answer helpful?

    0 comments