Windows and programs misinterpret my clock speed for minimum system requirements

[Chillstice]

Look at the screenshots before trying to answer...

 

For a while now my Windows 7 machine and some programs including but not limited to: NZXT CAM, CpuZ, and Samsung Magician think that my Intel i7 4790K is running at 800mhz. wot. Check screenshots because I'm having a hard time describing this.
 
Preface:
 
I recently re-installed windows about a month ago while installing a new Samsung 850 Evo SSD.
I followed a guide on "how to install windows properly" which gave me a couple tips I didn't know of, but didn't feature anything out-of-the-ordinary.
I like to keep my system optimized and clean using some trusted, automated tools that include registry cleaners.
I also have similar tools that notify me of any updated drivers, which doesn't currently notify me because they're already updated.
All windows updates are installed

Bios seems to be updated
Oh and yes, I did restart
 
Specs and Versions:
 
LTT Build Page
PC Part Picker
 
Windows 7 Ultimate 64-bit
Service Pack 1
CurrentBuildNumber 7601

 

System summary:

OS Name Microsoft Windows 7 Ultimate

Version 6.1.7601 Service Pack 1 Build 7601

Other OS Description Not Available

OS Manufacturer Microsoft Corporation

System Name CHRIS-PC

System Manufacturer ASUS

System Model All Series

System Type x64-based PC

Processor Intel® Core i7-4790K CPU @ 4.00GHz, 4001 Mhz, 4 Core(s), 8 Logical Processor(s)

BIOS Version/Date American Megatrends Inc. 1204, 6/17/2014

SMBIOS Version 2.8

Windows Directory C:\Windows

System Directory C:\Windows\system32

Boot Device \Device\HarddiskVolume2

Locale United States

Hardware Abstraction Layer Version = "6.1.7601.17514"

User Name CHRIS-PC\Chris

Time Zone Mountain Daylight Time

Installed Physical Memory (RAM) 16.0 GB

Total Physical Memory 15.9 GB

Available Physical Memory 9.63 GB

Total Virtual Memory 31.9 GB

Available Virtual Memory 24.4 GB

Page File Space 15.9 GB

Page File C:\pagefile.sys

 
The problem:
 
Specific programs that have minimum required specs to perform certain actions wrongly say that my CPU is running at a whopping 800mhz (.8ghz) When it's actually overclocked to 4.8, 4.7, 4.6, 4.6ghz for the 4 cores respectively.
 
This is an issue because I can't do things like Enable RAPID mode in Samsung Magician or even reserve windows 10 for my computer. (see screenshots)
 
Screenshots:

 

 

 

What I've already tried:

Yes, I know that overclocking could be the cause of the issue, that's why I tried with optimized defaults. 

I've run 'sfc /scannow'

I've cleaned the registry

I've re-seated the cpu and applied new TP

I didn't kick it yet

 

I'm sure I tried other things that I can't think of right now.

 

 

I'll try to respond to any questions as soon as I can.

Treat me like a human being and this whole process will happen a lot smoother/quicker. Thank you for your time and effort in advance.

[JefferyD90]

Im 99% sure that it is a software issue.  I'd reinstall Windows and make sure Im using newest drivers.  Potentially, you need a BIOS update.

[Enderman]

Its supposed to run at 800MHz at idle...

CPUZ shows 4.6GHz

It will only get to 4.6GHz when its under load

[2FA]

So turn off Turbo?

[Chillstice]

Its supposed to run at 800MHz at idle...

CPUZ shows 4.6GHz

It will only get to 4.6GHz when its under load

Well even Cpuz shows (8-4.6). At least it knows the cpu's full potential. Why can't anything else?

[Chillstice]

Im 99% sure that it is a software issue.  I'd reinstall Windows and make sure Im using newest drivers.  Potentially, you need a BIOS update.

I agree that this might solve the problem, but I'd rather not start over, again. I have so many programs and a lot of settings that took me about 2 days to all set up. I'd rather live with this than re-install again.

[JefferyD90]

I agree that this might solve the problem, but I'd rather not start over, again. I have so many programs and a lot of settings that took me about 2 days to all set up. I'd rather live with this than re-install again.

Then try a BIOS update and then update your drivers.  Although I'd highly recommend backing up your data first.

[Chillstice]

I forgot to mention that the bios is updated

[oskarha]

What happens when you put load on the CPU? My core 2 duo does the same thing (but at 2GHz), but when I put load on it (stress test, game etc.) It goes up to its fastest clock speed (in my case, using a C2D E8400, 3GHz).

[0x1e]

Turn off C states, do the validation, turn C states back on.

[DEDRICK]

Turn off C states, do the validation, turn C states back on.

 

To elaborate further.  Disabling C-States will cause the CPU to run at full speed at all times, instead of dropping to a lower clock speed based on load.

[0x1e]

To elaborate further.  Disabling C-States will cause the CPU to run at full speed at all times, instead of dropping to a lower clock speed based on load.

 

Yes. You must have disabled something that allows windows to detect anything above C states minimum. Not a clue what though.

So disable them, validate Windows 10, enable them and then Windows 10 shouldn't check again.

It doesn't seem like what ever you've done has actually harmed your PC in performance or stability, just monitoring.

 

So either find out what you've done and fix it permanently or do a cheap dirty quick fix when needed. 

 

Edit: You shouldn't disable things especially services unless you need to or know exactly what they do. Some if not most can have a chain reaction.

Some one can do a modification and it works for them. However they don't have the same hardware and software as you, so may not have the same results.

[Chillstice]

Turn off C states, do the validation, turn C states back on.

 

 

To elaborate further.  Disabling C-States will cause the CPU to run at full speed at all times, instead of dropping to a lower clock speed based on load.

 I'm going to try this and come back with the results.

[Chillstice]

Sorry it's been a while, but since this wasn't a in need of my immediate attention I waited until the next time I shutdown and started up my PC to make the changes in the bios.

 

Lo and behold:...

 

 

Temporarily changing the C-States to Disabled has solved this issue.

 

I will now choose the winning post.