Bitten once more by the OC bug
As you can all see in my sig, I run at 220 x 11 (2420MHz) usually. But what I never did was optimize the temperature of the CPU by playing with the voltage.. But I'm getting around to that now.
217 x 10.5 = 2280MHz, but check the screenshot for the required voltage. I basically work the FSB up 1MHz at a time with the nf7vcore program and then run tests. If it passes, I move it up another megaherz, and so on until it freezes. Then I go into the BIOS and set the last good FSB and increase the voltage by .025. Then I repeat the process.
The processor is currently at 38C full load.
217 x 10.5 = 2280MHz, but check the screenshot for the required voltage. I basically work the FSB up 1MHz at a time with the nf7vcore program and then run tests. If it passes, I move it up another megaherz, and so on until it freezes. Then I go into the BIOS and set the last good FSB and increase the voltage by .025. Then I repeat the process.
The processor is currently at 38C full load.
0
Comments
PS- Interesting process also, I'll keep it in mind if I get my hands on an nVidia board.
This chip is over two years old (Bought it on 8/12/2002 from newegg for $58 shipped); it's my baby, the Winbond BH5 of CPUs, kicking the collective asses of Bartons and Mobiles!
38C @ full load is a fantastic temp, whats cooling it?
Anyways, back on topic, is this the cpu that you burnt in for ages? If so is the goal to get it back up to it's norm operating speed (2420mhz) at the lowest possible voltage or to get to the highest possible speed at specific voltage/temp?
My basic goal is to once again return to 2420MHz with the lowest voltage and temperature I can stably find. The chip's upper limit is 2450MHz, so there isn't much else to shoot for. :\
Yeah. This CPU was burned in for 20 months to hit 2420.