Windows 8.1 Time Problems


Recommended Posts

Hi everyone.

 

I have Windows 8.1, and over the last 2 weeks, I have noticed that my time is not keeping accurate.  I can go in and sync it, and it will correct itself (With an error that it timed out...), but a couple of hours later the clock will be wrong again.  I have tried changing the Time Sync Server, Restarting the Time Service and setting it to Automatic, etc, but nothing seems to help at all.

 

Does anyone have any ideas?  This is really driving me nuts at this point...

 

Thanks for your help.

Link to comment
Share on other sites

gives you an error that it timed out?

 

But your saying it does correct the time?  Odd..  I am not really a big fan of the windows built in time sync stuff, will have to look into how it might of changed with w8..  I just always disable it on all my machines and sync to my ntp server directly using the actual ntp software from ntp.org

 

For troubleshooting time sync problems there is nothing like the actual ntp tools to work with..  ntpq can give you lots of information about the server your syncing too, etc.  With the actual ntp client you can get lots of details for troubleshooting time issues.

 

Now as of late there has been some major attacks being done with ntp, many of the ntp servers out there have had an issue where you could query their monitor list to the IPs using them - and this can be used in an amplification attack.. Its possible your ISP has blocked udp 123 which is the standard port ntp uses.

 

I would be pretty ###### if they did that - but without some actual tests its hard to say if this is the case or not.  Do any of your other machines have problems syncing time?  Where are you pointing to for your ntp server?  You can grab a windows copy of ntp from here - http://www.meinbergglobal.com/english/sw/ntp.htm

 

Should work on win8.. From there you can use tools like ntpdate and ntpq to get lots of info.. But with the built in tools you should be able to use w32tm to do a quick query to see if you can talk to the ntp server of your choosing, etc..

 

C:\>                                                            
C:\>w32tm /stripchart /computer:192.168.1.40 /dataonly          
Tracking 192.168.1.40 [192.168.1.40:123].                       
The current time is 3/12/2014 12:38:49 PM.                      
12:38:49, +00.0300881s                                          
12:38:51, +00.0298676s                                          
12:38:53, +00.0297662s                                          
12:38:55, +00.0298786s                                          
12:38:57, +00.0298868s                                          
^C                                                              
C:\>w32tm /stripchart /computer:pool.ntp.org /dataonly          
Tracking pool.ntp.org [184.22.51.42:123].                       
The current time is 3/12/2014 12:39:13 PM.                      
12:39:13, +00.0025268s                                          
12:39:16, +00.0023100s                                          
12:39:18, +00.0017327s                                          
12:39:20, +00.0060262s                                        

 

So as you can see doing a query against my own local ntp server, and then against one that is in the pool for ntp.org  Reporting offset, etc.  If you can not do get something like this to work to any ntp server off your network then its quite possible your isp is blocking ntp (udp 123)

 

Let me know how I can help - ntp is one of my favorite technologies to play with!!  So happy to help!

 

If you want more info you can add the /packetinfo flag like so

 

C:\>w32tm /stripchart /computer:192.168.1.40 /packetinfo /dataonly                            
Tracking 192.168.1.40 [192.168.1.40:123].                                                     
The current time is 3/12/2014 12:46:03 PM.                                                    
12:46:03, +00.0264113s                                                                        
[NTP Packet]                                                                                  
Leap Indicator: 0(no warning)                                                                 
Version Number: 1                                                                             
Mode: 4 (Server)                                                                              
Stratum: 2 (secondary reference - syncd by (S)NTP)                                            
Poll Interval: 3 (8s)                                                                         
Precision: -20 (953.674ns per tick)                                                           
Root Delay: 0x0000.0537 (+00.0203705s)                                                        
Root Dispersion: 0x0000.0EFD (0.0585480s)                                                     
ReferenceId: 0x40712005 (source IP:  64.113.32.5)                                             
Reference Timestamp: 0xD6CB1A909B534FFA (150915 17:40:32.6067400s - 3/12/2014 12:40:32 PM)    
Originate Timestamp: 0xD6CB1BDB3AEC3CD4 (150915 17:46:03.2301672s - 3/12/2014 12:46:03 PM)    
Receive Timestamp: 0xD6CB1BDB41CEB801 (150915 17:46:03.2570605s - 3/12/2014 12:46:03 PM)      
Transmit Timestamp: 0xD6CB1BDB41D114BB (150915 17:46:03.2570966s - 3/12/2014 12:46:03 PM)     
[non-NTP Packet]                                                                              
Destination Timestamp: Roundtrip Delay: 963900 (+00.0009639s)                                 
Local Clock Offset: 26411300 (+00.0264113s)                                                 

Link to comment
Share on other sites

I'm suspicious that this is a low battery, but, normally your system time should stay accurate until a reboot/shutoff/sleep because it should be using a different timer source when the system is on from when it is off (i.e. not the CMOS clock).

Link to comment
Share on other sites

I'm suspicious that this is a low battery, but, normally your system time should stay accurate until a reboot/shutoff/sleep because it should be using a different timer source when the system is on from when it is off (i.e. not the CMOS clock).

 

yup. sounds like classic battery issue. otherwise it looks like some problem with the hardware clock - that might be a doosey.

Link to comment
Share on other sites

Thanks everyone for your help.  Do you mean the battery on the board?  In the past, I've had computers with an issue at boot where the time was not maintained, but this one loses time while in use, which I find particularly odd.  I initially thought possibly something malicious, but after scanning with Norton, AVG, IOBit, and SpyBot, I don't think that's the issue at this point (Hopefully).  I have not noticed any odd processes either.

 

