BSOD when playing USB controller games.

Tashikie · Jun 22, 2012

Windows 7 x64 OEM
HP p6754y, bought it at Best Buy early 2011
AMD Athlon II X4 640 Processor, 3.00 GHZ

Hey guys, I'm ripping my hair out trying to figure this out. I'm guessing it's a USB problem, because it only happens when I play some old school emulator games with a USB controller. Regular mouse and keyboard games don't crash at all. The BSOD could happen anywhere from 20 seconds into the game to 20 minutes, but it's guaranteed to happen. I already tried the USB general fix for problems link and it's still happening. Any help would be VERY appreciated at this point. Here's my information.

usasma · Jun 24, 2012

I'm late for work - but we've seen issues with the USB XBox controller drivers.
There are not updates available, so the "test" is to uninstall the software and remove the device from your system.

If the BSOD's stop, then that's the cause.
The fix it to not install the USB XBox controller.

usasma · Jun 25, 2012

This device is disabled:

The device, Multimedia Video Controller, is disabled. If this device is no longer used it may be intentionally disabled. The Plug and Play ID for this device is PCI\VEN_BDBD-DEV_A117-SUBSYS_A117BDBD-REV_00\4-3B43D722-0-0038

If it's not needed, please enable it - then uninstall it's software - then remove it from the system (or disable it in the BIOS)
If it is needed, please enable it and update it's software/drivers. Re-disable it if you want to - after you've updated it.

SP1 isn't installed, please do the following:

Installing Windows 7 Service Pack 1
1. Visit the PC manufacturer's website and update ALL drivers. DO NOT use Windows Update or the "Update drivers" function of Device Manager.
2. Check Device Manager for any unknown/disabled devices - if there are unknown/disabled devices, fix them with the latest drivers from the device manufacturer's website (not the PC Manufacturer)
3. Visit Windows Update and get all updates (may take repeated visits)
4. Visit Windows Update and get Service Pack 1 (usually under Important Updates). Read these notes for installing SP1: Steps to follow before you install Windows 7 SP1 and Windows Server 2008 R2 SP1 from the Microsoft Download Center
NOTE: For Vista, read these notes:

Read these notes for installing Vista SP1: Learn how to install Windows Vista Service Pack 1 (SP1)
Read these notes for installing Vista SP2: Learn how to install Windows Vista Service Pack 2 (SP2)

Click to expand...

5. Visit Windows Update and get any other available updates. May take repeated visits, but keep it up until you get several "Windows is updated" results.
If you're having difficulties with installing a Service Pack, please use the SURTool from this link: What is the System Update Readiness Tool?
Also, check out this troubleshooting link from Microsoft: Troubleshoot problems installing Service Pack 1 (SP1) for Windows 7 and Windows Server 2008 R2

I have had limited success in installing updates/Service Packs when using a "clean boot". I suspect that I'm just bypassing the problem - and that it can come back to bite me in the butt later on.

Daemon Tools (and Alcohol 120% software) are known to cause BSOD's on some Win7 systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions).
Please uninstall both programs, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): DuplexSecure - FAQ

More to follow when the memory dumps are finished running.....

usasma · Jun 25, 2012

All of the memory dumps blame MotioninJoy simulate Xbox 360 controller (virtual Xinput device)
Please uninstall it.

Also blamed is the LibUSB-Win32 (whose drivers date from 2007). Please remove it also.

You also have AMD Overdrive installed - it causes BSOD's on some systems. Try this:

AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Win7 systems.

Please uninstall all AMD/ATI video stuff from Control Panel...Programs...Uninstall a program
Then, download (but DO NOT install) a fresh copy of the ATI drivers from Global Provider of Innovative Graphics, Processors and Media Solutions | AMD (in the upper right corner of the page)
Use this procedure to install the DRIVER ONLY: ATI video cards - DRIVER ONLY installation procedure

