A lil help with overclocking?

>inb4 >>Sup Forums or >>/wsr/
Fuck off this is the only half decent thread and i know you dont give that much of a shit of these kinds of threads


I have a 2500k i5 sandy bridge and i was going to up it from 3.3 to like 4.7. Read up a lot of overclocking shit and just finished updating the CPU clock ratio to 47. That being said, computer is now stuck at the loading screen and froze. I would follow my instinct but i have no budget to replace the CPU at the moment, so i want to be sure before i do jack shit.


Is this an issue of not enough Vcore? I remember some people posted some time ago an image simplifying the OC progress with a .png, however i seem to have lost that image.

At any issue i can reset CMOS anytime. However i would really like to get this shit done. This computer is old enough already.

Other urls found in this thread:

masterslair.com/vdroop-and-load-line-calibration-is-vdroop-really-bad
en.wikipedia.org/wiki/SpeedStep
twitter.com/NSFWRedditVideo

>I overclocked it
>Now it doesnt work
Reset your BIOS dumb dumb
Not every chip is going to hit the same clocks
Not every motherboard is going to provide whats necessary for a good overclock
You don't get 4.7
Too bad

Ok thanks for your input but let me rephrase my question:

I jumped the clock ratio multiplier and the windows wont boot. Should i increase vcore to try?

>not every chip is going to hit the same clock
I aint placing it up to 5ghz or some bullshit. Ive read that up to 4.8ghz its pretty fucking safe for an air cooled sandy bridge. Even i5.
>not every motherboard its going to provide what's necessary
Its a Z68 MOBO from gigabyte. And from what i read its the best MOBO to overclock an LGA1155

Safe. But not all chips can.
Cut your losses and back it to 4.5 and see how that goes.

same issue at 4.6. Bumped it down to 3.5 to check, windows boots fine. Definetlly think its a Vcore issue. So i beg you to help me just a little bit.

Every guide ive seen says that vcore should be increased in increments of 0.005 until the computer runs, then done a stress test like LinX or Prime95 or both. However, sandy bridge guide tells me that you should never bump it to 1.4 or beyond.

I really wanna be able to play shits like cities skylines, arma 3 and BeamNG at half decent framerates, and i dont have the money for a new computer. I wanted to try overclocking before i NEEDED a new computer and i really want to get to know how to do this shit for my first time.

CPU multiplier now at 35 with base Vcore. Will try LinX (fuck waiting 8-12 hours several times for this shit, maybe once that it passes LinX) and update.

YOU OVERCLOCKED A CHIP 1200Mhz ON AIR
BE FUCKING HAPPY. Seriously that's a rocking overclock. I'll be lucky if I can do 700Mhz for my 8350 on a 970 mobo on water because I'll blow my fucking VRM's

what.


3.3ghz from the base i5 2500k and ive seen people OC it up to around 4.8 on air alone.

I did a 200 MHZ just to stress test. I sure do hate how LinX and Prime95 like to take their sweet ass time.

12 times elapsed in LinX with 1/2 tests completed. Hyper Evo 212 with thermal paste showing 70 C (limit would be around 80 to 85) when it would work at 40C idling at base clock. Seems that the temperature is holding. If it keeps rising this is a lost fucking cause, not even being able to OC it to 4 ghz.

My bad missread. Thought you backed down to 4.5.
Undervolt it. That's pretty hot for just 200. The bios readings may be off some bit, you can never really trust readings from most devices. It's partially why overclocking is a by feel sport. If that doesn't help then you really crapped out on the silicon lottery.

I dont feel that OCing its like a sport but more like a surgery.

I did not touch the Vcore from the 3.3 base. Maybe the vcore its updated automatically? damn it i didn't pay attention to that setting in the BIOS.

At least the temperature remains still. Its actually 69 degrees for the hottest core. The coolest one is mostly 63/64. CPUZ claims that the torture test Vcore its 1.248 volts.


Sorry for the late update. This shit WILL take days of constant testing and i am burning time while doing this since i have no other computer and i am messing around.


Oh, and can i do other minor shit while stress testing? i aint talking playing games but i mean stuff like watching movies, browsing internet, hearing music or watching porn (opening images and video)

Because if i have to close every OS app and not even move the mouse while doing this, like back when i was trying to mine bitcoin, its going to be a pain in the ass.

>did not touch the Vcore from 3.3

If you're going to overclock that high you're going to have to dick around with the vcore.

1.4v is your voltage wall and you CAN set it a little bit passed that but don't go more than 1.42 or something like that. See if it's stable at 4.2ghz @ 1.4v and go from there.

Increase the cpu speed until it crashes @1.4(2)v and then back it down and keep it where it's stable.

4.2 at 1.4 v? isn't that a little bit overkill?

I wanted to check if linX reports no issues, increase the multiplier to end up with 4.0 ghz, and dick around with the vcore to increase.

Earlier i said that i want straight from 3.3 to 4.6 and the windows failed to boot. I think that's the issue.

i have NO IDEA if going step through step from OC to OC instead of directly doing a big OC jump will have a nule or negative effect on the computer. But like i said, my budget wont allow me fucking up and having to replace parts, so i tread careful here.

Small update:

6 tests done.

temp on the hotest core is still borderline 70 C but not quite.

Volts are still 1.248. Its been an hour already.

Looks like i underestimated the Evo 212 after all. Once its done i'll check up higher OCing.

>2500k
>you should upgrade soon anyway
just set it at 5ghz and put the vCore on auto, it might crisp in 6 months, but its time for an upgrade

No budget, friendo.

