CMOS Fail Error

cthulhuiscool

2[H]4U
Joined
Mar 15, 2006
Messages
3,069
My new rig has been seeing a fair number of crashes in games which tend to result in black screens with vertical grey lines appearing. At first I figured it was but gcard, but I tested that rigorously and had no issues whatsoever. I updated my bios and changed the hdd interface to ide and the issues went away for a little bit, but now they've come back but with a slightly different result. After the crash, when the computer boots the now says "CMOS error." Tried resetting default settings and reflashing the bios, but the errors still persist. What do you guys think is up, is the mobo shot or could something else be the culprit?

My mobo is a Biostar TZ77b.

It has resulted in the same kind of crash in the following games with no particular rhyme or reason (variable levels of system stress):
Bioshock
Rock of Ages
Battlefield Bad Company 2
Bittrip Runner
TF2
 
Last edited:
cmos battery is probably dying, if you have another motherboard laying around(doesn't matter if its 10 years old) grab the cmos battery out of it and swap it with the one in your board. see if that solves the problem. if that doesn't fix it then the boards probably bad or the bios chips dying.
 
this particular mobo doesnt use a battery for cmos, so reckon that means the chip's just bad? Could that account for the crashes I'm experiencing?
 
Could that account for the crashes I'm experiencing?

Doubtful. To me its more likely whatever is causing the crashes is the cause of the CMOS being reported as failing.
 
this particular mobo doesnt use a battery for cmos, so reckon that means the chip's just bad? Could that account for the crashes I'm experiencing?

? There is a standard cmos battery in the picture for this board right next to the 2 digit display? Is that wrong?

b20120313_4.jpg
 
It has resulted in the same kind of crash in the following games with no particular rhyme or reason (variable levels of system stress):

I would reset your ram down to auto and remove any overclock and run memtest86+ for 8 hours or more stopping on the first error. If that passes run IBT on maximum.
 
i was tripping I couldnt see it when opening my case so I just assumed it wasnt there... I derped.

Sometimes the errors also result in a weird artifacting frozen image, hard to explain I'll take a picture next time it occurs. Think ram could cause that? I'm not getting crashes outside of games, just in game.
 
Could be that, a bad overclock on the CPU, a bad video card, a bad motherboard ... We need to start eliminating things from the equation.
 
So I ran occt error checking on the gpu for an hr straight, no errors or anything which probably means that's in the clear.

Ran memtest ~1hr without error, that in the clear or should I run it overnight?

I'm not overclocking but it does have that turbo boost, could that derp it? Also are there any utilities for testing the cpu or mobo for errors?
 
I know it sounds unrelated but I had a similiar issue and it was actually related to a new IRST driver that had been released. Might want to give it a go.
 
An hour's probably ok, everytime I've had bad ram and run memtest it lights up like a christmas tree within minutes. But you could always try removing a DIMM and running a game, then swapping in the other DIMM, see if that crashes. Make sure the heat spreader is on all the way and making contact.
 
An hour's probably ok, everytime I've had bad ram and run memtest it lights up like a christmas tree within minutes. But you could always try removing a DIMM and running a game, then swapping in the other DIMM, see if that crashes. Make sure the heat spreader is on all the way and making contact.

Not necessarily the case. There were a few times in the DDR2 era where I've had computers giving problems, and Memtest86+ wouldn't pop up errors until near test #7 or #8 of a pass. At that point it would dump about 5 or 6 errors at a time. Replace the RAM and the PCs would work fine. I haven't run across that (or really, any bad RAM) in quite some time, but I personally let Memtest run for at least 3 full passes before I call it good.
 
Back
Top