Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Xbox 360 controller wired BSOD


20 Aug 2011   #1
qep

win 7 64 bit SP1
 
 
Xbox 360 controller wired BSOD

Hello everyone,
I just bought a xbox 360 controller wired via amazon.
After plugging it in there instantly appeared a blue screen:
Problemereignisname: BlueScreen
Betriebsystemversion: 6.1.7601.2.1.0.768.3
Gebietsschema-ID: 1031

Zusatzinformationen zum Problem:
BCCode: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: 0000000000000000
BCP3: FFFFF880031E0988
BCP4: FFFFF880031E01E0
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

also helpful when explaining the problem:
C:\Windows\Minidump\082011-23509-01.dmp
C:\Windows\Temp\WER-26488-0.sysdata.xml

i googled the issue and several threads came up but none solved my problem.
So i really hope some1 can help, wanna play fifa 11

Im using windows 7 64 bit SP1

My System SpecsSystem Spec
.

20 Aug 2011   #2

Windows 8.1 Pro x64
 
 

BSODs caused by MijXfilt.sys - MotioninJoy Virtual Xinput device Filter Driver, remove this software

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
You can use MagicDisc as an alternative.
Code:
sptd.sys        fffff880`010a4000    fffff880`011ca000    0x00126000    0x4ad24632    12/10/2009 00:55:14
Code:
*******************************************************************************
*                                                                             *
*                        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: fffff880031d2988, Exception Record Address
Arg4: fffff880031d21e0, 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: 
+2d21
00000000`00000000 ??              ???

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

CONTEXT:  fffff880031d21e0 -- (.cxr 0xfffff880031d21e0)
rax=fffffa8006dd4370 rbx=fffffa80040fbd20 rcx=0000057ff922bff8
rdx=0000000000000000 rsi=0000057ffbf043c8 rdi=0000057ff922bff8
rip=0000000000000000 rsp=fffff880031d2bc8 rbp=fffff800030262b8
 r8=fffff880071d6101  r9=fffffa80040fbd20 r10=fffffa8003b6a010
r11=0000000000000000 r12=fffffa8006a524c0 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 fffff800030b8100
 0000000000000000 

FOLLOWUP_IP: 
MijXfilt+2d21
fffff880`071c4d21 ??              ???

FAILED_INSTRUCTION_ADDRESS: 
+2d21
00000000`00000000 ??              ???

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff880071c4d21 to 0000000000000000

STACK_TEXT:  
fffff880`031d2bc8 fffff880`071c4d21 : fffffa80`040fbc30 00000000`00000000 00000000`00000001 fffffa80`00000000 : 0x0
fffff880`031d2bd0 fffffa80`040fbc30 : 00000000`00000000 00000000`00000001 fffffa80`00000000 00000000`00000031 : MijXfilt+0x2d21
fffff880`031d2bd8 00000000`00000000 : 00000000`00000001 fffffa80`00000000 00000000`00000031 fffffa80`06a524c0 : 0xfffffa80`040fbc30


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 0xfffff880031d21e0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_NULL_IP_MijXfilt+2d21

BUCKET_ID:  X64_0x7E_NULL_IP_MijXfilt+2d21

Followup: MachineOwner
---------
My System SpecsSystem Spec
Reply

 Xbox 360 controller wired BSOD




Thread Tools




Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 07:31 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33