Clock Drift driving me nuts. Any way to sync to CMOS clock?

Qdos said:

If you did what I suggested in the registry you could have Windows automatically correct its clock whenever it falls more than 'n' seconds out of sync' with the time server selected.

Your CMOS clock has nothing to do with it, as pointed out by others...

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config
Version

Thanks, I'll try that. Your reply was overlooked as it was mixed in with everyone telling me to use a different server. I'm not clear on how Windows can tell it is out of sync w/o actually polling a time server or the CMOS clock, but I don't need to understand "how" something works as long as it does. :)

I'm a little concerned about changing my "interval" from the default setting of "900" down to just "5". How frequent is that? Every 5 milliseconds it will be checking my clock?

I would seriously *not* poll the server more frequently than twice hourly as doing so more often could in itself cause errors in the Windows clock.

If you Google the registry key I've highlighted there are numerous web-pages surrounding the issue.

Qdos said:

I would seriously *not* poll the server more frequently than twice hourly as doing so more often could in itself cause errors in the Windows clock.

Yes, that's part of the reason I asked to sync to my CMOS clock instead.

Qdos said:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config
Version

This entry controls the period of time for which spike detection is disabled

Just a follow-up. After four days since making the noted Registry change, the problem appears to have been resolved. Yours was the only mention of "spike detection" I've read from anyone on this issue. MS should issue a patch.

Thanks.

I don't know why people had such a hard time understanding your question. While I don't know how to resync with your CMOS clock, I have found this to be the most reliable method of keeping time accurate: Make Windows synchronize time more often

Thanks for the reply to my old post, though I eventually found a fix after a bit of searching (I've long forgotten what it was), but I know it included polling the Time Server more often... which is a bit of a no-no, and eventually, even that wasn't enough.

I don't remember the exact cause, but it had to do with certain tasks using up too much CPU time too often, along with too many Tray apps (no more than ten, but that was enough to bog XP) causing the RTC to lose time.

I've since moved to 64bit Win7 and no longer have the problem. Thx.