*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10D, {5, 0, 1202, fffffa800bc15120}
*** WARNING: Unable to verify timestamp for MijXfilt.sys
*** ERROR: Module load completed but symbols could not be loaded for MijXfilt.sys
Probably caused by : MijXfilt.sys ( MijXfilt+363a )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
WDF_VIOLATION (10d)
The Kernel-Mode Driver Framework was notified that Windows detected an error
in a framework-based driver. In general, the dump file will yield additional
information about the driver that caused this bug check.
Arguments:
Arg1: 0000000000000005, A framework object handle of the incorrect type was passed to
a framework object method.
Arg2: 0000000000000000, The handle value passed in.
Arg3: 0000000000001202, Reserved.
Arg4: fffffa800bc15120, Reserved.
Debugging Details:
------------------
BUGCHECK_STR: 0x10D_5
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: Better DS3.exe
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
LAST_CONTROL_TRANSFER: from fffff88000e52a46 to fffff80002e8abc0
STACK_TEXT:
fffff880`09639688 fffff880`00e52a46 : 00000000`0000010d 00000000`00000005 00000000`00000000 00000000`00001202 : nt!KeBugCheckEx
fffff880`09639690 fffff880`06c3b63a : fffffa80`09d613f0 fffffa80`09d614f0 00000000`00000004 00000000`00000001 : Wdf01000!imp_WdfUsbTargetDeviceSendControlTransferSynchronously+0x8a
fffff880`096399b0 fffffa80`09d613f0 : fffffa80`09d614f0 00000000`00000004 00000000`00000001 fffff880`09639ae0 : MijXfilt+0x363a
fffff880`096399b8 fffffa80`09d614f0 : 00000000`00000004 00000000`00000001 fffff880`09639ae0 fffff880`09639a30 : 0xfffffa80`09d613f0
fffff880`096399c0 00000000`00000004 : 00000000`00000001 fffff880`09639ae0 fffff880`09639a30 fffff880`096399f8 : 0xfffffa80`09d614f0
fffff880`096399c8 00000000`00000001 : fffff880`09639ae0 fffff880`09639a30 fffff880`096399f8 00000000`00000000 : 0x4
fffff880`096399d0 fffff880`09639ae0 : fffff880`09639a30 fffff880`096399f8 00000000`00000000 fffffa80`0a656480 : 0x1
fffff880`096399d8 fffff880`09639a30 : fffff880`096399f8 00000000`00000000 fffffa80`0a656480 00000000`00000040 : 0xfffff880`09639ae0
fffff880`096399e0 fffff880`096399f8 : 00000000`00000000 fffffa80`0a656480 00000000`00000040 00000000`00000000 : 0xfffff880`09639a30
fffff880`096399e8 00000000`00000000 : fffffa80`0a656480 00000000`00000040 00000000`00000000 00000001`00000001 : 0xfffff880`096399f8
STACK_COMMAND: kb
FOLLOWUP_IP:
MijXfilt+363a
fffff880`06c3b63a ?? ???
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: MijXfilt+363a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: MijXfilt
IMAGE_NAME: MijXfilt.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4fade6a0
FAILURE_BUCKET_ID: X64_0x10D_5_MijXfilt+363a
BUCKET_ID: X64_0x10D_5_MijXfilt+363a
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x10d_5_mijxfilt+363a
FAILURE_ID_HASH: {14eb55f2-269f-4849-2c8a-1794e99697c8}
Followup: MachineOwner
---------
0: kd> lmvm MijXfilt
start end module name
fffff880`06c38000 fffff880`06c5a000 MijXfilt T (no symbols)
Loaded symbol image file: MijXfilt.sys
Image path: \SystemRoot\system32\DRIVERS\MijXfilt.sys
Image name: MijXfilt.sys
Timestamp: Sat May 12 09:57:12 2012 (4FADE6A0)
CheckSum: 00022009
ImageSize: 00022000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4