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

Anonymous
2013-11-30T23:32:10+00:00

Hello all,

I have a new Surface Pro 256 and I keep noticing these warnings (Event ID 37) in my System Event Log and wonder if anyone else is getting these.  There are 4 warnings in a row as follows (see attached screenshot):

The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.

The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.

The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.

The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.

Thank you in advance!

Hal

Surface | Surface Pro | Power and battery

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2014-03-28T13:43:08+00:00

Did you change the advanced options in the power plan such as the PCI express and processor power management?  I know the default for the cooling policy is passive which will slow the processor before increasing fan speed.  Active will do the opposite increase fan speed before slowing the processor.  Also the minimum processor state will need to be changed it allows allow the CPU to automatically down clock.  Default is 5% increase it to 100%.  Also change the graphics to max performance since it is built into the CPU.  Changing all of this will really cut the life of your battery an heat things up. 

I will warn you though, if you are in a situation where some rouge process is unknowingly maxing out the processor for a period of time and the fan can't keep up with the cooling the thermal protection will kick in and shut your pc off with no warnings.  Bad flash is a prime example.

I think you all are getting this warning because you are running hot at times and some function is kicking down the processor speed to dissipate the heat and this is where the firmware and power saving in windows is conflicting generating the warning.  A example might be a windows process says I need 100% CPU and the firmware says sorry I am to hot you only get 5% and logs it as a warning or vice versa.

Not all warnings are bad and if you see this in your event log and can't tell when it is being logged expect by looking into he event log I say ignore it.  If you are crashing and see this event logged right before the crash its something to worry about and I would suspect heat.  My guess is unlike a desktop and laptop the fans in the surface are not running all the time or barely spinning to preserve battery power and if the surface heats up real fast it dials back the CPU to cut down on heat and logs the warning and if it still does not cool down it cranks up the fans.... if that does not cool things down it just shuts off - just a guess.

The only 2 scenarios I can come up with that would cause this warning is aggressive power management so they can say the battery lasts 4 hours give or take or heat.

Was this answer helpful?

50+ people found this answer helpful.
0 comments No comments
Answer accepted by question author
Anonymous
2015-09-13T20:04:49+00:00

I stopped-in to the MSFT store.  They immediately agreed that this is problematic.  They uninstalled all drivers and let Windows (10) reinstall all drivers.  Device Manager showed all sorts of problems.

After this process, the issue in Device Manager went away.  I have been using the machine for hours since then without any issues.

They did say, however, that if the issue comes back, this would be a candidate for a swap-out for a new Surface.

On a side note, I can't say enough how helpful the folks at the MSFT store have been, in multiple locations.  Nice to see it from MSFT.

Was this answer helpful?

30+ people found this answer helpful.
0 comments No comments

63 additional answers

Sort by: Newest
  1. Anonymous
    2014-03-21T17:13:09+00:00

    This issue has been documented on other forums for causing unsuspected shutdowns.

    i have checked my event logs and these errors always precipitate the shutdown.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-03-21T16:46:30+00:00

    I don't see a connection - how does the speed being limited by the firmware make you lose work?

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2014-03-21T16:30:53+00:00

    So in the mean time, just because it doesn't effect performance, we need to put up with i?

    This has happened to me numerous times in the middle of work and I lost valuable data.

    Autosave can only "CYA" (Cover your !@#) for a limited amount. 

    It is kind of ridiculous that I would need to constantly remind myself to save every 5 minutes.

    This only started occurring after the firmware update (back in Jan). Does microsoft not test their patches???

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments