O/C increments

[Krumm]

After spending hours researching overclocking whilst waiting for parts to arrive, I still have no clear idea of how many mhz on the fsb I need to go up each time. I was thinking about 5-10mhz each time. Would anyone take big steps, or is it strictly just small ones?

I was also wondering how much benchmarking to use after each increase. Obviously I don't want to do a 12 hour othos or prime95. What tool do you use to benchmark after a small increase? Do I even need to test every time?

Specs are in sig, although the Gigabyte board is soon to be replaced with a p5k deluxe.

[oralpain]

I start at whatever I think the components can handle, then adjust from there.

With my E2140s I started with 350MHz FSB (stock is 200) out of the box, then I went up in 5-10 MHz increments.

[Oobie-]

http://forums.hexus.net/hexus-hardwa...beginners.html

Best to do it in small steps. I have gone in a 30+ step and it was fine, purely because I have done it before and I knew my system limitations/setup.

[GSte]

Orthos is great for testing, usually if it's gonna fail I find it does within 30 minutes, then once you've got what you think is a solid OC then you can give it 4-8hours to be certain, although in everyday use you're unlikely to be stressing the system 100% for such periods of time.

[Krumm]

Ok thanks alot, I'll have a go from 333 to 350 at the start and then go up in steps of 20 until 400. after that i'll raise the ram and fsb by 10 until it reports errors on benchys. That's the ideal situation, and ofc it won't work or i will get a bad o/c. That's my luck. I've been through 2 faulty motherboards and had a broken psu already .

[Hunain]

If it helps, sometimes you boot up fine and orthos runs fine too for around 30 mins, but you still get to know that the overclock needs more juice, more voltage for that FSB, when I boot up and windows starts up, I get minor flickering, the screen quivers just a bit at the start..maybe thats just me

Anyways, you can go to around 350 without worrying, after that keep increasing your FSB in increments of 10 untill you crash on Orthos or OCCT in 5 minutes, then increase voltage up, then run, keep doing that untill you dont crash in 5 minutes, then you can stress it for hours, if it crashed, give more voltage and then stress, this way you will find a stable overclock faster, IMO.

To put it again, what I do is that I aim for an overclock, lets say 2.3 Ghz, I increase FSB directly to correspond 2.3, run OCCT, if my CPU is very under-volted so to say, it will crash either under 10 seconds, or in 5 minutes. If it does, I just keep increasing the voltage till it does not, then stress it for long, and you will find the perfect combo sooner. I DO NOT KNOW IF THIS IS A SAFE WAY, I DO IT AND IT WORKS, PERHAPS SOMEONE ELSE CAN COMMENT ON THIS, I WOULD NOT LIKE TO BE HELD RESPONSIBLE IF YOU MELT YOUR CPU WITH THIS METHOD

[GSte]

Take it easy with the voltages, that's the CPU killer. Also, I wouldn't bother with the RAM, keep that low, just concentrate on the CPU until you reach your max OC then worry about the RAM later, otherwise you'll have to start trying to figure out whether it's the RAM or CPU that's failed, and not only will it confuse things, but in performance terms the RAM speed matters nowhere near as much as the CPU. Would be interested in your results too.

[arthurleung]

I usually just push speed up 10% at a time, and drop 5% when I hit the wall
(Same for undervolting, 10% at a time )

Just to get a general idea about what you CPU can do. My machines runs 7x24 doing encoding so I don't need the absolute top speed.

Getting error out of a 24 hours encoding session for the extra 5% speed is not really worth it.