If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
Locate the AODDriver entry, right click on it and select "Uninstall". Reboot for changes to take affect.

Click to expand...

Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.

If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs

- Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html
- Info on how to troubleshoot BSOD's (DRAFT): http://www.carrona.org/userbsod.html
- How I do it: http://www.carrona.org/howidoit.html

3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Code:

[font=lucida console]
AODDriver2.sys        Tue Mar 06 04:55:00 2012 (4F55DEF4)
AODDriver2.sys        Wed Jun 15 04:38:35 2011 (4DF86F8B)
AtiPcie64.sys         Wed Mar 10 09:33:45 2010 (4B97ADC9)
AtihdW76.sys          Thu Feb 23 07:30:12 2012 (4F463154)
AtihdW76.sys          Tue Jun 07 06:34:39 2011 (4DEDFEBF)
MijXfilt.sys          Sat May 12 00:27:12 2012 (4FADE6A0)
PxHlpa64.sys          Mon Oct 17 10:29:34 2011 (4E9C3BCE)
Rt64win7.sys          Fri Sep 03 01:58:32 2010 (4C808E88)
Rt64win7.sys          Tue Aug 23 09:55:41 2011 (4E53B15D)
SmartDefragDriver.sys Fri Nov 26 04:29:40 2010 (4CEF7E04)
[DEL]a12t12s6.SYS          Fri Aug 07 09:30:20 2009 (4A7C2C6C)
a2pqbo3d.SYS          Tue Dec 27 17:30:45 2011 (4EFA4715)
a83rlgnp.SYS          Fri Aug 07 09:30:20 2009 (4A7C2C6C)
abjo4e3v.SYS          Fri Aug 07 09:30:20 2009 (4A7C2C6C)
abrhev3a.SYS          Fri Aug 07 09:30:20 2009 (4A7C2C6C)
admb30qt.SYS          Fri Aug 07 09:30:20 2009 (4A7C2C6C)
adv6r87i.SYS          Tue Dec 27 17:30:45 2011 (4EFA4715)
afljc8z6.SYS          Tue Dec 27 17:30:45 2011 (4EFA4715)
ahse9k7s.SYS          Tue Dec 27 17:30:45 2011 (4EFA4715)
[/DEL]amd_sata.sys          Fri Apr 15 14:37:14 2011 (4DA8905A)
amd_sata.sys          Thu Jun 16 15:07:44 2011 (4DFA5480)
amd_xata.sys          Fri Apr 15 14:37:17 2011 (4DA8905D)
amd_xata.sys          Thu Jun 16 15:07:47 2011 (4DFA5483)
amdiox64.sys          Thu Feb 18 10:17:53 2010 (4B7D5A21)
amdxata.sys           Fri Mar 19 12:18:18 2010 (4BA3A3CA)
[DEL]an7hrdqd.SYS          Fri Aug 07 09:30:20 2009 (4A7C2C6C)
anszomww.SYS          Fri Aug 07 09:30:20 2009 (4A7C2C6C)
atdjpnzs.SYS          Tue Dec 27 17:30:45 2011 (4EFA4715)
[/DEL]atikmdag.sys          Thu Apr 05 21:48:25 2012 (4F7E4B69)
atikmdag.sys          Thu Jul 28 17:29:03 2011 (4E31D49F)
atikmpag.sys          Thu Apr 05 21:10:44 2012 (4F7E4294)
atikmpag.sys          Thu Jul 28 16:54:10 2011 (4E31CC72)
[DEL]aucllvq0.SYS          Tue Dec 27 17:30:45 2011 (4EFA4715)
[/DEL]avgidsdrivera.sys     Fri Dec 23 07:05:21 2011 (4EF46E81)
avgidsfiltera.sys     Fri Dec 23 07:05:40 2011 (4EF46E94)
avgidsha.sys          Wed Apr 18 22:19:15 2012 (4F8F7623)
avgldx64.sys          Tue Feb 21 22:57:53 2012 (4F4467C1)
avgmfx64.sys          Fri Dec 23 07:08:12 2011 (4EF46F2C)
avgrkx64.sys          Mon Jan 30 22:11:41 2012 (4F275BED)
avgtdia.sys           Sun Mar 18 23:53:32 2012 (4F66ADBC)
[DEL]aw7seqvi.SYS          Fri Aug 07 09:30:20 2009 (4A7C2C6C)
ayg5upag.SYS          Tue Dec 27 17:30:45 2011 (4EFA4715)
ayprm633.SYS          Tue Dec 27 17:30:45 2011 (4EFA4715)
[/DEL]btwampfl.sys          Thu Mar 29 14:51:21 2012 (4F74AF29)
dtsoftbus01.sys       Fri Jan 13 08:45:46 2012 (4F10358A)
dump_amd_sata.sys     Fri Apr 15 14:37:14 2011 (4DA8905A)
dump_amd_sata.sys     Thu Jun 16 15:07:44 2011 (4DFA5480)
dump_storport.sys     Fri Apr 22 14:11:55 2011 (4DB1C4EB)
dump_storport.sys     Mon Jul 13 20:01:00 2009 (4A5BCABC)
hidbth.sys            Mon Jul 13 20:06:52 2009 (4A5BCC1C)
libusb0.sys           Tue Mar 20 06:33:00 2007 (45FFB85C)
lvrs64.sys            Fri Aug 19 05:25:38 2011 (4E4E2C12)
lvuvc64.sys           Fri Aug 19 05:26:11 2011 (4E4E2C33)
netr28x.sys           Wed Jul 21 07:39:22 2010 (4C46DC6A)
sptd.sys              Sat Mar 03 11:45:52 2012 (4F524AC0)
usbfilter.sys         Wed Dec 15 05:34:49 2010 (4D0899C9)
xusb21.sys            Wed Apr 08 10:28:44 2009 (49DCB49C)
[/font]

