Computer clock keeps changing

Tommy154

Honorable
Aug 27, 2013
127
0
10,690
Earlier tonight I noticed it was like 2 hours behind, and I thought it was just because I lost power a few days ago and my computer shutdown and it just didn't resync the time, so I manual reset it. I was just playing FSX and Assetto Corsa and I look down at I see it say 1:07AM (it's 2:15AM right now). So I reset it again. What is going on??? I don't think these games are changing the time since I've played them before and it didn't do this, but that's the only thing I've done on my computer

UPDATE: from my last comment I said I resync at 9:33. The clock is now at 9:37 despite the fact that it is now 10:36. I think the clock just doesn't work when the computer goes to sleep or gets turned off. So I guess its the mobo battery? What can I do about this?
 
Solution
I just had the same problem on a brand new ASUS Z97 Deluxe motherboard. The battery voltage was fine, but it failed to maintain the time. It turned out to be a bad connection between the pre-installed motherboard battery and the battery socket. I took it out and wiped the battery clean and applied a DeoxIT® GOLD contact cleaning pen to the contact points and reinserted it in the socket. It works great now.

Tommy154

Honorable
Aug 27, 2013
127
0
10,690
I had it set to sync with time.windows.com and I just changed it to time.nist.gov. Idk what's going on. Right now it is 9:33PM and its saying 2:31AM. I have no idea why it is doing it. My mobo is brand new less than 2 months. My time is set correctly to -5 aka Eastern time. When I manual force a re-sync it syncs to the correct time.
 

ArJunaB

Reputable
Jul 26, 2014
3
0
4,520
I just had the same problem on a brand new ASUS Z97 Deluxe motherboard. The battery voltage was fine, but it failed to maintain the time. It turned out to be a bad connection between the pre-installed motherboard battery and the battery socket. I took it out and wiped the battery clean and applied a DeoxIT® GOLD contact cleaning pen to the contact points and reinserted it in the socket. It works great now.
 
Solution