The speed of processor 7 in group 0 is being limited by system firmware.

I keep getting this error in Event Log upon ever restart:

"The speed of processor 7 in group 0 is being limited by system firmware."

I tried with tDCP, without, with overclocking, without, doesn't matter, always happens, be it on Windows 8.1 or Windows 7

What's there in the firmware that's limiting the processor speed?

PS: With my new 4940MX CPU no more Event ID 18 (CPU Cache Hierarchy errors) in Windows 7

 

this error is caused by the power management when it throttles back the cpu when its idle or under light use. If you want to see what the cpu is currently operating at use CPU-Z. If you look at the clocks section under the cpu tab it updates in real time and you can see what the cpu is operating at. Test it at idle and under load. If its not hitting it max clock speed under load check the power management options in windows and the bios it may be set to minimum performance which will lower the clock speed to conserve power.

 

You know that windows do not like Hotwell ? Windows fails to read the correct information from the processor (clock speed). If the processor has the correct clock speed and Windows thinks otherwise, then it becomes so. Windows is unable to measure the correct clock speed from processor .. Even if you install everything again and do everything right, comes this event still inside the event list. Microsoft sucks . Even if you use the software "unpark cpu" you get this message in the event viewer .. Long live Micro$oft

 

I get that from Windows 8. I don't get that event from Windows 7. CPU performance blows with Windows 8. It's a really sucky operating system if you care about performance. You can butcher it easily enough to make the UI palatable, but there is no cure for its lousy performance. I expect the Windows 10 RTM flavor to be the same or worse. Micro$haft has gotten to be really sloppy at everything, like most other big corporations have.

You're wasting time trying to use cTDP overclocking. It doesn't work correctly with the Haswell Alienware machines because the settings you need to access are neatly tucked away on a hidden menu. cTDP overclocking with a fully unlocked BIOS on the M18xR2 works so-so, but not as well as regular, old fashioned BIOS overclocking settings.

I still recommend using the Unpark utility and setting HPET. Both will help your performance a little bit, but won't stop that Windows glitch from generating Event Viewer log bloat. In the Windows Power utility, use the "High performance" profile and go to the Advance Settings area. Make the CPU minimum and maximum processor states both 100% for AC and battery power. That will also help.

 

Is it so that other laptop brands have the same problem (win 8 dislikes Hotwell) as AW laptops? Is it perhaps the BIOS as AW use, that is the problem (garbage)?

 

I haven't seen any Clevo Haswell laptops that overclock the CPU as well as your Alienware 17 or this Alienware 18 CPU. They have thermal management issues that are worse than the 17 or 18. Haswell runs way too hot on everything, even though they generally need less voltage. In spite of their unresolved issues, until the most recent BGA turds were unleashed on the public Alienware still had the overall best laptops available anywhere if you don't count the amazing P570WM with 4930K/4960X CPU.

 

I thought more about this event. Have other(brands) laptop's same problem with Hotwell and Win8? My AW works brilliantly even though I have this event. A bug from Win 8 .. Now create Dellienware laptops with processors that can only hold base clock speed. After 1 min then cuts the processor turbo boost off in the new thin Apple boxes.