Need some guidance with OC'ing (first timer 2500k)

Toggle sidebar Toggle sidebar
H

heaver

Distinguished
Dec 30, 2009
12
0
18,510
First of all...I've read quite a bit of links, its like reading braile...Ima need some dumbing down haha

I have a 2500k on a Gigabyte z68ap-d3, a hyper 212 evo. My case is a Corsair Graphite 600T...also running an EVGA 550ti and Corsair xms3 1600 1.65v ram.

-So...I'm pretty positive about the airflow. Was hoping to get around 4.7 ghz...doable?
-Is my gpu decent for overclocking?
-Read some stuff about 1.65v and sandy bridge bla bla...can i still run it at 1600 at a lower voltage? do i need to?

With that said...I dunno anything about overclocking, those guides don't really helping...they talk too much and say too little.
Anywhere I can find what to disable and, given that the 2500k is pretty popular and so is the 212evo, straight out numbers (voltages) that I can just put on my BIOS and that's it, end of story? (Again, I'm positive about my airflow)..
Any other sugestions that don't involve testing?
 
Sort by date Sort by votes
G

Guest

Guest
Well, to start with you need to get into your bios and find "jumperfree" or "cpu" settings.

You have a 2500k which means that your multiplier is unlocked, as well as your fsb. You increase your multiplier by 0.5X and then reboot.

At this point comes the not-so addictive fun part, you need to download Prim95, or another stressing program, and Speedfan or HWmon to monitor the temperature. Stress it for 30 minutes to an hour, it should get no hotter than 55C.

Now you can repeat this until your system gets too toasty or it crashes. Once it gets toasty you can't really clock it further, but if it crashes from instabillity, you can bring the multi down to its highest stable point, and then try to increase the FSB, again, +1, then reboot and stress. Repeat until instable or too toasty.

At this point, you can either stick with your high clock, or you can push it further by adjusting voltages(not recommended). I don't know a lot about voltages, but I assume it is just like the FSB and Multi, you bump Vcore up a eency bit and see how many more Mhz you can squeeze out. Eventually you will hit a ceiling where no increase in Vcore will make the system more stable, this is the maximum limit and you cannot go past this as far as I know.

If your system gets unstable and you cant figure out why, try underclocking your ram, or lowering your PCIE bus frequency(keep it at 100mhz if you have that option).

You can skip the testing until your system gets unstable, then you can back it off a tad or keep pushing, which, requires the testing.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom