Sign in with
Sign up | Sign in
Your question

I5 2500k at 98ºc?

Last response: in CPUs
Share
December 7, 2011 5:09:38 AM

Hey guys, I just bought a computer and set it up myself piece by piece. It's the first time I did it, so just the fact that the computer turned on is already a big accomplishment for me!

Since I was the one who set it up together, I'm not sure if I didn't put the cpu cooler in the exact place/position.
I read somewhere that the core temperatures shouldn't be above 72º.. if thats true then I'm screwed!

But I also overclocked it, I used this little program that came with my motherboard called EasyTuner6, I'm running it at 4.33Ghz. It's stable, no crashes at all or anything, just the temperatures!

You guys thing that this is because of the OC with the stock cooler or is it really misplaced? Because it kind of seemed to me that it was well placed..

Also, I don't really know whys that Open Hardware Monitor says that my processor went to 14ghz..

http://s9.postimage.org/rpkd473bz/image.jpg

And temperatures when at idle are about 35º

More about : 2500k 98c

a b à CPUs
December 7, 2011 5:26:12 AM

Those numbers can't be correct. The CPU cannot run at 14GHz with that FSB speed, that would mean a 42x multiplier and a world-record overclock. I'm also interested in knowing what VCore is being pushed into the CPU.

Drop all overclocks before you're sure your temps are correct. If the CPU is really running at 98'C, you're busy frying it, specially with the standard HSF.
m
0
l
Related resources
December 7, 2011 6:00:27 AM

Yeah, it spikes at 98..

I'll take off the OC and run some games again to see if its gonna heat up that much. If it does, then the problem should be a misplaced cpu fan?

I got a new reading:

http://s9.postimage.org/lda9rh6lb/image.jpg

Quote:
I'm also interested in knowing what VCore is being pushed into the CPU.


What do you mean by VCore?
m
0
l
a b à CPUs
December 7, 2011 6:35:19 AM

With VCore I mean the voltage over your CPU. Usually around 1.2~1.35V, but can be dangerous when pushed too high, leading to high temps and damage to the CPU. Which is why I wanted to know.

Anyhow, the new readings seem to be a lot more in the ballpark. 50'C is more like it, although I think it's a little too low now. It should be closer to 65'C with the standard HSF. Try refitting the cooler, and run these tests again. Also make sure you have the correct amount of thermal grease on the CPU, not too much and not too little.
m
0
l
December 7, 2011 6:38:59 AM

Toxxyc said:
With VCore I mean the voltage over your CPU. Usually around 1.2~1.35V, but can be dangerous when pushed too high, leading to high temps and damage to the CPU. Which is why I wanted to know.

Anyhow, the new readings seem to be a lot more in the ballpark. 50'C is more like it, although I think it's a little too low now. It should be closer to 65'C with the standard HSF. Try refitting the cooler, and run these tests again. Also make sure you have the correct amount of thermal grease on the CPU, not too much and not too little.


these are idle temps.. they're a bit too high, no?

and i didnt put any thermal compound, i think the fan already has some pre-installed
m
0
l
a b à CPUs
December 7, 2011 6:55:12 AM

Idle temps are fine for the OC you're running. And the thermal compound that comes with the cooler works, but isn't the best. If you remove the cooler, specially after the temps you posted earlier, I'd recommend replacing the compound as well. It's cheap and can be picked up at any PC store.
m
0
l
December 7, 2011 7:03:58 AM

Toxxyc said:
Idle temps are fine for the OC you're running. And the thermal compound that comes with the cooler works, but isn't the best. If you remove the cooler, specially after the temps you posted earlier, I'd recommend replacing the compound as well. It's cheap and can be picked up at any PC store.


thanks, but still when i go full load the temps will still spike to 98.. is the only solution for that a new cooler?
m
0
l
a b à CPUs
December 7, 2011 7:41:39 AM

That's the thing. You first drop the OC and check the temps when spiking then. If it's still high, you may have a misfitted or faulty cooler, or still a crappy reading. It's hard to figure, but first you must drop the OC's.
m
0
l
a c 186 à CPUs
December 7, 2011 4:38:55 PM

You overclocked with the stock cooler? NEVER OVERCLOCK WITH THE STOCK COOLER!
m
0
l
December 7, 2011 6:42:14 PM

2 issues here.

1. Auto Vcore settings.
2. Stock cooler.

I'm unsure which to suggest as worse. I dropped about 15C by just tweaking the Vcore and LLC on my Gigabyte Z68 motherboard, so I'm sure that leaving it on Auto is a pretty bad idea....

