Can overclocking corrupt the bios?

[wju425]

Hi gang.

I was running an xp1700 tbred A on asus a7v133 at 12.5 x 133 (xp2000) for a few months when the mobo alarm started going off. The specs in the bios were in range so I clocked it down to normal (11 x 133). I thought I fixed it till after a while the alarm will go off again. It's been driving me nuts when I couldn't figure out what's wrong. Yesterday I decided to flash my bios with the same version (1009) and the alarm hasn't gone off since. I suppose o/c can mess the bios up? Thx.

\o/ Billy

EDI: I just remembered my sound card sounded bad and reinstalling the drivers didn't work. I ended up using my (homemade) recovery disk (thanks god for that).

[JayMan]

I belive on the nforce2 motherboard there were problems with o/cing corrupting the BIOS. But they would just flat out stop working then...

Not sure what would have cause your problem, but i spose it is possible that it did cause a small corruption...

JayMan

[wju425]

I guess if it happens to the nforce2 then it can happen to the kt133a mobo.

My system's running really good at normal clock but better than before. Must be that the bios had a bad flash.

\o/ Billy

[nukes]

No, it was a design fault with the NForce2 boards, with boardmakers leaving off a jumper that was required by the reference design. Causing the BIOS chip itself to die. Not what you're describing.
It could be possible that the overclock did corrupt it, and its fixed now, but it isn't the same sort of thing as the nforce2 at all.

[wju425]

I see. Thanks for the tip.

\o/ Billy