Trying To Push My 4600x2 to 2.7

Associate
Joined
5 Feb 2006
Posts
83
Hi all, posted something similar a week or so ago, but a few more questions needed! at the moment im @2.6 rock solid. idle 34 degs, max under prime on each core 50deg. Bios vcore is set to startup, but with the +6.6% option selected. fsb is at 217. mem on a div @ 2,3,2,5 1t (twin2048pc3200c2pt) (173=346ddr).
I can take the machine to 220 fsb with one degrees added on both idle and full. I need to hit 225 to reach 2.7 speed, but anything over 220 and the machine fails to boot into windows, logo appears then just resets. Will the jump to +9.9% from +6.6% solve? if so what are my temps likely to increase to? and would the temps still be safe for this processor?
colling is a SI-120 heat sink, Alaska 120mmfan, Arctic Silver5, Kandalf case.
Motherboard is MSI Neo 4 Platinum.

Thanks In advance
Ant.............
 
I've got my 4200+ up to 2.7 and it's not too hot, 52C under full load (60's about the max from what I've heard). Mine's only stock stuff too. I had the same problem with mine not booting after 220fsb, then I slackened up the memory timings to the point at which it'd boot and set it back to 400mhz (for a speed of almost ddr500!)
 
yep thanks you two, changed to 9.9....2.7 reached. idle 37.........not ran prime, for what im doing ill never be putting the cpu under such load on each core. Super Pi ran with no errors, 3DMark05 (11868) went smoothly, peaked at 50 degs, Half Life 2 peaked at 51 degs, everything seems solid........these temps still ok? im happy if you are ????!!!!

Ant.......
 
woohoo !! it actually maxed at 48 degs in Half Life 2 (plyd for an hour or so)!! i reset the machine and tested again! very happy now i can join the 2.7 club!!

Thanks Again
Ant........
 
You should get 2.7 out of that quite easily, if it's unstable try slacker mem timings to get stable then tighten them. Alternatively run a divider to test if its your mem or CPU topping out
 
its ok richd, everything is ok @2.7...........im happy to stick with that, mems @180 (360) it didnt clock to well at stock timings, hence the divider to get cpu up, thought the tight timings make up for the reduced speed.
 
Back
Top Bottom