Article ID: 323154 - Last Review: October 27, 2006 - Revision: 1.2

Mobile Processor May Remain on "High" After Resuming from Standby

View products that this article applies to.

System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.

This article was previously published under Q323154

Expand all | Collapse all

SYMPTOMS

If you put a laptop computer in standby and resume it repeatedly while the computer is using battery power, the processor may remain at full power until you restart the computer. This problem occurs only on computers with processors that support multiple power-consumption states.

Back to the top

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows XP. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

322389 (http://support.microsoft.com/kb/322389/EN-US/ ) How to Obtain the Latest Windows XP Service Pack

The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

   Date         Time   Version      Size    File name
   -----------------------------------------------------
   31-May-2002  15:35  5.1.2600.46  30,848  Processr.sys
   31-May-2002  15:35  5.1.2600.46  37,284  P3.sys
   31-May-2002  15:35  5.1.2600.46  31,744  Crusoe.sys
   04-Jun-2002  09:50  5.1.2600.46  32,256  Amdk6.sys
   04-Jun-2002  09:50  5.1.2600.46  32,768  Amdk7.sys

Back to the top

WORKAROUND

You can restart the computer to use the power-saving features of the processor again.

Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows XP Service Pack 1.

Back to the top