Just OCed my i5 but dont know if I did it right!

[slpnshot]

Ya definitely a good way to think about it. Thats why I was considering 4GHz and all power savers on...if thats possible. Though I dont know what Id do about LLC - apparently is dangerous to have on at the same time as the power savers. I think thats the reason why my computer crashed those two times. I had a stable voltage but it crashed with the power savers on.

Is LLC as dangerous as Im hearing? Mine is only at Level 4 and the voltage can only get as high as 1.38 v as far as I can tell. Under Prime95 it only got to 1.32 v and under IntelBurn Test it only got to 1.36 v. That sound about right? I have the vcore set to the fixed voltage of 1.35 v.

Wait... LLC and power management state shouldn't be enabled at the same time? Damn better run IBT again, this time with C-state enabled... Only ran it with OC and LLC together.

 

[latches]

lol ya. I ran it with all enabled and got a slam bam failure. Haha.

 

[latches]

Hey so, the OC was reset recently by some sort of failure. Im not sure what it was but it failed. Anyway - I left it at 3.3GHz with its power savers enabled for the time being BUT my temperatures are a little different from what they were before. Even with my A50 cooler the temps are hovering around 30*C. It used to hover around 22*C. I DID move the computer to another room from the living room which was usually colder but should it gain THAT much heat? Is something wrong? I ran IntelBurn Test to see if the comp would crash and...it didnt. Was the standard test. What do you think?

 

[dma0991]

You worry too much. 8C wouldn't make that much difference in terms of stability at idle, 8C at load is a different story. If it did 30C at idle then that is fine. You lost a little bit of overclocking potential from that additional 8C but not much. If you've moved your rig to a room that is smaller and warmer than your living room, definitely you would see an increase in temps.

 

[latches]

lol alright. I think Im just paranoid after the crash and bios reset. Im just worried that damaged something is all. I dont want to cost myself more money. I figured the safeguards made sure nothing got out of hand but I dont know. Ill do the OC again and see what happens.

 

[latches]

Temps at load are: 58*C using IBT. Are you sure nothing is wrong? I got those temps with my OC enabled...this cant be right...

 

[dma0991]

A rig that I've built for a friend of mine, Core i7 2600 + CM Hyper212+, 3.4GHz stock obviously. Idles at 38-42C and gaming load temps are in the 60s, IBT will stress more but not tested. There is nothing wrong with his rig and has more to do with the ambient temperature here.

Feeling happy now?

 

[latches]

lol yes...alright...thanks...

 

[latches]

Update: Turns out I WASNT doing it right. Before I would set a specific voltage and then hope that LLC would take care of the rest. After discovering that LLC was actually potentially harmful I decided to go with dynamic vcore only to discover that I didnt need any type of vdroop compensation at 4.2Ghz. I want to go for a 4.5GHz OC but my cooler seems to be inadaquate for that high an OC. I had it perfectly stable at 4.4GHz with vcore set to normal and DVID set to just .015v but the temps were as high as 84*C using IBT and I dont like that. Took 20 runs to get there but still.

Additionally the temps are actually down now. Idle went down to the upper 20s and at 4.2GHz the temps only get as high as 74*C. Now I just have to save up for that dual fan Noctua and Ill be golden for 4.5GHz. 4.2GHz is fine for now though. Not complaining - even though Id like the temps to be much lower.

Edit: AND - ALL my power savers are on. The C states and EIST. How sick is that? All stable at 4.2GHz. DVID is awesome.

 

[Rvenger]

But what is your Idle voltage? If you set a fixed Vcore, then your vcore doesn't throttle with your CPU speed.

 

[latches]

Oh, RIGHT NOW the vcore is set to "Normal" which allows the C states setting and EIST to throttle as needed. In other situations like a higher overclock Id need to add DVID to compensate for vdroop but it just isnt occuring at 4.2GHz so I didnt set it. Or more it set to auto so its probably compensating itself. I didnt set a fixed vcore for my current OC. Been good so far.