A number of Windows 10 users – Windows 10 users who have overclocked their computers’ processors, in most cases – have suffered from and continue to suffer from a pretty unusual issue where their computer’s time runs faster than it should. In most cases, a 25% increase in the rate at which an affected computer’s time runs is reported – meaning that every minute that passes in real time causes an affected computer’s time to advance by 75 seconds. Users affected by this issue see that the system time in their computers’ BIOS is unaffected by this issue and only the system time in Windows is affected by it.
The reason why this issue almost always affects computers that have overclocked processors has been theorized to be the excess voltage that runs through an overclocked processor, although that has not yet been confirmed. Thankfully, this issue can, in almost all cases, be fixed by simply resetting and re-synchronizing the Windows Time service in an elevated Command Prompt. In order to fix this issue, you need to:
Right-click on the Start Menu button to open the WinX Menu.
Click on Command Prompt (Admin) in the WinX Menu.
One by one, type the following commands into the elevated Command Prompt, pressing Enter once you are done typing each one and waiting for one command to be executed successfully before moving onto typing the next one:
net stop w32time
net start w32time
Close the elevated Command Prompt.
Restart your computer.
Once your computer boots up, keep an eye on your computer’s time within Windows for a few minutes, making sure that it is running at the pace it is supposed to – i.e., your computer’s system time advances by 60 seconds for every 60 seconds that go by in real-time.
Pro Tip: If you are suffering from this problem on a computer with an overclocked processor, you are almost certainly going to be able to resolve it by simply disabling the overclock, like many users affected by this issue in the past have. However, if your processor’s overclock is something that you cannot afford to lose, you’d be better off sticking to the solution to this problem that has been described above. You should definitely consider disabling your processor’s overclock to fix this issue if the solution described above does not work for you (which is, admittedly, a rare occurrence).