Random BSOD

[bylly]

Hi, i just found about your forum and thought i'd give it a try at solving my year old problem with my rig.

The blue screens apear to be random, so far i've had win xp, vista and 7 installed on this system and they still apear so i guess it's not OS related. I've also changed my mobo, my ram and finally changed the hdd's (well not changed, but aded a 1 tb samsung and reinstalled win 7 fresh on this disk) - and the problem still persists.

Last night i installed my new hdd, put the OS on it, and didn't configure the RAID (i also have 2xwdaaks) in system manager, so in my computer i could only see the samsung on which i had the OS. I started Dead Space 2, got a crash to desktop, tried to open Win explorer, got the not responding message and then the BSOD. After the restart, it took about 20 secs for the mobo to detect each HDD.

I plan on disconecting the RAID entirely and see if that helps, but still i wouldn't know if it's the raid chip or one of the hdd's.

That's why I attach my zip here as stated by the rules and see if any of you can help

Thanks in advance.

 

[Maguscreed]

The first thing I notice is the time stamps on your logs , dumps, and files are all wrong. Mostly saying the year is 2038.
That incorrect date setting could be causing all kinds of messed up issues in and of itself.

 

[bylly]

I didn't know that, i forgot to set it right the last time i reinstalled the OS. But shouldn't windows update the time by itself?

LE: I hit update now, but it fails, i don't know why, anyway i corrected date and time, but i can asure you the blue screens happened before even though the time was right then.

 

[Maguscreed]

Your creative drivers are out of date... they are actually pre-win 7 from what I see in the dump. You shouldn't have any trouble going to their website and updating to something whql certified.

You have a strangely outdated direct x sys file loading on your machine as well.
Have you scanned for malware lately?

Anyhow, immediately you need to update all your creative related stuff. None of it is up to date for win 7.

GizmoDrv.SYS is also very old, though I'm having trouble figuring out why it would even be on your system. Gizmodrv.sys driver | What is Gizmodrv.sys file?

I could keep going on, but basically you have a lot of out of date drivers. It would probably be worth the time to update them.

I was going to go to msi and link you directly to the updated drivers for your motherboard but that doesn't seem to be possible.

Here's the link for your audigy update though. Creative Worldwide Support > Audigy 2

 

[bylly]

I didn't update the drivers as i didn't know there are newer ones for audigy, i will update the others as well. As i said, i had just fresh installed 7 and didn't install all those things. Nevertheless, it made no difference before, but i'll do what you suggested.

 

[Maguscreed]

Well using vista drivers in win 7 works sometimes... but not always.
I'm hoping to get some of the junk data out of the way, and possibly cure the problem. If not, it will at least give me a much shorter list should you get another crash dump.

 

[bylly]

Got an other error, i forgot to mention sometimes it's a Bsod followed by automatic restart, some other times it just freezes and i need to restart my self. I had just disconected the two hdd's that were in raid, and i got a freeze with a repeated sound (i was playing ds2). Now i will update the audigy drivers and see what happens. Strangley enough, the few last times i had problems, it was all in the first 5 minutes since starting the system.

LE: updated the audigy drivers - same problem crash with repeating sound in speakers.

So i guess it wasn't the wdaaks's fault, it must be something else, but what? I almost changed my whole system and can't get it to run stable. This is killing me!

 

[bylly]

Although more than a week passed since the last crash, the problem isn't solved. Here is the minudump and the xml generated after this last crash.

Can somebody please help me?