Windows Clock

[Adron]

When does it say it is going to auto sync next? Be around for that time and run a packet capture...

[MrRaza]

Update your service pack, it might fix your problem

[MyndFyre]

I always hate to suggest service pack updates, especially because SP2 is so much...  but at the same time, it's scary that you're running XP without any and service packs.

About your timing, though: how long does it take for your clock to get 10 minutes off?  Are we talking days/weeks, or minutes/hours?

I once had a problem with the timing chip on a 486 DX/2 where the internal clock effectively ran twice as fast as real time.  I don't think it damaged anything permanently, but it didn't allow me to really use the computer for anything (*ALL* of the clock pulses were doubled), and it very quickly destablized the system.

I also used to have a similar problem to this with Windows 9x-based machines; when doing something hardware-intensive, it was not uncommon for my clock to miss its interrupts and update.  I haven't experienced this on an NT-based machine, so I hesitate to believe that this is the case (evidently the Clock process is of higher importance in the NT kernel), and I don't think you're experiencing the same phenomenon (your clock is actually going faster).

[Forged]

it takes a couple of hours to get off time. I realized a couple of days ago it is because it auto syncs like once a week.  I assumed it would do it every hour or so.

[Kp]

it takes a couple of hours to get off time. I realized a couple of days ago it is because it auto syncs like once a week.  I assumed it would do it every hour or so.

It still shouldn't be drifing that much.  I have a fairly old system that only syncs on my command (been several months now), and it's only drifted a minute or so.

[hismajesty]

I have the same problem. My computer clock is usually 4-6 minutes off of what time it actually is, and it's a pain. I'll manually sync it and then a day or so later it will be off again.

[Warrior]

RTC sounds like it's getting messed up or something, happens when I do a hard shutdown (flip the switch :])