Windows 7: BSOD Crash With XBOX Controller

Nomadski · 08 May 2011

Hi,

Ive got a pretty stable system generally (few games crash anyway) but when I plug in my Xbox controller into my USB slot I get a BSOD. Have attached the required dump and system health check plus a screenshot of the actual BSOD.

Windows 7 Pro 64bit (Retail bought when Windows 7 first launched in UK, original install)
Intel C2D 8400 @ 3.0GHz
Ati 4870 1GB
Asus P5Q Pro
4GB RAM
1000W Coolermaster PSU
Coolermaster Cosmos S case /w 1x200mm Side Fan, 5x120mm Fans front top and rear.

I saw another thread regarding this issue so I uninstalled Daemon Tools as requested in that one, to no effect.

Thanks

zigzag3143 · 08 May 2011

Quote: Originally Posted by Nomadski

Hi,

Ive got a pretty stable system generally (few games crash anyway) but when I plug in my Xbox controller into my USB slot I get a BSOD. Have attached the required dump and system health check plus a screenshot of the actual BSOD.

Windows 7 Pro 64bit (Retail bought when Windows 7 first launched in UK, original install)
Intel C2D 8400 @ 3.0GHz
Ati 4870 1GB
Asus P5Q Pro
4GB RAM
1000W Coolermaster PSU
Coolermaster Cosmos S case /w 1x200mm Side Fan, 5x120mm Fans front top and rear.

I saw another thread regarding this issue so I uninstalled Daemon Tools as requested in that one, to no effect.

Thanks

Several problems

1-ASACPI.SYS a major cause of BSOD's in the 2005 rev.

The pre 2009 version of this driver is a known BSOD cause.

The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit" (it's about the 12th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).

2- your mijxfilt.sys driver (Related to MijXfilt.sys DS3 driver from MotioninJoy) caused all three of these remove it.

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\050811-31059-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`03054000 PsLoadedModuleList = 0xfffff800`03291e50
Debug session time: Sun May  8 13:25:48.327 2011 (GMT-4)
System Uptime: 0 days 0:02:13.982
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
....
Unable to load image \SystemRoot\system32\DRIVERS\MijXfilt.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for MijXfilt.sys
*** ERROR: Module load completed but symbols could not be loaded for MijXfilt.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, 0, fffff88002fe0988, fffff88002fe01f0}

