BSOD when dealing with controllers

I have uploaded the SF_Diagnostic_Tool.exe .rar as asked.

Basically, my Win 7 BSOD back when I had my 360 controller hooked up to it.

Well I noticed that the controller's wires were weak at the connection, when I moved it, it would unplug and plug, and enough of that would cause the BSOD.

So I then moved to the ps3 motionjoy controller.

Everything was working fine till last night.

I went to try and play a game from my cd on an emulator...Which now freezes- it's the controller not working, it's not freezing.

In trying to get it to work on the emulator, it started to BSOD now.

So in short.

PS3 motionjoy now BSOD when messing with it, not sure if just on emulator or not... I will test this.

Messing with = connecting > turning on motionjoy > testing vibration - when I do this it makes the usb plugged in noise > Try to play on the emulator while it seems frozen? > BSOD.




Um not sure what else I should let you know.... if there's anything let me know.
I can stream up to a BSOD if wanted, XD.

SPECS: uploaded dxdiag.exe as well.

i5 cpu 650@3.20
HD 4870 radeon.



*update*
Tested playing Skyrim:

Turned on Motionjoy > Plugged in ps3 > tested vibration- do this to make sure it's working. > turned on Skyrim > moved around worked fine. > wiggled wire- lost connection to Ps3 > went back to motionjoy got controller back connected > went back into game moved around - BSOD.


For now I think it has to do with motionjoy, so I uninstalled it. but to make sure I'd like to see if anyone else can figure anything out?



*update #2*
I installed an older version of Motionjoy and it works fine, so it's gotta be the drivers or something to deal with that?


*note*
un related...but anyone know why my logitech G5 mouse keeps unconnecting and reconnecting when I'm doing something heavy, like playing games?

Hello neosky5k.

The BSOD is caused by MotioninJoy Virtual Xinput device Filter Driver (c:\windows\system32\drivers\mijxfilt.sys)

Code:

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

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

And it appears that the driver is the latest version.

Code:

fffff880`06962000 fffff880`06984000   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

But you check it yourself. Go to MotioninJoy simulate Xbox 360 controller(virtual Xinput device) | MotioninJoy and search for updates. If any update is available, apply it.

If no updates are available, either wait for another update release or use one wired controller there.

But, if an earlier version of the driver is working fine, use that one.

The mouse is getting disconnected, coz the Logitech SetPoint KMDF Mouse Filter Driver (c:\windows\system32\drivers\lmoufilt.sys) is also very old.

Code:

fffff880`0694e000 fffff880`06962000   LMouFilt   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\LMouFilt.Sys
    Image name: LMouFilt.Sys
    Timestamp:        Fri Sep 02 11:53:15 2011 (4E607653)
    CheckSum:         0001BEE5
    ImageSize:        00014000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it from http://www.logitech.com/en-in/support.

I think about Cloud in the same line

Your USB drivers are chipset drivers. In ASUSTeK Computer Inc. -Support- Drivers and Download CG5275 there is no chipset update, but there is one BIOS update, to version 0502. You may apply it, if you know all about BIOS updating.

Otherwise, considering using another mouse, if that one also behaving in the same way, think that there are some deeper issue. Let us know in that case.

Let us know about the advancements (or otherwise) of your BSOD issue :)

You are welcome mate.
Let us know for any further issue.