*Official Retail G0 Q6600 Overclocking Thread*

[Zucker2k]

I hate Prime not showing the elapsed time without you stop it. You need to calculate it.

It does show; you'll need to look at the iterations... towards the end.

Orthos is Prime95 code, exactly. It is the enhanced GUI of Prime95.

Actually, Orthos has not been updated for a long time, so I don't think this statement is correct.

[chew*]

So far with my chip i'm managing 3.0 on stock volts with loadline calibration enabled.....cpu-z reports 1.192v as well as asus probe, VID for this particular cpu is 1.225 for reference.......this is with a stock cooler mind you........temps are between 50-60c loaded. I will continue to push it on stock volts till prime crashes.......

figured i'd update, apparently i had voltage set @ 1.125 oops...set it to 1.225 and vdroop is minimal it appears cpu-z reports 1.208 and pc probe reports 1.21..........currently priming at 3330 still on stock volts and stock HS

On a side note temps seemed to have gotten better with loadline calibration on and the actual vcore applied to the cpu.........

[jonny_ftm]

It does show; you'll need to look at the iterations... towards the end.



Actually, Orthos has not been updated for a long time, so I don't think this statement is correct.

Thanks for the hint on iterations. Yep, that way, Prime95 is easier to use as it is natively 4 cores compatible.

Otherwise, the algorithm in the mersene number calculation wasn't changed since the begining. Just solving bugs in some instances...

Anyway, just for all people to remember. At 400 FSB and above, the NB is a major limit on many boards. So, a test with OCCT in RAM mode is vital for your stability testing (not really related to the CPU though). Blend doesn't reveal the NB limitations well

Anyway, thanks for the Prime95 hint