Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\011710-35474-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*d:\symbols*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 Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a62000 PsLoadedModuleList = 0xfffff800`02c9fe50
Debug session time: Sun Jan 17 10:19:40.283 2010 (GMT-5)
System Uptime: 1 days 7:01:13.077
Loading Kernel Symbols
...............................................................
................................................................
...............................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff80000b9a8d0, 0, 0}
Unable to load image \SystemRoot\system32\DRIVERS\k57nd60a.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for k57nd60a.sys
*** ERROR: Module load completed but symbols could not be loaded for k57nd60a.sys
Probably caused by : k57nd60a.sys ( k57nd60a+bd3b )
Followup: MachineOwner
---------
0: 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: fffff80000b9a8d0, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, 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:
+5c3f952f02a5d9a4
fffff800`00b9a8d0 f8 clc
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d0a0e0
0000000000000000
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x1E
PROCESS_NAME: System
CURRENT_IRQL: 2
EXCEPTION_RECORD: fffff80000b9b7f8 -- (.exr 0xfffff80000b9b7f8)
ExceptionAddress: fffff88003e75d3b (k57nd60a+0x000000000000bd3b)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME: fffff80000b9b8a0 -- (.trap 0xfffff80000b9b8a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ff00fa80059cd800 rbx=0000000000000000 rcx=0000000000000002
rdx=fffffa80059fac10 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88003e75d3b rsp=fffff80000b9ba30 rbp=0000000000000001
r8=0000000000000001 r9=fffffa80059fac10 r10=fffffa8005a5b380
r11=fffff80000b9bcb8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
k57nd60a+0xbd3b:
fffff880`03e75d3b ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002b64b2b to fffff80002ad3f00
STACK_TEXT:
fffff800`00b9a818 fffff800`02b64b2b : 00000000`0000001e ffffffff`c0000005 fffff800`00b9a8d0 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9a820 fffff800`02b27390 : ffff0080`00000000 fffffa80`047645c4 fffffa80`069e7824 fffff880`0679cf4c : nt!KipFatalFilter+0x1b
fffff800`00b9a860 fffff800`02b024dc : fffffa80`07d25060 00000000`00000000 fffffa80`069e7664 fffff880`0679c440 : nt! ?? ::FNODOBFM::`string'+0x95d
fffff800`00b9a8a0 fffff800`02af9bed : fffff800`02c1a470 fffff800`00b9c330 00000000`00000000 fffff800`02a62000 : nt!_C_specific_handler+0x8c
fffff800`00b9a910 fffff800`02b01250 : fffff800`02c1a470 fffff800`00b9a988 fffff800`00b9b7f8 fffff800`02a62000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9a940 fffff800`02b0e1b5 : fffff800`00b9b7f8 fffff800`00b9b050 fffff800`00000000 00000000`00000005 : nt!RtlDispatchException+0x410
fffff800`00b9b020 fffff800`02ad3542 : fffff800`00b9b7f8 fffffa80`058d9000 fffff800`00b9b8a0 00000000`00000000 : nt!KiDispatchException+0x135
fffff800`00b9b6c0 fffff800`02ad1e4a : fffff800`00b9bc90 fffffa80`059fac10 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff800`00b9b8a0 fffff880`03e75d3b : 00000000`00000000 fffffa80`07b93db0 fffffa80`058d0000 fffff800`00b9bc00 : nt!KiGeneralProtectionFault+0x10a
fffff800`00b9ba30 00000000`00000000 : fffffa80`07b93db0 fffffa80`058d0000 fffff800`00b9bc00 00000000`00000002 : k57nd60a+0xbd3b
STACK_COMMAND: kb
FOLLOWUP_IP:
k57nd60a+bd3b
fffff880`03e75d3b ?? ???
SYMBOL_STACK_INDEX: 9
SYMBOL_NAME: k57nd60a+bd3b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: k57nd60a
IMAGE_NAME: k57nd60a.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a3cc959
FAILURE_BUCKET_ID: X64_0x1E_k57nd60a+bd3b
BUCKET_ID: X64_0x1E_k57nd60a+bd3b
Followup: MachineOwner
---------
