Solved BSOD while playing games.

[Shardx1]

Since I use a PS3 controller with my laptop to play most games, I've had to install the unsigned "MotioninJoy" driver for the controller, test sign it myself and run my laptop in Test mode all the time. For a while I had no problems, but then I started getting BSOD's like nobody's business, so I restored to the factory image (twice). It's recently become more important that I protect the files on here. That said, I had two BSODs occur two days in a row (both while playing games, albeit different ones), and two nights ago I had the "noise" that usually accompanies a BSOD while I'm playing, but no blue screen.

From the dump I'm posting, is it just the ps3 driver that's causing my BSODs, or is there another problem?

All help is appreciated.

EDIT: I've also had a problem where Windows simply hangs for an extended period of time, ranging from <1 minute to half an hour. i.e., all programs become unresponsive, parts of the interface freeze when I try to use them (start button, dock, task bar), etc. Is there a possibility that this is related?

 

[Jonathan_King]

Looks like the crash was caused by DirectX. Try updating your sound and video card drivers.

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


Loading Dump File [C:\Users\Jonathan\Desktop\033010-20732-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
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a61000 PsLoadedModuleList = 0xfffff800`02c9ee50
Debug session time: Tue Mar 30 23:04:33.020 2010 (GMT-4)
System Uptime: 0 days 0:30:28.846
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
.....
Unable to load image \SystemRoot\system32\DRIVERS\xusb21.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for xusb21.sys
*** ERROR: Module load completed but symbols could not be loaded for xusb21.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88001d60a03, fffff88002df54f8, fffff88002df4d50}

*** WARNING: Unable to verify timestamp for MijXfilt.sys
*** ERROR: Module load completed but symbols could not be loaded for MijXfilt.sys
Probably caused by : xusb21.sys ( xusb21+2a03 )

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

1: 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: fffff88001d60a03, The address that the exception occurred at
Arg3: fffff88002df54f8, Exception Record Address
Arg4: fffff88002df4d50, 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: 
xusb21+2a03
fffff880`01d60a03 488b01          mov     rax,qword ptr [rcx]

EXCEPTION_RECORD:  fffff88002df54f8 -- (.exr 0xfffff88002df54f8)
ExceptionAddress: fffff88001d60a03 (xusb21+0x0000000000002a03)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000

CONTEXT:  fffff88002df4d50 -- (.cxr 0xfffff88002df4d50)
rax=fffffa80069c1c00 rbx=fffffa80069bcbc0 rcx=0000000000000000
rdx=fffffa80069c1c00 rsi=fffffa80069c1c00 rdi=fffffa80069bcbc0
rip=fffff88001d60a03 rsp=fffff88002df5730 rbp=0000000000000020
 r8=0000000000000020  r9=000000000000100a r10=0000057ff964b768
r11=fffff88002df5718 r12=0000000000000000 r13=fffffa80069c0d90
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
xusb21+0x2a03:
fffff880`01d60a03 488b01          mov     rax,qword ptr [rcx] ds:002b:00000000`00000000=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  NULL_DEREFERENCE

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

EXCEPTION_PARAMETER2:  0000000000000000

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d090e0
 0000000000000000 

FOLLOWUP_IP: 
xusb21+2a03
fffff880`01d60a03 488b01          mov     rax,qword ptr [rcx]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffffa8006796018 to fffff88001d60a03

STACK_TEXT:  
fffff880`02df5730 fffffa80`06796018 : fffffa80`04ff51a0 fffffa80`04ff0000 fffffa80`069c2060 fffffa80`069bcbc0 : xusb21+0x2a03
fffff880`02df5738 fffffa80`04ff51a0 : fffffa80`04ff0000 fffffa80`069c2060 fffffa80`069bcbc0 fffff880`01d60c79 : 0xfffffa80`06796018
fffff880`02df5740 fffffa80`04ff0000 : fffffa80`069c2060 fffffa80`069bcbc0 fffff880`01d60c79 00000000`00000020 : 0xfffffa80`04ff51a0
fffff880`02df5748 fffffa80`069c2060 : fffffa80`069bcbc0 fffff880`01d60c79 00000000`00000020 fffff880`00ef0130 : 0xfffffa80`04ff0000
fffff880`02df5750 fffffa80`069bcbc0 : fffff880`01d60c79 00000000`00000020 fffff880`00ef0130 fffffa80`069c0e60 : 0xfffffa80`069c2060
fffff880`02df5758 fffff880`01d60c79 : 00000000`00000020 fffff880`00ef0130 fffffa80`069c0e60 fffffa80`069c21b0 : 0xfffffa80`069bcbc0
fffff880`02df5760 00000000`00000020 : fffff880`00ef0130 fffffa80`069c0e60 fffffa80`069c21b0 fffffa80`069b4890 : xusb21+0x2c79
fffff880`02df5768 fffff880`00ef0130 : fffffa80`069c0e60 fffffa80`069c21b0 fffffa80`069b4890 fffff880`00e840dd : 0x20
fffff880`02df5770 fffffa80`069c0e60 : fffffa80`069c21b0 fffffa80`069b4890 fffff880`00e840dd 00000000`00000000 : Wdf01000!FxDevice::m_PriorityBoosts+0x14a0
fffff880`02df5778 fffffa80`069c21b0 : fffffa80`069b4890 fffff880`00e840dd 00000000`00000000 fffff880`766f4900 : 0xfffffa80`069c0e60
fffff880`02df5780 fffffa80`069b4890 : fffff880`00e840dd 00000000`00000000 fffff880`766f4900 fffffa80`06796000 : 0xfffffa80`069c21b0
fffff880`02df5788 fffff880`00e840dd : 00000000`00000000 fffff880`766f4900 fffffa80`06796000 fffffa80`069c21b0 : 0xfffffa80`069b4890
fffff880`02df5790 fffff880`00ea122b : fffffa80`069c1020 00000000`00000000 fffffa80`04ff5050 fffff880`00000000 : Wdf01000!FxUsbPipeContinuousReader::_FxUsbPipeRequestComplete+0x65
fffff880`02df5810 fffff880`00e77c9b : fffffa80`069b4890 fffffa80`069b4890 fffffa80`069b48a0 fffffa80`0597c901 : Wdf01000!FxRequestBase::CompleteSubmitted+0x177
fffff880`02df5890 fffff880`00e77dc4 : fffffa80`06974e00 00000000`00000001 00000000`00000000 00000000`00000001 : Wdf01000!FxIoTarget::RequestCompletionRoutine+0x1cb
fffff880`02df5900 fffff800`02abd935 : fffffa80`055890a0 fffff880`009ea000 fffff880`009e9180 00000000`00006bd0 : Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x3c
fffff880`02df5930 fffff800`02ad5516 : fffffa80`069c1e53 00000000`00000000 00000000`00000000 fffffa80`069c1c60 : nt!IopUnloadSafeCompletion+0x55
fffff880`02df5960 fffff880`00e9aa52 : 00000000`00000000 fffffa80`06842600 00000000`00000001 00000000`00000000 : nt!IopfCompleteRequest+0x3a6
fffff880`02df5a40 fffff880`00e8b13e : fffffa80`069c1c60 00000000`00000001 fffffa80`05b27300 fffffa80`069c1c60 : Wdf01000!FxRequest::CompleteInternal+0x646
fffff880`02df5af0 fffff880`01d5242b : fffffa80`06974e70 fffffa80`06974e70 00000000`00000000 00000000`00000002 : Wdf01000!imp_WdfRequestCompleteWithInformation+0x1aa
fffff880`02df5b60 fffffa80`06974e70 : fffffa80`06974e70 00000000`00000000 00000000`00000002 0000057f`f968b188 : MijXfilt+0x842b
fffff880`02df5b68 fffffa80`06974e70 : 00000000`00000000 00000000`00000002 0000057f`f968b188 fffffa80`042e0008 : 0xfffffa80`06974e70
fffff880`02df5b70 00000000`00000000 : 00000000`00000002 0000057f`f968b188 fffffa80`042e0008 00000000`00000000 : 0xfffffa80`06974e70


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  xusb21+2a03

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: xusb21

IMAGE_NAME:  xusb21.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  49dcb49c

STACK_COMMAND:  .cxr 0xfffff88002df4d50 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_xusb21+2a03

BUCKET_ID:  X64_0x7E_xusb21+2a03

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

 

[usasma]

In addition, I'd also suggest removing these 2 drivers because of their presence in the stack text:
xusb21.sys - most likely a driver for an XBox USB wireless controller
MijXfilt.sys - MotioninJoy Virtual Xinput device Filter Driver (most likely associated with the xusb21.sys driver also)

Remove the programs associated with these drivers - and see if that stops the BSOD's.

 

[Shardx1]

In addition, I'd also suggest removing these 2 drivers because of their presence in the stack text:
xusb21.sys - most likely a driver for an XBox USB wireless controller
MijXfilt.sys - MotioninJoy Virtual Xinput device Filter Driver (most likely associated with the xusb21.sys driver also)

Remove the programs associated with these drivers - and see if that stops the BSOD's.

Those would be two of the drivers used with the PS3 controller, so I guess my suspicions were correct.

Thanks to both of you for your help, updating the drivers + removing the MotioninJoy ones now.