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

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

No such parameter /P

Microsoft Windows [Version 6.1.7601]

Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\M>chkdsk /P

Invalid parameter - /P

C:\Users\M>CHKDSK /?

Checks a disk and displays a status report.

CHKDSK [volume[[path]filename]]] [/F] [/V] [/R] [/X] [/I] [/C] [/L[:size]] [/B]

  volume          Specifies the drive letter (followed by a colon),

                  mount point, or volume name.

  filename        FAT/FAT32 only: Specifies the files to check for fragmentation

.

  /F              Fixes errors on the disk.

  /V              On FAT/FAT32: Displays the full path and name of every file

                  on the disk.

                  On NTFS: Displays cleanup messages if any.

  /R              Locates bad sectors and recovers readable information

                  (implies /F).

  /L:size         NTFS only:  Changes the log file size to the specified number

                  of kilobytes.  If size is not specified, displays current

                  size.

  /X              Forces the volume to dismount first if necessary.

                  All opened handles to the volume would then be invalid

                  (implies /F).

  /I              NTFS only: Performs a less vigorous check of index entries.

  /C              NTFS only: Skips checking of cycles within the folder

                  structure.

  /B              NTFS only: Re-evaluates bad clusters on the volume

                  (implies /R)

The /I or /C switch reduces the amount of time required to run Chkdsk by

skipping certain checks of the volume.

you cant do checkdisk on a ssd and im having the same BOSD as the others here and im runing SSD's.

for thge past 3 weeks ive had so mutch problem im about to )(&?(&(/ hdd's ( ssd's ) been returned, ram returned and the next is my mobo. errors all over the place.

new sata cables, all drivers to every thing up to date, bios up to date, win updates up to date,++++++++++++++

im loosing patient.....

Rob,

Thank you very much for an excellent, interesting and detailed problem description with lots of howtos!

I also ran into the KERNEL_DATA_INPAGE_ERROR STOP 0x0000007A error with DUMP FAIL 0x00000010 (no HDD present) problem.

My assumption is that the problem occured because I had tested a thirdparty software during a 30-day trial period and did not wanted to pay for it when the trial period expired. I preferred to uninstall the software and got thus possibly "punished" with this problem killing access to my HDD (not a cable problem).

I've tried the CHKDSK /F /R solution and it seems to have solved the problem as the problem appeared relatively quickly after a cold restart (warm restart only gave the diagnostic message NO BOOT DEVICE).

Sorry to have to say that I haven't saved the parameters and thus I am not fully aware about the indications about the cause nature. Of course, it could be malware still remaining in computer or only a bad stamp put on the HDD giving this STOP error in my cause

• but your generalised advice about actions seem to have worked fine!

Kind regards,

Axel Skough

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