And yes, when I try to synch the time with the time server (And I've tried several), I get the error message below:

post-264514-0-65852800-1394715206.png

And while I get this error, the time still gets updated.  This is what originally led me to believe it was something malicious, because it was almost as if there was something between me and the time server...

 

I don''t think this is a result of the ISP blocking anything either, as this occurs both at home and work and those are both different ISP's.  One of them is Verizon, so I imagine a lot of people would be screaming if they did that...

 

The hardware clock mentioned by primexx is definitely a concern.  I honestly didn't realize there was hardware dedicated to that and have no idea how I would determine if that was the issue or how that might be resolved...  So, I'm really hoping it's not that.

 

BudMan, thank you for your detailed post as well, to answer your questions, none of the other computers at home or work appear to be having this issue.

 

I tried to run w32tm to get the diagnostic information, and it immediately closes upon running.  Looking at the NTP software linked, it doesn't say that it supports WIndows 8, so I'm not sure if I should install that or not.  It appears to have been last  updated for Windows 7.

 

One interesting bit that I noticed today.  The time went BACKWARDS...  My clock was showing 9:42 AM then a few minutes later was showing 8:48 AM...  This is in keeping with the time issues I've noticed, but I had not yet actually witnessed it.  Often I go to do something and will find that the clock is 2 or 3 hours behind, but don't see the change...  I'd assumed it was slowing or stopping, not actually reversing...  I have absolutely no idea what would cause something like that.

 

Thank you all for your help, I greatly appreciate it.

Link to comment
Share on other sites

^ Lyons, yeah we were talking about the cmos battery. First thing I would do is try replacing it. These things do tend to be cmos battery related. It could be a red herring because as you say, it is odd that it is losing time while on, but I'd do it anyway. I could potentially see a case where the RTC register is being used to keep system time; though I was under the impression that other clocks sources (RTC and HPET) would be used instead normally in modern Windows. 

Link to comment
Share on other sites

"I tried to run w32tm to get the diagnostic information, and it immediately closes upon running"

 

You have to be in a cmd prompt first..

 

run cmd

 

then in the black window you get run the w32tm cmds

Link to comment
Share on other sites

Thank you for the help.  I tried the w32tm cmd line commands, but they were returned as unknown.  I did try changing the IP Address to mine.

 

I was able to enable logging for w32tm and it produced the following log.  I'm not sure if this helps at all...

 

150919 02:35:43.2957115s - ---------- Log File Opened -----------------
150919 02:47:22.5803950s - W32TmServiceMain: Network Topology Change
150919 02:47:22.5803950s - TimeProvCommand([NtpClient], TPC_NetTopoChange) called.
150919 02:47:22.5803950s - NtpProvider: Network Topology Change
150919 02:47:22.5803950s - Reachability:  removing peer time.nist.gov,0x9 (ntp.m|0x9|0.0.0.0:123->165.193.126.229:123).  LAST PEER IN GROUP!
150919 02:47:22.5803950s -   Peer (special) now pending: <Name:time.nist.gov,0x9 (ntp.m|0x9|0.0.0.0:123->165.193.126.229:123) poll:604800 diff:940 last:130394107016563704 resync?:FALSE>
150919 02:47:22.5803950s -   Peers reset: p-p:0 a-p:1 a-x:0
150919 02:47:22.5803950s - NtpProvider: Created 2 sockets (0 listen-only): [::]:123<0x0>, 0.0.0.0:123<0x0>
150919 02:47:22.5803950s - StartListeningThread completed!
150919 02:47:22.5803950s - PeerPollingThread: waiting 590206.766s
150919 02:47:22.5803950s - StartPeerPollingThread completed!
150919 02:47:22.5803950s - W32TmServiceMain: waiting 99.058s
150919 02:47:22.5803950s - W32TmServiceMain: RequestNetTopoChangeNotification Succeed
150919 02:47:22.5803950s - PeerPollingThread: PeerListUpdated
150919 02:47:22.5803950s - PeerPollingThread: waiting 590206.766s
150919 02:49:01.6516696s - W32TmServiceMain: timeout
150919 02:49:01.6516696s - W32TmServiceMain: waiting 1024.000s
150919 02:49:13.7698889s - W32TmServiceMain: Network Topology Change
150919 02:49:13.7698889s - TimeProvCommand([NtpClient], TPC_NetTopoChange) called.
150919 02:49:13.7698889s - NtpProvider: Network Topology Change
150919 02:49:13.7698889s -   Peer (special) now pending: <Name: poll:604800 diff:1052 last:130394107016563704 resync?:FALSE>
150919 02:49:13.7698889s -   Peers reset: p-p:1 a-p:1 a-x:0
150919 02:49:13.7698889s - NtpProvider: Created 2 sockets (0 listen-only): [::]:123<0x0>, 0.0.0.0:123<0x0>
150919 02:49:13.7698889s - StartListeningThread completed!
150919 02:49:13.7698889s - PeerPollingThread: waiting 590095.577s
150919 02:49:13.7698889s - StartPeerPollingThread completed!
150919 02:49:13.7698889s - PeerPollingThread: PeerListUpdated
150919 02:49:13.7698889s - PeerPollingThread: waiting 590095.577s
150919 02:49:13.7698889s - W32TmServiceMain: waiting 1011.881s
150919 02:49:13.7698889s - W32TmServiceMain: RequestNetTopoChangeNotification Succeed
150919 02:49:26.8252938s - W32TmServiceMain: Network Topology Change
150919 02:49:26.8252938s - TimeProvCommand([NtpClient], TPC_NetTopoChange) called.
150919 02:49:26.8252938s - NtpProvider: Network Topology Change
150919 02:49:26.8252938s -   Peer (special) now pending: <Name: poll:604800 diff:1065 last:130394107016563704 resync?:FALSE>
150919 02:49:26.8252938s -   Peers reset: p-p:1 a-p:1 a-x:0
150919 02:49:26.8252938s - NtpProvider: Created 2 sockets (0 listen-only): [::]:123<0x0>, 0.0.0.0:123<0x0>
150919 02:49:26.8252938s - StartListeningThread completed!
150919 02:49:26.8252938s - PeerPollingThread: waiting 590082.521s
150919 02:49:26.8252938s - StartPeerPollingThread completed!
150919 02:49:26.8252938s - W32TmServiceMain: waiting 998.826s
150919 02:49:26.8252938s - W32TmServiceMain: RequestNetTopoChangeNotification Succeed
150919 02:49:26.8252938s - PeerPollingThread: PeerListUpdated
150919 02:49:26.8252938s - PeerPollingThread: waiting 590082.521s
150919 02:50:46.5085684s - W32TmServiceMain: Network Topology Change
150919 02:50:46.5085684s - TimeProvCommand([NtpClient], TPC_NetTopoChange) called.
150919 02:50:46.5085684s - NtpProvider: Network Topology Change
150919 02:50:46.5241947s -   Peer (special) now pending: <Name: poll:604800 diff:1144 last:130394107016563704 resync?:FALSE>
150919 02:50:46.5241947s -   Peers reset: p-p:1 a-p:1 a-x:0
150919 02:50:46.5241947s - NtpProvider: Created 2 sockets (0 listen-only): [::]:123<0x0>, 0.0.0.0:123<0x0>
150919 02:50:46.5241947s - StartListeningThread completed!
150919 02:50:46.5241947s - PeerPollingThread: waiting 590002.822s
150919 02:50:46.5241947s - StartPeerPollingThread completed!
150919 02:50:46.5241947s - W32TmServiceMain: waiting 919.143s
150919 02:50:46.5241947s - PeerPollingThread: PeerListUpdated
150919 02:50:46.5241947s - W32TmServiceMain: RequestNetTopoChangeNotification Succeed
150919 02:50:46.5241947s - PeerPollingThread: waiting 590002.822s
150919 02:50:52.8171149s - W32TimeHandler called: SERVICE_CONTROL_SHUTDOWN
150919 02:50:52.8171149s - Beginning System Shutdown
150919 02:50:52.8171149s - ClockDisciplineThread: hShutDownEvent signaled. Exiting.
150919 02:50:53.6369903s - TimeProvCommand([NtpClient], TPC_Shutdown) called.
150919 02:50:53.6369903s - Shutdown clock disciplining thread, restart service async150919 02:50:53.6369903s - NotifyShutdown: error = 0
150919 02:50:53.6369903s - Exiting System Shutdown
150919 02:50:59.7684557s - W32TmServiceMain: Network Topology Change
150919 02:50:59.7684557s - TimeProvCommand([NtpClient], TPC_NetTopoChange) called.
150919 02:50:59.7684557s - NtpProvider: Network Topology Change
150919 02:50:59.7684557s -   Peer (special) now pending: <Name: poll:604800 diff:1158 last:130394107016563704 resync?:FALSE>
150919 02:50:59.7684557s -   Peers reset: p-p:1 a-p:1 a-x:0
150919 02:50:59.7684557s - NtpProvider: Created 2 sockets (0 listen-only): [::]:123<0x0>, 0.0.0.0:123<0x0>
150919 02:50:59.7684557s - StartListeningThread completed!
150919 02:50:59.7684557s - PeerPollingThread: waiting 589989.578s
150919 02:50:59.7684557s - StartPeerPollingThread completed!
150919 02:50:59.7684557s - W32TmServiceMain: Network Topology Change
150919 02:50:59.7684557s - TimeProvCommand([NtpClient], TPC_NetTopoChange) called.
150919 02:50:59.7684557s - W32TmServiceMain: waiting 892.654s
150919 02:50:59.7684557s - PeerPollingThread: PeerListUpdated
150919 02:50:59.7684557s - PeerPollingThread: waiting 589989.578s
150919 02:50:59.7684557s - NtpProvider: Network Topology Change
150919 02:50:59.7684557s -   Peer (special) now pending: <Name: poll:604800 diff:1158 last:130394107016563704 resync?:FALSE>
150919 02:50:59.7684557s -   Peers reset: p-p:1 a-p:1 a-x:0
150919 02:50:59.7684557s - NtpProvider: Created 2 sockets (0 listen-only): [::]:123<0x0>, 0.0.0.0:123<0x0>
150919 02:50:59.7684557s - StartListeningThread completed!
150919 02:50:59.7684557s - PeerPollingThread: waiting 589989.578s
150919 02:50:59.7684557s - StartPeerPollingThread completed!
150919 02:50:59.7684557s - W32TmServiceMain: waiting 892.654s
150919 02:50:59.7684557s - PeerPollingThread: PeerListUpdated
150919 02:50:59.7684557s - PeerPollingThread: waiting 589989.578s
150919 02:52:11.1947881s - ---------- Log File Opened -----------------
150919 02:52:11.3666701s - CurSpc:15625000ns  BaseSpc:15625000ns  SyncToCmos:Yes
150919 02:52:11.3666701s - PerfFreq:2143570c/s
150919 02:52:11.3666701s - ReadConfig: Found provider 'NtpClient':
150919 02:52:11.3666701s - ReadConfig:   'Enabled'=0x00000001
150919 02:52:11.3666701s - ReadConfig:   'DllName'='C:\WINDOWS\system32\w32time.DLL'
150919 02:52:11.3666701s - ReadConfig:   'DllName'='C:\WINDOWS\system32\w32time.DLL'
150919 02:52:11.3666701s - ReadConfig:   'DllName'='C:\WINDOWS\system32\w32time.DLL'
150919 02:52:11.3666701s - ReadConfig:   'InputProvider'=0x00000001
150919 02:52:11.3666701s - ReadConfig:   'RunOnVirtualOnly'=0x00000000
150919 02:52:11.3666701s - ReadConfig: Found provider 'NtpServer':
150919 02:52:11.3666701s - ReadConfig:   'Enabled'=0x00000000
150919 02:52:11.3666701s - ReadConfig:   'DllName'='C:\WINDOWS\system32\w32time.DLL'
150919 02:52:11.3666701s - ReadConfig:   'DllName'='C:\WINDOWS\system32\w32time.DLL'
150919 02:52:11.3666701s - ReadConfig:   'DllName'='C:\WINDOWS\system32\w32time.DLL'
150919 02:52:11.3666701s - ReadConfig:   'InputProvider'=0x00000000
150919 02:52:11.3666701s - ReadConfig:   'RunOnVirtualOnly'=0x00000000
150919 02:52:11.3666701s - ReadConfig: Found provider 'VMICTimeProvider':
150919 02:52:11.3666701s - ReadConfig:   'Enabled'=0x00000001
150919 02:52:11.3666701s - ReadConfig:   'DllName'='C:\WINDOWS\System32\vmictimeprovider.dll'
150919 02:52:11.3666701s - ReadConfig:   'DllName'='C:\WINDOWS\System32\vmictimeprovider.dll'
150919 02:52:11.3666701s - ReadConfig:   'DllName'='C:\WINDOWS\System32\vmictimeprovider.dll'
150919 02:52:11.3666701s - ReadConfig:   'InputProvider'=0x00000001
150919 02:52:11.3666701s - ReadConfig:   'RunOnVirtualOnly'=0x00000001
150919 02:52:11.3666701s - ReadConfig:  not running on a VM - overriding 'Enabled' setting to 0 (FALSE) for provider VMICTimeProvider
150919 02:52:11.3666701s - ReadConfig: 'PhaseCorrectRate'=0x00000001 (2)
150919 02:52:11.3666701s - ReadConfig: 'UpdateInterval'=0x00057E40 (2)
150919 02:52:11.3666701s - ReadConfig: 'FrequencyCorrectRate'=0x00000004 (2)
150919 02:52:11.3666701s - ReadConfig: 'PollAdjustFactor'=0x00000005 (2)
150919 02:52:11.3666701s - ReadConfig: 'LargePhaseOffset'=0x02FAF080 (2)
150919 02:52:11.3666701s - ReadConfig: 'SpikeWatchPeriod'=0x00000384 (2)
150919 02:52:11.3666701s - ReadConfig: 'HoldPeriod'=0x00000005 (2)
150919 02:52:11.3666701s - ReadConfig: 'MinPollInterval'=0x0000000A (2)
150919 02:52:11.3666701s - ReadConfig: 'MaxPollInterval'=0x0000000F (2)
150919 02:52:11.3666701s - ReadConfig: 'AnnounceFlags'=0x0000000A (2)
150919 02:52:11.3666701s - ReadConfig: 'LocalClockDispersion'=0x0000000A (2)
150919 02:52:11.3666701s - ReadConfig: 'MaxNegPhaseCorrection'=0x0000D2F0 (2)
150919 02:52:11.3666701s - ReadConfig: 'MaxPosPhaseCorrection'=0x0000D2F0 (2)
150919 02:52:11.3666701s - ReadConfig: 'EventLogFlags'=0x00000002 (2)
150919 02:52:11.3666701s - ReadConfig: 'MaxAllowedPhaseOffset'=0x00000001 (2)
150919 02:52:11.3666701s - ReadConfig: 'TimeJumpAuditOffset'=0x00007080 (2)
150919 02:52:11.3666701s - lastClockRate=156250, clockPrecision=-6
150919 02:52:11.3666701s - SetTimeSlipNotification succeeds with 0x00000000.
150919 02:52:11.3666701s - W32TmServiceMain: RequestNetTopoChangeNotification Succeed
150919 02:52:11.3666701s - W32TmServiceMain: RequestNetTopoChangeNotification Succeed
150919 02:52:11.3666701s -   DomainHierarchy: LSA role change notification. Redetecting.
150919 02:52:11.3823038s - ClockDisciplineThread: Starting: SetUnsync: LI:3 S:0 RDl:0 RDs:0 TSF:0x0  LastUTC:5068
150919 02:52:11.3823038s - Starting Providers.
150919 02:52:11.3823038s - Starting 'NtpClient', dll:'C:\WINDOWS\system32\w32time.DLL'
150919 02:52:11.3823038s - LoadLibrary
150919 02:52:11.3823038s - NtpTimeProvOpen("NtpClient") called.
150919 02:52:11.3823038s - StartNtpProv
150919 02:52:11.3823038s - sysPrecision=-6, systmeClockResolution=156250
150919 02:52:11.3823038s - NtpProvider: Created 2 sockets (0 listen-only): [::]:123<0x0>, 0.0.0.0:123<0x0>
150919 02:52:11.5073023s - StartListeningThread completed!
150919 02:52:11.5073023s - PeerPollingThread: waiting forever
150919 02:52:11.5073023s - StartPeerPollingThread completed!
150919 02:52:11.5073023s - ReadConfig: 'AllowNonstandardModeCombinations'=0x00000001 (2)
150919 02:52:11.5073023s - ReadConfig: 'CompatibilityFlags'=0x80000000 (2)
150919 02:52:11.5073023s - ReadConfig: 'SpecialPollInterval'=0x00093A80 (2)
150919 02:52:11.5073023s - ReadConfig: 'ResolvePeerBackoffMinutes'=0x0000000F (2)
150919 02:52:11.5073023s - ReadConfig: 'ResolvePeerBackoffMaxTimes'=0x00000007 (2)
150919 02:52:11.5073023s - ReadConfig: 'EventLogFlags'=0x00000001 (2)
150919 02:52:11.5073023s - ReadConfig: 'LargeSampleSkew'=0x00000003 (2)
150919 02:52:11.5073023s - ReadConfig: 'SignatureAuthAllowed'=0x00000001 (2)
150919 02:52:11.5073023s - ReadConfig: 'Type'=NTP (2)
150919 02:52:11.5073023s - ReadConfig: 'NtpServer'=time.nist.gov,0x9 (2)
150919 02:52:11.5073023s - ReadConfig: 'ManualPeerList'(parsed)='time.nist.gov,0x9'
150919 02:52:11.5073023s - AddNewPendingPeer: manual
150919 02:52:11.5073023s - StartListeningThread completed!
150919 02:52:11.5073023s - PeerPollingThread: waiting 603568.493s
150919 02:52:11.5073023s - StartPeerPollingThread completed!
150919 02:52:11.5073023s - PeerPollingThread: PeerListUpdated
150919 02:52:11.5073023s - NtpClient started.
150919 02:52:11.5073023s - Successfully started 1 providers.
150919 02:52:11.5073023s - PeerPollingThread: waiting 603568.493s
150919 02:52:11.5073023s - /--TimeProvider: All providers started
150919 02:52:11.5073023s - | Name:NtpClient, Started:1, Input:1, Marked:0, RefCount:0, DllName:C:\WINDOWS\system32\w32time.DLL
150919 02:52:11.5073023s - >--
150919 02:52:11.5073023s - | Total:1, Input: 1, Marked: 0
150919 02:52:11.5073023s - \--
150919 02:52:11.5073023s - W32TmServiceMain: waiting i16.000s (1024.000s)
150919 02:52:11.5073023s - W32TmServiceMain: Network Topology Change
150919 02:52:11.5073023s - TimeProvCommand([NtpClient], TPC_NetTopoChange) called.
150919 02:52:11.5073023s - W32TmServiceMain: Network Topology Change
150919 02:52:11.5073023s - NtpProvider: Network Topology Change
150919 02:52:11.5073023s - TimeProvCommand([NtpClient], TPC_NetTopoChange) called.
150919 02:52:11.5073023s -   Peer (special) now pending: <Name: poll:604800 diff:1231 last:130394107000000000 resync?:FALSE>
150919 02:52:11.5073023s -   Peers reset: p-p:1 a-p:1 a-x:0
150919 02:52:11.5073023s - NtpProvider: Created 2 sockets (0 listen-only): [::]:123<0x0>, 0.0.0.0:123<0x0>
150919 02:52:11.5073023s - StartListeningThread completed!
150919 02:52:11.5073023s - PeerPollingThread: waiting 603568.493s
150919 02:52:11.5073023s - StartPeerPollingThread completed!
150919 02:52:11.5073023s - W32TmServiceMain: waiting i16.000s (1024.000s)
150919 02:52:11.5073023s - W32TmServiceMain: RequestNetTopoChangeNotification Succeed
150919 02:52:11.5073023s - PeerPollingThread: PeerListUpdated
150919 02:52:11.5073023s - PeerPollingThread: waiting 603568.493s
150919 02:52:11.5073023s - NtpProvider: Network Topology Change
150919 02:52:11.5073023s -   Peer (special) now pending: <Name: poll:604800 diff:1231 last:130394107000000000 resync?:FALSE>
150919 02:52:11.5073023s -   Peers reset: p-p:1 a-p:1 a-x:0
150919 02:52:11.5073023s - NtpProvider: Created 2 sockets (0 listen-only): [::]:123<0x0>, 0.0.0.0:123<0x0>
150919 02:52:11.5073023s - StartListeningThread completed!
150919 02:52:11.5073023s - PeerPollingThread: waiting 603568.493s
150919 02:52:11.5073023s - StartPeerPollingThread completed!
150919 02:52:11.5073023s - W32TmServiceMain: waiting i16.000s (1024.000s)
150919 02:52:11.5073023s - W32TmServiceMain: RequestNetTopoChangeNotification Succeed
150919 02:52:11.5073023s - PeerPollingThread: PeerListUpdated
150919 02:52:11.5073023s - PeerPollingThread: waiting 603568.493s
150919 02:52:14.8984181s - W32TimeHandler called: SERVICE_CONTROL_STOP
150919 02:52:14.8984181s - shutdown in service control handler, w/o restart service async150919 02:52:14.8984181s - NotifyShutdown: error = 0
150919 02:52:14.8984181s - Service shutdown initiated with exit code: 0.
150919 02:52:14.8984181s - ClockDisciplineThread: hShutDownEvent signaled. Exiting.
150919 02:52:14.8984181s - Service is shutting down, but no time adjustment occured.
150919 02:52:14.8984181s - RemoveProviderFromList: NtpClient
150919 02:52:14.8984181s - Stopping 'NtpClient', dll:'C:\WINDOWS\system32\w32time.DLL'
150919 02:52:14.8984181s - NtpTimeProvClose("0000000000000002") called.
150919 02:52:14.8984181s - NtpTimeProvClose([NtpClient]) called.
150919 02:52:14.8984181s - StartListeningThread completed!
150919 02:52:14.8984181s - PeerPollingThread: waiting forever
150919 02:52:14.8984181s - StartPeerPollingThread completed!
150919 02:52:14.8984181s - PeerPollingThread: PeerListUpdated
150919 02:52:14.8984181s - StopNtpProv
150919 02:52:14.8984181s - PeerPollingThread: waiting forever
150919 02:52:14.8984181s - ListeningThread: StopEvent
150919 02:52:14.8984181s - PeerPollingThread: StopEvent
150919 02:52:14.8984181s - FreeLibrary dll:C:\WINDOWS\system32\w32time.DLL
150919 02:52:14.8984181s - /--TimeProvider: Provider list after the provider is actually removed
150919 02:52:14.8984181s - >--
150919 02:52:14.8984181s - | Total:0, Input: 0, Marked: 0
150919 02:52:14.8984181s - \--
150919 02:52:14.8984181s - SetTimeSlipNotification succeeds with 0x00000000.
150919 02:52:14.8984181s - Exiting ServiceShutdown
150919 02:52:14.8984181s - ---------- Log File Closed -----------------

 

I also spoke with ASUS support (This computer isn't more than a year old).  As a result, I would hope that the CMOS Battery wouldn't be bad already.  They recommended a Windows Refresh, which wouldn't be ideal due to the amount I would lose and have to reinstall.  He said that changing the battery would void the  warranty...  Not that it probably matters if I don't have a computer that works...  lol

 

As for new software installed around the time this started...  I did not install anything recently.  A couple of weeks before this occurred, I installed IOBit, and since I've installed AVG...  But nothing around the time this started. 

 

In reading up on the CMOS battery as well, it doesn't sound like this would affect anything while the machine was running, but I of course could be wrong.

 

This is by far the strangest issue I've ever run into with a machine.

Link to comment
Share on other sites

Hi everyone.

 

I have Windows 8.1, and over the last 2 weeks, I have noticed that my time is not keeping accurate.  I can go in and sync it, and it will correct itself (With an error that it timed out...), but a couple of hours later the clock will be wrong again.  I have tried changing the Time Sync Server, Restarting the Time Service and setting it to Automatic, etc, but nothing seems to help at all.

 

Does anyone have any ideas?  This is really driving me nuts at this point...

 

Thanks for your help.

Choose a different server. This error you have has been happening on all versions of windows (down to Windows XP). I think each server doesn't allow multiple attempts in one day.

Link to comment
Share on other sites

You think time.nist.gov is dead?  Or time.windows.com? 

 

ReadConfig: 'ManualPeerList'(parsed)='time.nist.gov,0x9'

 

Both answer just fine

 

C:\>w32tm /stripchart /computer:time.nist.gov /dataonly /packetinfo                            
Tracking time.nist.gov [128.138.141.172:123].                                                  
The current time is 3/16/2014 5:28:06 AM.                                                      
05:28:06, -00.0038400s                                                                         
[NTP Packet]                                                                                   
Leap Indicator: 0(no warning)                                                                  
Version Number: 1                                                                              
Mode: 4 (Server)                                                                               
Stratum: 1 (primary reference - syncd by radio clock)                                          
Poll Interval: 0 (unspecified)                                                                 
Precision: -29 (1.86265ns per tick)                                                            
Root Delay: 0x0000.0000 (unspecified)                                                          
Root Dispersion: 0x0000.0000 (unspecified)                                                     
ReferenceId: 0x41435453 (source name:  "ACTS")                                                 
Reference Timestamp: 0xD6CFFB32D9C274FC (150919 10:28:02.8506234s - 3/16/2014 5:28:02 AM)      
Originate Timestamp: 0xD6CFFB363AB8C0A6 (150919 10:28:06.2293816s - 3/16/2014 5:28:06 AM)      
Receive Timestamp: 0xD6CFFB363E57B6E4 (150919 10:28:06.2435259s - 3/16/2014 5:28:06 AM)        
Transmit Timestamp: 0xD6CFFB363E59C3DA (150919 10:28:06.2435572s - 3/16/2014 5:28:06 AM)       
[non-NTP Packet]                                                                               
Destination Timestamp: Roundtrip Delay: 35968700 (+00.0359687s)                                
Local Clock Offset: -3840000 (-00.0038400s)                                                    

 

C:\>w32tm /stripchart /computer:time.windows.com /dataonly /packetinfo                   
Tracking time.windows.com [65.55.56.206:123].                                            
The current time is 3/16/2014 5:41:04 AM.                                                
05:41:04, -00.0302918s                                                                   
[NTP Packet]                                                                             
Leap Indicator: 0(no warning)                                                            
Version Number: 3                                                                        
Mode: 4 (Server)                                                                         
Stratum: 2 (secondary reference - syncd by (S)NTP)                                       
Poll Interval: 0 (unspecified)                                                           
Precision: -6 (15.625ms per tick)                                                        
Root Delay: 0x0000.0800 (+00.0312500s)                                                   
Root Dispersion: 0x0000.0E56 (0.0559998s)                                                
ReferenceId: 0x0A14E533 (source IP:  10.20.229.51)                                       
Reference Timestamp: 0xD6CFFE00E3F708E0 (150919 10:40:00.8904882s - 3/16/2014 5:40:00 AM)
Originate Timestamp: 0xD6CFFE407B977857 (150919 10:41:04.4827800s - 3/16/2014 5:41:04 AM)
Receive Timestamp: 0xD6CFFE407C076B2E (150919 10:41:04.4844882s - 3/16/2014 5:41:04 AM)  
Transmit Timestamp: 0xD6CFFE407C076B2E (150919 10:41:04.4844882s - 3/16/2014 5:41:04 AM)
[non-NTP Packet]                                                                         
Destination Timestamp: Roundtrip Delay: 64000000 (+00.0640000s)                          
Local Clock Offset: -30291800 (-00.0302918s)                                           

                                                                                             

Again you NEED to do a manual test to see if you can actually reach who your pointing to - or resolve the name even.

 

Looks like it was removed

Reachability:  removing peer time.nist.gov,0x9

 

And as not allowing multiple queries a day?  Now if you were hitting them every second or say every minute on a 64 second poll for a very extended period then sure they might ban you if they notice..  Depending on what time server your using.. Some are open to public, some ask for an email etc..

Listing here http://support.ntp.org/bin/view/Servers/WebHome of stratum 1 and 2 servers, if you use pool.ntp.org you might even query my box ;)

 

As to your problem running the command on 8.1?? Here open a cmd prompt elevated

 

post-14624-0-65922900-1394966838.png

 

Then clearly the cmd works - query a time server you want to use - you can find many in your area here http://support.ntp.org/bin/view/Servers/WebHome

 

post-14624-0-38803500-1394966874.png

 

Windows built in poll time is quite large - so yes its possible for your box to drift..  You never really said how much your drifting?  Are we talking seconds, or minutes or hours?

 

"150919 02:49:26.8252938s - PeerPollingThread: waiting 590082.521s"

 

590k seconds your just shy of a week there.. 

 

Here is my time server I run, uses multiple public servers and picks the best one..  Polling is currently at 1024 seconds - this is MAX polling time for ntp..

 

post-14624-0-89563000-1394969205.png

 

server ntp2.netwrx1.com
server nist.netservicesgroup.com
server ntp.mya.org
server nist1-lnk.binary.net

And yes the ntp window port runs just fine on windows 8 or 8.1 - here I installed it on my 8.1 box

 

post-14624-0-98999200-1394967981.png

 

Next Next Next until asked what time servers you want to use - hit the drop down and pick your region of the world

post-14624-0-17577000-1394968033.png

 

Then you will see this page - just leave everything it will then ask you for ntp account password, and disable the built in service, start the service, etc. etc..

post-14624-0-07478700-1394968086.png

 

You can then open a cmd window (needs to be reopened if still using old one so that new path is gotten) So you can run ntpq which is a way to look a your status.  Then run pe and see how your doing.

 

So here you see it disabled the built in service and its doing queries to ntp servers - it starts off doing quick polls, but as it gets answers it will back those off to longer 1024 seconds, etc.

 

post-14624-0-01737400-1394968222.png

 

Now the software from meinburg is a bit dated - if you want to run bleeding edge version you can get from here http://www.satsignal.eu/ntp/x86/index.html

 

I am currently running on this main workstation

C:\>ntpq                                                        
ntpq> version                                                   
ntpq 4.2.7p416@1.2483-o Jan 31 13:45:44.41 (UTC-00:00) 2014  (1)
ntpq>                                                         

 

But might as well update to 432, you just download his zip and stop the service and replace the binary files - there you go bing bang zoom latest and greatest ntp client/server

 

post-14624-0-29439400-1394968887.png

 

As you can see it just restarted and polling my local server at 64 seconds

 

post-14624-0-99584400-1394968978.png

Link to comment
Share on other sites

This problem arises due to the dynamic system tick in Windows 8+, on all older computers with older BIOSes the Windows clock will be off by a couple of tens of seconds, to a minute. I'm not aware of a way of resolving this, other than disabling dynamic ticker.

Link to comment
Share on other sites

You know what, I just realized something: this could just be a DST issue (we did just change). He stated above that his clock went from 9:42am --> 8:48am a few minutes later (back in time). He never actually said whether it is just losing an hour or if it is losing random periods of time.

Link to comment
Share on other sites

Its likely the battery losing time, and if it falls that far behind you probably have bad caps on your RTC chip, bad RTC registers as mentioned already, and/or possibly a corrupted CMOS or bad drivers even. It goes really deep. If you can pull the HDD and try another HDD with a fresh install of something and see if it follows will help conclude software or hardware.

 

As for windows time update, it will always throw that error when really far out because its contacting an NNTP server over the internet, and it wants you to have the EXACT time, to the picoosecond. It can't transmit you the time to set it to because it takes time to do that. The NNTP server tries to set it and averages out to see how long the transmission took, but since your first time difference is so far out of tolerance, it skews the average error and the NNTP server says NO DAMN WAY IT TAKES THAT LONG and tells your comp to set the time to what it thinks is the EXACT time, but it really don't know because of your first clock reading being so far out.

 

If you re-run it again, it usually won't error out unless theres a network bug of sorts. This boggled my mind for years, but its just poor diagnostics from MS. Theres no need to worry about it. If you get your clock ballpark within a few seconds manually then run the internet sync it'll likely will not error out.

Link to comment
Share on other sites

Thanks Tomaya Rex, I did try that, but the problem persists.  :(

 

@Snaphat, it starts as an hour, but soon becomes 2, 3, or 4...  Currently it reads 12:51 PM Yesterday...  (I haven't synced yet as I was trying to run the diagnostics Bud Man wanted me to do.)  This issue did however begin around the DST change, but that might have been a coincidence?

 

@Srbeen, thank you for the explanation.  That appears to be exactly what I'm seeing here too.  The sync does work the second attempt without an error.  That was driving me nuts.  I figured something was interfering with the sync for some reason. 

 

@Bud Man, thank you for your post, that was very helpful.

 

Here is the log that you were asking for.  I read through it, but don't really know what I'm looking for.

 

Root Delay: 0x0000.0800 (+00.0312500s)
Root Dispersion: 0x0000.0DFA (0.0545959s)
ReferenceId: 0x0A14E533 (source IP:  10.20.229.51)
Reference Timestamp: 0xD6D16BB11AEB6467 (150920 12:40:17.1051543s - 3/17/2014 8:
40:17 AM)
Originate Timestamp: 0xD6D06189EE18A28E (150919 17:44:41.9300634s - 3/16/2014 1:
44:41 PM)
Receive Timestamp: 0xD6D16BF406F3958E (150920 12:41:24.0271543s - 3/17/2014 8:41
:24 AM)
Transmit Timestamp: 0xD6D16BF406F3958E (150920 12:41:24.0271543s - 3/17/2014 8:4
1:24 AM)
[non-NTP Packet]
Destination Timestamp: Roundtrip Delay: 78107600 (+00.0781076s)
Local Clock Offset: 68202058037100 (+68202.0580371s)

13:44:44, +68202.0656643s
[NTP Packet]
Leap Indicator: 0(no warning)
Version Number: 3
Mode: 4 (Server)
Stratum: 2 (secondary reference - syncd by (S)NTP)
Poll Interval: 0 (unspecified)
Precision: -6 (15.625ms per tick)
Root Delay: 0x0000.0800 (+00.0312500s)
Root Dispersion: 0x0000.0EAB (0.0572968s)
ReferenceId: 0x0A14E533 (source IP:  10.20.229.51)
Reference Timestamp: 0xD6D16BE89EDE6729 (150920 12:41:12.6205811s - 3/17/2014 8:
41:12 AM)
Originate Timestamp: 0xD6D0618C062834D2 (150919 17:44:44.0240510s - 3/16/2014 1:
44:44 PM)
Receive Timestamp: 0xD6D16BF622F6FA9D (150920 12:41:26.1365811s - 3/17/2014 8:41
:26 AM)
Transmit Timestamp: 0xD6D16BF622F6FA9D (150920 12:41:26.1365811s - 3/17/2014 8:4
1:26 AM)
[non-NTP Packet]
Destination Timestamp: Roundtrip Delay: 93731500 (+00.0937315s)
Local Clock Offset: 68202065664300 (+68202.0656643s)

13:44:46, +68202.0731072s
[NTP Packet]
Leap Indicator: 0(no warning)
Version Number: 3
Mode: 4 (Server)
Stratum: 2 (secondary reference - syncd by (S)NTP)
Poll Interval: 0 (unspecified)
Precision: -6 (15.625ms per tick)
Root Delay: 0x0000.0800 (+00.0312500s)
Root Dispersion: 0x0000.0EAD (0.0573273s)
ReferenceId: 0x0A14E533 (source IP:  10.20.229.51)
Reference Timestamp: 0xD6D16BE89EF0C92B (150920 12:41:12.6208616s - 3/17/2014 8:
41:12 AM)
Originate Timestamp: 0xD6D0618E223983AF (150919 17:44:46.1336901s - 3/16/2014 1:
44:46 PM)
Receive Timestamp: 0xD6D16BF83EF0C92B (150920 12:41:28.2458616s - 3/17/2014 8:41
:28 AM)
Transmit Timestamp: 0xD6D16BF83EF0C92B (150920 12:41:28.2458616s - 3/17/2014 8:4
1:28 AM)
[non-NTP Packet]
Destination Timestamp: Roundtrip Delay: 78128500 (+00.0781285s)
Local Clock Offset: 68202073107200 (+68202.0731072s)

13:44:48, +68202.0661008s
[NTP Packet]
Leap Indicator: 0(no warning)
Version Number: 3
Mode: 4 (Server)
Stratum: 2 (secondary reference - syncd by (S)NTP)
Poll Interval: 0 (unspecified)
Precision: -6 (15.625ms per tick)
Root Delay: 0x0000.0800 (+00.0312500s)
Root Dispersion: 0x0000.0D12 (0.0510559s)
ReferenceId: 0x0A14E533 (source IP:  10.20.229.51)
Reference Timestamp: 0xD6D16BB181377913 (150920 12:40:17.5047527s - 3/17/2014 8:
40:17 AM)
Originate Timestamp: 0xD6D061903A3EE6C5 (150919 17:44:48.2275223s - 3/16/2014 1:
44:48 PM)
Receive Timestamp: 0xD6D16BFA552F47EC (150920 12:41:30.3327527s - 3/17/2014 8:41
:30 AM)
Transmit Timestamp: 0xD6D16BFA552F47EC (150920 12:41:30.3327527s - 3/17/2014 8:4
1:30 AM)
[non-NTP Packet]
Destination Timestamp: Roundtrip Delay: 78259200 (+00.0782592s)
Local Clock Offset: 68202066100800 (+68202.0661008s)

13:44:50, error: 0x800705B4
[NTP Packet]
Leap Indicator: 0(no warning)
Version Number: 1
Mode: 3 (Client)
Stratum: 0 (unspecified)
Poll Interval: 0 (unspecified)
Precision: 0 (unspecified)
Root Delay: 0x0000.0000 (unspecified)
Root Dispersion: 0x0000.0000 (unspecified)
ReferenceId: 0x00000000 (unspecified)
Reference Timestamp: 0x0000000000000000 (unspecified)
Originate Timestamp: 0x0000000000000000 (unspecified)
Receive Timestamp: 0x0000000000000000 (unspecified)
Transmit Timestamp: 0xD6D061925258C818 (150919 17:44:50.3216672s - 3/16/2014 1:4
4:50 PM)
[non-NTP Packet]
Destination Timestamp: Roundtrip Delay: -2015885700 (-02.0158857s)
Local Clock Offset: 1007942800 (+01.0079428s)

13:44:53, error: 0x800705B4
[NTP Packet]
Leap Indicator: 0(no warning)
Version Number: 1
Mode: 3 (Client)
Stratum: 0 (unspecified)
Poll Interval: 0 (unspecified)
Precision: 0 (unspecified)
Root Delay: 0x0000.0000 (unspecified)
Root Dispersion: 0x0000.0000 (unspecified)
ReferenceId: 0x00000000 (unspecified)
Reference Timestamp: 0x0000000000000000 (unspecified)
Originate Timestamp: 0x0000000000000000 (unspecified)
Receive Timestamp: 0x0000000000000000 (unspecified)
Transmit Timestamp: 0xD6D06195566C8564 (150919 17:44:53.3375934s - 3/16/2014 1:4
4:53 PM)
[non-NTP Packet]
Destination Timestamp: Roundtrip Delay: -5031811900 (-05.0318119s)
Local Clock Offset: 2515905900 (+02.5159059s)

13:44:56, +68202.0711047s
[NTP Packet]
Leap Indicator: 0(no warning)
Version Number: 3
Mode: 4 (Server)
Stratum: 2 (secondary reference - syncd by (S)NTP)
Poll Interval: 0 (unspecified)
Precision: -6 (15.625ms per tick)
Root Delay: 0x0000.0800 (+00.0312500s)
Root Dispersion: 0x0000.0CEA (0.0504456s)
ReferenceId: 0x0A14E533 (source IP:  10.20.229.51)
Reference Timestamp: 0xD6D16B99EEBB21A9 (150920 12:39:53.9325429s - 3/17/2014 8:
39:53 AM)
Originate Timestamp: 0xD6D061985A76B99A (150919 17:44:56.3533741s - 3/16/2014 1:
44:56 PM)
Receive Timestamp: 0xD6D16C0276AABF5B (150920 12:41:38.4635429s - 3/17/2014 8:41
:38 AM)
Transmit Timestamp: 0xD6D16C0276AABF5B (150920 12:41:38.4635429s - 3/17/2014 8:4
1:38 AM)
[non-NTP Packet]
Destination Timestamp: Roundtrip Delay: 78128100 (+00.0781281s)
Local Clock Offset: 68202071104700 (+68202.0711047s)

13:44:58, error: 0x800705B4
[NTP Packet]
Leap Indicator: 0(no warning)
Version Number: 1
Mode: 3 (Client)
Stratum: 0 (unspecified)
Poll Interval: 0 (unspecified)
Precision: 0 (unspecified)
Root Delay: 0x0000.0000 (unspecified)
Root Dispersion: 0x0000.0000 (unspecified)
ReferenceId: 0x00000000 (unspecified)
Reference Timestamp: 0x0000000000000000 (unspecified)
Originate Timestamp: 0x0000000000000000 (unspecified)
Receive Timestamp: 0x0000000000000000 (unspecified)
Transmit Timestamp: 0xD6D0619A72862BFE (150919 17:44:58.4473598s - 3/16/2014 1:4
4:58 PM)
[non-NTP Packet]
Destination Timestamp: Roundtrip Delay: -2015857600 (-02.0158576s)
Local Clock Offset: 1007928800 (+01.0079288s)

13:45:01, error: 0x800705B4
[NTP Packet]
Leap Indicator: 0(no warning)
Version Number: 1
Mode: 3 (Client)
Stratum: 0 (unspecified)
Poll Interval: 0 (unspecified)
Precision: 0 (unspecified)
Root Delay: 0x0000.0000 (unspecified)
Root Dispersion: 0x0000.0000 (unspecified)
ReferenceId: 0x00000000 (unspecified)
Reference Timestamp: 0x0000000000000000 (unspecified)
Originate Timestamp: 0x0000000000000000 (unspecified)
Receive Timestamp: 0x0000000000000000 (unspecified)
Transmit Timestamp: 0xD6D0619D769AC512 (150919 17:45:01.4632991s - 3/16/2014 1:4
5:01 PM)
[non-NTP Packet]
Destination Timestamp: Roundtrip Delay: -5031796900 (-05.0317969s)
Local Clock Offset: 2515898400 (+02.5158984s)

13:45:04, +68202.0751141s
[NTP Packet]
Leap Indicator: 0(no warning)
Version Number: 3
Mode: 4 (Server)
Stratum: 2 (secondary reference - syncd by (S)NTP)
Poll Interval: 0 (unspecified)
Precision: -6 (15.625ms per tick)
Root Delay: 0x0000.0800 (+00.0312500s)
Root Dispersion: 0x0000.0CF0 (0.0505371s)
ReferenceId: 0x0A14E533 (source IP:  10.20.229.51)
Reference Timestamp: 0xD6D16B99EE54E534 (150920 12:39:53.9309829s - 3/17/2014 8:
39:53 AM)
Originate Timestamp: 0xD6D061A07909B3DD (150919 17:45:04.4728043s - 3/16/2014 1:
45:04 PM)
Receive Timestamp: 0xD6D16C0A964482E6 (150920 12:41:46.5869829s - 3/17/2014 8:41
:46 AM)
Transmit Timestamp: 0xD6D16C0A964482E6 (150920 12:41:46.5869829s - 3/17/2014 8:4
1:46 AM)
[non-NTP Packet]
Destination Timestamp: Roundtrip Delay: 78129000 (+00.0781290s)
Local Clock Offset: 68202075114100 (+68202.0751141s)

13:45:06, error: 0x800705B4
[NTP Packet]
Leap Indicator: 0(no warning)
Version Number: 1
Mode: 3 (Client)
Stratum: 0 (unspecified)
Poll Interval: 0 (unspecified)
Precision: 0 (unspecified)
Root Delay: 0x0000.0000 (unspecified)
Root Dispersion: 0x0000.0000 (unspecified)
ReferenceId: 0x00000000 (unspecified)
Reference Timestamp: 0x0000000000000000 (unspecified)
Originate Timestamp: 0x0000000000000000 (unspecified)
Receive Timestamp: 0x0000000000000000 (unspecified)
Transmit Timestamp: 0xD6D061A2951B010D (150919 17:45:06.5824433s - 3/16/2014 1:4
5:06 PM)
[non-NTP Packet]
Destination Timestamp: Roundtrip Delay: -2031510000 (-02.0315100s)
Local Clock Offset: 1015755000 (+01.0157550s)

13:45:09, +68202.0649085s
[NTP Packet]
Leap Indicator: 0(no warning)
Version Number: 3
Mode: 4 (Server)
Stratum: 2 (secondary reference - syncd by (S)NTP)
Poll Interval: 0 (unspecified)
Precision: -6 (15.625ms per tick)
Root Delay: 0x0000.0800 (+00.0312500s)
Root Dispersion: 0x0000.0E50 (0.0559082s)
ReferenceId: 0x0A14E533 (source IP:  10.20.229.51)
Reference Timestamp: 0xD6D16B4F39A54E02 (150920 12:38:39.2251786s - 3/17/2014 8:
38:39 AM)
Originate Timestamp: 0xD6D061A599304F53 (150919 17:45:09.5983934s - 3/16/2014 1:
45:09 PM)
Receive Timestamp: 0xD6D16C0FB5CE43C5 (150920 12:41:51.7101786s - 3/17/2014 8:41
:51 AM)
Transmit Timestamp: 0xD6D16C0FB5CE43C5 (150920 12:41:51.7101786s - 3/17/2014 8:4
1:51 AM)
[non-NTP Packet]
Destination Timestamp: Roundtrip Delay: 93753400 (+00.0937534s)
Local Clock Offset: 68202064908500 (+68202.0649085s)

13:45:11, +68202.0654828s
[NTP Packet]
Leap Indicator: 0(no warning)
Version Number: 3
Mode: 4 (Server)
Stratum: 2 (secondary reference - syncd by (S)NTP)
Poll Interval: 0 (unspecified)
Precision: -6 (15.625ms per tick)
Root Delay: 0x0000.0800 (+00.0312500s)
Root Dispersion: 0x0000.0E11 (0.0549469s)
ReferenceId: 0x0A14E533 (source IP:  10.20.229.51)
Reference Timestamp: 0xD6D16BB119F5BE5D (150920 12:40:17.1014060s - 3/17/2014 8:
40:17 AM)
Originate Timestamp: 0xD6D061A7B542784A (150919 17:45:11.7080455s - 3/16/2014 1:
45:11 PM)
Receive Timestamp: 0xD6D16C11D20620AB (150920 12:41:53.8204060s - 3/17/2014 8:41
:53 AM)
Transmit Timestamp: 0xD6D16C11D20620AB (150920 12:41:53.8204060s - 3/17/2014 8:4
1:53 AM)
[non-NTP Packet]
Destination Timestamp: Roundtrip Delay: 93755300 (+00.0937553s)
Local Clock Offset: 68202065482800 (+68202.0654828s)

13:45:13, +68202.0571433s
[NTP Packet]
Leap Indicator: 0(no warning)
Version Number: 3
Mode: 4 (Server)
Stratum: 2 (secondary reference - syncd by (S)NTP)
Poll Interval: 0 (unspecified)
Precision: -6 (15.625ms per tick)
Root Delay: 0x0000.0800 (+00.0312500s)
Root Dispersion: 0x0000.0E12 (0.0549622s)
ReferenceId: 0x0A14E533 (source IP:  10.20.229.51)
Reference Timestamp: 0xD6D16BB119FD8277 (150920 12:40:17.1015245s - 3/17/2014 8:
40:17 AM)
Originate Timestamp: 0xD6D061A9D554BDC7 (150919 17:45:13.8333243s - 3/16/2014 1:
45:13 PM)
Receive Timestamp: 0xD6D16C13EDF55150 (150920 12:41:55.9295245s - 3/17/2014 8:41
:55 AM)
Transmit Timestamp: 0xD6D16C13EDF55150 (150920 12:41:55.9295245s - 3/17/2014 8:4
1:55 AM)
[non-NTP Packet]
Destination Timestamp: Roundtrip Delay: 78113700 (+00.0781137s)
Local Clock Offset: 68202057143300 (+68202.0571433s)
 

 

My time is drifting hours.  It's really odd.  I spent a lot of time watching it this weekend.  It appears to go ahead a minute, then back an hour and it continues to lose time until I'm hours or even a day behind.  It currently is reading 12:59 PM yesterday (It's 8:56 AM at the moment).

 

The software you're talking about.  Is that something I should install and run here on my machine in place of the built in time service?  Is it lightweight?  Does it require any management from me, or does it pretty much just run itself once installed?

 

Thanks everyone for all of your help.  This is easily the most frustrating thing I've ever experienced with a machine.

Link to comment
Share on other sites

hello,

 

i've seen that happening (time was way offset, either forward or backward) in one PC; changing the CMOS battery resolved quickly (long thread so i didn't read if you already changed it). Also time.windows.com works as expected, but you might use an alternative ntp server that's close to you, to see if it helps, but it all seems to me like CMOS battery kicking the bucket.

 

also what does the event viewer show (time warnings / errors)?

Link to comment
Share on other sites

yes the time service runs in place of the built in one - once you turn it on you really have little to do with it.. You set it an forget it sort of software - and it takes no more resources that the built in tool  And you can always just turn it off and go back to the built in one if you want.

 

Yeah your local clock is WAY OFF!!!

 

Local Clock Offset: 68202057143300 (+68202.0571433s)

 

Your taking 18hours off..  You need to set your time to close to correct then turn ntp software - ntp has a hard time adjusting large differences in time.

 

Also what does this command show for your setup?

 

C:\>w32tm /tz                                                              
Time zone: Current:TIME_ZONE_ID_DAYLIGHT Bias: 360min (UTC=LocalTime+Bias)
  [standard Name:"Central Standard Time" Bias:0min Date:(M:11 D:1 DoW:0)]  
  [Daylight Name:"Central Daylight Time" Bias:-60min Date:(M:3 D:2 DoW:0)]

 

 

C:\>date /t        
Mon 03/17/2014     
                   
C:\>time /t        
08:41 AM         

Link to comment
Share on other sites

hello,

 

i've seen that happening (time was way offset, either forward or backward) in one PC; changing the CMOS battery resolved quickly (long thread so i didn't read if you already changed it). Also time.windows.com works as expected, but you might use an alternative ntp server that's close to you, to see if it helps, but it all seems to me like CMOS battery kicking the bucket.

 

also what does the event viewer show (time warnings / errors)?

I'm really afraid that's the problem.  The computer is less than a year old though, so I just can't believe the CMOS battery would be going already...  :-\

 

I've never replaced the CMOS Battery (And tend not to tinker inside the machine generally), so that option really scares me.  lol

 

As for warnings, I do have some Time Service Warnings, however they don't appear very helpful:

 

Log Name:      System

Source:        Microsoft-Windows-Time-Service

Date:          3/17/2014 9:00:00 AM

Event ID:      52

Task Category: None

Level:         Warning

Keywords:      

User:          LOCAL SERVICE

Computer:      Matthew

Description:

The time service has set the time with offset 71802 seconds.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" />

    <EventID>52</EventID>

    <Version>0</Version>

    <Level>3</Level>

    <Task>0</Task>

    <Opcode>0</Opcode>

    <Keywords>0x8000000000000000</Keywords>

    <TimeCreated SystemTime="2014-03-17T13:00:00.424956700Z" />

    <EventRecordID>33974</EventRecordID>

    <Correlation />

    <Execution ProcessID="1628" ThreadID="10312" />

    <Channel>System</Channel>

    <Computer>Matthew</Computer>

    <Security UserID="S-1-5-19" />

  </System>

  <EventData Name="TMP_EVENT_TIME_JUMP_AUDIT">

    <Data Name="TimeOffsetSeconds">71802</Data>

  </EventData>

</Event>

 

Log Name:      System

Source:        Microsoft-Windows-Time-Service

Date:          3/16/2014 12:18:41 PM

Event ID:      52

Task Category: None

Level:         Warning

Keywords:      

User:          LOCAL SERVICE

Computer:      Matthew

Description:

The time service has set the time with offset 45233 seconds.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" />

    <EventID>52</EventID>

    <Version>0</Version>

    <Level>3</Level>

    <Task>0</Task>

    <Opcode>0</Opcode>

    <Keywords>0x8000000000000000</Keywords>

    <TimeCreated SystemTime="2014-03-16T16:18:41.378837100Z" />

    <EventRecordID>33939</EventRecordID>

    <Correlation />

    <Execution ProcessID="1628" ThreadID="10312" />

    <Channel>System</Channel>

    <Computer>Matthew</Computer>

    <Security UserID="S-1-5-19" />

  </System>

  <EventData Name="TMP_EVENT_TIME_JUMP_AUDIT">

    <Data Name="TimeOffsetSeconds">45233</Data>

  </EventData>

</Event>

 

Log Name:      System

Source:        Microsoft-Windows-Time-Service

Date:          3/15/2014 3:04:52 PM

Event ID:      52

Task Category: None

Level:         Warning

Keywords:      

User:          LOCAL SERVICE

Computer:      Matthew

Description:

The time service has set the time with offset 90028 seconds.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" />

    <EventID>52</EventID>

    <Version>0</Version>

    <Level>3</Level>

    <Task>0</Task>

    <Opcode>0</Opcode>

    <Keywords>0x8000000000000000</Keywords>

    <TimeCreated SystemTime="2014-03-15T19:04:52.303899200Z" />

    <EventRecordID>33724</EventRecordID>

    <Correlation />

    <Execution ProcessID="1604" ThreadID="1700" />

    <Channel>System</Channel>

    <Computer>Matthew</Computer>

    <Security UserID="S-1-5-19" />

  </System>

  <EventData Name="TMP_EVENT_TIME_JUMP_AUDIT">

    <Data Name="TimeOffsetSeconds">90028</Data>

  </EventData>

</Event>

 

The warning appears to be the TimeOffsetSeconds...

Link to comment
Share on other sites

@Bud Man: I synced the date because I had to get into some software for work that requires time stamping...  But here is the information currently:

Microsoft Windows [Version 6.3.9600]
© 2013 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>w32tm/tz
Time zone: Current:TIME_ZONE_ID_DAYLIGHT Bias: 300min (UTC=LocalTime+Bias)
  [standard Name:"Eastern Standard Time" Bias:0min Date:(M:11 D:1 DoW:0)]
  [Daylight Name:"Eastern Daylight Time" Bias:-60min Date:(M:3 D:2 DoW:0)]

C:\>date /t
Mon 03/17/2014

C:\>time /t
09:46 AM

C:\>

 

Will that other software resolve the issue if it is the CMOS Battery?  I REALLY hope it isn't that...

Link to comment
Share on other sites

I'm really afraid that's the problem.  The computer is less than a year old though, so I just can't believe the CMOS battery would be going already...  :-\

the cmos battery could still be low or dead. i've seen boards shipped with dead or bad cmos batteries before so it's definitely in the realm of possibility

Link to comment
Share on other sites

^ At this point you really should try the cmos battery solution. If you are dropping more than an hour it's definitely not DST issues. 

Link to comment
Share on other sites

I'm really afraid that's the problem.  The computer is less than a year old though, so I just can't believe the CMOS battery would be going already...  :-\

 

I've never replaced the CMOS Battery (And tend not to tinker inside the machine generally), so that option really scares me.  lol

 

As for warnings, I do have some Time Service Warnings, however they don't appear very helpful:

 

Log Name:      System

Source:        Microsoft-Windows-Time-Service

Date:          3/17/2014 9:00:00 AM

Event ID:      52

Task Category: None

Level:         Warning

Keywords:      

User:          LOCAL SERVICE

Computer:      Matthew

Description:

The time service has set the time with offset 71802 seconds.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" />

    <EventID>52</EventID>

    <Version>0</Version>

    <Level>3</Level>

    <Task>0</Task>

    <Opcode>0</Opcode>

    <Keywords>0x8000000000000000</Keywords>

    <TimeCreated SystemTime="2014-03-17T13:00:00.424956700Z" />

    <EventRecordID>33974</EventRecordID>

    <Correlation />

    <Execution ProcessID="1628" ThreadID="10312" />

    <Channel>System</Channel>

    <Computer>Matthew</Computer>

    <Security UserID="S-1-5-19" />

  </System>

  <EventData Name="TMP_EVENT_TIME_JUMP_AUDIT">

    <Data Name="TimeOffsetSeconds">71802</Data>

  </EventData>

</Event>

 

Log Name:      System

Source:        Microsoft-Windows-Time-Service

Date:          3/16/2014 12:18:41 PM

Event ID:      52

Task Category: None

Level:         Warning

Keywords:      

User:          LOCAL SERVICE

Computer:      Matthew

Description:

The time service has set the time with offset 45233 seconds.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" />

    <EventID>52</EventID>

    <Version>0</Version>

    <Level>3</Level>

    <Task>0</Task>

    <Opcode>0</Opcode>

    <Keywords>0x8000000000000000</Keywords>

    <TimeCreated SystemTime="2014-03-16T16:18:41.378837100Z" />

    <EventRecordID>33939</EventRecordID>

    <Correlation />

    <Execution ProcessID="1628" ThreadID="10312" />

    <Channel>System</Channel>

    <Computer>Matthew</Computer>

    <Security UserID="S-1-5-19" />

  </System>

  <EventData Name="TMP_EVENT_TIME_JUMP_AUDIT">

    <Data Name="TimeOffsetSeconds">45233</Data>

  </EventData>

</Event>

 

Log Name:      System

Source:        Microsoft-Windows-Time-Service

Date:          3/15/2014 3:04:52 PM

Event ID:      52

Task Category: None

Level:         Warning

Keywords:      

User:          LOCAL SERVICE

Computer:      Matthew

Description:

The time service has set the time with offset 90028 seconds.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" />

    <EventID>52</EventID>

    <Version>0</Version>

    <Level>3</Level>

    <Task>0</Task>

    <Opcode>0</Opcode>

    <Keywords>0x8000000000000000</Keywords>

    <TimeCreated SystemTime="2014-03-15T19:04:52.303899200Z" />

    <EventRecordID>33724</EventRecordID>

    <Correlation />

    <Execution ProcessID="1604" ThreadID="1700" />

    <Channel>System</Channel>

    <Computer>Matthew</Computer>

    <Security UserID="S-1-5-19" />

  </System>

  <EventData Name="TMP_EVENT_TIME_JUMP_AUDIT">

    <Data Name="TimeOffsetSeconds">90028</Data>

  </EventData>

</Event>

 

The warning appears to be the TimeOffsetSeconds...

 

 

Actually the offset is quite high (more than 20 hours in some cases), so i would check, while on BIOS / UEFI, if the time does drifts so much (in BIOS / UEFI there isn't an NTP delivering time, just the clock, so if it's a CMOS problem it should be noticeable).

Link to comment
Share on other sites

How are those event logs not helpfu - your making huge adjustments 90K seconds..  I don't believe its cmos in a year either that would be really odd - but something is wrong with the clock on this system.  Have you installed real ntp and see if that can make adjustments.. NTP normally adjusts the clock setting so that it keeps better time, while windows just sets it every so often.

 

Set time, run ntp -- if your still drifting like that, give it a while to adjust but if in say couple of days your off by hours and hours then something wrong with the real time clock.  Or you got something running on the system that is altering the time, or preventing the system clock from working like it should.

 

But it can not hurt to change the battery as well - as stated its under $5.. So unless yours is soldered onto the MB it is 2 seconds to pop in a new one - no different than changing a battery in your watch, etc.

Link to comment
Share on other sites

This topic is now closed to further replies.