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\021911-19874-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.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02a15000 PsLoadedModuleList = 0xfffff800`02c52e50
Debug session time: Sat Feb 19 04:08:16.777 2011 (UTC - 5:00)
System Uptime: 0 days 0:57:35.744
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
....
Unable to load image \SystemRoot\system32\DRIVERS\BdfNdisf6.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for BdfNdisf6.sys
*** ERROR: Module load completed but symbols could not be loaded for BdfNdisf6.sys
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffff80000003, The exception code that was not handled
Arg2: fffff88001a30002, The address that the exception occurred at
Arg3: fffff88008f92528, Exception Record Address
Arg4: fffff88008f91d90, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid
FAULTING_IP:
BdfNdisf6+2002
fffff880`01a30002 cc int 3
EXCEPTION_RECORD: fffff88008f92528 -- (.exr 0xfffff88008f92528)
ExceptionAddress: fffff88001a30002 (BdfNdisf6+0x0000000000002002)
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000000
NumberParameters: 1
Parameter[0]: 0000000000000000
CONTEXT: fffff88008f91d90 -- (.cxr 0xfffff88008f91d90)
rax=0000000000000103 rbx=fffffa800521d700 rcx=f88001a403960000
rdx=0000000000000002 rsi=fffffa80072cfc10 rdi=0000000000000001
rip=fffff88001a30002 rsp=fffff88008f92760 rbp=fffffa80072a4e00
r8=fffffa800447b500 r9=ffffffffffffffff r10=fffffa800447b600
r11=fffff88008f92690 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00000246
BdfNdisf6+0x2002:
fffff880`01a30002 cc int 3
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x7E
PROCESS_NAME: System
CURRENT_IRQL: 2
ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached.
EXCEPTION_PARAMETER1: 0000000000000000
LAST_CONTROL_TRANSFER: from fffffa800521d700 to fffff88001a30002
STACK_TEXT:
fffff880`08f92760 fffffa80`0521d700 : fffff880`01a37ec0 fffffa80`00000000 fffffa80`00000000 00000000`00000000 : BdfNdisf6+0x2002
fffff880`08f92768 fffff880`01a37ec0 : fffffa80`00000000 fffffa80`00000000 00000000`00000000 fffffa80`072cfc10 : 0xfffffa80`0521d700
fffff880`08f92770 fffffa80`00000000 : fffffa80`00000000 00000000`00000000 fffffa80`072cfc10 fffff880`08f927a0 : BdfNdisf6+0x9ec0
fffff880`08f92778 fffffa80`00000000 : 00000000`00000000 fffffa80`072cfc10 fffff880`08f927a0 fffffa80`072a4ec0 : 0xfffffa80`00000000
fffff880`08f92780 00000000`00000000 : fffffa80`072cfc10 fffff880`08f927a0 fffffa80`072a4ec0 00000000`00000000 : 0xfffffa80`00000000
FOLLOWUP_IP:
BdfNdisf6+2002
fffff880`01a30002 cc int 3
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: BdfNdisf6+2002
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: BdfNdisf6
IMAGE_NAME: BdfNdisf6.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a92aa1a
STACK_COMMAND: .cxr 0xfffff88008f91d90 ; kb
FAILURE_BUCKET_ID: X64_0x7E_BdfNdisf6+2002
BUCKET_ID: X64_0x7E_BdfNdisf6+2002
Followup: MachineOwner
---------
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\021911-20264-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.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02a01000 PsLoadedModuleList = 0xfffff800`02c3ee50
Debug session time: Sat Feb 19 05:00:51.385 2011 (UTC - 5:00)
System Uptime: 0 days 0:51:53.491
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\BdfNdisf6.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for BdfNdisf6.sys
*** ERROR: Module load completed but symbols could not be loaded for BdfNdisf6.sys
Probably caused by : BdfNdisf6.sys ( BdfNdisf6+2003 )
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:
+6638393335336338
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: BitTorrent.exe
CURRENT_IRQL: 2
EXCEPTION_RECORD: fffff80000ba27f8 -- (.exr 0xfffff80000ba27f8)
ExceptionAddress: fffff88001bd7002 (BdfNdisf6+0x0000000000002002)
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000000
NumberParameters: 1
Parameter[0]: 0000000000000000
TRAP_FRAME: fffff80000ba28a0 -- (.trap 0xfffff80000ba28a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000103 rbx=0000000000000000 rcx=f88001be73e40000
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001bd7003 rsp=fffff80000ba2a30 rbp=fffffa80052fc500
r8=fffffa8003c1c800 r9=ffffffffffffffff r10=fffffa8003c1c8a0
r11=fffff80000ba2960 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
BdfNdisf6+0x2003:
fffff880`01bd7003 ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002a6946e to fffff80002a71710
STACK_TEXT:
fffff800`00ba18e8 fffff800`02a6946e : 00000000`00000002 00000000`00000002 fffff800`00ba2060 fffff800`02a9e668 : nt!KeBugCheck
fffff800`00ba18f0 fffff800`02a9740d : fffff800`02c7fb7c fffff800`02bb9ea4 fffff800`02a01000 fffff800`00ba27f8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00ba1920 fffff800`02a9ea90 : fffff800`02bc0a60 fffff800`00ba1998 fffff800`00ba27f8 fffff800`02a01000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00ba1950 fffff800`02aab9ef : fffff800`00ba27f8 fffff800`00ba2060 fffff800`00000000 00000000`00000006 : nt!RtlDispatchException+0x410
fffff800`00ba2030 fffff800`02a70d82 : fffff800`00ba27f8 fffffa80`0749abe0 fffff800`00ba28a0 fffffa80`052fc5f0 : nt!KiDispatchException+0x16f
fffff800`00ba26c0 fffff800`02a6ebb4 : fffffa80`07a359a4 fffffa80`07a359a4 fffffa80`08a097a0 fffffa80`04ec36a0 : nt!KiExceptionDispatch+0xc2
fffff800`00ba28a0 fffff880`01bd7003 : fffffa80`0749abe0 fffff880`01bdeec0 fffffa80`00000000 fffffa80`00000000 : nt!KiBreakpointTrap+0xf4
fffff800`00ba2a30 fffffa80`0749abe0 : fffff880`01bdeec0 fffffa80`00000000 fffffa80`00000000 00000000`00000000 : BdfNdisf6+0x2003
fffff800`00ba2a38 fffff880`01bdeec0 : fffffa80`00000000 fffffa80`00000000 00000000`00000000 fffffa80`052fc5f0 : 0xfffffa80`0749abe0
fffff800`00ba2a40 fffffa80`00000000 : fffffa80`00000000 00000000`00000000 fffffa80`052fc5f0 fffff800`00ba2a70 : BdfNdisf6+0x9ec0
fffff800`00ba2a48 fffffa80`00000000 : 00000000`00000000 fffffa80`052fc5f0 fffff800`00ba2a70 fffffa80`052fc510 : 0xfffffa80`00000000
fffff800`00ba2a50 00000000`00000000 : fffffa80`052fc5f0 fffff800`00ba2a70 fffffa80`052fc510 00000000`00000000 : 0xfffffa80`00000000
STACK_COMMAND: kb
FOLLOWUP_IP:
BdfNdisf6+2003
fffff880`01bd7003 ?? ???
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: BdfNdisf6+2003
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: BdfNdisf6
IMAGE_NAME: BdfNdisf6.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a92aa1a
FAILURE_BUCKET_ID: X64_0x1E_0_BdfNdisf6+2003
BUCKET_ID: X64_0x1E_0_BdfNdisf6+2003
Followup: MachineOwner
---------