My win 7 x64 machine BSOD's whenever it resumes from sleep. This is a new install with no third party applications and yes all the drivers and bios have been updated. If anyone can read the mini dump to help me with clues as to what the heck might be causing this I'd greatly appreciate it!
Hi and welcome
Well just took a quick look at your dmps. the cause was pretty evident. Hard disk error.
run chkdsk/f and let us know the results
Kenn J+
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\112709-13468-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*d:\symbols*
Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02852000 PsLoadedModuleList = 0xfffff800`02a8fe50
Debug session time: Fri Nov 27 23:23:10.286 2009 (GMT-5)
System Uptime: 0 days 8:51:16.129
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7A, {20, ffffffffc000009d, fffffa80053467c8, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4c830 )
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: 0000000000000020, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000009d, error status (normally i/o status code)
Arg3: fffffa80053467c8, 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 fffff800028fbbec to fffff800028c3f00
STACK_TEXT:
fffff880`03308828 fffff800`028fbbec : 00000000`0000007a 00000000`00000020 ffffffff`c000009d fffffa80`053467c8 : nt!KeBugCheckEx
fffff880`03308830 fffff800`028ade67 : fffffa80`05346760 00000000`c000009d 00000000`00000000 fffffa80`053467f8 : nt! ?? ::FNODOBFM::`string'+0x4c830
fffff880`033088f0 fffff800`028a092f : fffffa80`0392e530 fffffa80`0392e580 00000000`00000000 00000000`00000000 : nt!IopCompletePageWrite+0x57
fffff880`03308920 fffff800`028cb25d : fffffa80`0392e530 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7
fffff880`033089a0 fffff800`028c754b : 00000103`053c6f01 00000000`00000000 00000000`00000000 fffff880`03308a50 : nt!KiCommitThreadWait+0x3dd
fffff880`03308a30 fffff800`0285ca8f : fffffa80`00000002 fffff880`03308d20 00000000`00000001 fffffa80`00000013 : nt!KeWaitForMultipleObjects+0x271
fffff880`03308ce0 fffff800`02b67166 : fffffa80`0392e530 00000000`00000000 00000000`00000080 00000000`00000001 : nt!MiModifiedPageWriter+0xcf
fffff880`03308d40 fffff800`028a2486 : fffff880`02f63180 fffffa80`0392e530 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03308d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+4c830
fffff800`028fbbec cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+4c830
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
FAILURE_BUCKET_ID: X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+4c830
BUCKET_ID: X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+4c830
Followup: MachineOwner
---------
