Windows 10: Clock "slows down", yet is able to manually sync correctly

Hello!

Windows clock somehow manages to get out of sync even when the computer is up and running. For example, I now synced the clock and it went from about 12:17 to 14:05! Usually the difference is not so big, about 5-10 minutes. It also happens when I've set the time manually. And when I shut the computer down or put it to sleep, it resumes correctly (not entirely sure though as the time is constantly showing wrong results). When manually switching off the automatic sync and then turning it back on, the system receives the correct time from time.windows.com. Yet it isn't able to sync itself correctly automatically.

The motherboard is now about six years old - it feels that I might have to change its battery. Should I go forward with that or could the problem lie elsewhere?

Edit: During posting this question (about 10 minutes), the system lost 3 minutes! This forum showed the correct time, my system did not.

:)

 

Lumia " The Future is Here "

This is a support forum, not a complaints department.

I suggest you directly submit your complaints about hardware to Nokia and software to Microsoft.



Also it often helps to read reviews when switching platforms to make sure it suits your needs. From what you've said the Lumia 820 clearly doesn't suit you.

 

Lumia " The Future is Here "

psychomania: This is a support forum, not a complaints department.



psychomania: Also it often helps to read reviews when switching platforms to make sure it suits your needs. From what you've said the Lumia 820 clearly doesn't suit you.



What RSXforever wrote was a kind of review, that can help other people to judge, if Lumia is the right phone for them.

 

It might well be that the CMOS battery is getting empty. Before you get a new one, you can also try the below procedure:

This issue can be caused by the Windows Time service being corrupt. You can try to take the following steps to troubleshoot this issue.

Run the following command in an elevated command prompt: net stop w32time
w32tm /unregister
w32tm /register
net start w32time
Then, please restart the computer to test the issue again.

If any error message was received when doing these steps, please let us know.

 

Your system battery is on its way out. Get a replacement.

 

Are you, by chance, dual booting with a Linux distro?

 

No, I'm not. This system had a W7Pro clean install plus user-initiated W10 upgrade on the launch day.

I now tried Joergi's solution:
Attachment 37010

I'll report if there's any improvement.

Thanks for suggestions!

 

Have you tried changing the time sync settings from time.windows.com to time.nist.gov?

 

The CMOS battery isn't used when PC is running - clock - Why do PCs still require a CMOS battery? - Super User and as time is kept OK when turned off the battery is most likely not the issue.

You could have a look here for other causes (I know it is an old thread but so is your MB *Wink ) Slow Clock or Lagged Time on Win7 x64

 

It seems that as of now, changing the update server address from time.windows.com to time.nist.gov did solve the problem! The clock has been correct for at least 12 hours *Smile

Thanks to everyone for input!

 

You're welcome, keep us updated please*Biggrin.

 

So, out of nowhere, the problem has returned. I checked and the update server is still time.nist.gov (meaning Windows hasn't forced the default one).

It all still happens when the computer is running, so I'm reluctant in terms of going for a new battery, though maybe I should just do it "just in case". I've heard different opinions about whether the clock is using the CMOS battery during computer uptime or not.

Edit: I think I'm going to try the motherboard's (Gigabyte) support service also.

 

That's a good idea, maybe they have a new BIOS for Windows 10(although that really shouldn't effect the clock, but one never knows).

 

Well as far as I've checked, I'm running the latest BIOS which is from 2010. But I'll try and contact them.

 

Before going on with contacting the motherboard's manufacturer, I also created a simple test and found out that compared to the smartphone's stopper, the system clock lost 11 seconds during a 1 minute test period. This means that the clock is continously losing time.

Secondly, I tried to test the battery by shutting the computer down completely for the night (I forgot to pull the plug from the wall though), but during the night and during today's uptime (about 6 hours now), the system clock has been correct. So it would seem that the restart did solve the problem (and probably solved it the last time, too). It seems that something is getting in the clock's way while using the computer as usual.

I currently don't know where to look and I don't have much faith in the support line also...