another BSOD on system wake thread

[woodinvilleguy]

I have the same problem as many that my windows 7 x64 system will bsod on wake from sleep about 1/5 of the time. I've attached the minidump

 

[Capt.Jack Sparrow]

Hello and Welcome to SF !

We need the complete logs http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

Based on the crash dump you attached it's pointing to Windows Kernel which may not be the problem. Lets start with basics

Found something it maybe the problem "DISK_HARDWARE_ERROR: There was error with disk hardware"

Run a Hardware Diagnostic !! « Captain Debugger follow this thread

If your Overclocking please reset the BIOS values to default settings How to Reset Your BIOS - wikiHow

Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Remove the following driver i.e.

MRESP50a64.SYS Sat Nov 19 13:44:28 2005 - NDIS Protocol kernel driver.

Can't find the manufacture of this driver i would recommend to deactivate it.
Go to C:\Windows\System32\Drivers MRESP50a64.SYS to MRESP50a64.old

Bugcheck:

KERNEL_DATA_INPAGE_ERROR (7a)
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: 0000000000000020, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000009d, error status (normally i/o status code)
Arg3: fffffa8004e50078, current process (virtual address for lock type 3, or PTE)
Arg4: 0000000000000000, 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:  1

LAST_CONTROL_TRANSFER:  from fffff8000330b3fc to fffff800032d3740

STACK_TEXT:  
fffff880`033b9828 fffff800`0330b3fc : 00000000`0000007a 00000000`00000020 ffffffff`c000009d fffffa80`04e50078 : nt!KeBugCheckEx
fffff880`033b9830 fffff800`032bd637 : fffffa80`04e50010 00000000`c000009d 00000000`00000000 fffffa80`04e500a8 : nt! ?? ::FNODOBFM::`string'+0x4c5e0
fffff880`033b98f0 fffff800`032b00c7 : fffffa80`024f3b60 fffffa80`024f3bb0 00000000`00000000 00000000`00000000 : nt!IopCompletePageWrite+0x57
fffff880`033b9920 fffff800`032dab9d : fffffa80`024f3b60 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7
fffff880`033b99a0 fffff800`032d6d4b : 00000103`03e46d01 00000000`00000000 00000000`00000000 fffff880`033b9a50 : nt!KiCommitThreadWait+0x3dd
fffff880`033b9a30 fffff800`0326dabf : fffffa80`00000002 fffff880`033b9d20 00000000`00000001 fffffa80`00000013 : nt!KeWaitForMultipleObjects+0x271
fffff880`033b9ce0 fffff800`03577c06 : fffffa80`024f3b60 ad1cad1c`c6afc6af 00000000`00000080 00000000`00000001 : nt!MiModifiedPageWriter+0xcf
fffff880`033b9d40 fffff800`032b1c26 : fffff880`009b1180 fffffa80`024f3b60 fffff880`009bc0c0 d741d741`abcdabcd : nt!PspSystemThreadStartup+0x5a
fffff880`033b9d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+4c5e0
fffff800`0330b3fc cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4c5e0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+4c5e0

BUCKET_ID:  X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+4c5e0

Followup: MachineOwner