A Microsoft Windows Server 2003-based server may experience time-stamp counter drift if the server uses dual-core AMD Opteron processors or multiprocessor AMD Opteron processors. When this problem occurs, operations that rely on the time-stamp counter may not function correctly. These operations include network communications and performance monitoring. For example, if the server is an Active Directory domain controller, you may receive the following error message:

CAUSE

This problem occurs when the time-stamp counters for different processor cores are not synchronized. Windows Server 2003 uses the time-stamp counter as a timekeeping source. Each processor contains a time-stamp counter.

To resolve this problem, configure Windows Server 2003 to use the PM_TIMER setting instead of the time-stamp counter. To do this, add the /usepmtimer parameter to the Boot.ini file, and then restart the server.

Note The /usepmtimer parameter is automatically added to the Boot.ini file when you install the latest AMD PowerNow! Technology driver from AMD. The updated driver does not resolve this problem itself. However, the installation process makes the necessary changes to the Boot.ini file to resolve this problem.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.