If the the Speed-stepping was enable, then from the hardware perspective should be working fine. However we would recommend updating the firmware again just in case.
Bear in mind that this could also be that your operative system may be running a software that is causing this spike in the processor, in this case it would be a matter of checking what software or services are running on this system.
We are not aware about any other tool from us to check this besides the one that you already provided. At this point it will be a matter of checking in the operative system the services or programs running that may be causing this.
I have tried to find the source of the problem, but am not finding the corresponding service or software doing this.
Can someone help and post a way to find what is causing the cpu not to use a lower multiplier?
You may know what is needed to keep it up at full multiplier so hopefully can help in finding the problem.
Maybe there is also a software beeing able to overpower this malfunction and set the multiplier autmatically, like
0-10% multiplier 1
10-50% multilier 2
and so on
Thank you for a hint.
The processor does this automatically so there is not utility to bypass this settings as previously mentioned.
Have you tried updating the server board firmware?
I've sent you and email with some information regarding this issue too.
Let me know if you received it.
@ Estenan.V.: I got your mail, and no, it's not usable,
It states: Attempted to install on an unsupported platform.
Checked CPU for rest-able settings in powerconfig.
HWInfo64 states this picture all the time:
The firmware was updated but did not change anything.
Currently running: S5000.86B.15.00.0101.110920101604
Given the CPU can go to sleep-mode, what tool can I use to see what is causing it to stay awake?
There is supposed to be a Signal to the CPU telling not to rest.
As stated before there is no utility to tell the processor to do that. This feature runs automatically within the processor, so if it's enabled in BIOS then should be working fine. If you already check in deep the processes running at the operative system level then the next course of action is trying using a different processor a see if it exhibits the same behavior.