You can call a 4.4GHz 2500K @ 1.25V at "stock voltage" because thats what the chip requests at 3.4GHz turbo, but you almost definitely have to use fixed volts or offsets which is clearly not the factory default mode.
I think the confusion arises because some people OCed their SBs at auto voltages and assume that their OCed chips use the same voltage at load as a non-OCed one.
Intel knows. The max VID for the SKU is not specified willy-nilly.
There is a physics-based reason, bounded by an economic one (minimizing infield fails that are covered by warranty), which is data-driven and empirically derived for the product.
The only voodoo involved is that there is a whole heap of people out there who know jack squat about device physics and lifetime reliability analysis, and the void of ignorance gets filled in with a whole lot of guessing compounded by arrogance.
The middle-ground comes in when people want to knowingly reduce their CPU's lifetime but only to the extent that the odds of it dieing within 2yrs is increased only a little tiny bit. People will say "I don't care if my CPU lasts 10yrs, I only need it to last me 2yrs...so how much morecowbellVcc boost can I give it?".
That's when it helps to have some education and experience (industry experience, not enthusiast zuber-overclocker garage experience)
Hardware monitor shows 1.46 - 1.48 ..
I've hung onto my e8600 @ 4.5 Ghz. for years, and was toying w/ the idea of grabbing a 2600K setup,
but I would only do so if it can go 5GHz + on air.
I've read maybe only 2-3 out of 100 chips will do this.
Thats about the volts I was pulling @5ghz on my 2500k, the temps were no more then 80c at max load for over an hour which is fine by my own standards but thats just too much voltage to run daily all year then I'm comfortable with. I would run this at 4.8 if I wanted a max OC daily but I'm using this thing as a server so 4.5ghz is fine for me.
Intel knows. The max VID for the SKU is not specified willy-nilly.
There is a physics-based reason, bounded by an economic one (minimizing infield fails that are covered by warranty), which is data-driven and empirically derived for the product.
The only voodoo involved is that there is a whole heap of people out there who know jack squat about device physics and lifetime reliability analysis, and the void of ignorance gets filled in with a whole lot of guessing compounded by arrogance.
The middle-ground comes in when people want to knowingly reduce their CPU's lifetime but only to the extent that the odds of it dieing within 2yrs is increased only a little tiny bit. People will say "I don't care if my CPU lasts 10yrs, I only need it to last me 2yrs...so how much morecowbellVcc boost can I give it?".
That's when it helps to have some education and experience (industry experience, not enthusiast zuber-overclocker garage experience)
e8600 @ 4.5 Ghz. Man stick with that until 2012 at least I dont think you will see a HUGE difference. Wait for Ivybridge.
I presume that the LOL is in reference to cowbell...
So anyone else @ 5Ghz on air, 24/7?
what volts, motherboard, etc....
Last 2500k stable OC I had in my hands was 4.9 @ 1.3911 vCore or something like that
Hi there. I work for a financial services organisation, and part of my job is making things go fast. As such, I've built ~30 SB overclocked servers running at around 5Ghz on the following platform: -
1. SB 2600k
2. Asus Maximus Extreme IV
3. Crazy custom air cooling.
What I've noticed is this based on this platform:-
1. All the chips will run to at least 4.0-4.1Ghz with stock volts.
2. All of them have made 4.8Ghz, the only variation is the volts used to get there. I have consistently used around 1.350vcore to get to 4.8 - with the exception of a few very good chips, I've found that most of them hit a wall at this speed and it requires larger jumps in voltages (and associated cooling) to get them to even 4.9Ghz. The fastest I've gotten so far has been 5.0Ghz at 1.355vcore.
Let me qualify what I'm doing though.
1. We don't use SpeedStep.
2. We don't use HyperThreading.
3. Temps at 4.8Ghz are around high 50's, low 60's - at 5.0Ghz they're around mid 70's.
4. The CPU's run at 100% utilisation on 3 of the 4 cores for around 10 hours a day, Monday to Friday, and this has been the case for ~2 months. We haven't had a machine crash even once.
I'm intrigued to see what people's settings are - I'm of the opinion that the voltages I've been using to bump past 4.8Ghz just aren't worth it - I'll happily run anywhere up to absolute maximum 1.38vcore, but am happier around 1.35vcore - on the mobo I'm consistently able to get 4.8Ghz. The stories I'm seeing of people pushing 1.42vcore or whatever to get to 5.0Ghz seem to me to be ridiculously high - or has anyone tested 1.40 consistently 24/7 with no problems?
They really let you overclock the servers? Are you the head IT there? I guess I don't understand what kind of application it is... I'm awfully surprised you're even using non-ECC memory, let alone overclocking. Why not use Xeon parts? And do they not care about power consumption? How do you test stability?
I don't mean to sound like a jerk, I'm just very surprised to see this being used in a server environment and I hope you understand why I'd be skeptical. I feel like there's a lot to be learned here
Yeah, we overclock the servers, for a very specific purpose. We're totally aware of the fact we're not using ECC RAM, along with the inherent limitations of not going for something like multi-cpu Xeons with QPI and a bunch of cores - basically we have an application that's single threaded and has to run *super* fast - so fast that multi-threading isn't even an option. It's not about throughput, it's all about latency. Power consumption is immaterial, as is whether the chips burn out in 12 months - by then we'll have moved on to the next Intel processor tree.
It sounds like you have an incredible job! Haha. So the 2600k is just for the extra 2mb cache over the 2500k then?


They really let you overclock the servers? Are you the head IT there? I guess I don't understand what kind of application it is... I'm awfully surprised you're even using non-ECC memory, let alone overclocking. Why not use Xeon parts? And do they not care about power consumption? How do you test stability?
I don't mean to sound like a jerk, I'm just very surprised to see this being used in a server environment and I hope you understand why I'd be skeptical. I feel like there's a lot to be learned here
financial services organisation
The systems that were in cases were water cooled Core i7s, overclocked to 5GHz. There are two folks at Centaur who build each and every one of these machines, and overclock them. You and I know that overclocking both Nehalem and Sandy Bridge results in much better performance for the same dollar amount, but this is the first time I've seen overclocking used to speed up the simulation of microprocessors.
Source
