Frequent BSoD's, usually when playing games.

[zuiaki]

I'm getting BSoD's such as:

• 
  PFN_LIST_CORRUPT
  SYSTEM_SERVICE_EXCEPTION
  BAD_POOL_HEADER
  DRIVER_IRQL_NOT_LESS_OR_EQUAL
  MEMORY_MANAGEMENT
  CACHE_MANAGER
  *Most recently (and never seen before)* SYSTEM_EXIT_OWNED_MUTEX

I've done several scans with no luck whatsoever. I'm fairly certain that it doesn't have anything to do with Daemon Tools, seeing as I experienced BSoD's prior to installing. I've experienced problems with Windows Update - I couldn't install updates.

 

[Dsprague]

Hello zuiaki, I took a look through your dump files and a lot of them point to memory corruption, and hardware as the source of the problem. So please do the following:

Run memtest86+ for at least 8 passes: RAM - Test with Memtest86+
Tip: Do this over night it can take quite some time.


Run the system file checker:

SFC.EXE /SCANNOW
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the search box, right click on the cmd.exe and select "Run as adminstrator"
In the black window that opens, type "SFC.EXE /SCANNOW" (without the quotes) and press Enter.
Let the program run and post back what it says when it's done.

PLease also update the drivers for your Broadcom USB wireless adapter: Welcome to NETGEAR Support

And updated the drivers for your video card: Drivers | GeForce

 

[zuiaki]

I will do said things. Both my video card and adapter are up to date though... The only newer driver for my video card is in beta. *EDIT* Adapter wasn't up to date. *EDIT*

I wouldn't be shocked if it was due to faulty hardware, seeing as I've had my fair share of BSoD's. Back then they were caused by overheating though. If it turns out to be memory corruption and hardware being the root, what's your advice? Can my computer be saved with little to no money, or should I give up on this one and try acquiring a new PC?

The sfc-scan couldn't find any problems... Will scan again and report back when I've done the memtest.

 

[Dsprague]

Are you sure its beta? just had a quick look at the page for the newest driver for your graphics card and it does not appear to be beta: Drivers | GeForce

 

[zuiaki]

Definitely

 

[Dsprague]

IN that case it appears that your system is doing something rather odd with your display driver, as according to your Msinfo32 file, and according to the dump files the time stamp on the driver is Jan, 18 2013 a full month before that driver was released. So on that note, please uninstall the display driver and run through this tutorial to make sure that all traces of your old display driver are gone before reinstalling it:

Drivers - Clean Left over Files after Uninstalling

 

[zuiaki]

Should I uninstall everything nvidia related?

 

[Dsprague]

no just the display driver.

 

[zuiaki]

Okay I did that thing. Do you want me to upload something so you can check?

 

[Dsprague]

no for now test and see if you get the BSOD still.

 

[zuiaki]

Alright. I'll start the memtests as soon as I find an empty USB. Is it really necessary to use an EMPTY USB key?

 

[Dsprague]

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.

 

[zuiaki]

I did the memtest with 10 passes and it didn't find anything. I'll report back if I get another BSoD.

 

[Dsprague]

Lets hope that you dont have further BSOD problems, perhaps the clean reinstall of your display driver sorted things out.

 

[zuiaki]

Computer crashed while I was playing a game. It's hella slow by the way. Here's the newest dump.

 

[Dsprague]

It looks like your newest crash is being acused by the old Xbox USB controller:

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

Driver Reference Table - xusb21.sys

looking at the time stamp we can see it is the problematic driver from 2009:

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:        [COLOR=Red]Wed Apr 08 10:28:44 2009 [/COLOR](49DCB49C)
    CheckSum:         00014BBB
    ImageSize:        00010D80
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Please update the driver from here: Software Downloads | Microsoft Hardware

 

[zuiaki]

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.

 

[Dsprague]

According to the dump files it is your MotioninJoy driver that is now causing the BSOD:

*******************************************************************************
*                                                                             *
*                        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
---------

Driver Reference Table - MijXfilt.sys

You can update the driver here: MotioninJoy simulate Xbox 360 controller(virtual Xinput device) | MotioninJoy

 

[zuiaki]

It's happening again. Much worse now...

 

[Dsprague]

Please re-upload the file there seems to be something wrong with it