Windows 7 BSod when resuming from sleep

[fredo0877]

Hello,

Sorry for my english but I'm french I've just bought a new computer and I get BSoD (yellow screen in fact) each time I resume from sleep

Link Removed :


KERNEL_DATA_INPAGE_ERROR


I took a picture of it:

Link Removed due to 404 Error


Thank you for your help.

My computer:

Windows 7 édition familiale premium
Asus P8P67-M Pro
i5 2500K non oc
CG Sapphire Ati HD 5750 512 Mo
2x2 Go Corsair XMS3
DD WD Caviar black 7200 tpm 1 To

 

[kaos]

hi welcome to the forums

MINIDUMP

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7A, {fffff6fc4001e100, ffffffffc000009d, 1a851be0, fffff88003c20000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+34bce )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
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: fffff6fc4001e100, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000009d, error status (normally i/o status code)
Arg3: 000000001a851be0, current process (virtual address for lock type 3, or PTE)
Arg4: fffff88003c20000, 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 fffff800050f9278 to fffff80005084700
STACK_TEXT: 
fffff880`0331d808 fffff800`050f9278 : 00000000`0000007a fffff6fc`4001e100 ffffffff`c000009d 00000000`1a851be0 : nt!KeBugCheckEx
fffff880`0331d810 fffff800`0507654b : fffffa80`068a0900 fffff880`0331d980 fffff800`05211440 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x34bce
fffff880`0331d8f0 fffff800`0509f5c4 : 00000000`00000000 00000000`00000001 ffffffff`ffffffff 00000000`00000000 : nt!MiIssueHardFault+0x28b
fffff880`0331d9c0 fffff800`05078ffc : 00000000`00000001 fffff6fc`4001e0d8 fffffa80`07179b00 00000000`00000000 : nt!MmAccessFault+0x11c4
fffff880`0331db20 fffff800`050791f0 : fffffa80`06d47b60 00000000`00000001 fffffa80`07179b60 fffff800`0507742b : nt!MiInPageSingleKernelStack+0x134
fffff880`0331dc30 fffff800`0507917f : fffffa80`07179b60 00000000`00000080 fffffa80`03c55a90 fffffa80`06d47c00 : nt!MmInPageKernelStack+0x40
fffff880`0331dc90 fffff800`05078e2c : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`03c55a00 : nt!KiInSwapKernelStacks+0x1f
fffff880`0331dcc0 fffff800`05327bc6 : 50fe9640`263005f9 5d76c956`b8105cec 8004ae2c`07ea8309 19fec4e4`a4994ebe : nt!KeSwapProcessOrStack+0x84
fffff880`0331dd00 fffff800`05062bc6 : fffff880`02f41180 fffffa80`03d07b60 fffff880`02f4bfc0 cd3954cc`f2539d93 : nt!PspSystemThreadStartup+0x5a
fffff880`0331dd40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND: kb
FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+34bce
fffff800`050f9278 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+34bce
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4d9fdd34
FAILURE_BUCKET_ID: X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+34bce
BUCKET_ID: X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+34bce
Followup: MachineOwner
---------