• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

~~~~~IMPORTANT SANDYBRIDGE OC INFO: Voltages & OC Guide!!~~~~~

Just last night put my new i5 parts together, and delighted with it so far. Running at stock it was more than capable of handling BF3 and hovered around 50-51 degrees with all fans on inaudibly low speeds :D

Not exactly sure what multiplier I'm tweaking - just using the Asus AI Suite for now, doing it all within windows while I establish some solid settings. Suspect it's the turbo because it was at 37x to start with... but it appears to get applied to all cores, which is confusing :P

Is there any particular reason why my vcore reading under load is consistently 0.1v above what I actually set? E.g. I currently have it set to 1.11 and get readings between 1.21 and 1.23. Obviously well within tolerance and I can manually compensate, but just feels a bit uncontrolled :)

Currently running primes at 4.4 GHz on ~1.22 vcore to establish a baseline. Hoping for a good bit of headroom beyond to give me something to fiddle over the weekend!
 
9 hours prime stable @4.4 with cpu-z reading 1.208-1.216 vcore - which means it seems to have dropped a little during the day for some reason. Still, this pleases me greatly as a starting point :)

Still mystified by VCCIO voltage, PLL, PCH, etc... just leaving them well alone for the moment!
 
What PSU have you got? Hope my 600W is up to it - Seasonic so hopefully be ok.

Actually it's a 3 year old Akasa Paxpower 460W xD

But I figure it as:
95W CPU overclocked, probably to about 120-130.
150W graphics card (6870).

Leaves me about 180 watts of headroom for motherboard, RAM, soundcard, and hard drives. Which they just will not consume. Never gets too hot, never generates low voltage numbers in any monitoring program :)
 
I see another 25K has bit the dust, lucky it lasted this long was experimenting with some hairy voltages compared to the guidelines!
 
Nice efficiency there Eddie :) My Killawatt shows that I'm pulling 90w from the wall at idle and 295w during a Furmark run. Happy with that. :)

Nice, that's a bit less than I'd expect even for a single GPU system... :)

Not sure about my at-the-wall draw; I used to have a UPS that could measure it - but then one day I had a power cut, the PC went off, and 2 seconds later the UPS clicked and started delivering. So I left it in the garage when I moved house :P
 
@Gibbo please can you up date your original thread as the info supplied on the ocuk website contradicts what you have written here and is sending mixed messages.

many thanks and thank you for starting this thread ;)
 
Ok, just trying to suss out one key question: when people talk about "safe" voltages (i.e. don't go over 1.35 or 1.38), does that take vdroop into account?

For instance, would it considered to be within these safe limits to key 1.42 into the BIOS if I knew that actually translated to 1.36 as shown in CPUZ due to vdroop?

Basically - is it BIOS-set or actually monitored load vcore that we're talking about?
 
Manual Voltage

Ok, just trying to suss out one key question: when people talk about "safe" voltages (i.e. don't go over 1.35 or 1.38), does that take vdroop into account?

For instance, would it considered to be within these safe limits to key 1.42 into the BIOS if I knew that actually translated to 1.36 as shown in CPUZ due to vdroop?

Basically - is it BIOS-set or actually monitored load vcore that we're talking about?

My understanding of manual voltage is that the manual voltage input becomes constant no voltage stepping! so I prefer to use voltage offset. With regards vdroop thats should be seen by monitoring core temp/cpuz voltages and making the necessary adjustments. My overall feeling about 1.42v is why risk it ;) some screenies btw my pc runs 24/7/365.

i72600k42Ghz-1.png
 
Last edited:
I always found DVID(Offset) far more unstable on my gigabyte board, idle bsods... Windows not booting... Instant BSOD in prime 95. But using Load Line Levels and Set volts it works perfectly.
 
sandybridge is the new q6600. I've just ordered mine, should be here tuesday or wednesday

Don't insult Sandybridge, it is way better than the q6600 as it really has no decent alternative. :P

Back in the day the Intel Core 2 were better choice for a lot of people. :)
Most games didn't use more than 2 cores so a faster 2 core CPU was a better option for a lot of gamers.

With Sandybridge the 4 core processors are faster than any 2 core alternative just with 2 cores active, so it is the best whatever number of cores are required. :)
 
My understanding of manual voltage is that the manual voltage input becomes constant no voltage stepping! so I prefer to use voltage offset. With regards vdroop thats should be seen by monitoring core temp/cpuz voltages and making the necessary adjustments. My overall feeling about 1.42v is why risk it ;) some screenies btw my pc runs 24/7/365.

Right. Thanks. I think I'm slowly getting to grips with all this new BIOS gubbins. Now using auto offset, and it's reading between 1.320 and 1.336v in CPUZ, which seems okay - but I was a bit worried about whether or not this was safe taking vdroop into account as well.

It seems like it should be fine from what I'm reading now?

I always found DVID(Offset) far more unstable on my gigabyte board, idle bsods... Windows not booting... Instant BSOD in prime 95. But using Load Line Levels and Set volts it works perfectly.

Seems to work on my Asus board (touch wood!). I think it's giving me slightly more than I need, because when I was playing around with P95 and the AI Suite, I managed to get 4.5GHz running okay with 1.312-1.320v, and now the offset is putting through an extra 0.01-0.015v. Other than that it seems fine, though.
 
Back
Top Bottom