SB Overclocking Thread

[Castiel]

Is this correct?

Stock 2600K: runs at 3.4GHz when it's idle and jumps to 3.8GHz when Turbo engages under load
OCed 2600K: runs at 3.4GHz when it's idle and jumps to OC speed when Turbo engages under load

Overclocked 2600K : Idle's at 1600 and jumps to 4.6ghz when under full load.

 

[mclaren777]

1600 = 1.6GHz?

And what triggers Turbo Mode? Does the CPU have to be at/over 95% for a certain length of time or actually hit 100% or something else entirely?

 

[Castiel]

1600 = 1.6GHz?

And what triggers Turbo Mode? Does the CPU have to be at/over 95% for a certain length of time or actually hit 100% or something else entirely?

Depends on the percentage of CPU usage.

1% - 2ghz,
3% - 4.6ghz

 

[HotDogHero]

Hey,

I set my BIOS to 100.0 BCLK (manual) and multiplier 46x. However, when I go into CPU-Z it shows that my BCLK is sub-80, like 73.9 or something like that. This even happens when I am running P95 or Linpack. I know that my board (P8P67) only allows me to lower it to 80 at the minimum. So, is this just a CPU-Z reporting error? In the Probe for AI Suite II it shows correctly that I'm running at 46x100.0, so which program is wrong?

 

[tech960]

Is this correct?

Stock 2600K: runs at 3.4GHz when it's idle and jumps to 3.8GHz when Turbo engages under load
OCed 2600K: runs at 3.4GHz when it's idle and jumps to OC speed when Turbo engages under load

You can set the turbo multiplier to whatever you want. I turned speed step off so it doesn't idle @ 1.6ghz.. for now at least.

 

[jimhsu]

Hey,

I set my BIOS to 100.0 BCLK (manual) and multiplier 46x. However, when I go into CPU-Z it shows that my BCLK is sub-80, like 73.9 or something like that. This even happens when I am running P95 or Linpack. I know that my board (P8P67) only allows me to lower it to 80 at the minimum. So, is this just a CPU-Z reporting error? In the Probe for AI Suite II it shows correctly that I'm running at 46x100.0, so which program is wrong?

Use this edition:

http://www.cpuid.com/news/36-cpuid_reviewer_kit_for_intel_sandy_bridge.html

 

[HotDogHero]

Thanks!

And, does anyone think that 65~68C with Venomous X single fan config load (Prime 95) is hot? And, is 1.360Vcore about where I should be at when I'm at 4.6GHz?

 

[Castiel]

Hey,

I set my BIOS to 100.0 BCLK (manual) and multiplier 46x. However, when I go into CPU-Z it shows that my BCLK is sub-80, like 73.9 or something like that. This even happens when I am running P95 or Linpack. I know that my board (P8P67) only allows me to lower it to 80 at the minimum. So, is this just a CPU-Z reporting error? In the Probe for AI Suite II it shows correctly that I'm running at 46x100.0, so which program is wrong?

Sounds like it might be throttling. What are temps like under load?

 

[Axon]

Thanks!

And, does anyone think that 65~68C with Venomous X single fan config load (Prime 95) is hot? And, is 1.360Vcore about where I should be at when I'm at 4.6GHz?

I have a beaten to all hell Scythe Mugen 2 on my rig and it only goes to 60c on one core. Everything else is between 55-58c. So I think it's a little hot.

1.36v on the 2500k? Sounds good.

 

[MrTransistorm]

Is this correct?

Stock 2600K: runs at 3.4GHz when it's idle and jumps to 3.8GHz when Turbo engages under load
OCed 2600K: runs at 3.4GHz when it's idle and jumps to OC speed when Turbo engages under load

That's Turbo overclocking. However, on Gigabyte boards you can disable Turbo completely. Doing that along with disabling EIST, C-states, etc. forces the multiplier to remain fixed (even at idle) at whatever you set it at.

I don't know if it's possible to disable Turbo on other boards. I'm pretty sure you can't on Intel's own boards.

 

[mclaren777]

I'm super confused now. Is there something I could read about the various speeds of Sandy Bridge? Apparently it's much more complex than I thought. This whole 1.6GHz thing is news to me.

 

[MrTransistorm]

I'm super confused now. Is there something I could read about the various speeds of Sandy Bridge? Apparently it's much more complex than I thought. This whole 1.6GHz thing is news to me.

The 1.6GHz thing is likely EIST (Enhanced Intel SpeedStep). The multiplier drops below the set multiplier at idle to save energy.

