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

Anonymous

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).

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

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

0 comments

65 additional answers

Anonymous

2011-11-12T18:52:48+00:00

Hi tungle,

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 No comments
Anonymous

2011-11-12T18:50:41+00:00

Hi, I got the same problem. These are what I get from BlueScreenViewer, mostly the ntoskrnl.exe causes the trouble, how to fix? Tks

==================================================

Dump File : 111311-27690-01.dmp

Crash Time : 11/13/2011 4:58:59 AM

Bug Check String : KERNEL_DATA_INPAGE_ERROR

Bug Check Code : 0x0000007a

Parameter 1 : fffff6fc`5008d318

Parameter 2 : ffffffff`c0000185

Parameter 3 : 00000000`0dabc880

Parameter 4 : fffff8a0`11a63000

Caused By Driver : ntoskrnl.exe

Caused By Address : ntoskrnl.exe+7cc40

File Description : NT Kernel & System

Product Name : Microsoft® Windows® Operating System

Company : Microsoft Corporation

File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)

Processor : x64

Crash Address : ntoskrnl.exe+7cc40

Stack Address 1 :

Stack Address 2 :

Stack Address 3 :

Computer Name :

Full Path : C:\Windows\Minidump\111311-27690-01.dmp

Processors Count : 2

Major Version : 15

Minor Version : 7601

Dump File Size : 299,488

==================================================

==================================================

Dump File : 111111-22729-01.dmp

Crash Time : 11/11/2011 9:47:18 PM

Bug Check String : KERNEL_DATA_INPAGE_ERROR

Bug Check Code : 0x0000007a

Parameter 1 : fffff6fc`40008400

Parameter 2 : ffffffff`c0000185

Parameter 3 : 00000001`06483860

Parameter 4 : fffff880`01080008

Caused By Driver : ataport.SYS

Caused By Address : ataport.SYS+19008

File Description :

Product Name :

Company :

File Version :

Processor : x64

Crash Address : ntoskrnl.exe+7cc40

Stack Address 1 :

Stack Address 2 :

Stack Address 3 :

Computer Name :

Full Path : C:\Windows\Minidump\111111-22729-01.dmp

Processors Count : 2

Major Version : 15

Minor Version : 7601

Dump File Size : 299,480

==================================================

==================================================

Dump File : 110911-28407-01.dmp

Crash Time : 11/9/2011 10:44:51 PM

Bug Check String : KERNEL_DATA_INPAGE_ERROR

Bug Check Code : 0x0000007a

Parameter 1 : fffff6fc`40008378

Parameter 2 : ffffffff`c0000185

Parameter 3 : 00000000`0b1c5860

Parameter 4 : fffff880`0106f008

Caused By Driver : ataport.SYS

Caused By Address : ataport.SYS+19008

File Description :

Product Name :

Company :

File Version :

Processor : x64

Crash Address : ntoskrnl.exe+7cc40

Stack Address 1 :

Stack Address 2 :

Stack Address 3 :

Computer Name :

Full Path : C:\Windows\Minidump\110911-28407-01.dmp

Processors Count : 2

Major Version : 15

Minor Version : 7601

Dump File Size : 294,792

==================================================

==================================================

Dump File : 110711-42900-01.dmp

Crash Time : 11/7/2011 9:01:07 PM

Bug Check String : KERNEL_DATA_INPAGE_ERROR

Bug Check Code : 0x0000007a

Parameter 1 : fffff6fc`400083c8

Parameter 2 : ffffffff`c0000185

Parameter 3 : 00000000`dae11860

Parameter 4 : fffff880`01079008

Caused By Driver : ataport.SYS

Caused By Address : ataport.SYS+19008

File Description :

Product Name :

Company :

File Version :

Processor : x64

Crash Address : ntoskrnl.exe+7cc40

Stack Address 1 :

Stack Address 2 :

Stack Address 3 :

Computer Name :

Full Path : C:\Windows\Minidump\110711-42900-01.dmp

Processors Count : 2

