4790k not boosting exactly to 4.4GHz (according to 3Dmark Firestrike)

Sturmgewehr_44

Honorable
Jul 21, 2014
375
0
10,810
According to Firestrike, my brand-new 4790k is not boosting exactly at 4.4GHz. Rather, it seems to be staying at 4.399GHz (1 MHz away). Why is this? Is it normal or ideal??

I have seen it stay at 4.4GHz turbo elsewhere, but for some odd reason, it rarely crosses the 4.4GHz threshold during the benchmark. My previous 2700k and 3770k CPUs stayed consistently at 3.920 GHz during Firestrike before. Why is this any different?

Also, why is my Turbo boost reported to be at 800 MHz??? I don't have any type of power saving enabled in the uefi. Is this just a SystemInfo bug??
 
if your that worried about it, bump up the speed by .1mhz lol. and check your minimum processor state under processor power management in control panel and set it to 100%, thats if you want it running at 4.4ghz all the time
 
However, why isn't it going to 4.4 GHz whenever it can? In P95 (which I'm afraid to run for more than a few minutes on Haswell), it stays at 4.4GHz most of the time. However, in games, it mostly stays at 4.390GHz. Why does this happen? Intel guarantees 4.4GHz, correct?

Will programmes that show the max turbo (i.e Firestrike) display the max turbo as 4.39 or 4.4GHz?

Despite this, is it "normal" for a 4790k to stay directly under 4.4GHz with turbo most of the time?

What about Firestrike? It does display the max turbo speed as "800 MHz". This also could happen on my retired 3770k. It happened for some odd reason because of XMP mode. This is not the case here, yet I'm still seeing that erroneous number from SystemInfo. Is it a bug?

Is there any OSD that I can use (Rivatuner/MSI Afterburner do not have a CPU core clock option) to monitor clocks in-game without having to minimise or alt-tab?

http://www.3dmark.com/fs/4659029 (note this also displays my ram at 1333 speeds. This is also erroneous).

 
Maybe it is running at 4.4GHz for the most part?

It is hard to tell. The loads drop instantly upon alt-tabbing to view RealTemp. It is possible that the loads drop enough that I can no longer see 4.4GHz. I believe it runs at that past 12.8% load.

No idea why 3Dmark isn't though...
 


4.399ghz IS 4.4ghz. The value you see reported is the product of bclk * cpu clock multiplier. If the bclk is 99.99mhz and the multiplicator 44, 99.99x44 makes 4399,5mhz, which is exactly what you see.
 
My BCLK is at 100MHz.

When I ran Cinebench, I stayed at 4.4GHz exact the entire time. Possibly I'm just becoming hysteric? I get like that after installing new hardware...

Maybe Firestrike SystemInfo is getting it all wrong? It displays my Ram wrong, my boost, and now possibly it says I'm running at 4.399GHz when I'm really at 4.4?

 


I don't know what firestrike is, but if you use cpu-z and it displays 99.99mhz bclk that is accurate. Maybe 1% of all motherboards have the bclk running at the exact speed that's set in the bios. If the blck is indeed 100mhz, there is no way that your cpu runs at 4399mhz. It's physically impossible.
 
I can double check, but I believe the bclk is at 100mhz. It is possible I'm being fed wrong info from Firestrike. If you didn't know, it is a synthetic benchmark. I generally use it quite a bit after upgrading to new hardware. It uses software called "SystemInfo" to gather information about the user's system. In this case, I might have been misled by it. It is known for displaying bugs at time. I was already aware of it falsely depicting my ram at 1333 speeds instead of 1600 (800mhz ddr). When I fired up Cinebench, I was at 100% load at 4.4GHz exact the entire time. This must mean that my observations were all wrong and that I am boosting to 4.4GHz normally. I will post some screenshots.

 
Um, remedial math lesson. 4.399 fulfills the definition of 4.4. With the significant digits being only two, that's the precision you need to evaluate. In other words, if you're told 4.4, you can expect (at four significant digits) anything between 4.350 and 4.449.
 
Sorry. I'm illiterate math-speaking.

CPUz depicts the BCLK at 100mhz. However, the clock monitoring on it goes up to exactly 4.399. The idle is 799.98. Why exactly is this? My old CPU(s) had this same thing, but the max turbo appeared to be 3920.50 Ghz according to Realtemp.

So...I seem to be getting different numbers from Realtemp and CPUz. Why? I often see 4.4ghz straight from Realtemp whilst for CPUz I observe a max of 4.399, which is exactly what Firestrike told me???

Screenshot: http://i.imgur.com/lsCg6nz.jpg

 
Well either reading of cpu-z is wrong, because it is not possible to have 4399mhz with 100mhz bclk. Since 3 values speak for 4400mhz and one for 4399, I'd believe the former. However, after all, it doesn't matter in the slightest anyway.
 
Aye. I agree. Both are likely wrong.

From that screenshot, you can easily tell that I have a BCLK of 100mhz. I am also running at 44x multiplier. So, that undoubtedly means that I am running exactly at 4.4GHz and nothing less. It is odd. I've been fed wrong information from two/three programmes that I trusted...

I mean, if I am 44x and a base clock of 100mhz, that obviously means full 4.4GHz, right? No weird number tricks or anything? Another oddity is that 3Dmark also fed me the erroneous 4.399GHz dilemma. All three must be wrong then.

If I am correct then, I am to believe that CPUz is actually reporting 4.4GHz?

 
Makes sense to me. How can I verify for certain that my bclk is at 100 mhz? I am almost completely sure, considering the bios and CPUz have reported it as such.

Do you have any idea why CPUz is doing this? I am using the ROG version, which does not have a more up-to-date release. I would like to use it, but I could switch to the regular skin to see what happens. I don't get why it rounds down like that. My ram is also showing up as 799.9 mhz instead of 800.00 according to CPUz as well...

Well, despite the cosmetic difference, I guess that means my 4790k is running normally...at 4.4GHz full turbo.
 


Same significant digit explanation. "100MHz" has only one significant digit. The true block frequency could be 99.977 MHz, which would yield 4.399 GHz. That's the math explanation, but it could also simply be there is a round-off or other small error. As has been written, it is of little consequence. We're firmly in the weeds at this point.
 
If you want an extra digit of BCLK accuracy, check out

RealTemp T|I Edition
https://www.sendspace.com/file/55yvry

XMeEJFw.png


You should see less BCLK variation compared to some other utilities.