On the other hand, the stock cooler is terrible. My idiot roomate basically left his OC on the Auto settings at about 4.33GHz with probably similar too high Vcore, but he also had a Cooler Master Hyper 212 plus, so the load temps topped out at 67C in prime95. Which is safe.

Sooo.... yeah. Let's get a new cooler eh? And then work on tweaking those bios settings for a nice efficient OC, rather than relying on the lame Auto stuff.
m
0
l
December 7, 2011 7:03:21 PM

Ok, so I removed the auto OC, but I'm not sure it came back to default config, coz now it says that my CPU is running at 3592Mhz, shouldn't the i5 2500k be at 3300?

Anyway, in this configuration the core 1 temperature doesn't go past 61º (core#2 59, core#3 54 core#4 51) so the cooler should be working properly under its capacities, right?

I'm about to get a new cooler sometime next week, what do you guys think about this one?

http://www.newegg.ca/Product/Product.aspx?Item=N82E1683...

And is there a tutorial for a good and stable OC for this processor? Something that even beginners like me could do.
Well, I think that basically all I need is matching numbers for Vcore and the multiplier?

Thanks a lot guys!
m
0
l
December 7, 2011 8:12:02 PM

The clockspeed is normal. Max turbo frequency at stock is actually 3.7GHz IIRC.

Temps sound good at the stock settings. So everything is normal there...

Yeah, that's pretty much the cooler everyone is getting. Although, it's unfortunate it's not on a better sale. I think the EVO version might be the step up from that one, and was 3 dollars cheaper on newegg.ca (people keep distracting me tho, so I wasn't able to look at the specs that close).

For overclocking an i5 2500K....

Toms had a OC guide here:
http://www.tomshardware.com/forum/265056-29-2600k-2500k...

Bit-tech had one here:
http://www.bit-tech.net/hardware/cpus/2011/01/07/how-to...
m
0
l
December 7, 2011 9:10:17 PM

If you're going to overclock you should do it yourself. I would never let my computer decide what it's VCore needs to be.

Another thing...when using auto overclock on Sandy Bridge machines it must also change the Base Clock. I see in your screenshots it says Bus Speed 103 Mhz (it means Base Clock). I don't own a Sandy Bridge cpu, but everything I've read says deviating from the 100 Mhz leads to instability in a hurry. That could also be causing some problems with your auto overclock.
m
0
l
December 7, 2011 9:52:47 PM

Thanks a lot, boys!

@thebski: i saw on your sig that you have 2 gtx 570 superclockeds.. thats the one i have.

im planning on getting a 2nd in a couple months. do you really think its worth it? im a little bit disappointed with my single card while playing batman arkham city fully maxed
m
0
l
a b à CPUs
December 7, 2011 9:56:05 PM

Download and run Intel Burn Test to see what sort of load temps you really get
m
0
l
December 7, 2011 10:10:13 PM

thebski said:
If you're going to overclock you should do it yourself. I would never let my computer decide what it's VCore needs to be.

Another thing...when using auto overclock on Sandy Bridge machines it must also change the Base Clock. I see in your screenshots it says Bus Speed 103 Mhz (it means Base Clock). I don't own a Sandy Bridge cpu, but everything I've read says deviating from the 100 Mhz leads to instability in a hurry. That could also be causing some problems with your auto overclock.


I think I left all of my voltage settings on auto. CPU-Z shows ~1.28vcore under load and it's stable at 4.4Ghz. If I set vcore manually, it won't lower the vcore when idle. I know I could overclock MORE setting vcore manually, but I care more about it being able to down-volt than getting a couple hundred extra Mhz. It really depends on how the motherboard handles it, though. If mine decided to give 1.4v, there's no way I'd leave it on auto. But I'd agree with everyone ever that using the motherboard's auto-overclock tool is a terrible idea. It's a subtle difference, but it is different.
m
0
l
December 8, 2011 1:10:30 AM

I'm confused....you seem to be both for auto overclocking, and then you say it is a terrible idea. On the ASUS P8Z68-V Pro board that I have, flipping the TPU switch to "ON" raises the turbo limit, without doing anything else. This allows my 2500K to troll along at ~1.648 GHZ most of time, @0-5% load. When the cores are put under 100% load, like in the Prime95 Blend Test, the frequency leaps to ~4.38 GHZ (I was getting 55-60 C temps). Now, are you saying that letting the TPU function automate the clocking of my CPU is not good? Are there multiple ways to auto-overclock the CPU?
m
0
l
December 8, 2011 1:40:02 AM

