SOLVED Tired of BSOD.

[Xaiji]

Just made a new build recently, and get BSOD whenever I'm playing games. I've solved a couple of previous problems, but this one keeps plaguing me. It usually only happens when I'm playing WoW, but other games do it too, after awhile.

 

[TorrentG]

Hello and welcome.

Glad to hear you solved some previous issues.

1) AVG is simply notorious, especially here for you. Uninstall it in safe mode with the tool here:

http://windows7forums.com/blue-screen-death-bsod/50402-removal-tools-antivirus-software-drivers.html

It seems you already have MSE installed which is great. In the future, never install 2 antivirus at the same time.

2) Update your Saitek device driver:

SaiK8018 SaiK8018.sys Tue Jul 29 07:32:49 2008

http://www.saitek.com/uk/down/drivers.php

3) Update your Realtek lan driver:

Rt64win7 Rt64win7.sys Thu Feb 26 04:04:13 2009

RTL8111

4) Enjoy.

 

[Xaiji]

Just reinstalled video drivers, so we'll see if that helps any. oops, didn't see you replied already

 

[TorrentG]

No, the video driver was already the latest and you were having 0x3b errors.

But ya, complete those steps and I'm fairly sure you'll be well there.

If not, of course let me know. Please let me know how it's going in any case.

 

[Xaiji]

When I try to install the Saitek drivers, the program asks me to connect the controller, windows pick it up but the installer wont. Sounds like something I need to contact them with?

 

[TorrentG]

Extract the driver to a folder or run it to do so if it is an .exe.

Then copy the new SaiK8018.sys and paste it over the one at C:\Windows\System32\drivers

Reboot and check the device manager for the new date.

 

[Xaiji]

There we go, updated. We'll see how things go, thanks

 

[Xaiji]

Just happened again, I reran the AVG uninstall thing again in safe mode, it seemed to pick up a bit more than when I ran it the first time...?

 

[TorrentG]

The Saitek driver has not been updated.

SaiK8018 SaiK8018.sys Tue Jul 29 07:32:49 2008

I would uninstall the software, remove the game pad from the machine physically then reboot.

Check the device manager that it is gone. If not, uninstall there and check the box to delete the driver.

Now use the pc as much as possible. When it doesn't crash, you can be sure it was the cause here.

Out of curiosity, which gamepad or hardware do you have from them?

The driver is being unloaded with the crash. That fact and it's date make it the first culprit to remove.

Unloaded modules:
fffff880`055b9000 fffff880`055e2000   SaiH80C0.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00029000
fffff880`04e4c000 fffff880`04e57000   SaiBus.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000B000
fffff880`054e0000 fffff880`054e4000   SaiMini.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00004000
fffff880`05e00000 fffff880`05e71000   spsys.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00071000
fffff880`011dd000 fffff880`011eb000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000E000
fffff880`011eb000 fffff880`011f7000   dump_ataport
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000C000
fffff880`011f7000 fffff880`01200000   dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00009000
fffff880`03886000 fffff880`03899000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000

 

[Xaiji]

It's the Saitek Pro Gamer Command unit. I got it to replace the Belkin N52te, as it's not compatible with Win7. Which is odd, because when I first upgraded to 7, I just did a Vista upgrade, so all my programs/files xferred with it, and the belkin worked fine, but after getting a new HDD and doing a fresh install, the programming software would not detect the pad.

Now, the drivers, when I first plugged the pad into my pc, Windows 7 found drivers and I just used Xpadder to program the keys, as I'm impressed by the simplicity of that program, and I can customize my keybinds almost any way I like with game controllers, as some manufacturer software can sometimes be restricting on what commands you can map to which inputs. IE, I can map my WSAD keys to the joystick on the pad, whereas in the included software, I either haven't found it, or cannot do that. Anyway, sidetracked. When I downloaded and installed the drivers from Saitek's website, Xpadder would not pick up the keys as it would before. I'm re downloading the programming software from Saitek, but they must be running dial up as it's only downloading at 41kbps XD

EDIT: I forgot, also using an Eclipse III keyboard from them, but that's a new model and the gamepad is one of their older products, so I doubt it's the KB drivers. The KB was plug and play, but the LED volume bars would not change with the actual level, so I did have to install an additional driver for that functionality.

 

[TorrentG]

Ya, i just downloaded the driver install myself. It actually contains an older driver from 2007.

Simply because a company claims Windows 7 compatibility and provides drivers, does not mean they are well on Windows 7.

I would do as I advised. Completely eliminate the hardware and software from the system until you are sure one way or the other that crashes stop or do not.

 

[Xaiji]

Yeah, we'll find out. It's all uninstalled and stuff so we'll see what happens.

Just saddens me that more companies don't make products like this, they're really handy.

 

[Xaiji]

Oh, goodie. Played wow for an hour and it froze again :x

 

[TorrentG]

Navigate to C:\Windows\System32\drivers and delete

SaiK8018 SaiK8018.sys Tue Jul 29 07:32:49 2008

which is still present. Reboot. Try again...

Also, post a screen shot each of the CPU-Z spd and memory tabs.

 

[Xaiji]

Okay, I used device manager the first time, so dunno why that one was still there, anyway.

Just out of curiosity, I plugged the controller back in, let windows install it's own drivers, and SaiK8108.sys is no longer present, yet the controller works. Going to unplug it again till we find out the issue.

 

[TorrentG]

The problem is definitely incorrect RAM settings in the bios.

Go into the bios and Load the Optimized Defaults on the first page. Save.

Reboot and post a new screen shot of the memory tab.

Enjoy.

 

[Xaiji]

Here it is, I'll let you know.

Huh, failed, lemme crop it, maybe it's too big.

There we go

 

[TorrentG]

Congrats. You've fixed your machine. Install your Saitek driver and enjoy.

Keep us updated after some time to tell us the good news, if it remains well.

 

[Xaiji]

Awesome.

 

[Xaiji]

Been 3 days, only one crash, and that was WoW being stupid. No bluescreens or hard lockups. Thanks TorrentG.