Solved BSOD when 360 controller plugged in

[Kandur]

I recently bought a wired 360 controller (Microsoft brand). I've used one on my old computer before with no issues but this one crashes this computer every time. I've tried installing and uninstalling the Microsoft driver from their website, as well as Motionjoy, uninstalling Daemon Tools and stopping automatic drive installation all to no avail. Here's the report from when the computer restarts:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: 0000000000000000
BCP3: FFFFF880031B99C8
BCP4: FFFFF880031B9220
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

I've attached the crash report from minidump and system health report. I appreciate any and all help.

 

[smarteyeball]

Crash dump is showing MijXfilt.sys to be the offending file, part of motionjoy

 

[Kandur]

So...I deleted MijXfilt.sys for the second time. I've done this before. I restarted the computer and plugged in the controller, this time no BSOD but the computer won't recognize the controller. I install driver from Microsoft and plug in the controller again and here comes the BSOD again. I check and MijXfilt.sys is back. I delete it and try my controller again. This time the green light ring flashes on for a second, turns off and still won't work. Suggestions?

 

[zigzag3143]

So...I deleted MijXfilt.sys for the second time. I've done this before. I restarted the computer and plugged in the controller, this time no BSOD but the computer won't recognize the controller. I install driver from Microsoft and plug in the controller again and here comes the BSOD again. I check and MijXfilt.sys is back. I delete it and try my controller again. This time the green light ring flashes on for a second, turns off and still won't work. Suggestions?

Just in passing. Do what smarteyeball suggests first if that doesnt resolve the issue it is related to a memory exception and these tests will verify your ram and find the driver.


These crashes were caused by memory corruption (probably a driver).
Please run these two tests to verify your memory and find which driver is causing the problem.
If you are overclocking anything reset to default before running these tests.
In other words STOP!!!


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



2-Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[JMH]

I suggest that it will be beneficial if you also attend to this...

Please remove any CD visualization programs such as Daemon Tools and Alcohol 120%.

They use a driver, found in your dmp, called sptd.sys, that is notorious for causing BSODs.

Use this SPTD uninstaller DuplexSecure - Downloads DuplexSecure - FAQ

On completion you can use this Freeware in its place:

MagicISO Virtual CD/DVD-ROM (MagicDisc)

Using MagicISO to create ISO image files

 

[Kandur]

I suggest that it will be beneficial if you also attend to this...

Please remove any CD visualization programs such as Daemon Tools and Alcohol 120%.

They use a driver, found in your dmp, called sptd.sys, that is notorious for causing BSODs.

Use this SPTD uninstaller DuplexSecure - Downloads DuplexSecure - FAQ

On completion you can use this Freeware:

MagicISO Virtual CD/DVD-ROM (MagicDisc) in its place

Using MagicISO to create ISO image files

Already tried this. I've been scouring forums for hours and trying all kinds of tips but no luck yet. Might try zigzag's suggestion but I'll have to wait for a day I have plenty of time.

 

[Kandur]

I figured it out. After more forum scrounging I check my C:\Windows\System32\DriverStore\FileRepository folder and found a mijxinput file even though I had already deleted motion joy. After adjusting the system permissions I deleted this file, installed my controller and this time no MijXfilt.sys. Now I can finally use my Microsoft controller with my Microsoft OS after only 4 days. Hope this can help someone else.

 

[JMH]

Thanks for reporting back.
Safe surfing...