New Mobo, 6700 (locked) i7, recycling RAM and with a 1060 GPU, using the same case and PSU in this shitty southamerican country would cost me a fucking lot.

Besides, other than maybe some indie/low end shit, BeamNG, Arma 3 i dont really use my computer to play videogames at all.

God fucking damn it.

14/20 stress tests done and its been 2 hours 40 minutes.

Is it common for overclock tests to be made through several days instead of being done all in one sitting?

Yes. Welcome to #overclocking

well, at least now i dont have to sit through 4 days of constant lack of test of the computer.

Tell me, you think i should overclock in small steps or say fuck it and go directly to the end goal and increase vcore until the system boots and passes all the stress tests?

Update: LinX finished with no errors in 3 hours 40 minutes. record high temperature was done 3 hours ago at just 70 C. I guess its time to notch it up to 4.0 and tune the vcore a little bit.

How odd. Notched to 4.0 and with an 0.005 vcore increase the OS booted just fine (and pretty much instantly).

It already was pretty fast with an SSD but now with the CPU going faster its pretty fucking quick.

How odd. It seems that the VPU Vcore its quite higher than what i set it up to be. I made it be 1.285 on 4.0 yet BIOS tells me its working at 1.345. Is this because of the intel Turbo boost tech? should i disable it?

From what i gather is that the PLL is automatically making sure that the CPU is running at its optimal Vcore regardless of what i set it up to be from checking up what i want the core speed to be.

Is it a replacement to me checking the correct volts or should i just turn it off and manually set it up anyways?

Im reading up that they are reccomended for 4.8+ GHZ OC, however some people suggest them for 4.5.


Nobody reports ANY issue with leaving it off at 4.8 GHZ OCs but nobody reports leaving them on either. Apparently its a small boost used if you dont want to increase the vcore manually.

Should i still do it? or if it passes the 12 hour prime 95 stress test i should just let it be and roll with it?

Turned off both the intel turbo boost and the PLL shit. I am not sure what each one does however i have heard people suggest to turn them off for actual OCing.

The new issue is that the computer turns off and restarts after trying to load windows.


More vcore to fix, right?

This fucking stupid shit.

I was able to make windows boot but i keep getting the 0x000124 BSOD shit.

Since it tells me "increase OR decrease VTT OR vcore" i have 4 possible options as candidates and i am not sure up to what fucking point.

Reduced vcore to 1.395 and QPI/VTT increased to 1.080 but this issue still presists. Anyone has a tip? or should i just fucking give up and turn on PLL to manage this?

i need someone to help me a little here.

Set VTT to 1.050 and 1.080 (intel supposed safe max) And the issue still happened. Set VCCIO to auto and issue still happened.


Should i just directly set a higher VCCIO? Because i am not even touching the CPU memory clock nor the RAM clock. Its still at 13.33

Aparently while OCing a sandy bridge the 124 BSOD is common due to some retarded C3/C6 state support. That being said, even after disabled the BSOD still bothers. I am seriously out of ideas here.

unfortunately overclocking is a lot of trial and error, it may be that you can't push it that high, see if you can get stable on a lower frequency

in the end, you'll have to be either satisfied with what you can achieve (4.5GHz?) or look elsewhere, there's probably communities out there with people who still fiddle with i5 2500K (overclock.net?)

i AM trying that website.

All i hear is weird conflictive shit.

>BSOD 124 will only appear if you messed with VCCIO
which i didn't
>BSOD 124 will only appear if you have a weird vcore
Which i dont. vcore 1.990 will freeze on boot screen, 1.995 will start up just fine and then BSOD
>on sandy bridge if you have manual voltage you gotta turn them off
Which i did. I also turned them on. I also tried with them on auto. No dice.


I know that OCing its like making a car and not all of them will be the same. But is my sandy bridge truly fucking unable to even reach 4.6 Ghz? I wouldn't be that mad, but i would still be dissapointed and i wanna hear if there's something else i am not trying yet.

Had to stick it to 4.5 ghz and 1.390 vcore to work.

The odd thing is that in CPUZ the vcore goes between 1.392 and 1.404 every so often. Did i fuck up? did i left on an option that fucks with the vcore?

also, the multiplier likes to jump from 45 to 16 every so often. Is the CPU underclocking itself automatically when not in use?

voltage isn't exactly set in stone, it can fluctuate slightly. the difference between those two figures are just 0.012 volts, which is barely anything to worry about. read this to see why:

masterslair.com/vdroop-and-load-line-calibration-is-vdroop-really-bad

old article but the terms and how it works is still relevant

yes, that's a feature, might be called speedstep or something like P states. speedstep saves power but also allows the processor to run a bit less warm.

en.wikipedia.org/wiki/SpeedStep

you could turn it off in BIOS or through windows, but there's not really much of a reason to turn it off though. barring buggy drivers, the communication between motherboard and windows is good enough that when you run a demanding program like a game, the system will know not to let the processor underclock itself super low.

u sure there's no risk? vcore was already "risky for constant use" at 1.4 and beyond and this thing gives me 1.404.


Still a fucking shame that the CPU OC is locked at 4.5ghz

Is this something to do with the age of the CPU? its been 5 years already.

If the fluctuations are REALLY nothing to worry about i will worry about stress tests later and i really fucking hope i dont have to increase vcore.

Sorry for beating a dead horse.

I really dont mind ending up with a 4.5 ghz OC but i really cant get out of my mind if its just the CPU or if i just messed up an option that made me get the 124 BSOD.

Could it be that it wasn't enough vcore although i was giving what's considered the limit for constant 24/7 use?