Since purchasing my new PC, the clock stays consistently 10-12 minutes behind. When I set it to current time, it lasts for a day, then reverts back to 10 minutes behind. Is there a fix for this? Is this a Windows 10 issue, or desktop manufacturer issue?
Check the BIOS and make sure that is set to the correct time.
DeaconFrost is most likely correct, seeing it is a brand new machine, but if that is not the case, set your Time Server Sync to use time.nist.gov, not time.windows.com. The windows time server is notorious for getting finicky.
Check the System log in Event Viewer. Filter on source Time-Service. You should see event IDs 37 and 35. Event ID 37 will show you when the service receives a time update (and from which time source... time.windows.com by default), immediately followed by event ID 35 which shows the time being synchronised. There should only be a delay of microseconds between the 2 events (e.g. received at 02:33:38 and synced at 02:33:56).
Event ID 35 also shows the stratum number, i.e. the distance from the time source (in terms of 'router hops', not miles.) In terms of accuracy, a 'stratum-0' service is the most accurate, i.e. an atomic clock reference source. Windows, by default, includes 2 lower stratum sources, time.windows.com and time.nist.gov. These can be seen in the registry at:
Code:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\DateTime\Servers
(There is nothing to prevent you adding more time sources (as REG_SZ) to the list or replacing the 2 defaults.)
By comparison, the system clock (i.e. in the BIOS) is considered a 'stratum-12' service to show that it's not really considered accurate at all, hence the need to continually update it.
Hope this helps...
Quote
