stupid question about Sandy Bridge Turbo

[Twsmit]

How do I test if turbo is working? I cannot hit 3.8ghz when at stock.

I was trying to break my 2600k in at stock and for the life of me I cannot get it to turbo to 3.8ghz. (only turbos to 3.6 or 3.7ghz) I have the Asus P67 board and a i7-2600k.

Is there a particular bios setting that I need to enable? or a specific benchmark that will push a single thread to 3.8ghz?

I'm interested from a purely academic point of view, I just want to make sure everything is working at stock settings.

thanks!

 

[Phynaz]

Fold on one thread.

 

[Majic 7]

Here are my settings, I had the same situation as you, found this just noodling around. Not much actually. 1204 Bios, both EPU and TPU switches flipped to on, XMP profile enabled, newest AI Suite installed, drivers off install disk installed, EPU set to High Performance. Tried Turbo V but it raised idle voltages. All Bios setting stock except Internal PLL voltage disabled and all controllers disabled that I don't use. Made sure By all cores was enabled in Bios. This gives 4.3 on all cores at load, 1.28 volts, and 1.6 at idle with around 1 volts. Could probably lower load volts on manual but this is just too easy. 33/34C at idle, 60 to 64C at load. Noctua 12P. Here is a pretty good article on the Bios and what everything does. http://www.techreaction.net/2011/02/03/review-asus-p8p67-deluxe-fully-loaded-mid-range/5/

 

[eddietandy]

I was thinking 3.4 GHz was the default, meaning the turbo multiplier comes stock at 34. Set it to 38 and you should get 3.8 GHz, especially if you run folding or BOINC.

 

[Majic 7]

I was in the same situation as the OP. Just wanted to see how things were running, but I wanted to stress it a little to check temps. At stock your cores go from 3.4 to 3.8 on turbo, not sure of the exact step up. I think the 3.6 is an average. I wasn't expecting 4.3 and all cores overclocked with EPU, but like I said it was just too easy so I left it.

 

[PreferLinux]

Use a single-threaded benchmark, such as SuperPi. You may have to use Task Manager to lock it on to one particular core so Windows doesn't keep moving it around. You will also need to minimise any other any other activity at the time, or lock that on to the same core as SuperPi or whatever else you are using.