Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 37 Source: Microsoft-Windows-Kernel-Processor-Power
The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 423 seconds since the last report.
|English: Request a translation of the event description in plain English.|
IT System Admin
This is a known bug with Dell PowerEdge T320 Servers and Server 2012 R2. In my case, it was happening randomly only once or twice a month. The CPU would go down to below 0.20 Ghz and the server would crawl.
If your CPU has been tested and is not overheating, this is the workaround:
In the PowerEdge Bios, change the System Profile to Performance Optimized. This will disable C-States and C1E.
This is a known bug with Windows 2012/2012R2.
This Windows error is informational but is marked as an Error in the event log and is just reporting normal processor speed step and C State transitions.
To solve this "error", do the following:
- In Windows, check your Power Options. Make sure that your Power Scheme is set to High Performance, and check that every option is set to “Always On”.
- Make sure you have installed all latest drivers and firmware, especially for your motherboard and CPU.
- Reboot your computer and go to your BIOS settings. Make sure that your power settings are set to maximum. This differs from computer to computer.
In case the error occurs on a server and the above does not resolve the issue, you may optionally set the Minimum Processor Idle Power State “No C-states”.
See EV100511 (PET620 Hyper-V Issue).
Little Tech Guru
When you see this warning please also check the time, when this event was happened. Can you remember, if your machine was running on battery power at this time? If so, this is the answer. At least in my case, every time I get this event id 37 warning, I was running on battery.
Got this error on my M1530 running Windows 7 x64. I could tell the system was running hot and I could hear the fans working really hard on occasions. So, I opened it up and used a can of air to clean out all the dust. Put it back together and the error has not reappeared. Seems to me the CPU got too hot and the fans could not keep the heat under control so the BIOS down-clocked it for safety.
Several posts on support forums suggested that the first step in troubleshooting this error would be to update the motherboard firmware.
EV100176 provides some suggestions to fix this event on HP DL360G6 servers.
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
|Custom search for *****: Google - Bing - Microsoft - Yahoo|
Send comments or solutions
- Notify me when updated