The confusion comes from the reviews. The majority of Sandy Bridge reviews I've seen were on Asus boards, along with a few MSI and Intel boards. If those boards don't have an option to disable Turbo, then by the sheer number of those reviews it would appear to the casual web-surfer that Turbo is the only way to overclock. This is apparently not the case.

Hopefully those boards that can only overclock via Turbo will get BIOS updates to allow fixed overclocking. In the meantime I'm going to go with a board that gives me full control, even if it means forgoing UEFI in the short term.

EDIT: looking at the Asus P8P67 Deluxe manual, it appears that Turbo can be disabled. From the reviews I read I got the impression that that option was not present at the time. That's good news.

 

[mclaren777]

The more I read the more I'm leaning towards leaving my 2600K completely stock.

There are just too many variables to worry about with OCing.

 

[Castiel]

The more I read the more I'm leaning towards leaving my 2600K completely stock.

There are just too many variables to worry about with OCing.

It's not as confusing as it sounds. Its so easy to overclock now.

 

[StinkyPinky]

So you should disable turbo when overclocking? I want around 4.4/4.5. So I just disable the turbo, up the multiplier (and voltage) and that's it?

 

[flopper]

SB is easy,
raise multiple, add vcore.
MSI P67 gd55 2500K

Priming some at 5ghz 1.432v

 

[M1A]

If I had one not sure I would put 1.432v on it just yet...........
Anyway how about seeing some passmark details guys?

 

[muskie32]

Oh my....

I wish i could do that with my i7 875K....

4.0ghz with 1.36v temps high 70's under load

Cooler H70


I WANT SB!

 

[mclaren777]

It's not as confusing as it sounds. Its so easy to overclock now.

My assumption was that overclocking just raised the ceiling on what Turbo Mode could reach. I thought the CPU stayed at 3.4GHz until it was under sufficient load, then it would trigger Turbo. So my plan was to keep it entirely stock this year and then bump up the Turbo to 3.9 next spring. Then the following year raise it to 4.0 and so on (probably cap off at 4.4GHz in 2017).

But apparently this plan doesn't sound like it's going to work. :\

 

[d33pblue]

SB is easy,
raise multiple, add vcore.
MSI P67 gd55 2500K

Priming some at 5ghz 1.432v

ttp://i56.tinypic.com/jife3n.jg[]
ttp://i51.tinypic.com/vrwnzm.jg[]
http://i52.tinypic.com/2dahopl.jg[]

Intel specifies 1.385v max for this processor. Let me know how long that chip lasts at 1.4v. I'm happy to let you be the guinea pig.

 

[flopper]

If I had one not sure I would put 1.432v on it just yet...........
Anyway how about seeing some passmark details guys?

idle 1.384v.
watercooled.

not even tried to tweak for lower vcore yet,
just amazingly easy.

 

[mnewsham]

idle 1.384v.
watercooled.

not even tried to tweak for lower vcore yet,
just amazingly easy.

Well 1.38 or so was the highest proclaimed "safe" that i have seen.

 

[d33pblue]

My assumption was that overclocking just raised the ceiling on what Turbo Mode could reach. I thought the CPU stayed at 3.4GHz until it was under sufficient load, then it would trigger Turbo. So my plan was to keep it entirely stock this year and then bump up the Turbo to 3.9 next spring. Then the following year raise it to 4.0 and so on (probably cap off at 4.4GHz in 2017).

But apparently this plan doesn't sound like it's going to work. :\

Turbo really only makes sense if you are leaving the processor at it's stock speed. If you are overclocking it to the max, "turbo" is useless since you are already at the processor's peak output.

Also, turbo reduces the number of effective cores in order to reach this elevated speed. Overclocking raises the frequency on *all* of the cores.

 

[tech960]

My assumption was that overclocking just raised the ceiling on what Turbo Mode could reach. I thought the CPU stayed at 3.4GHz until it was under sufficient load, then it would trigger Turbo. So my plan was to keep it entirely stock this year and then bump up the Turbo to 3.9 next spring. Then the following year raise it to 4.0 and so on (probably cap off at 4.4GHz in 2017).

But apparently this plan doesn't sound like it's going to work. :\

Sure it will. You can set the normal and turbo multiplier independently of each other. Say 3.6ghz normal / 4.8ghz turbo. Or no turbo at all and just leave it OC. Before I even booted it the 1st time I set the turbo to 4.2, and left the normal to stock 3.4

 

[d33pblue]

Well 1.38 or so was the highest proclaimed "safe" that i have seen.

I feel like a lot of people on here (and other places as well) overclock more for bragging rights than for any sort of practicality. Frankly I see NO reason at all to risk destroying a processor just to get another 200-300mhz out of an already insanely fast processor.

I won't be going over 1.37 with mine when I get it.