Major Version : 15

Minor Version : 7601

Dump File Size : 299,496

==================================================

==================================================

Dump File : 110411-24398-01.dmp

Crash Time : 11/4/2011 12:56:48 AM

Bug Check String : KERNEL_DATA_INPAGE_ERROR

Bug Check Code : 0x0000007a

Parameter 1 : fffff6fc`40009900

Parameter 2 : ffffffff`c0000185

Parameter 3 : 00000000`23cc5860

Parameter 4 : fffff880`01320f44

Caused By Driver : Ntfs.sys

Caused By Address : Ntfs.sys+eff44

File Description :

Product Name :

Company :

File Version :

Processor : x64

Crash Address : ntoskrnl.exe+7cc40

Stack Address 1 :

Stack Address 2 :

Stack Address 3 :

Computer Name :

Full Path : C:\Windows\Minidump\110411-24398-01.dmp

Processors Count : 2

Major Version : 15

Minor Version : 7601

Dump File Size : 299,488

==================================================

==================================================

Dump File : 110211-64366-01.dmp

Crash Time : 11/2/2011 2:27:11 PM

Bug Check String : KERNEL_DATA_INPAGE_ERROR

Bug Check Code : 0x0000007a

Parameter 1 : fffff6fc`400097f8

Parameter 2 : ffffffff`c0000185

Parameter 3 : 00000000`55812860

Parameter 4 : fffff880`012ff6b0

Caused By Driver : Ntfs.sys

Caused By Address : Ntfs.sys+f06b0

File Description :

Product Name :

Company :

File Version :

Processor : x64

Crash Address : ntoskrnl.exe+7cc40

Stack Address 1 :

Stack Address 2 :

Stack Address 3 :

Computer Name :

Full Path : C:\Windows\Minidump\110211-64366-01.dmp

Processors Count : 2

Major Version : 15

Minor Version : 7601

Dump File Size : 299,544

==================================================

==================================================

Dump File : 092811-26395-01.dmp

Crash Time : 9/28/2011 12:32:53 PM

Bug Check String : KERNEL_DATA_INPAGE_ERROR

Bug Check Code : 0x0000007a

Parameter 1 : fffff6fc`5000b790

Parameter 2 : ffffffff`c0000185

Parameter 3 : 00000000`b9346820

Parameter 4 : fffff8a0`016f2e1c

Caused By Driver : ntoskrnl.exe

Caused By Address : ntoskrnl.exe+7cc40

File Description : NT Kernel & System

Product Name : Microsoft® Windows® Operating System

Company : Microsoft Corporation

File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)

Processor : x64

Crash Address : ntoskrnl.exe+7cc40

Stack Address 1 :

Stack Address 2 :

Stack Address 3 :

Computer Name :

Full Path : C:\Windows\Minidump\092811-26395-01.dmp

Processors Count : 2

Major Version : 15

Minor Version : 7601

Dump File Size : 299,488

==================================================

==================================================

Dump File : 092211-29780-01.dmp

Crash Time : 9/22/2011 10:24:22 PM

Bug Check String : DRIVER_POWER_STATE_FAILURE

Bug Check Code : 0x1000009f

Parameter 1 : 00000000`00000004

Parameter 2 : 00000000`00000258

Parameter 3 : fffffa80`036df040

Parameter 4 : fffff800`0446f510

Caused By Driver : ntoskrnl.exe

Caused By Address : ntoskrnl.exe+7f4da

File Description : NT Kernel & System

Product Name : Microsoft® Windows® Operating System

Company : Microsoft Corporation

File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)

Processor : x64

Crash Address : ntoskrnl.exe+7f4da

Stack Address 1 :

Stack Address 2 :

Stack Address 3 :

Computer Name :

Full Path : C:\Windows\Minidump\092211-29780-01.dmp

Processors Count : 2

Major Version : 15

Minor Version : 7601

Dump File Size : 508,712

==================================================

==================================================

Dump File : 091711-24320-01.dmp

Crash Time : 9/17/2011 4:17:16 PM

