New
#11
Alright. I'll start the memtests as soon as I find an empty USB. Is it really necessary to use an EMPTY USB key?
Alright. I'll start the memtests as soon as I find an empty USB. Is it really necessary to use an EMPTY USB key?
Yes, unless you dont mind loosing everything on the USB drive that you use, part of the process of making the drive boot able is formatting the drive, but what you can do is copy all of the stuff off of the USB drive, put memtest on the drive and then copy it back onto the drive if there is enough room left afterwards.
I did the memtest with 10 passes and it didn't find anything. I'll report back if I get another BSoD.
Lets hope that you dont have further BSOD problems, perhaps the clean reinstall of your display driver sorted things out.
Computer crashed while I was playing a game. It's hella slow by the way. Here's the newest dump.
It looks like your newest crash is being acused by the old Xbox USB controller:
Driver Reference Table - xusb21.sysCode:fffff880`02dd2ff8 fffff880`02625dd1Unable 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 xusb21+0x3dd1
looking at the time stamp we can see it is the problematic driver from 2009:
Please update the driver from here: Software Downloads | Microsoft HardwareCode:kd> lmvm xusb21 start end module name fffff880`02622000 fffff880`02632d80 xusb21 T (no symbols) Loaded symbol image file: xusb21.sys Image path: \SystemRoot\system32\DRIVERS\xusb21.sys Image name: xusb21.sys Timestamp: Wed Apr 08 10:28:44 2009 (49DCB49C) CheckSum: 00014BBB ImageSize: 00010D80 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
I actually use a program called "MotioninJoy" to play with my Playstation 3 controller. Windows installs a faulty driver so it doesn't work. The program basically overwrites that driver. Shouldn't be a problem though... Whelp, I got a BSoD again and I don't think it was the same problem.
According to the dump files it is your MotioninJoy driver that is now causing the BSOD:
Driver Reference Table - MijXfilt.sysCode:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {fffff880024a0638, 2, 8, fffff880024a0638} *** 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+1b638 ) Followup: MachineOwner ---------
You can update the driver here: MotioninJoy simulate Xbox 360 controller(virtual Xinput device) | MotioninJoy
It's happening again. Much worse now...