[SOLVED] i5-6600K never reaches 3.9 GHz in benchmarks: resulting in low scores

saihv

Honorable
Oct 19, 2013
28
0
10,530
I have an i5-6600K (up to 3.9 GHz turbo) on an MSI Z170a Gaming Pro motherboard and a Hyper 212 Evo cooler. The temperatures in Prime95 and intel burn in never exceeded 70 in any core (mostly 63-68 range), but the core frequency never goes beyond 3.6 GHz. When I run Fire Strike physics test, or Cinebench R15, I am getting lower scores than what most review articles have posted about the i5. Again, the processor is never taxed beyond 3.6 GHz for some reason: but during normal Windows tasks, I have seen it go up to 3.9 in some cases. I am really confused about what's going on here. Isn't the whole point of a benchmark like Cinebench or Prime95 to push the processor to the max? HWINFO shows all four cores at 100%, cool enough temps, but only up to 3.6 GHz.
 
Solution
turbo boost means lower the others unused cores to raise the other core (first core)
in other word, if your are playing game using all cores, it will only raise up to 3.6 GHz
for single threaded program, it will raise up to 3.9 GHz (gained about 300 MHz or so from the others unused cores)

Crixilian

Distinguished
Aug 1, 2015
398
0
18,910
turbo boost means lower the others unused cores to raise the other core (first core)
in other word, if your are playing game using all cores, it will only raise up to 3.6 GHz
for single threaded program, it will raise up to 3.9 GHz (gained about 300 MHz or so from the others unused cores)
 
Solution

saihv

Honorable
Oct 19, 2013
28
0
10,530
Okay. So could there be another reason for my CPU benchmark scores being lower than what a lot of i5 review articles have listed? Fire Strike physics, PassMark, Cinebench all of them report a lower score on my PC.
 

Crixilian

Distinguished
Aug 1, 2015
398
0
18,910
while you are running the test, did you close all running programs??
and set the power scheme to high performance??
and before running the test, check task manager make sure the CPU usage has the lowest %
besides, make sure your BIOS/UEFI settings are not set to something like power saver, max CPU usage, not using all cores or something else