Very strange WinXP clock problem... need help.

[hawkeyewx]

The Windows clock gets its initial time from the motherboard when it boots up, but how does the clock keep accurate time after that?

I'm having a very stange problem with my Windows XP clock. Sometimes when my computer boots up the Windows XP clock runs very fast, about 9 minutes too fast after one hour. Sometimes the clock runs perfectly normal. If I turn my system on in the morning and it is running too fast, I have to reset the system once to get the clock to run at normal speed. The two or three times I've gone into the bios menu to watch the clock, it was normal and also, every time I turn my computer on in the morning the windows xp clock starts out in sync with real time. These facts would suggest the motherboard's clock is not at fault.

I'd really appreciate any help on this. It has been very difficult to find anyone who has even the slightest clue about this strange problem.

 

[Nothinman]

It should keep track via the timer interrupt, but I can't say for sure. Search the MSDN pages and see if they say anything.

 

[NogginBoink]

If you are in a domain, XP will query the domain controller for time at regular intervals.

Other than that, the timer interrupt is indeed the primary mechanism.

You can also configure XP to get time from an external SNTP server such as the Navy's atomic clock. Search the KB.

 

[MrChad]

I believe the XP in a workgroup synchronizes with an internet server by default. Double click the clock in the system tray and check the "Internet Time" tab.

 

[Canterwood]

Yes, I'd agree with Chad on this one.

It might be the internet time synchronizing with microsoft's clock.

 

[filmmaker]

Yeah, it used to be mainly dependent on the battery on the motherboard, but most clocks update themselves through Microsoft.