Legit Reviews

Alright so, I decided to change my Vcore from Auto on the board in my sig, to 1.3125 and bump the clock a bit.

Temps at Auto, dual F@H 52C @ 2.95Ghz mem at 4-4-4-7 1.8V

Temps at 1.3125 dual F@H 47C @ 3.04Ghz mem at 4-4-4-7 1.8V

Temps via CoreTemp ambients the same

Um, how is that possible.

because usually auto is a bit higher than the voltages needed to reduce the number of stability problems. many companies also do this with MHz as 266MHz FSB on auto is usually 270MHz on the desktop... Some call it benchmark cheating, but all seem to do it.

but here's the kicker. I couldn't run 3GHZ stable with it at auto. But I can run 3.04 Stable with the 1.3125. Just odd. Wish there was some program that actually read vcore right.

dicecca112 wrote:Wish there was some program that actually read vcore right.

Could always use a multi-meter and check it yourself if you knew the right places to check.

I could but that would involve effort. 3.3Ghz on 1.35 set in bios. No idea what it is actually. 3.4 wasn't stable. I think I might have a good chip here. Temps still at 47C load. We'll see how far she clocks.

dicecca112 wrote:I could but that would involve effort. 3.3Ghz on 1.35 set in bios. No idea what it is actually. 3.4 wasn't stable. I think I might have a good chip here. Temps still at 47C load. We'll see how far she clocks.

It does look like a good chip........keep oc'in......there's prolly alot more!

trying to keep the downtime on this rig at a minimum so I can overtake hainer. I lost a 600pointer at 60% done yesterday. But the oc from 2.95 to 3.3 has cut the 600pointer times by 2minutes. Went from 17min to 15min per frame and upped my benchmark from 11K to almost 16K. Overtake to hainer is down to 6 days. He's gonna have a very Beeker friendly sig come this time next week

dicecca112 wrote:He's gonna have a very Beeker friendly sig come this time next week

LOL