My system clock is gaining one second every four seconds. For every minute that passes, the system clock advances by 75 seconds.
When looking at the time in the BIOS, it appears to tick at normal speed, but in Windows it is fast.
Toggling time synchronisation in the settings corrects the time, but it still ticks fast. I've tried a few time servers now.
This started after my graphics card drivers (non-fatally) overheated/crashed (not sure which but it wasn't that hot when I watched it) and I had to reset the system a couple of times. I have a CPU overclock of 33% but this has not caused issues in the past.
Thanks for any assistance on the matter!
Hi, see if there's anything here that might help:
Windows Time is constantly out of sync - Windows 10 blog
Reboot your machine a couple of times is advice I have seen somewhere.
Also see this:
Timer Tweaks Benchmarked TweakHound
May be a high voltage problem due to the overclocking.
Windows time service may be corrupt, this below may work, was for win 7, ymmv on 10:
Usually, this issue is caused by Windows Time service corrupt. You can try to take following steps to troubleshoot this issue.
Run the following command in a elevate privileges cmd window.
net stop w32time
w32tm /unregister
w32tm /register
net start w32time
w32tm /resync
Then, please restart the computer to test the issue again.
W32tm.exe is used to configure Windows Time service settings. It can also be used to diagnose problems with the time service. W32tm.exe is the preferred command line tool for configuring, monitoring, or troubleshooting the Windows Time service.
Refer this link for more information:
You could also try resetting your BIOS, and testing without the OC, though I doubt that the OC is doing it, resetting it may correct, and you could then reapply your settings. on my board I just switch to a different BIOS I left as default (I have three)
Thank you RWOne, the steps you described fixed the issue. I had to run the resync command twice for it to complete successfully, but perhaps I didn't wait long enough after sending the previous command.
Disabling the overclock also fixed the issue, but it's a 30% overclock so it's not something I'm willing to lose!
Cool! good to hear it.
Please mark the thread as solved for us when you get a chance.
