Clock is off by less than a minute.

[bru]

I noticed that my clock is a bit slow. I think it started happening within the last week or so. Prior to that there were no problems.

It is set to synchronize automatically but I manually synchronized and sure enough it is now correct. So is it not synchronizing on it's own? Any ideas?

 

[derekimo]

Mine was doing that too for about a week, it finally caught up.

 

[jumanji]

Keep a watch. Your motherboard battery may be coming to its end of life and replacing it may be a good idea if your machine is constantly losing time when not in use or needs frequent manual synchronisation.

 

[bru]

Keep a watch. Your motherboard battery may be coming to its end of life and replacing it may be a good idea if your machine is constantly losing time when not in use or needs frequent manual synchronisation.

I sure hope not. It's an nine month old computer.

 

[arkhi]

Check Task Scheduler under Task Scheduler Library->Microsoft->Windows->Time Synchronization and see what the options are and diagnose from there.

Also, I set mine to synchronize with time.nist.gov since it's more reliable.

 

[jumanji]

Keep a watch. Your motherboard battery may be coming to its end of life and replacing it may be a good idea if your machine is constantly losing time when not in use or needs frequent manual synchronisation.

I sure hope not. It's an nine month old computer.

I too hope it is not. But premature failure of any component is not unknown. And I made a conditional statement if blah, blah....

Now a definitive statement: If for no other reason your clock is losing time, then it is the battery. False positives and false negatives can always happen in any diagnosis.

Given your situation, I would have changed the battery without a blink -and irrespective of the battery manufacturing date, and think of any other thing only if it fails to resolve the problem. My way.

 

[bru]

Check Task Scheduler under Task Scheduler Library->Microsoft->Windows->Time Synchronization and see what the options are and diagnose from there.

Also, I set mine to synchronize with time.nist.gov since it's more reliable.

Screen shot attached. It says it's ready and that it ran succesfully. But it definitely was not run this Sunday at 1:00 AM. Does the computer have to be on? Because it is not at that time.

After the computer being off about nine hours clock is spot on at this point.

 

[arkhi]

It runs at the next opportunity it gets after the scheduled run time. In your case, it ran on Tuesday last week at 6:14 pm (that answers the "So is it not synchronizing on it's own?" part. Your clock synchronizes every sunday). If you could remember that it wasn't synchronized back then, it might have gotten an error but task scheduler still reported it as successful. Personally, I had my issues with synchronizing with time.microsoft.com.

On another note, there really is no need to synchronize your clock more than once a week. If your clock really gets that off often, then I would follow jumanji's advice since that's most likely the culprit. The other possibility is that some program with admin access is messing with your clock.

 

[logicearth]

Are you sure the clock is off? What are you using to compare it to? Sure it is not off? And is less then a minute really worth all the trouble?

 

[Comp Cmndo]

You can use Web Time to set time.
Software Design - WebTime for Windows by Gregory Braun

 

[stormy13]

I sure hope not. It's an nine month old computer.

Doesn't mean that it is a 9 month old battery. Have you checked the time in the bios to make sure it isn't out? As already mentioned Windows gets its time from the bios, and if the battery is weak/dying Windows will be syncing all the time till the battery is changed.

Nice thing is that it is about the cheapest component in the computer to replace (a couple of $$ at most) and can be bought anywhere watch batteries are sold (unless they used an odd battery, most use a CR2032).

 

[bru]

It definitely was off by about 90 seconds. Being off isn't really a problem but I was more concerned as to why it was off and why it had changed. It had been perfect for nine months and even my old computer never wavered in six years.

I was given the possibility of a battery going bad. After manually synchronizing the clock has been perfect for two days, even with the computer being off for many hours at a time. So I'm thinking it must have been related to the last synch. Perhaps microsoft.time had a glitch. Another user reported they had a problem too.

I will definitely keep an eye on things. If it again goes off then I will have to further investigate. As mentioned, it's not the clock per se being off, it's why it is happening.