We help IT Professionals succeed at work.

erratic clock behaviour in Windows XP

doublehorn
doublehorn asked
on
3,419 Views
Last Modified: 2012-05-04
I administer a Dell Dimension P4 desktop running Windows XP Pro, SP1. This computer, like 5 others on the same subnet, is acquiring an NTP/GPS time signal via Tardis Time Server (running as a service). Occasionally, but with increasing frequency, this system clock on this machine becomes uselessly erratic. This erratic behaviour seems to fall into one of two categories:

1.) the clock spins forward at a rate of 15 sysclock minutes: 1 real second.
2.) the clock spins backward at a rate of 5 sysclock seconds: 1 real second.

This computer runs client software for a 911 Emergency Dispatch CAD system, so the accuracy of the timestamp of data sent from this computer to the CAD server is fairly important for legal purposes. Obviously, the timestamp of the data sent from this problem machine is worthless when the clock is behaving this way - which, these days, is at least once a week. A reboot usually resolves the problem for a period, but since this machine needs to be on and operational 24/7 (911 dispatch business requirement), rebooting in the middle of a 911 call is not always an option.

I see one of 3 options:

1.) some sort of NTP clock-variation suppressing software, that suppresses variations in time above a certain threshold, say 500ms.
2.) install some sort of monitoring tool to see if there is some specific circumstance that might cause a clock to behave in this way.
3.) buy a new computer - not really a feasible option, since Dispatch guys just bought this computer and probably couldn't make an argument for buying yet another.

There are 2 identical Dell Dimensions running the same suite of software on the same subnet off the same NTP time signal that are behaving just fine, so I've ruled out ambient heat or some other digital or physical environmental condition. I've tried a few shareware monitoring and suppressing utilities, but so far haven't found anything that is really helpful. Any thoughts, I'm all ears.

doublehorn - from the not-quite-so-frozen wilds of Southern BC.
Comment
Watch Question

Fatal_ExceptionSystems Engineer
Top Expert 2005

Commented:
Try replacing the battery on the motherboard first..  An inexpensive solution to an otherwise drastic problem..
Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION

Commented:
Atomic Clock Sync utility

Free! - Atomic Clock Sync utility
Our freeware Atomic Clock Sync utility can help you keep your local computer up-to-date with the exact current time.

This program will reference an atomic clock server to get the current time with the greatest accuracy available and update your PC's information. It can even be set to automatically check the time once a day to keep your PC's time accurate forever. Best of all, you can download and use this utility at no cost to you!

No spyware! No ad banners! No cost! No questions asked! So why do we do give Atomic Clock Sync away as freeware? Simply to encourage you to use and return to World Time Server.com for the current time in places other than where you live!

  download Atomic Clock Sync 2.6 via WinSite.com        

(this free utility requires Windows XP, 2000, Me, 98, 95 or NT 4)

http://www.worldtimeserver.com/atomic-clock/




Keep your PC time accurate with our FREE Atomic Clock Sync

http://www.worldtimeserver.com/


SHAREWARE:


 Welcome to AtomTime.com -- Home of AtomTime95, AtomTime98 and AtomTime Pro

 http://www.atomtime.com


 iTimeSync
 
The accuracy of your PCs clocks is important for many reasons, but keeping it that way can be a chore. iTimeSync does the job for you by contacting one of many NIST time servers over the internet. No configuration is needed, simply connect to the internet, run the program and press "Correct". iTimeSync can also be set to automatically synchronize any minute / hour / day period and it supports both the RFC-868 (TIME) and the RFC-2030 (SNTP) protocols. While servers names are included, this list can be easily changed, for example, to servers that are closer to your locality or to a local server on your LAN. iTimeSync can even sync from another iTimeSync as it can be used as a TIME server on a LAN. Other features include detailed logging, auto advance to another server if the selected one fails, auto start, minimize to tray, check without change, correct only minutes and seconds mode, and a positive or negative time offset can be set if you are in a obscure time zone or if you like your clock to be fast or slow.

http://www.sinnercomputing.com/iTimeSync.htm


http://www.tucows.com/preview/323370.html


http://www.softcities.com/iTimeSync/download/2331.htm

I think your best bet is to check with Dell.  If you "just purchased" this one, they'll most likely send someone up for free on-site service.  Or just threaten to return the unit for replacement.

I don't think it is a battery issue.  Usually the batter is used to keep the bios and/or clock when the computer is off.  It should affect the outcome of the clock when the computer is turned on.

I don't think the automic clock sync would help either.  If what you said was true, then this problem occurs while the computer is running.  Which means that you may have synchronized your clock 3 hours ago, but it could just go off on you... and setting the computer to sync on a minute-by-minute bases isn't a real option.

I think this could either be a hardware issue or a software glitch.  Perhaps you should ask Dell and see what they think.  Let them know that you're calling from a 911 dispatcher, because I'm sure they don't want to be blamed for a system foul-up during an emergency 911 situation :-P

- Info
Fatal_ExceptionSystems Engineer
Top Expert 2005

Commented:
Very true info..  just that replacing that battery could (emphasize could) be a $4 solution..  And letting Dell know that this is for 911 dispatch purposes is excellent..  They will definitely be more helpful if they know that..  

Author

Commented:
Sorry about the delay in awarding points for this question. The intermittent nature of the problem dictated that I needed to see several weeks of stable behviour before calling the problem resolved.

LRI41's suggested that Dell had issued a patch to correct some system clock weirdness which I downloaded from Dell and applied. In the weeks since I've applied the patch, the clock has been 100% stable and accepts its time from the NTP time signal as reliably as the rest of the 911 workstations in the Dispatch Centre. While I'm going to maintain a high degree of skepticism about the fix, it seems like this actually worked. All 250 Points go to LRI41.
Fatal_ExceptionSystems Engineer
Top Expert 2005

Commented:
Very good..  Kudos to LR for finding that fix..

FE

Commented:
Nothing brillant about it, I boughty a Dell for myself and my two sons a couple of years ago, and myself and one son had clock problems until we applied this fix.  Now my runs almost perfectly, mayby gets a second or so behind every 6 or 8 months.

Thanks
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.