BSOD after hibernation Kernel Data Inpage Error 0x0000007A

[Vullun]

Every time I turn on my Dell Vostro 3550 from hibernation, it gets a blue screen with a kernel data inpage error 0x0000007A. I'm using windows 7, please help!

 

[koolkat77]

No dumps.

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

 

[Vullun]

I think I got the dump files now.

 

[koolkat77]

Apologies for the late response

The dump does not give a correct probable cause BUT BSOD Index
STOP 0x0000007A: KERNEL_DATA_INPAGE_ERROR

Usual causes: Memory, Paging file corruption, File system, Hard drive, Cabling, Virus infection, Improperly seated cards, BIOS, Bad motherboard, Missing Service Pack

BSOD Analyze

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

Use !analyze -v to get detailed debugging information.

[COLOR=Blue]BugCheck 7A[/COLOR], {fffff6fc4002b730, ffffffffc000009d, 518b5be0, fffff880056e6000}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : [COLOR=Blue]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3717a )
[/COLOR] 
Followup: MachineOwner
---------

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

[COLOR=Blue]KERNEL_DATA_INPAGE_ERROR (7a)[/COLOR]
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fc4002b730, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000009d, error status (normally i/o status code)
Arg3: 00000000518b5be0, current process (virtual address for lock type 3, or PTE)
Arg4: fffff880056e6000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:
------------------


ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c000009d

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80003154542 to fffff800030e71c0

STACK_TEXT:  
fffff880`0351d708 fffff800`03154542 : 00000000`0000007a fffff6fc`4002b730 ffffffff`c000009d 00000000`518b5be0 : nt!KeBugCheckEx
fffff880`0351d710 fffff800`0310dfff : fffffa80`066ead40 fffff880`0351d880 fffff800`03319540 fffffa80`066ead40 : nt! ?? ::FNODOBFM::`string'+0x3717a
fffff880`0351d7f0 fffff800`030f4789 : 00000000`00000000 00000000`00000001 ffffffff`ffffffff fffff800`03105f23 : nt!MiIssueHardFault+0x28b
fffff880`0351d8c0 fffff800`0311adb0 : 00000000`00000001 fffff880`056e6000 fffffa80`0a774300 fffff6fc`4002b708 : nt!MmAccessFault+0x1399
fffff880`0351da20 fffff800`0311afa0 : fffffa80`09ac3060 00000000`00000001 fffffa80`00000000 fffff800`03117ddb : nt!MiInPageSingleKernelStack+0x134
fffff880`0351db30 fffff800`0311af2f : 00000000`00000000 00000000`00000001 fffffa80`036d56f0 00000000`00000080 : nt!MmInPageKernelStack+0x40
fffff880`0351db90 fffff800`0311ac74 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`036d5600 : nt!KiInSwapKernelStacks+0x1f
fffff880`0351dbc0 fffff800`0337de6a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeSwapProcessOrStack+0x84
fffff880`0351dc00 fffff800`030d7ec6 : fffff880`009ea180 fffffa80`036f7b50 fffff880`009f4fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0351dc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+3717a
fffff800`03154542 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+3717a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4fa390f3

FAILURE_BUCKET_ID:  X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+3717a

BUCKET_ID:  X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+3717a

Followup: MachineOwner

Please follow the instructions mentioned in the quotes below:

If you are overclocking any hardware, please stop.

• Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html (you may need to search for wininit instead of chkdsk).
  For any drives that do not give the message:
  Windows has checked the file system and found no problems
  run disk check again as above. In other words, if it says:
  Windows has made corrections to the file system
  after running the disk check, run the disk check again.
• Run the short and long tests with SeaTools for HDDs.
  SeaTools for Windows
  
  SeaTools for DOS​
• If you have an SSD, make sure the following are up to date:
  • SSD firmware
  • BIOS Version
  • Chipset Drivers
  • Hard disk controller drivers/SATA drivers
  • If you have a Marvell IDE ATA/ATAPI device, uninstall it in device manager and see if the system performs better.
• Check Windows for corruption. Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations. Use OPTION THREE of http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html to provide us with the sfcdetails.txt file if errors occur.

I really think the first priority should be backing up your data. Running diagnostics can cause an already failing drive to fail, so it is best to get your data off the drive before that happens. I am not saying your drive is failing, just that it is a possibility and it is better to be safe than sorry.