a8n32-sli - cpu overvolting

8r0m4n

Distinguished
Oct 14, 2006
2
0
18,510
hey guys. i just got my new computer yesterday, but i ran into some problems. i booted up and i went into the bios. cpu fan was a little noisy, so i checked the temps, and voltages first..then i found out that the cpu voltage was 1.425 istead of 1.3v (x2 4200+). so i set the voltage manually to 1.3v, but it was still overvolting to 1.34. so i set it to 1.275v and than it was ok.

My question is: is this normal, or should i rma the mobo?

2nd question: could the cpu get damaged, while it was running on 1.425v for a few minutes?

3rd question: can i trust the bios? how do i know that it's running on 1.3v now?

thx...
 

shata

Distinguished
Dec 10, 2005
727
0
18,980
Um it does not have to be your motherboards fault. This is a sticky subject where i dont know alot about. I think the bottom line is when people push 1.5v on a good heatsink no it wont damage it. and 2nd the motherboard may be reading the voltage rong. 1.3 vs 1.425 isnt bad you will live.

I blew my amd64 3000+ at 2.6ghz with a vcore of 1.525v so dont worrie your fine.
 

endyen

Splendid
How do you know the chip voltage? Is the OPN code ADA4200IM****?
Most of thge newer x2 chips come with a ADAXXXIA opn. That means the voltage varies according to demand.
I wouldn't worry about 1.45 volts at bios screen. It would probably drop some as soon as you got busy. Asus vrms are not exactly famous for stable v-core.
You may find that your system is not stable with that voltage, since under load, the voltage goes down a little, and there is always a touch of fluctuation.
run a burn-in prog, like prime95 or sandra's burn-in. If you are good, be greatfull for the lower power usage.
 

8r0m4n

Distinguished
Oct 14, 2006
2
0
18,510
nevermind, it's all good now..just wondering why did the bios set the voltage to 1.425v, instead of 1.35v. i would understand if the bios would set 1.35, and than it would overvolt it to 1.425v, but it went straight to 1.425v...did it identify the cpu wrong or what? new bios didn't help...