Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\042111-38173-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`03007000 PsLoadedModuleList = 0xfffff800`03244e50
Debug session time: Thu Apr 21 09:17:19.704 2011 (UTC - 4:00)
System Uptime: 0 days 8:59:59.625
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck F4, {3, fffffa8007d4a770, fffffa8007d4aa50, fffff800033802d0}
Probably caused by : csrss.exe
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa8007d4a770, Terminating object
Arg3: fffffa8007d4aa50, Process image file name
Arg4: fffff800033802d0, Explanatory message (ascii)
Debugging Details:
------------------
PROCESS_OBJECT: fffffa8007d4a770
IMAGE_NAME: csrss.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: csrss
FAULTING_MODULE: 0000000000000000
PROCESS_NAME: csrss.exe
EXCEPTION_RECORD: fffff88006fb5b38 -- (.exr 0xfffff88006fb5b38)
ExceptionAddress: 00000000779857bd
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 0000000002310fd8
Attempt to write to address 0000000002310fd8
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000001
EXCEPTION_PARAMETER2: 0000000002310fd8
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032af0e0
0000000002310fd8
FOLLOWUP_IP:
+3238663431356133
00000000`779857bd ?? ???
FAULTING_IP:
+3238663431356133
00000000`779857bd ?? ???
FAILED_INSTRUCTION_ADDRESS:
+3238663431356133
00000000`779857bd ?? ???
BUGCHECK_STR: 0xF4_C0000005
STACK_TEXT:
fffff880`06fb50b8 fffff800`03403f62 : 00000000`000000f4 00000000`00000003 fffffa80`07d4a770 fffffa80`07d4aa50 : nt!KeBugCheckEx
fffff880`06fb50c0 fffff800`033aba23 : ffffffff`ffffffff fffffa80`082aeb60 fffffa80`07d4a770 fffffa80`07d4a770 : nt!PspCatchCriticalBreak+0x92
fffff880`06fb5100 fffff800`0333390c : ffffffff`ffffffff 00000000`00000001 fffffa80`07d4a770 fffff6fb`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17666
fffff880`06fb5150 fffff800`03076993 : fffffa80`07d4a770 fffff800`c0000005 ffffe40e`c92e3c81 fffffa80`082aeb60 : nt!NtTerminateProcess+0x20c
fffff880`06fb51d0 fffff800`03072f30 : fffff800`030b1dbc fffff880`06fb5b38 fffff880`06fb58a0 fffff880`06fb5be0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`06fb5368 fffff800`030b1dbc : fffff880`06fb5b38 fffff880`06fb58a0 fffff880`06fb5be0 000007fe`fce8a300 : nt!KiServiceLinkage
fffff880`06fb5370 fffff800`03076d82 : fffff880`06fb5b38 00000000`02350000 fffff880`06fb5be0 000007fe`fce8f024 : nt!KiDispatchException+0x53b
fffff880`06fb5a00 fffff800`030758fa : 00000000`00000001 00000000`02350000 00000000`00000001 fffffa80`08566450 : nt!KiExceptionDispatch+0xc2
fffff880`06fb5be0 00000000`779857bd : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`02310fe0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x779857bd
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0xF4_C0000005_IMAGE_csrss.exe
BUCKET_ID: X64_0xF4_C0000005_IMAGE_csrss.exe
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\042111-29374-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`0300e000 PsLoadedModuleList = 0xfffff800`0324be50
Debug session time: Thu Apr 21 11:10:17.552 2011 (UTC - 4:00)
System Uptime: 0 days 1:51:08.473
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7A, {20, ffffffffc000009d, fffffa8007e657c8, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4c5e0 )
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: fffffa8007e657c8, 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 fffff800030b63fc to fffff8000307e740
STACK_TEXT:
fffff880`033087e8 fffff800`030b63fc : 00000000`0000007a 00000000`00000020 ffffffff`c000009d fffffa80`07e657c8 : nt!KeBugCheckEx
fffff880`033087f0 fffff800`03068637 : fffffa80`07e65760 00000000`c000009d 00000000`00000000 fffffa80`07e657f8 : nt! ?? ::FNODOBFM::`string'+0x4c5e0
fffff880`033088b0 fffff800`0305b0b7 : fffffa80`04f1b680 fffffa80`04f1b6d0 fffffa80`05d30840 00000000`00000056 : nt!IopCompletePageWrite+0x57
fffff880`033088e0 fffff800`03085b9d : fffffa80`04f1b680 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7
fffff880`03308960 fffff800`03081d4b : fffffa80`05ec9de0 fffffa80`06a718d0 fffff880`00000000 fffff880`0102f23f : nt!KiCommitThreadWait+0x3dd
fffff880`033089f0 fffff800`03018abf : fffffa80`00000002 fffff880`03308ce0 00000000`00000001 fffffa80`00000013 : nt!KeWaitForMultipleObjects+0x271
fffff880`03308ca0 fffff800`033217c6 : fffffa80`04f1b680 40ff0004`ff000000 00000000`00000080 00000000`00000001 : nt!MiModifiedPageWriter+0xcf
fffff880`03308d00 fffff800`0305cc26 : fffff880`02f64180 fffffa80`04f1b680 fffff880`02f6efc0 00000008`590015ff : nt!PspSystemThreadStartup+0x5a
fffff880`03308d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+4c5e0
fffff800`030b63fc 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: 4cc791bd
FAILURE_BUCKET_ID: X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+4c5e0
BUCKET_ID: X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+4c5e0
Followup: MachineOwner
---------