Sign in with
Sign up | Sign in
Your question

Intel Turbo Boost

Last response: in CPUs
Share
March 4, 2012 10:04:21 PM

Recently I noticed the Intel Turbo Boost doesn't reach its full extent, 3.4 GHz with i5 2400. Instead it stays on the lowest level, 1.6, all the time. To test CPU speed, I opened the MSI control center to monitor each core while running OCCT CPU test, and all the cores maintained 3.2 this time. but not 3.4 in any core. Then 3D Mark 11 result reported my CPU ran @1600MHz, and the Physics score was lower than before, from 6100 to 5900. I checked the BIOS, and everything is as before. I didn't install any new driver except the new GeForce WHQL one. How can I resolve this?

CPU: i5 2400
MB: MSI H67
Memory: Corsair DDR3 1333
GPU: EVGA GTX 560 Ti 448 Classified
PSU: Antec HCG-620

More about : intel turbo boost

a c 184 à CPUs
a b å Intel
March 4, 2012 10:21:13 PM

When you are doing something that isn't very cpu intensive the processor downclocks itself to 1.6ghz.

Turbo boost works this way when certain cores are stressed at full load.
your processor.
4 Cores Full load 3.4ghz
3 cores, 3.5ghz
2 cores, 3.6ghz
1 core, 3.7ghz
March 4, 2012 10:27:32 PM

The reason why I'm concerned is the turbo boost monitor used to fluctuate before between 1.6 and 3.4, even when the PC was not running a particular program. Now, it just stick to the bottom without a slightest movement. I ran the OCCT test because of this observation. Also 3dmark 11 used to report 3299MHz for CPU, not 1600, and the physics score is down now.

I don't have any other change except the nvidia driver update.
Related resources
a c 122 à CPUs
a b å Intel
March 4, 2012 10:29:12 PM

The cpu downclocks when it's idling not for cpu intensiveness. Also, wrong speeds, he has 2400 not 2500.
4-3.2
3-3.2
2-3.3
1-3.4
(Can't remember if it was 2 or 3 cores that is the same.)
It was probably just fluctuating from a background process. But speedstep shouldn't mess up for anything.
a c 184 à CPUs
a b å Intel
March 4, 2012 10:30:14 PM

k1114 said:
The cpu downclocks when it's idling not for cpu intensiveness. Also, wrong speeds, he has 2400 not 2500.
4-3.2
3-3.2
2-3.3
1-3.4

Oops oh well :wahoo: 
!