Bug Check String : DRIVER_POWER_STATE_FAILURE

Bug Check Code : 0x1000009f

Parameter 1 : 00000000`00000004

Parameter 2 : 00000000`00000258

Parameter 3 : fffffa80`036f9b60

Parameter 4 : fffff800`00b9c510

Caused By Driver : ntoskrnl.exe

Caused By Address : ntoskrnl.exe+7f4da

File Description : NT Kernel & System

Product Name : Microsoft® Windows® Operating System

Company : Microsoft Corporation

File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)

Processor : x64

Crash Address : ntoskrnl.exe+7f4da

Stack Address 1 :

Stack Address 2 :

Stack Address 3 :

Computer Name :

Full Path : C:\Windows\Minidump\091711-24320-01.dmp

Processors Count : 2

Major Version : 15

Minor Version : 7601

Dump File Size : 508,552

==================================================
Was this answer helpful?

0 comments No comments
Anonymous

2011-11-10T03:29:47+00:00

Hello,

Due to the age of this issue, it would be best to create a new thread for this.

Doing so will avoid any confusion between your issue and that of the original poster.

Best regards,

Matthew_Ha
Was this answer helpful?

0 comments No comments
Anonymous

2011-11-09T07:36:47+00:00

I was wrong......

The CHKDSK C: /F /R command did not fixed the problem in my cause although the computer desktop was up and running for a while without any STOP error.

But at last it happened. I put the computer in the hibernate state overnight. In the morning the computer was dead and the screen was turned off, I could not see any message on the screen and could not wake up the screen to display its content.

I may assume that the KERNEL_DATA_INPAGE_ERROR with STOP code 0x0000007A has occured again, but the computer behavior is now different. Before the repair action with CHKDSK /F /R I could make a cold restart by turning power off and on again - now even the cold restart fails and there is no HDD present anymore, the BIOS setup shows that no HDD is present. The lack should indicate a cable problem, but I do not think it is the cause here, however, further analysis will be performed. The HDD should be intact - I haven't seen any indications concerning defectives on the HDD.

However, the try to repair using the CHKDSK made things worser and the defectives indicate that a serious BIOS problem has occured, maybe caused by a virus infection?

So let's see how the story will continue ....

Axel

Hi,

The story is continuing......

Since my previous message I have been talking with both the Microsoft support and the hardware vendor.

The Microsoft support has been paused for a while, the hardware vendor accepted this problem as being related to hardware and has replaced motherboard as well as HDD and carefully checked all cable connections.

Warranty conditions applies in my case - the computer was bought a number of months ago as well as upgrading from delivery status, Microsoft Windows 7 Home to Ultimate.

I got the computer back two days ago (Monday afternoon) and until now I am going to check it carefully, system has been restored from backup and a number of software updates have been (operating system as well as other softwares so the computer is not crying for updates and restarts all the time anymore.

Now I am going to check whether the STOP 0x7A problem still persists. Let's see, indeed the actions performed are close to replace the whole computer (new motherboard) and the HDD was replaced, too, as being the critical thing pointed out although I don't suspect the failure to be caused by the HDD or related directly to it.

But to be honest, I have to say that there were more problems than the 0x7A STOP condition related to the HDD.

Another issue is that I have an USB attached printer device and after having the computer restored from the hibernate state the USB attached printer has failed to reconnect more than 20 times since being installed in late June this year. It is a relatively seldom appearing state, causing printer driver to fail with a general system error 5 code (from system log, no dump is taken).

But the fail is similar, external device connection fails in conjunction with computer being restored from the hibernate state. If HDD fails, then STOP 0x7A is issued, if USB attached printer device fails then printer driver fails with a system error 5 issued.

None of these conditions are normal, they are hard to reproduce and the cause is still unknown.

Let's see if these actions regarding replacing motherboard and HDD were effective with the desired result. Until now nothing has happened, but the computer was fixed and returned only a very few days ago.

Axel
Was this answer helpful?

0 comments No comments