strange fix to an annoying BSOD

warpus

Sommerswerd asked me to change this
Joined
Aug 28, 2005
Messages
53,927
Location
Definitely not America
Ok, so I've had this annoying problem where my computer would reboot during games.. or anything that's 3d.. I would get like an hour of game time, at most, in ut3, and then it would just either BSOD or crash and reboot.

I posted my problem and my quest to resolve it on various forums, and I got like 50 different pieces of advice.. mostly shrugs and things like "yeah i have that problem too"

My specs:

4600+ dual core 64
8800gts 640
750 pc power cooling silencer PS
2 320gb sata 7200 drives running in raid-1
2gb of dual channel ram

Now.. I tested my ram with memtest86 and other memory testing tools and it checked out fine.. the PS is new, I bought it thinking that my problems were related to my old 550W PS.. and my 8800 was rma'd for the same reason, so that's new too.

I just played 1 hour of Crysis on high, with no slowdowns and no crashes
the same for UT3, but 4 hours

Wanna know what I did?

I changed the voltage on my RAM from 1.9V (default) to 2.1

There was one obscure comment on a forum from some guy who didn't even sound legit to try this.. and it works.. I have no idea why though.

I'm kind of hesitant to declare victory yet, because it's just such a strange fix... but hey, so far so good!

Any ideas why it worked?
 
Some memory modules need a higher voltage than that set by the motherboard automatically. Just another reason to read the manual and go through BIOS when you put in a new component.

What you actually did was most likely set the memory to what it should have been by default for your timings.
 
Some memory modules need a higher voltage than that set by the motherboard automatically. Just another reason to read the manual and go through BIOS when you put in a new component.

Well, my RAM didn't come with a manual at all.. the system was 100% stable too, when not running 3d games.

Something to do with my video card was making the 1.9 setting on the RAM inadequate.

How long did you run memtest for?

On systems that were almost stable (because of memory issues), I've had memtest go for ages before turning up errors. A standard run for me is 8 hours, if I want to be thourough, I'll let it go a full 24 hours.

I ran it for about 8-10 hours, maybe longer. I think i started the test before going to bed, or going to work, or something like that.

I also ran prime95 which didn't give me any errors after 3 hours.
 
I generally let prime95 run for at least 24 hours ( I did 48 when breaking in my newest computer ). As for memtest, its also generally 12 hours at least.
 
Is having to go from 1.9 to 2.1V one of the signs of dying RAM?

I'll run prime95 tonight again to see if it comes up with anything..

Not really. It sounds like the defualt setting on your motherboard caused you to underclock those particular memory sticks. Different ram runs on different voltages depending on frequency, latency and the cpu speed and if you use the wrong one the most common effect is a BSOD followed by a restart. What you experienced is exactly what happens when you overclock/underclock your ram or cpu and a limit is reached. I've run prime95 just fine for 24hrs only to see the first attempt at gaming immediately crash my system. This is very typical.
 
Yeah, right after I posted my solution to the forums I've been posting the problem to, people pounced on my post with posts like yours, but before that.. nothin.

I wasn't able to find any references to upping your ram voltage.. except for one.. out of hundreds.

So it's common but it appears as though many people haven't figured out this fix yet.
 
Yeah, right after I posted my solution to the forums I've been posting the problem to, people pounced on my post with posts like yours, but before that.. nothin.

I wasn't able to find any references to upping your ram voltage.. except for one.. out of hundreds.

So it's common but it appears as though many people haven't figured out this fix yet.

Probably because you weren't trying to overclock your cpu. Thats the most likely situation where someone would suggest that you adjust voltages. I failed to mention that when I experienced this I was overclocking my cpu.

If you are trying to assemble a stable system at recommended settings then voltage is typically adjusted until stability is achieve, especially with high end components such as low latency ram and a factory overclocked video card such as the one you are using. If I assumed you did the basics then I would probably look to the video card drivers first and throw you in the wrong direction.
 
Basics never involved updating RAM voltage, and I've put together a buncha systems over the years :)

Turns out OCZ RAM is picky.

Amateurs often get by without knowing the basics. Aside from being jealous of your hardware I'm kind of shocked that you think this isn't basic when you managed to select such fine components (pc power and ocz) that are ironically made to run at non-standards settings. This may help you get up to speed:

"Even with the most informed part selections, one can still run into snags when assembling a system. In fact, one of our previous guides recommended a motherboard and memory combination that didn't play nicely together, affecting system stability and even the ability to POST. Such issues are usually caused by a motherboard BIOS's defaults not setting the correct timings or voltage for the memory used in the system. Because it tends to adhere to base JEDEC standards, "value" RAM usually gets along with even the most obscure motherboards. However, enthusiast-oriented memory designed to run at nonstandard voltage or latency settings can be more problematic."

http://techreport.com/articles.x/13218

OCZ is good stuff, its definitely "enthusiast-oriented memory designed to run at nonstandard voltage or latency settings."
 
RAM was just never an issue.. It was always all plug n play.

I wouldn't call myself an amateur, but "enthusiast" is going a bit too far ;)

And yes, it is very nice being able to play Crysis on high settings without any slowdowns :).. FINALLY
 
Back
Top Bottom