5.25GHz on a 4690K? Not really

[SuperCookie78]

First tings first, I was compiling a map in the Hammer Editor for CSGO. Source is a cpu intensive engine and my 980 wasn't being use. Second, i just rebuilt this computer (my old mobo died) so i upgraded to a 4690k and msi  z97 pc mate. I only have a 120mm water AIO i rushed it back together. about a day after i built it i put in a fast and dirty overclock of 43x multiplier and 1.35V. it works and the system has been stable ever since. But i never stress tested it and so opened up task manager to see if it was hitting the right speed and it wasn't it was almost a full 1GHz out of it should be. So i download hardware monitor and it said only 4.3Ghz. What i assume is happening is the cpu is telling windows for windows is seeing the cpu and applying a boost to 4.3Ghz i set. in reality this isn't happening its just that windows thinks it is. This is the second time i have found something like this. Last time it was a buged out CPU ID that said my cpu (a g3258 at the time) was at 7GHz. it was not. Maybe their is a weird bug with how Hasewell reports its speed to windows. But never the less it still is funny.

Spoiler

 

[paddy-stone]

If you look at base speed on the left screenshot, it is reported there at 4.3Ghz.

[SuperCookie78]

3 minutes ago, paddy-stone said:

If you look at base speed on the left screenshot, it is reported there at 4.3Ghz.

yea i kn its just funny that windows thinks that after a boost that isn't there it is 5.25GHz. lol

[Hans Power]

Interesting - I don't have this issue on my i5-4690k which I also overclocked to 4.3 Ghz. But I ended up overclocking my boostclock and used a voltage offset so that it doesn't burn quite as much power on idle but before that I used static clock to test things out. Have you deactivated Turbo boost in your Bios? That's what you're supposed to do if you statically overclock your base clock.

And just a sidenote - I ended up with a max voltage of 1.210v @4.3Ghz so you propably can lower your voltage quite a bit - 1.300v should be achievable for pretty much everyone using Haswell.

[SuperCookie78]

1 minute ago, Hans Power said:

Interesting - I don't have this issue on my i5-4690k which I also overclocked to 4.3 Ghz. But I ended up overclocking my boostclock and used a voltage offset so that it doesn't burn quite as much power on idle but before that I used static clock to test things out. Have you deactivated Turbo boost in your Bios? That's what you're supposed to do if you statically overclock your base clock.

And just a sidenote - I ended up with a max voltage of 1.210v @4.3Ghz so you propably can lower your voltage quite a bit - 1.300v should be achievable for pretty much everyone using Haswell.

my overclock was a quick and dirty OC. i need to go back and dial it in. maybe pushing it farther then lowering the voltage. boost clock is not disabled but it shouldn't go past a set valve (as protection for people who overclock without disabling) 

[Hans Power]

Just now, SuperCookie78 said:

my overclock was a quick and dirty OC. i need to go back and dial it in. maybe pushing it farther then lowering the voltage. boost clock is not disabled but it shouldn't go past a set valve (as protection for people who overclock without disabling) 

True, but disabling Turbo boost when base overclocking is concidered to be best practice. Propably to avoid bugs like that. In my Gigabyte BIOS I had to deal with quite a few bugs as well - just different ones.

[SuperCookie78]

1 minute ago, Hans Power said:

True, but disabling Turbo boost when base overclocking is concidered to be best practice. Propably to avoid bugs like that. In my Gigabyte BIOS I had to deal with quite a few bugs as well - just different ones.

over course. But the last time this happened it was a software issue not a mistake in programming the BIOS on my part. 

[Zando_]

That's a common bug with Task Manager, makes for some good funny moments. Other doods have had windows think they had a 25Ghz OC going...

[SuperCookie78]

Just now, Zando Bob said:

That's a common bug with Task Manager, makes for some good funny moments. Other doods have had windows think they had a 25Ghz OC going...

thats amazing. 

[Princess Luna]

1 minute ago, SuperCookie78 said:

thats amazing. 

Not really, it's easy through registry editing to make Task Manager show about whatever you want it to show.

[SuperCookie78]

Just now, Princess Cadence said:

Not really, it's easy through registry editing to make Task Manager show about whatever you want it to show.

but for it to do it randomly is quite a funny occurrence.