Probably caused by : MijXfilt.sys ( MijXfilt+2d21 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: fffff88002fe0988, Exception Record Address
Arg4: fffff88002fe01f0, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
+16
00000000`00000000 ??              ???

EXCEPTION_RECORD:  fffff88002fe0988 -- (.exr 0xfffff88002fe0988)
ExceptionAddress: 0000000000000000
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000008
   Parameter[1]: 0000000000000000
Attempt to execute non-executable address 0000000000000000

CONTEXT:  fffff88002fe01f0 -- (.cxr 0xfffff88002fe01f0)
rax=fffffa8003a4a370 rbx=fffffa8003b47b00 rcx=0000057ffc5b5ff8
rdx=0000000000000000 rsi=0000057ffc4b85e8 rdi=0000057ffc5b5ff8
rip=0000000000000000 rsp=fffff88002fe0bc8 rbp=fffff800032695f8
 r8=fffff88006694101  r9=fffffa8003b47b00 r10=fffffa8007087c60
r11=0000000000000000 r12=fffffa8003a61a00 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
00000000`00000000 ??              ???
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000008

EXCEPTION_PARAMETER2:  0000000000000000

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032fc0e0
 0000000000000000 

FOLLOWUP_IP: 
MijXfilt+2d21
fffff880`06682d21 ??              ???

FAILED_INSTRUCTION_ADDRESS: 
+5cca952f030edc1c
00000000`00000000 ??              ???

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff88006682d21 to 0000000000000000

STACK_TEXT:  
fffff880`02fe0bc8 fffff880`06682d21 : fffffa80`03b47a10 fffff800`03300000 00000000`000007ff 00000000`00000030 : 0x0
fffff880`02fe0bd0 fffffa80`03b47a10 : fffff800`03300000 00000000`000007ff 00000000`00000030 00000000`00000031 : MijXfilt+0x2d21
fffff880`02fe0bd8 fffff800`03300000 : 00000000`000007ff 00000000`00000030 00000000`00000031 fffffa80`03a61a00 : 0xfffffa80`03b47a10
fffff880`02fe0be0 00000000`000007ff : 00000000`00000030 00000000`00000031 fffffa80`03a61a00 fffffa80`07087c60 : nt!PopAcquirePolicyLock+0x38
fffff880`02fe0be8 00000000`00000030 : 00000000`00000031 fffffa80`03a61a00 fffffa80`07087c60 fffff880`00e636fb : 0x7ff
fffff880`02fe0bf0 00000000`00000031 : fffffa80`03a61a00 fffffa80`07087c60 fffff880`00e636fb fffffa80`03b47a10 : 0x30
fffff880`02fe0bf8 fffffa80`03a61a00 : fffffa80`07087c60 fffff880`00e636fb fffffa80`03b47a10 00000000`00000000 : 0x31
fffff880`02fe0c00 fffffa80`07087c60 : fffff880`00e636fb fffffa80`03b47a10 00000000`00000000 fffffa80`07087c60 : 0xfffffa80`03a61a00
fffff880`02fe0c08 fffff880`00e636fb : fffffa80`03b47a10 00000000`00000000 fffffa80`07087c60 fffffa80`03b47a10 : 0xfffffa80`07087c60
fffff880`02fe0c10 fffff800`033be943 : fffffa80`03afd4e0 fffffa80`06f32200 fffffa80`039e0040 fffffa80`039e0040 : Wdf01000!FxWorkItem::WorkItemThunk+0x113
fffff880`02fe0c40 fffff800`030d1961 : fffffa80`06f32200 fffff800`0306298c fffffa80`54515750 00000000`00000000 : nt!IopProcessWorkItem+0x23
fffff880`02fe0c70 fffff800`033677c6 : fffff8a0`05844000 fffffa80`039e0040 00000000`00000080 fffffa80`0396d890 : nt!ExpWorkerThread+0x111
fffff880`02fe0d00 fffff800`030a2c26 : fffff880`009e9180 fffffa80`039e0040 fffff880`009f3f40 00000000`00001000 : nt!PspSystemThreadStartup+0x5a
fffff880`02fe0d40 00000000`00000000 : fffff880`02fe1000 fffff880`02fdb000 fffff880`02fe09b0 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  MijXfilt+2d21

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: MijXfilt

IMAGE_NAME:  MijXfilt.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ca69a22

STACK_COMMAND:  .cxr 0xfffff88002fe01f0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_NULL_IP_MijXfilt+2d21

BUCKET_ID:  X64_0x7E_NULL_IP_MijXfilt+2d21

Followup: MachineOwner
---------

Nomadski · 08 May 2011

Thanks ZigZag but unfortunately that didn't work.

I downloaded and installed that Asus file, and confirmed it is now signed 2009. I uninstalled Motionjoy and plugged the xbox controller in and it was ok.

Then I rebooted and tried again and got the BSOD. Even though I downloaded the official controller driver from Microsoft, I did notice in device control panel for the controller it was being controlled by MotionJoy even though that was removed??

I wonder if MJ hasnt been removed completely, or if they provide MS driver for their controller? I guess the latter is unlikely.

Any other suggestions?

Thanks

EDIT: I went back into the driver folder and mijxfilt.sys was still there. So I deleted it, reinstalled the Xbox driver from MS, rebooted. Checked driver folder, no mijxfilt.sys. So I plugged my controller in and it came up "installing device", after which it promptly BSOD'd again. After the reboot I checked and mijxfilt.sys was back in the driver folder.

Im assuming from this mijxfilt.sys is part of the MS controller driver??

If you need a new crash log, let me know.

mgorman87 · 08 May 2011

Quote: Originally Posted by Nomadski

Thanks ZigZag but unfortunately that didn't work.

I downloaded and installed that Asus file, and confirmed it is now signed 2009. I uninstalled Motionjoy and plugged the xbox controller in and it was ok.

Then I rebooted and tried again and got the BSOD. Even though I downloaded the official controller driver from Microsoft, I did notice in device control panel for the controller it was being controlled by MotionJoy even though that was removed??

I wonder if MJ hasnt been removed completely, or if they provide MS driver for their controller? I guess the latter is unlikely.

Any other suggestions?

Thanks

EDIT: I went back into the driver folder and mijxfilt.sys was still there. So I deleted it, reinstalled the Xbox driver from MS, rebooted. Checked driver folder, no mijxfilt.sys. So I plugged my controller in and it came up "installing device", after which it promptly BSOD'd again. After the reboot I checked and mijxfilt.sys was back in the driver folder.

Im assuming from this mijxfilt.sys is part of the MS controller driver??

If you need a new crash log, let me know.

It could be the driver that are being installed automatically are bad. I would uninstall the device, disable automatic driver install and then plug in the device and install the drivers you downloaded from MS.
Turn off Windows 7 Automatic Driver Installation

zigzag3143 · 08 May 2011

Unsure about motionjoy being part of MS driver but it is starting to sound hardware related. Does this only happen when plugging or unplugging? if you leave it plugged in all the time and reboot does it crash?

Nomadski · 09 May 2011

I turned off automatic driver install, and I found an article covering my exact problem with this driver on the MiJ website (link below for anyone interested). Found the last post very useful.

The issue was I uninstalled MiJ thru add/remove programs. Which didn't actually delete the driver. When I was plugging in my Xbox controller, Windows 7 was trying to use my MiJ driver and that caused some kind of conflict.

I had to reinstall MiJ, and with the PS3 connected right click it in device manager and uninstall driver plus checking delete driver.

Funnily enough when I rebooted that damn sys file was STILL in the driver folder, so I manually deleted it, reinstalled the official Xbox driver and plugged it in and so far it seems to be working fine.

Thanks to both of you who took the time to help me here, was really useful. Now if you can only offer some advice to make me suck less in games, that would be great!

Thanks again.

Link for MiJ issue - http://forums.motioninjoy.com/viewtopic.php?f=53&t=1070

Windows 7: BSOD Crash With XBOX Controller

BSOD Crash With XBOX Controller problems?