BSOD kernal_data_inpage_error 0x00000007a

[inogen]

Hiya,

I get this BSOD sometimes when I resume my PC from sleep. It doesn't happen each and every time - but tends to become more likely the longer the sleep has been. Almost certain if I leave it overnight.

I get to the logon screen, sometimes get to type in a few characters and BLUE...

I've updated to the latest drivers for my GPU, which has fairly recently had a bios update, so has my motherboard.

There is yellow triangle in device manager - an unknown device, but I'm pretty sure that's the onboard USB 3.0 device which isn't in use.


If I upload the minidump folder would someone be kind enough to take a look at it for me please? I'm quite good with PCs really, but this is at the outer egdes of my knowledge.

John

 

[lorddenis]

please folow this posting instructions:

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[Tews]

Try this...

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.

source

 

[inogen]

CHKDSK is verifying files (stage 1 of 3)...
193280 file records processed.
File verification completed.
81 large file records processed.
0 bad file records processed.
2 EA records processed.
44 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
242406 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 3)...
193280 file SDs/SIDs processed.
Security descriptor verification completed.
24564 data files processed.
CHKDSK is verifying Usn Journal...
33578248 USN bytes processed.
Usn Journal verification completed.
Windows has checked the file system and found no problems.


Doesn't look like a HD problem...

 

[inogen]

I did read somewhere about a hotfix for this error - but it was to do with >1TB hard disks and windows timing out before they have a chance to spin up.

My HD is the newest 500GB WD Green 5400-7200RPM 32mb Cache.

 

[Tews]

Go ahead and upload the actual .dmp file...

 

[inogen]

info as per debugging instructions :

it mentions the USB device... not sure if that's relevant though....

 

[Tews]

Start here while I look at the .dmp files...

Device drivers are not installed.
Cause: A driver has not been installed for this device preventing it from working properly.
Details: The device driver for Universal Serial Bus (USB) Controller has not been installed. This device will not be available until the correct device driver is installed.
Resolution:
1. Try installing the drivers using Windows Update.
2. Install the drivers that are on the installation media that came with the device.
3. Check with the manufacturer for an updated driver.

 

[inogen]

I did try to find the drivers for that device the other day... It doesn't update though windows update or device manager. There's nothing on my Mobo disks that look specific and I'm loathed to install all the bloatware.

Asus' site as usual is all flash and no trousers. I can't even get to the page relating to my motherboard...

I've found this... Asus P7P55D-E EVO NEC USB3.0 Controller Firmware 3.0.2.1 Driver for Windows XP / Windows Vista / Windows XP X64 / Windows Vista64 / Windows 7 / Windows 7 x64 Free Download - Softpedia but it's taking an age to download. Are softpedia a reliable source of drivers / firmware?

 

[inogen]

this is the second installation of the same version of windows I've had on this machine. I never installed any specific drivers for USB 3.0 on the last installation. That didn't have this problem - although - that really means nothing does it

 

[inogen]

Hmmm. The installer tells me I have the latest firmware...

I've still got the yellow triangle.

I've disabled it. I've got no USB 3.0 devices anyway. Hopefully a windows update or SP1 will fix this...

 

[Tews]

All of but one of your October .dmp files are blaming core window files, however these are rarely the cause of a BSOD... It did however show Rt64win7 (Realtek 8101E/8168/8169 PCI/PCIe Adapters) as the cause of one of your crashes..
Download the latest version of this driver from http://www.realtek.com.tw/downloads
We may need to enable driver verifier if you continue to have BSOD problems... Test and let us know how you do...

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {20, ffffffffc000009d, fffffa800567d7c8, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4c5e0 )

Followup: MachineOwner
---------
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8004afda20, fffff80000b9c518, fffffa800419f750}

Probably caused by : pci.sys

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************



DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc117

MODULE_NAME: pci

FAULTING_MODULE: fffff88000f57000 pci

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9FRt64win7

PROCESS_NAME:  System

CURRENT_IRQL:  2

STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_Rt64win7_IMAGE_pci.sys

BUCKET_ID:  X64_0x9F_3_Rt64win7_IMAGE_pci.sys

Followup: MachineOwner
---------


..................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 9, 0, fffff88000ea8eae}

Probably caused by : msahci.sys ( msahci!AhciCompleteIssuedIRBs+82 )

Followup: MachineOwner
---------

 

[inogen]

Thanks a lot.

I've installed this... Realtek

Another website that is wierd!

Driver seemed to install correctly - a new ethernet driver anyway.

I will post again soon if I get more BSODs - if not I'll post an all clear in week or so.

Thanks

John

 

[Tews]

Good Luck!

 

[inogen]

I've had two BSODs since installing that new driver. Both the same in page error as before.

The last one didn't restart automatically - I had to restart by holding the power button in. Which is a new twist...

 

[Tews]

upload the new .dmp files..