Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\a\Minidump\D M P\DMP\092610-27346-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c58000 PsLoadedModuleList = 0xfffff800`02e95e50
Debug session time: Sun Sep 26 10:45:38.779 2010 (UTC - 5:00)
System Uptime: 0 days 0:22:30.276
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff880044510d8, 0, ffffffffffffffff}
Unable to load image \SystemRoot\system32\drivers\stwrt64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for stwrt64.sys
*** ERROR: Module load completed but symbols could not be loaded for stwrt64.sys
Probably caused by : stwrt64.sys ( stwrt64+510d8 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880044510d8, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
stwrt64+510d8
fffff880`044510d8 c3 ret
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f000e0
ffffffffffffffff
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR: 0x1E_c0000005
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
EXCEPTION_RECORD: fffff88004691218 -- (.exr 0xfffff88004691218)
ExceptionAddress: fffff880044510d8 (stwrt64+0x00000000000510d8)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME: fffff880046912c0 -- (.trap 0xfffff880046912c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=fffffa8004e3d120
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880044510d8 rsp=fffff88004691450 rbp=0000000000000000
r8=0000000000000001 r9=fffffa8004e27001 r10=0000000000000002
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac po nc
stwrt64+0x510d8:
fffff880`044510d8 c3 ret
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002d02a39 to fffff80002cc8740
STACK_TEXT:
fffff880`04690a48 fffff800`02d02a39 : 00000000`0000001e ffffffff`c0000005 fffff880`044510d8 00000000`00000000 : nt!KeBugCheckEx
fffff880`04690a50 fffff800`02cc7d82 : fffff880`04691218 00000000`00000000 fffff880`046912c0 00000000`00000000 : nt!KiDispatchException+0x1b9
fffff880`046910e0 fffff800`02cc668a : 00000000`00000000 fffff880`0121db69 00000000`00000000 fffff880`04691308 : nt!KiExceptionDispatch+0xc2
fffff880`046912c0 fffff880`044510d8 : 04211030`00000000 00000000`00000000 fffff880`04691ca0 00000000`00000001 : nt!KiGeneralProtectionFault+0x10a
fffff880`04691450 04211030`00000000 : 00000000`00000000 fffff880`04691ca0 00000000`00000001 fffffa80`04d52c50 : stwrt64+0x510d8
fffff880`04691458 00000000`00000000 : fffff880`04691ca0 00000000`00000001 fffffa80`04d52c50 fffffa80`04e27030 : 0x4211030`00000000
STACK_COMMAND: kb
FOLLOWUP_IP:
stwrt64+510d8
fffff880`044510d8 c3 ret
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: stwrt64+510d8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: stwrt64
IMAGE_NAME: stwrt64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 46e0b605
FAILURE_BUCKET_ID: X64_0x1E_c0000005_stwrt64+510d8
BUCKET_ID: X64_0x1E_c0000005_stwrt64+510d8
Followup: MachineOwner
---------