Code:

[font=lucida console]
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\062112-41652-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Thu Jun 21 21:31:21.424 2012 (UTC - 4:00)
System Uptime: 0 days 9:05:38.234
BugCheck 10D, {5, 0, 1202, fffffa8003ae2530}
*** 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 )
BUGCHECK_STR:  0x10D_5
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  DS3_Tool.exe
FAILURE_BUCKET_ID:  X64_0x10D_5_MijXfilt+363a
Bugcheck code 0000010D
Arguments 00000000`00000005 00000000`00000000 00000000`00001202 fffffa80`03ae2530
BiosVersion = 6.04
BiosReleaseDate = 09/07/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = p6754y
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\062112-46909-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Thu Jun 21 22:49:27.552 2012 (UTC - 4:00)
System Uptime: 0 days 0:08:15.363
BugCheck 10D, {d, fffffa8003ba3550, fffffa8003c4d6f0, fffffa80081ea9d0}
*** WARNING: Unable to verify timestamp for libusb0.sys
*** ERROR: Module load completed but symbols could not be loaded for libusb0.sys
Probably caused by : libusb0.sys ( libusb0+288a )
BUGCHECK_STR:  0x10D_d
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x10D_d_libusb0+288a
Bugcheck code 0000010D
Arguments 00000000`0000000d fffffa80`03ba3550 fffffa80`03c4d6f0 fffffa80`081ea9d0
BiosVersion = 6.04
BiosReleaseDate = 09/07/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = p6754y
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\062112-48984-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Thu Jun 21 23:01:38.973 2012 (UTC - 4:00)
System Uptime: 0 days 0:11:31.393
BugCheck 10D, {5, 0, 1202, fffffa80051b9830}
*** 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 )
BUGCHECK_STR:  0x10D_5
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  DS3_Tool.exe
FAILURE_BUCKET_ID:  X64_0x10D_5_MijXfilt+363a
Bugcheck code 0000010D
Arguments 00000000`00000005 00000000`00000000 00000000`00001202 fffffa80`051b9830
BiosVersion = 6.04
BiosReleaseDate = 09/07/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = p6754y
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\062112-52603-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Thu Jun 21 21:42:16.465 2012 (UTC - 4:00)
System Uptime: 0 days 0:10:15.275
BugCheck 10D, {5, 0, 1202, fffffa800421de70}
*** 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 )
BUGCHECK_STR:  0x10D_5
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  DS3_Tool.exe
FAILURE_BUCKET_ID:  X64_0x10D_5_MijXfilt+363a
Bugcheck code 0000010D
Arguments 00000000`00000005 00000000`00000000 00000000`00001202 fffffa80`0421de70
BiosVersion = 6.04
BiosReleaseDate = 09/07/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = p6754y
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\062112-55395-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Thu Jun 21 12:24:44.203 2012 (UTC - 4:00)
System Uptime: 8 days 2:23:22.539
BugCheck 10D, {5, 0, 1202, fffffa800968e470}
*** 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 )
BUGCHECK_STR:  0x10D_5
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  DS3_Tool.exe
FAILURE_BUCKET_ID:  X64_0x10D_5_MijXfilt+363a
Bugcheck code 0000010D
Arguments 00000000`00000005 00000000`00000000 00000000`00001202 fffffa80`0968e470
BiosVersion = 6.04
BiosReleaseDate = 09/07/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = p6754y
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\062112-62119-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Thu Jun 21 23:09:58.362 2012 (UTC - 4:00)
System Uptime: 0 days 0:07:47.782
BugCheck 10D, {5, 0, 1202, fffffa8006347a70}
*** 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 )
BUGCHECK_STR:  0x10D_5
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  DS3_Tool.exe
FAILURE_BUCKET_ID:  X64_0x10D_5_MijXfilt+363a
Bugcheck code 0000010D
Arguments 00000000`00000005 00000000`00000000 00000000`00001202 fffffa80`06347a70
BiosVersion = 6.04
BiosReleaseDate = 09/07/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = p6754y
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\062212-43009-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Fri Jun 22 01:36:16.384 2012 (UTC - 4:00)
System Uptime: 0 days 0:20:19.195
BugCheck 10D, {5, 0, 1202, fffffa800469d730}
*** 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 )
BUGCHECK_STR:  0x10D_5
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  DS3_Tool.exe
FAILURE_BUCKET_ID:  X64_0x10D_5_MijXfilt+363a
Bugcheck code 0000010D
Arguments 00000000`00000005 00000000`00000000 00000000`00001202 fffffa80`0469d730
BiosVersion = 6.04
BiosReleaseDate = 09/07/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = p6754y
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\062212-60153-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Fri Jun 22 00:38:28.873 2012 (UTC - 4:00)
System Uptime: 0 days 1:26:24.293
BugCheck 10D, {5, 0, 1202, fffffa80040a8010}
*** 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 )
BUGCHECK_STR:  0x10D_5
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  DS3_Tool.exe
FAILURE_BUCKET_ID:  X64_0x10D_5_MijXfilt+363a
Bugcheck code 0000010D
Arguments 00000000`00000005 00000000`00000000 00000000`00001202 fffffa80`040a8010
BiosVersion = 6.04
BiosReleaseDate = 09/07/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = p6754y
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

[/FONT]

Tashikie · Jun 25, 2012

It definitely was a controller issue, I uninstalled everything related to MotionJoy and am using a different controller all together and that seemed to do the trick. Thanks man, I appreciate it.

usasma · Jun 25, 2012

Glad to hear that it worked for you!

Happy gaming!!!

BSOD when playing USB controller games.

Tashikie

New member

My Computer

usasma

Mr. Cranky Pants

My Computer

usasma

Mr. Cranky Pants

My Computer

usasma

Mr. Cranky Pants

My Computer

Tashikie

New member

My Computer

usasma

Mr. Cranky Pants

My Computer