I'm NOT auto-overclocking. I selected the multiplier and what settings to enable/disable, ran stress tests, monitored voltage and temperatures, repeat, and changed settings accordingly. I'm letting the motherboard decide what voltage to use (after testing that it's acceptable), therefore allowing it to down-volt when it idles. In my case auto-voltage works well, in some cases (maybe most) it won't. Auto-overclocking is when your motherboard picks all the settings. It's not the same thing.
m
0
l
December 8, 2011 1:46:11 AM

Okay, I see. So the voltage modulation is entirely automatic, but you select the multiplier? What about the baseclock, mine says 103.02 MHZ (the board/BIOS did that automatically)?

Edit:
Nevermind, I flipped the TPU off, restarted, and my baseclock dropped to 100.33 MHZ.
m
0
l
a b à CPUs
December 9, 2011 6:43:41 AM

Keep your Vcore under 1.4 and ideally keep your temps below 75-80 degree's.

You should see some vast improvements using an aftermarket cooler :) 
m
0
l
December 16, 2011 2:23:26 AM

I just got and installed an aftermarket cooler, I got the Hyper 212 evo. I can definitely see differences in the temps.

Before I had ~33c at idle and ~60c full load without any overclock.

Now I have ~22c idle and ~38c load.

So it's time to OC properly!

I went to the bios and couldn't find any option to change the voltage, so I think it's on automatic mode.

I changed the multiplier to 47x so now I have a max clock speed of 4689Mhz sitting at ~30c idle.
I just booted up the comp and the little program Core Temp shows my "VID" moving from 1.25v to a maximum of 1.38v.

So far I haven't pushed the cpu yet, I wanted to check first if its safe to try any benchmark programs without changing the voltage manually.

Or am I good as long as the temps are low?


EDIT: cpuz says that my core voltage is 1.044v, is that too low? should I revert the OC?
m
0
l
December 16, 2011 2:58:18 AM

Woah, woah, woah. You need to start slow.

Reset your BIOS to stock. Read a few different guides to get a feel for what the settings do and what you need enabled/disabled. Some settings won't be correct for overclocking by default. After you've got your research done, increase your multiplier to x40. Boot into Windows, pull up CPU-Z to monitor your v-core, and something like Core Temp that will show your processor temperature. Now you need to stress test. I like Intel Burn Test because errors show up quickly, but others swear by running Prime 95 for 24 hours or whatever. 10 passes in IBT using whatever RAM you have should be sufficient. Or if you're using Prime 95, maybe an hour at a time during this phase. If you pass, and your v-core stays below ~1.37 and your temps are below ~90, you can up your multiplier by 1 and repeat your stress tests. Repeat until if fails, and go back to your last stable multiplier. At this point you can also go into your BIOS and change ONE setting at a time (which you gathered during your research) to see if that helps. Now play some games for a week, making sure to monitor your temps. The more demanding they are, the better. If it makes it through 10 passes of IBT, it should be ok, but you need to use it in a real-world setting to make sure it's stable. If your computer crashes, reduce the multiplier by 1 and play games for a week again. Repeating as necessary. If you don't crash, you're good to go.

This is the quick and easy way, but it still takes time and patience. i5-2500k is really easy to overclock compared to previous chips, but you can still damage things if you don't take the time to do it correctly. There are additional things you can tweak to get a few hundred extra Mhz. I don't necessarily think it's worth the time and effort for daily use, especially since they perform well at stock anyway and overclock easy, but there's that option too.
m
0
l
December 16, 2011 5:01:42 AM

its weird, my vcores are still too low.

i checked a couple of sites, videos, tutorials.. i managed to run at 4.6ghz stable (so far)
i ran intel burn test a few times, running prime95 now for about 20 mins and everything seems fine. my temps below 60c..

buut my vcore still at 1.07. is that a problem?
m
0
l
a b à CPUs
December 16, 2011 8:15:12 AM

The lower the vcore, the better (as long as the OC is stable).

Just be careful using auto-voltage and setting a high multiplier. The CPU can sometimes over-compensate and have damaging effects. I wouldn't recommend pushing past 4.5GHz using auto voltage.

Personally i've been running 4.5GHz for a while on my i5 and to be fair, i really didnt notice all that much difference from 4.0GHz. So to increase the lifetime of my CPU i've just clocked it back down. Pushing to the limits is fun, but for daily use, really isn't necessary - no matter what cooling you have :) 
m
0
l
a b à CPUs
December 16, 2011 2:00:19 PM

Intel Burn Test at High stress for 20 passes. And go!

That Vcore is super low, so I'd bet it'll fail but who knows.

Also, I definitely don't recommend CPUZ as a "monitoring" tool since it doesn't always update itself.

Get HWMonitor instead. It has everything.
m
0
l
!