ASUS X99-A/USB 3.1 + Intel i7 5820k Core Speed Issue

Zavyr

Reputable
Jul 1, 2015
2
0
4,510
Hello,

A little while ago I bought new components because my older computer (after a good 6 years) died.

Here are the specifications:

Mobo: ASUS X99-A/USB 3.1, 2011-3, 8xDDR4, ATX
CPU: Intel i7 5820k @3.3Ghz S2011-3
GPU: EVGA GTX 980 FTW ACX 2.0
Memory: Kingston HyperX 16 GB DDR4-2666 Quad-Kit (CL13 13-14-14-33)
PSU: CoolerMaster Silent Pro M2 850w
Case: Be Quiet Silent Base 800 (Black)
OS: Windows 7 Ultimate x64 (Service Pack 1 installed)

Everything is assembled, booted up successfully, installed Windows, installed drivers and updated them to the latest version and finally updated the BIOS to the latest update and all went well.

When I looked in CPU-Z or Windows Properties for that matter. It says that my CPU Core Speed runs on 2.9Ghz while, correct me if I am wrong, the Core Speed should be on 3.3Ghz. I have not touched any settings in the BIOS.

So my question is, why is the Core Speed being limited to 2.9Ghz or what is limiting the Core Speed to 2.9Ghz. And is there a way to fix this issue?

I have had the CPU under heavy load before by running multiple benchmarking tools but I never saw the core speed change to 3.3Ghz nor did it change anything when playing games.

---

Another short question I have is:

When I activated a XMP Profile for my memory, I believe it was the 2666mhz profile, the computer did boot, but didn't post anything. I only saw a black screen and it turned itself off after a few minutes. I waited a total of 15 minutes and I was finally able to go into the BIOS to turn it off again. I have yet to try the 2400mhz profile.

I am pretty sure the components are not defect and since I am not that handy with computers in the first place. I'd rather wait for someone with more experience to come look at this issue.
 
Solution
I believe that you motherboard probably has a setting that is dynamically controlling the cpu multiplier and possibly the voltage as well. What I have found is that the cpu under heavy load ramps up to the max 3.3Ghz stock speed & 3.6Ghz Turbo speed, but whilst the machine is idling it drops down to save power. You can fix your multiplier at its stock, or even attempt to overclock your 'k' chip, i've managed to get 4.3Ghz out of mine, though I'm still testing its stability through long duration stress testing.

This dynamic setting can be altered in your BIOS or within software provided by ASUS, but generally speaking I have been recommended to leave it be if your not overclocking, as it is a fairly sensible way to manage power...

mic1983

Distinguished
Mar 21, 2014
111
0
18,690
I believe that you motherboard probably has a setting that is dynamically controlling the cpu multiplier and possibly the voltage as well. What I have found is that the cpu under heavy load ramps up to the max 3.3Ghz stock speed & 3.6Ghz Turbo speed, but whilst the machine is idling it drops down to save power. You can fix your multiplier at its stock, or even attempt to overclock your 'k' chip, i've managed to get 4.3Ghz out of mine, though I'm still testing its stability through long duration stress testing.

This dynamic setting can be altered in your BIOS or within software provided by ASUS, but generally speaking I have been recommended to leave it be if your not overclocking, as it is a fairly sensible way to manage power consumption. That being said, if your intention is to overclock, which is what I have been trying to do, these power saving measures can contribute to a less stable system.

A good way to monitor your CPU usage and see what speeds your system is running at is to throw a stress test at it. I have used Aida64 which is free software, and also Intel XTU which is geared towards the overclocking of machines. Both have a utility that will push your system to 100% CPU load, and will indicate the speeds at which your system is actually running. I have also been recommended x264 as a testing utility, but cannot vouch for it as I have yet to use it.

Regarding the XMP, I'm afraid I cannot comment. I opted for less fancy crucial RAM...
 
Solution