BSOD playing Dark Souls, windows driver framework error

zalgocykel · 01 Mar 2014

As the title states, when playing dark souls I have started getting BSODs. I am playing the game with motioninjoy (a program where I can play using my playstation 3 controller). I think I began having this issue after switching my video card from a nvidia to a new xfx radeon card. Included multiple dump files and a photo of the bluescreen. I've filled the system specs but i'll write it here just in case.

Windows 7 Ultimate 64-bit Service pack 1 /OS
Intel Core i7 930 @ 2,8GHz /CPU
Asus P6X58D-E /motherboard
3x2GB (unsure of brand and speed) /memory
XFX Radeon HD 7850 Core Edition /graphicscard
2TB Seagate mechanical /harddrive

Thanks in advance and please let me know if you need additional info.

Arc · 02 Mar 2014

Hi zalgocykel.

The BSODs are caused by MotioninJoy simulate Xbox 360 controller (virtual Xinput device), and it is very common with the driver version you have installed.

Uninstall the driver and install an earlier version form Playstation 3 controller(Dualshcok 3 or Sixaxis) driver for windows | MotioninJoy.

Let us know the situation.
__________________________________________________

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10D, {5, 0, 1202, fffffa8007b2d720}

*** 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
---------

6: 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: fffffa8007b2d720, Reserved.

Debugging Details:
------------------


BUGCHECK_STR:  0x10D_5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  DS3_Tool.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from fffff88000f1ca46 to fffff80003490bc0

STACK_TEXT:  
fffff880`0bbd37c8 fffff880`00f1ca46 : 00000000`0000010d 00000000`00000005 00000000`00000000 00000000`00001202 : nt!KeBugCheckEx
fffff880`0bbd37d0 fffff880`07f1763a : fffffa80`05faac60 fffffa80`05faad60 00000000`00000004 00000000`00000001 : Wdf01000!imp_WdfUsbTargetDeviceSendControlTransferSynchronously+0x8a
fffff880`0bbd3af0 fffffa80`05faac60 : fffffa80`05faad60 00000000`00000004 00000000`00000001 fffff880`0bbd3c20 : MijXfilt+0x363a
fffff880`0bbd3af8 fffffa80`05faad60 : 00000000`00000004 00000000`00000001 fffff880`0bbd3c20 fffff880`0bbd3b70 : 0xfffffa80`05faac60
fffff880`0bbd3b00 00000000`00000004 : 00000000`00000001 fffff880`0bbd3c20 fffff880`0bbd3b70 fffff880`0bbd3b38 : 0xfffffa80`05faad60
fffff880`0bbd3b08 00000000`00000001 : fffff880`0bbd3c20 fffff880`0bbd3b70 fffff880`0bbd3b38 00000000`00000000 : 0x4
fffff880`0bbd3b10 fffff880`0bbd3c20 : fffff880`0bbd3b70 fffff880`0bbd3b38 00000000`00000000 fffffa80`07af6a40 : 0x1
fffff880`0bbd3b18 fffff880`0bbd3b70 : fffff880`0bbd3b38 00000000`00000000 fffffa80`07af6a40 00000000`00000040 : 0xfffff880`0bbd3c20
fffff880`0bbd3b20 fffff880`0bbd3b38 : 00000000`00000000 fffffa80`07af6a40 00000000`00000040 00000000`00000000 : 0xfffff880`0bbd3b70
fffff880`0bbd3b28 00000000`00000000 : fffffa80`07af6a40 00000000`00000040 00000000`00000000 00000001`00000001 : 0xfffff880`0bbd3b38


STACK_COMMAND:  kb

FOLLOWUP_IP: 
MijXfilt+363a
fffff880`07f1763a ??              ???

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
---------

6: kd> lmvm MijXfilt
start             end                 module name
fffff880`07f14000 fffff880`07f36000   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