Core i5-2500k OC help needed ::::::::::::

redfaction95

Honorable
Nov 9, 2013
161
0
10,710
Hello, I hope you are doing good, need a lil bit of help here:-

PC specs:-
core i5 2500k
gigabyte z77x UD3H 1.1
corsair xms3 1800mhz 2x2GB
rosewill capstone 550 gold / thermaltake litepower 600
msi r9 280x / pny 560ti
WD blue 500GB + Silicon Power C70 ssd

I bought my GIGA z77x UD3H and 2500k brand new 1.3 years back but I am unable to OC my cpu at all, any slightest change results in Boot Loops but eventually PC boots into OS and passes any stress test/ benchmark with good temps, but the boot loops make them effed.

I am having this problem from about almost my first Overclock on this board which was I guess 1.2 years ago, I used to have Thermaltake Litepower 600 PSU and PNY 560ti back then (rest remain the same as I said in above post), and now at this very moment I have upgraded to Rosewill Capstone 550 80+ Gold and msi R9 280X (Which I am running it at 1000mhz clock like the reference design's clocks though it comes at 1020mhz) so the problem then and the problem now is the same 1.2 year back I wanted my CPU OC'ed to at least 3.8ghz or 4.0ghz (all cores), but the problem was that, with just even a slight change in the settings (for example, setting the multiplier to 37 and using my rams xmp profile at its given 1600mhz speed and all other things on stock) the systems just pushed itself to boot loops, though after 2-3 loops when I got into OS finally, every stress test passed no core ever crossed 55C even in my damn hot room. So after much trying and consulting, some guys guided be for even 3.8ghz (as you know these clocks are sooo close to stock turbo clocks that they merely need any voltage tweaking) but still I tried to set voltage to normal LLC to high voltage response to fast and offset to +0.05 but loops every where, I started from F16 bios and now I am on F20e latest still same, I left the hope, returned to full stock 24/7 for an year and then now that I have upgraded to a quite decent PSU, its only 2 days old loving it, did many GPU and CPU stress testing, ALL ok.

SO the thing is that, when I use optimized defaults in BIOS, everything works like a CHARM, I have used full stock settings (except ram set to xmp 1600mhz auto and changed boot priority) for almost a year, and guess how many boot loops, ZERO in whole year.
So when I tried changing today again after a year, same story, so I thought to give it another try.

PS every single temp is fine and my PC is in good health, not even a bit of dust there. I also have cooler master 212+

I will be really really thankful for ANY help in advance :)
 
Solution


Problem solved.
I disabled every single power saving feature in the bios and then booted into windows and got the multiplier I typed in the bios.
Then I went back and enabled them all and again rebooted, it was still showing the one in the bios, yea I know this sounds weird, but it did solve the problem. And btw I have disabled the "thermal monitor" permanently.

PS when I was having problem in "in" OS multiplier, the clock shown in the BIOS was still showing correctly my given multiplier value.

Just one more question:
I am having these volts @ 3.8ghz
1.344-1.356 V
It is on auto volt and LLC...

redfaction95

Honorable
Nov 9, 2013
161
0
10,710


Yes, it is the latest bios i.e F20e.
And if you are asking for "Clock ratio"...? Which is "33" @ stock, the least i've tried is setting it to "37" because you know 3.7 is already the turbo multiplier that applies to 2 cores.
But sure I will check that too ASAP and report back, thanks.
 

redfaction95

Honorable
Nov 9, 2013
161
0
10,710


Yeah, I use BIOS for OC,
I will check that it allows the turbo to be disabled, though I have not seen any such options, there is also a "Advanced tubo frequency" type thing, I will post screen shots of some important pages if you say?
 

redfaction95

Honorable
Nov 9, 2013
161
0
10,710


So here is an update:
As you said, I switched the turbo off, so as you know the main multiplier as "33" and then I tried "35" and "37" also. So what ever I set in BIOS, I get that in cpu-z and HWiNFO. Good news is no boot LOOPS what so ever, completely stable 24/7 all stress test/ temps perfect. But then I tried setting the clock ratio to "38" and then "39" also but you know in the OS cpu-z and HWiNFO show the "37" instead of 38 or 39 relatively, but again no boot loops.
So how can I take my CPU beyond 37 while disabling the turbo...?
 

redfaction95

Honorable
Nov 9, 2013
161
0
10,710


Problem solved.
I disabled every single power saving feature in the bios and then booted into windows and got the multiplier I typed in the bios.
Then I went back and enabled them all and again rebooted, it was still showing the one in the bios, yea I know this sounds weird, but it did solve the problem. And btw I have disabled the "thermal monitor" permanently.

PS when I was having problem in "in" OS multiplier, the clock shown in the BIOS was still showing correctly my given multiplier value.

Just one more question:
I am having these volts @ 3.8ghz
1.344-1.356 V
It is on auto volt and LLC to High.
Is that fine?

And temps under aida64 test are:
38-40 idle (nearly all cores)
and 54 60 60 62 (are the highest temps per core respectively)

No boot loop for now at least.
 
Solution

clutchc

Titan
Ambassador
First, congrats on your troubleshooting. I have an older BIOS w/o all those power saving features. I wasn't aware you had so many you had to disable them. But now that you can increase the multi normally, are you able to reset the power saving features w/o losing the multi?

There's always an argument on whether or not to leave the CPU voltage on auto. I have tried it both ways with no noticeable difference. I leave my 'old-timer' on auto. That will allow the vcore to remain low when not needed. Saves wear on the CPU for 90% of its life. But it has the drawback of possible over-volting the CPU unless the BIOS has a voltage limiter. I have no idea if it does, but I'm keeping my fingers crossed.

Your voltages are safe, if that is what you are asking. 1.4v is even commonly used for OC'ing if needed for stability.