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

I'm also getting this, i set my clock before i went to work about 9 hours ago, and I've lost an hour. I have also noticed that my keyboard seems to think it's American(it's a UK keyboard).

Can't really contribute to an answer, but I can add, I am also running a rather old build.

I first noticed this problem approximately 48 hours ago.

 

Well, it's not the battery, that's for sure. In my case at least. I tested the battery extensively and it precisely maintained the time.

I checked all the running applications also and found that I had (somewhat foolishly) installed a codec pack for the VLC player, which also added a running application. I tried it as a (bad) solution for a problem I've also described in this forum (but got no answer). Neither the AVG nor Malwarebytes said anything bad about it. The problem with video playback was also somewhat time related as different players had different problems syncing the audio with video. I've now uninstalled the suspicious application.

The current state of the system needs some testing time but the moral of the story is - check if everything is clean and there's no useless crap running in the background.

 

Isn't trouble shooting fun*Biggrin.(as long as it isn't your business PC*Shock)

 

Yeah I guess it is. That's my PC, but I do some IT-stuff at work so I hope they won't see it. *Biggrin

 

I'm sorry if it's wrong to dig up this old thread, but for anyone who might have some suggestions or who face similar problems, I have some additional input on this:

* The problem is still there.
* Restart or Shut-down+power up solves it.
* It happens only after the computer has been in the sleep state.
* It's not about the motherboard's battery.
* It also messes up video playback - sound fails in VLC, video may fail in W10 player, legacy windows media player is sometimes unaffected.
* Adobe Premiere Pro workflow is completely interrupted, lags horribly.
* The windows clock loses time continuosly​.

 

I'm having the same problem. It's like the CPU is being held hostage and only gets to take a breath every 3 1/2 seconds. I've exhausted everything I know to do. Maddening!

I'm running Windows 10 Home on a Dell Studio XPS 2.67GHz with 8GB of RAM.

Anyone got any ideas?

 

This is a longshot and only relates to the clock issue. I ran into a similar issue on WIN 7. It turned out to be caused by an update I did to AOL Desktop. I reverted to the prior AOL Desktop and the clock went back to normal. If you don't have AOL Desktop just ignore this, but I thought I'd toss it out since you seem to have tried all the most logical fixes already. Good luck.

 

Thanks Poolmon. I don't run AOL, but I did uninstall/reinstall some other apps I had recently installed, to no avail. HOWEVER, out of desperation, I tried what Microsoft tells you and rebooted a few times and to my amazement - it worked! Clock is ticking away like it should and has been for about 16 hours now. I'm at a total loss to explain it!

 

I also had this issue, the clock was visibly running slowly. After reading this thread I did a few reboots but I'm not sure that fixed it.
However it ran its battery down overnight in sleep mode, and this morning, after powering it up, the clock is running normally.

 

So now, after completely resetting the computer (because of moving to another machine) through Windows 10 settings and after all the recent updates, the problem still persists. The quick and clear fix for me is to not use the sleep mode and only shut down the computer if neccesary. This problem affects the clock, video playback, some programs and most of the games I play. For example, in Starcraft II, the game works otherwise as intended, but the speed of gameplay is very slow. I first though that this was because the lower difficulty setting I chose in the campaign. Can't really think of the reasons this could happen *Rolleyes.

 

Jitter - Wikipedia, the free encyclopedia

Electromagnetic interference - Wikipedia, the free encyclopedia

 

Thanks for the interesting links, but if it's related to the actual physical components of the computer, then...

... why did it start after upgrading to Windows 10?
... why does not using sleep mode and shutting down the computer work? and restart cures it?
... why doesn't my new computer have it even though it's on the exact same wall connection?

 

This worked like a charm on my windows 8.1 nextbook tablet Jeorgi!!! You Rock!!!! TY!