• 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.

***Official Ivybridge Overclock Thread***

My cpu is stable at 4.4Ghz; 1.165vcore.

Is that about right?

IBT temps after 30 times max temp was about 76c

Folding for 5 hours max temp 66c

Think I'll keep it at this setting, since I only play starcraft II and D3.
 
Argh, mine just won't get stable at 4.5Ghz, gonna turn it down to 4.4, at least I'll get better temps :D.

Strangely it passed 12 hours of prime and ibt but i'm getting whea errors and lagging in games :(
 
Argh, mine just won't get stable at 4.5Ghz, gonna turn it down to 4.4, at least I'll get better temps :D.

Strangely it passed 12 hours of prime and ibt but i'm getting whea errors and lagging in games :(


4.5 I need 1.285

4.4 I need 1.215 - far lower temps - more than 10C less
 
4.5 I need 1.285

4.4 I need 1.215 - far lower temps - more than 10C less

I'm on 1.284 at the moment with 4.5 getting upto 77C in prime. But I got really bad stuttering playing Dead Island and a few whea errors in the event viewer.

Is there anything I could do to maybe improve stability other than increasing the voltage. One thing I have noticed on my board is even though I set the BCLK to 100 it actually sets it to 100.1 and if i set it to 99.99 it sets it to 100.05. Could that be causing any issues?
 
Arron I kept on having to up voltage till I didn't get WHEA errors - I was on LLC Extreme too so really under load it was 1.30V or so for 4.5 ...

encoding temps overnight got into the low 90s ... not ideal - but that was the volts required to get totally stable :(

4.4 is much cooler
 
Arron I kept on having to up voltage till I didn't get WHEA errors - I was on LLC Extreme too so really under load it was 1.30V or so for 4.5 ...

encoding temps overnight got into the low 90s ... not ideal - but that was the volts required to get totally stable :(

4.4 is much cooler

Yeh, think i might settle for 4.4 then I've got LLC on high, But i don't get any vdroop so I don't see the point in turning it up.
 
knocking the base clock down to 99.97 seemed to get rid of the WHEA errors but the temps were hitting 85 in IntelBurnTest so I decided to try 4.4 and I think I've got it stable at 1.212 hitting 78C now in IntelBurnTest.
 
ok well my pc was stable at 4.6.... IBT no probs, 10+ hours prime.... but now when playing bf3 i'm getting those WHEA triangles.... what the ****... like seriously?!even pumped up the voltage to 1.312 just on the fly through the asus AIsuite and still got them... :\ hummmm

ok now all of a sudden using the settings i used 2 days ago and ran all the test no problem....now i'm getting the whea-loggers in IBT....... starting to think this was a mistake... i enjoy the challenge... but if it's just going to change it's mind on a daily basis then i might DSR it

lol now running IBT again and no errors in event viewer... although before when playing bf3 i did get lag/stuttering, i checked the logs and i did get them at that time... is it a simple case of just pump some more volts through or is there something else we are missing?

just did a quick test at 4.5ghz, no errors during just 2 loops of ibt with volts dropped to 1.240ish... mad that even adding .06v and cant get those extra 100mhz al of a sudden... might just stick with 4.5...or when i butcher the chip and put liquid pro inside might up the volts again temp depenent. 4.5 knocked almost 10oC off the IBT temps... and it was about 4 degrees warmer in the room :P
 
Last edited:
ok well my pc was stable at 4.6.... IBT no probs, 10+ hours prime.... but now when playing bf3 i'm getting those WHEA triangles.... what the ****... like seriously?!even pumped up the voltage to 1.312 just on the fly through the asus AIsuite and still got them... :\ hummmm

ok now all of a sudden using the settings i used 2 days ago and ran all the test no problem....now i'm getting the whea-loggers in IBT....... starting to think this was a mistake... i enjoy the challenge... but if it's just going to change it's mind on a daily basis then i might DSR it

lol now running IBT again and no errors in event viewer... although before when playing bf3 i did get lag/stuttering, i checked the logs and i did get them at that time... is it a simple case of just pump some more volts through or is there something else we are missing?

just did a quick test at 4.5ghz, no errors during just 2 loops of ibt with volts dropped to 1.240ish... mad that even adding .06v and cant get those extra 100mhz al of a sudden... might just stick with 4.5...or when i butcher the chip and put liquid pro inside might up the volts again temp depenent. 4.5 knocked almost 10oC off the IBT temps... and it was about 4 degrees warmer in the room :P

Are you using off set voltage still? from what I have read, most say it is only good to use if going for an average overclock of something like 4.2 and the likes, 4.5 and above most recommend manual voltage but obviously you will loose speedstep and the such.
 
nah i went back from the offset as couldn't quite get it right, still have speed step enabled.... but that shouldn't be an issue really as it stress tested fine like 2 days ago, and seeing as the volts stay the same it's neither here nor there imo...if it's stable @45x with 1.298...why shouldn't it be stable @16x with the same volts :p I had it off when i was doing the initial testing... but also ran it with SS on and it didnt have errors.

just annoyed that i had what seemed to be a stale clock, all the stress tests fine and played D3 and bf3 the other night with no problems or errors (i check after i finished gaming)... and now tonight bf3 crashed, checked the logs and got the whea errors, did IBT again and got errors.... just not fair :( :p
 
Last edited:
yellow exclamation in the windows event viewer under system. seems to be vltage related, like not quite enough to cause windows to crash/bsod but enough so it gets a warning.

but as i said i had a bf3 stutter/crash and there were a few entries in the viewer coinciding with the time of crash
 
Last edited:
Back
Top Bottom