I am having a huge problem with the clock on a Windows XP machine. Whether getting its time from the domain controller using w32time and an ntp server (PDC) / client, from a GPS clock directly using meinberg NTP client (ethernet), or the computer's internal clock only, we are getting times that are way off (on the order of minutes per hour, sometimes more, sometimes less). I'm at the point where I can't go a full day without it being refused from the PDC because of time inaccuracies. However, it doesn't seem to skew like this all the time. Unfortunately, the computer is almost constantly being used, and the applications that run on it are reasonably heavy (~30% average CPU load, ~60% average memory load), so I don't have the luxury of running, say, no applications for a day, then starting some, etc. to try and figure out what is going on. Does anyone have any remote/'hands-off' tips that I can use to monitor and pinpoint what is going on here? I used the meinberg monitoring tool to gather NTP information, and all that told me was that the clock was getting way off during the day and coming back slowly at night, which is another thing that makes me think a specific kind of usage is an issue. Any tips would be greatly appreciated.