Loading Dump File [C:\DUMPS\Maytoh\021211-31453-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\XSymCache*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.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`0325d000 PsLoadedModuleList = 0xfffff800`0349ae50
Debug session time: Sat Feb 12 14:01:25.620 2011 (UTC + 0:00)
System Uptime: 0 days 0:10:59.432
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {0, 0, 0, 0}
Unable to load image \SystemRoot\system32\drivers\dadder.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dadder.sys
*** ERROR: Module load completed but symbols could not be loaded for dadder.sys
Probably caused by : dadder.sys ( dadder+16d2 )
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: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, 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: (Win32) 0 (0) - The operation completed successfully.
FAULTING_IP:
+3837653932343135
00000000`00000000 ?? ???
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0
BUGCHECK_STR: 0x1E_0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff800032c546e to fffff800032cd710
STACK_TEXT:
fffff800`00b9bba8 fffff800`032c546e : fffffa80`02eea1b0 fffffa80`02b18010 fffff800`00b9c3b0 fffff800`032fa668 : nt!KeBugCheck
fffff800`00b9bbb0 fffff800`032f340d : fffff800`034dbb7c fffff800`03415ea4 fffff800`0325d000 fffff800`00b9c310 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00b9bbe0 fffff800`032faa90 : fffff800`0341cb34 fffff800`00b9bc58 fffff800`00b9c310 fffff800`0325d000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9bc10 fffff800`032fc06a : fffff800`00b9c310 fffff800`00b9c3b0 00000000`00000001 00000000`00000000 : nt!RtlDispatchException+0x410
fffff800`00b9c2f0 fffff800`03328112 : fffffa80`025b0000 fffffa80`04bb27d0 fffffa80`03b70b98 fffff880`0fd1f5c2 : nt!RtlRaiseStatus+0x4e
fffff800`00b9c890 fffff880`069c66d2 : fffffa80`04706900 00000000`00000000 00000000`00000001 fffffa80`0463d800 : nt! ?? ::FNODOBFM::`string'+0xf5fc
fffff800`00b9c910 fffffa80`04706900 : 00000000`00000000 00000000`00000001 fffffa80`0463d800 fffffa80`00000009 : dadder+0x16d2
fffff800`00b9c918 00000000`00000000 : 00000000`00000001 fffffa80`0463d800 fffffa80`00000009 fffffa80`025af110 : 0xfffffa80`04706900
STACK_COMMAND: kb
FOLLOWUP_IP:
dadder+16d2
fffff880`069c66d2 ?? ???
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: dadder+16d2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dadder
IMAGE_NAME: dadder.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 46b1a4cf
FAILURE_BUCKET_ID: X64_0x1E_0_dadder+16d2
BUCKET_ID: X64_0x1E_0_dadder+16d2
Followup: MachineOwner