| Event Id | 36 |
| Source | W32Time |
| Description | The time service has not synchronized the system time for %1 seconds because none of the time service providers provided a usable time stamp. The time service is no longer synchronized and cannot provide the time to other clients or update the system clock. Monitor the system events displayed in the Event Viewer to make sure that a more serious problem does not exist. |
| Event Information | W32Time reports itself as "unsynchronized," and it stops serving time to requesting clients. In response to the unsynchronized status, an event ID 36 message is logged in the system event log. CAUSE: This problem occurs because there is a code bug in the Release Candidate 1 (RC1) release of Windows Server 2003. The problem is aggravated by network congestion, a high CPU load or a high network load, and synchronization from low accuracy time sources. RESOLUTION: The problem has been resolved in post-RC1 builds of Windows Server 2003. |
| Reference Links | Registry entries for the W32Time service How to configure an authoritative time server in Windows Server 2003 W32Time reports an incorrect time for how long a computer is on standby Availability and description of the Port Reporter tool List of fixes included in Windows XP Service Pack 2 Resolution Information |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.