Note This problem also applies to x64-based versions of Microsoft Windows Server 2003. However, this article and its associated private hotfix are not intended to resolve timing problems in games and other applications that run on AMD dual-core computers. For more information about performance issues on dual-core computers, click the following article number to view the article in the Microsoft Knowledge Base:
Update informationThe following file is available for download from the Microsoft download center:
Download the WindowsXP-KB896256-v4-x86-ENU.exe package now.
Release Date: December 19, 2006
For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
PrerequisitesNo prerequisites are required.
Restart requirementYou must restart the computer after you apply this update.
Update replacement informationThis update does not replace any other updates.
File informationThe English version of this update has the file attributes (or later file attributes) 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 item in Control Panel.
|File name||File version||File size||Date||Time||Platform||SP requirement|
- Multiple physical sockets
- Multiple-core designs
- Multiple logical threads, such as Intel hyper-threading technology
This hotfix also addresses the following issues on computers that have multiple processors that support processor performance states:
- A possible decrease in performance on single-threaded workloads when processor performance states are using demand-based switching.
- The synchronization of the processor Time Stamp Counter (TSC) registers across processors when you use the ACPI Power Management timer on multiprocessor systems.
- ACPI C-state promotion and demotion issues in the kernel power manager.
Possible decrease in performance during demand-based switchingDemand-Based Switching (DBS) is the use of ACPI processor performance states (dynamic voltage and frequency scaling) in response to system workloads. Windows XP processor power management implements DBS by using the adaptive processor throttling policy. This policy dynamically and automatically adjusts the processor’s current performance state in response to system CPU use without user intervention.
When single-threaded workloads run on multiprocessor systems that include dual-core configurations, the workloads may migrate across available CPU cores. This behavior is a natural artifact of how Windows schedules work across available CPU resources. However, on systems that have processor performance states that run with the adaptive processor throttling policy, this thread migration may cause the Windows kernel power manager to incorrectly calculate the optimal target performance state for the processor. This behavior occurs because an individual processor core, logical or physical, may appear to be less busy than the whole processor package actually is. On performance benchmarks that use single-threaded workloads, you may see this artifact in decreased performance results or in a high degree of variance between successive runs of identical benchmark tests.
This hotfix includes changes to the kernel power manager to track CPU use across the processor package. These changes enable visibility into the true activity level of a CPU complex and therefore help correctly calculate an increased target performance state.
Note This solution favors performance gains over power savings. Although benchmark performance scores may improve, battery life could be negatively affected. Accordingly, this kernel policy change may be disabled by a registry key to allow for maximum flexibility.
How to disable the new performance state policy behaviorImportant This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
After you install the hotfix that is described in this article, you may use registry settings to disable the new performance state policy behavior.
To have us disable the new performance state policy behavior for you, go to the "Fix it for me" section. If you prefer to fix this problem yourself, go to the "Let me fix it myself" section.
Fix it for me
To fix this problem automatically, click the Fix it button or link. In the File Download dialog box, click Run and then follow the steps in the Fix it Wizard.
- Please install the hotfix that is described in this article before you run this package.
- This wizard may be in English only. However, the automatic fix also works for other language versions of windows.
- If you are not on the computer that has the problem, save the Fix it solution to a flash drive or a CD and then run it on the computer that has the problem.
Then, go to the "Did this fix the problem?" section.
Let me fix it myselfTo use registry settings to disable the new performance state policy behavior, follow these steps:
- Click Start, click Run, type regedit, and then click OK.
- Right-click HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager, point to New, and then click Key.
- Type Throttle for the new key name.
- Right-click Throttle, point to New, and then click DWORD Value.
- Type PerfEnablePackageIdle for the value name.
- Right-click PerfEnablePackageIdle, and then click Modify.
- In the Value data box, type 0. Make sure that Hexadecimal is selected in the Edit DWORD Value dialog box, and then click OK.
Note You can type 1 in the Value data box to enable the new performance state policy behavior.
- Quit Registry Editor.
Did this fix the problem?
- Check whether the problem is fixed. If the problem is fixed, you are finished with this section. If the problem is not fixed, you can contact support.
- We would appreciate your feedback. To provide feedback or to report any issues with this solution, please leave a comment on the "Fix it for me" blog or send us an email message.