Sign in with
Sign up | Sign in
Your question

I5-2500k OC Help

Last response: in Overclocking
Share
March 12, 2012 10:12:30 PM

\"\"

I'm not sure how I am doing with this overclock. I have an i5-2500k, corsair h60 in a push-pull set up. For fans I'm currently using the 120 case fan from the haf922 and the fan that comes with the h60. I am running 4gb or ram as well. I have the the multiplier to 4.5 and the voltage set to 1.325 in the bios. I have my pll set to 1.8, it seems to be less stable when I move it to 1.7. The temps seem fairly high, I'm not sure if that is normal for a intel burn run. I had a 20time run and had the max hit 76 instead of 75. Any help in reducing these temps and stabilizing this overclock would be greatly appreciated.

More about : 2500k

March 12, 2012 10:42:51 PM

hmmm i have a similar problem, when i tried OC my i5 2500k today (first time in my life) the temps got to around 80C and i was only OC'ing to 4.3Ghz, maybe its because i have a cheap water cooler. So if anyone finds you an answer they find me it too (within reason :p )
m
0
l
March 12, 2012 10:58:09 PM

The temps don't seem horrible, I mean it only really spikes up that high occasionally. My biggest question is the reason for those high temps. Is it normal to have the voltage jump up so high when set so low, even under load?
m
0
l
Related resources
March 13, 2012 12:51:27 AM

Anyone? I think its odd that I set it to 1.325 and it runs at up to 1.395 according to cpuz. Is that normal or safe for this clock? is there anything i can do to fix it. Oh, i forgot my board is an msi p67-gd65 (b3)
m
0
l
a b K Overclocking
March 13, 2012 1:10:48 AM

Crzywhiteskata said:
Anyone? I think its odd that I set it to 1.325 and it runs at up to 1.395 according to cpuz. Is that normal or safe for this clock? is there anything i can do to fix it. Oh, i forgot my board is an msi p67-gd65 (b3)

That voltage is really high. Especially for that clock. Try setting the voltage to a manual.
m
0
l
March 13, 2012 1:21:58 AM

It is set to manual in yhe bios unless I missed something. In the bios its set to 1.325.
m
0
l
a b K Overclocking
March 13, 2012 1:38:58 AM

Crzywhiteskata said:
\"\"

I'm not sure how I am doing with this overclock. I have an i5-2500k, corsair h60 in a push-pull set up. For fans I'm currently using the 120 case fan from the haf922 and the fan that comes with the h60. I am running 4gb or ram as well. I have the the multiplier to 4.5 and the voltage set to 1.325 in the bios. I have my pll set to 1.8, it seems to be less stable when I move it to 1.7. The temps seem fairly high, I'm not sure if that is normal for a intel burn run. I had a 20time run and had the max hit 76 instead of 75. Any help in reducing these temps and stabilizing this overclock would be greatly appreciated.


Does it pass the 20 time run? if it does then you are good. Have you tried Prime95? try runnuning it for a minimum of 2 hrs then try running it for about 6-8 hrs, if it does not crash(BSOD) then you got a stable overclock. Be aware that you should monitor the core temps, use HW Monitor from CPUID.com
About the temps that you got running Intel Burn Test that is normal, just don't let it go over 80 deg Celsius.
m
0
l
March 13, 2012 1:54:43 AM

Are those good temps for an h60 push pull? Is there something wrong there or would maybe a fan upgrade help it?
m
0
l
March 13, 2012 2:03:29 AM

maybe re seat with fresh thermal paste may drop your temps? i normally remove any paste that comes on any HSF/coolers, and use any aftermarket thermal paste.
m
0
l
a b K Overclocking
March 13, 2012 2:05:54 AM

Is the direction of the push/pull setting of the fans going out or going inside the case? I ask this because I've read about that it is better to drive the air going inside the case, the reason is outside air temps are lower than air temps coming out of the case.
m
0
l
a b K Overclocking
March 13, 2012 9:55:49 AM

Try turning off Load-Line Calibration and set a manual voltage. That may fix it.
m
0
l
March 13, 2012 10:11:24 AM

Both of those should be off, I have to double check. I.ve read now that the msi boards seem to overcompencate hardcore under load by .2 to.4 volts but with a 1.325 initial voltage im getting like a .6 to .75 jump.
m
0
l
a b K Overclocking
March 13, 2012 7:42:38 PM

Crzywhiteskata said:
Both of those should be off, I have to double check. I.ve read now that the msi boards seem to overcompencate hardcore under load by .2 to.4 volts but with a 1.325 initial voltage im getting like a .6 to .75 jump.

Lower the voltage and see what happens.

Also, you could set it to offset voltage.

When you enter the BIOS, check what the Vcore is at in there.
m
0
l
March 13, 2012 10:25:38 PM

I was able to move it down to 1.32 and run a stable max inyel burn for 20 rounds now only peaking at 1.384 which is better but still a big jump
m
0
l
a b K Overclocking
March 13, 2012 10:29:00 PM

Crzywhiteskata said:
I was able to move it down to 1.32 and run a stable max inyel burn for 20 rounds now only peaking at 1.384 which is better but still a big jump

Even lower. Like 1.2x.

What does the BIOS say that the Vcore is running at?
m
0
l
March 13, 2012 10:47:55 PM

In the bios i set it to 1.32. In cpuz it says that is the lowest voltage as well. Let me go into the bios real quick and see exactly what it is saying.
m
0
l
a b K Overclocking
March 13, 2012 10:49:01 PM

Alright, sounds good. Also, there may be a setting where you are setting 1.32v as the lowest voltage possible. Check that too.
m
0
l
March 13, 2012 11:03:31 PM

It was saying 1.344 in the bios under the voltage
m
0
l
a b K Overclocking
March 13, 2012 11:04:46 PM

Crzywhiteskata said:
It was saying 1.344 in the bios under the voltage

Is that when it is set to 1.35v?
m
0
l
March 14, 2012 1:13:23 AM

No that was 1.32. I set it now to 1.305 and it did an 10.srt max intel burn no issue maxing at about 1.36 volts, much better.
m
0
l
a b K Overclocking
March 14, 2012 1:15:53 AM

Crzywhiteskata said:
No that was 1.32. I set it now to 1.305 and it did an 10.srt max intel burn no issue maxing at about 1.36 volts, much better.

Still, that is high. There may be an issue with the board, but it could also be a misreading from the software. Use Hardware Monitor.
m
0
l
!