I5 2500k heat/voltage issues

[Charlie98]

Interesting. I really do think it is a VCore issue. ANd if you're havingt he heat problem on that HSF, then it is not the culprit.

I went in and reset everything to stock and worked my way back up to 4.2GHz, then I started reducing vCore... just dropping the voltage dropped the temps 10C. I reduced it all the way down .10v where it finally crashed, so I bumped the voltage back up to -.08 and dropped the clock to 4.1GHz where I am now. Under full memory load on LinX I get a top temp of 72C where it would have been 80-82C before.

I'm also staying away from those Gigabyte tuning utilities... D:

 

[TheAdvocate]

Bump - looking for more suggestions. I pulled my cooler off last night and the thermal grease looked fine. No degradation. Im going to have to scrape and re-apply but I doubt it'll change anything.

I'm trying to find the Hard OCP guide to 2500k OCing on Asus UEFI that I used before, but so far I am FAIL at teh GoOglez. If anyone has a link or some more suggestions, let me know. I am just bafffled by the ridiculous heat on 1.1VCore. That's insane. And it's like instant heat - I had just started that BF3 session 5 minutes before that screencap. It's not heat soak/buildup from a marathon session and poor airflow.

 

[Charlie98]

Bump - looking for more suggestions. I pulled my cooler off last night and the thermal grease looked fine. No degradation. Im going to have to scrape and re-apply but I doubt it'll change anything.

I'm trying to find the Hard OCP guide to 2500k OCing on Asus UEFI that I used before, but so far I am FAIL at teh GoOglez. If anyone has a link or some more suggestions, let me know. I am just bafffled by the ridiculous heat on 1.1VCore. That's insane. And it's like instant heat - I had just started that BF3 session 5 minutes before that screencap. It's not heat soak/buildup from a marathon session and poor airflow.

When I was fooling with the Gigabyte OC utilities and LinX, it would overheat in about 20 seconds from start... it didn't take long.

Are you sure you are looking at the vCore reading? I was using CPUz to read vCore and I found it was NOT vCore, but VTT (I believe.) It didn't really dawn on me until I was looking in the BIOS and saw the difference in voltages... then the lightbulb in my brain came on.

 

[TheAdvocate]

I would think that it was VCore, but I guess I can tinker some more in BIOS.

Something else that I noticed - in that screen cap, the CPU fan is only @ 1100rpm. The max is only 2200, but it would seem like the fan should be spun up a good deal more if the cpu is overheating. I am almost sure I have it set to auto.

 

[Charlie98]

I would think that it was VCore, but I guess I can tinker some more in BIOS.

Something else that I noticed - in that screen cap, the CPU fan is only @ 1100rpm. The max is only 2200, but it would seem like the fan should be spun up a good deal more if the cpu is overheating. I am almost sure I have it set to auto.

My GB BIOS has a few different settings... performance or quite fan settings... maybe check those. I can tell when the CPU fan spools up to 100%... it's quite obvious.

 

[TheAdvocate]

I tore my machine completely apart tonight. Every component. Yanked the CMOS battery. Put it all back together. Booted up. Ran BIOS defaults (same as Ive been trying to run), and voila.

Everything is fine again. CPU between 23-35 idle/low. 50 at load @ 3.7GHz. 60 @ 4.2GHz. Just finished a 3 hour session of BF3 with not one glitch or heat issue. Weird. MY SSD didnt even crash (which is a miracle given the brand).

 

[TheAdvocate]

FIXED! 5 hours and running under 70C.

 

[Charlie98]

I tore my machine completely apart tonight. Every component. Yanked the CMOS battery. Put it all back together. Booted up. Ran BIOS defaults (same as Ive been trying to run), and voila.

Everything is fine again. CPU between 23-35 idle/low. 50 at load @ 3.7GHz. 60 @ 4.2GHz. Just finished a 3 hour session of BF3 with not one glitch or heat issue. Weird. MY SSD didnt even crash (which is a miracle given the brand).

Sweet! Certainly it was some setting that got changed somewhere...

...now, don't go picking on OCZ... :awe:

 

[kbp]

There has GOT to be a problem with the way your heat sink is seating your cpu.