cancel
Showing results for 
Search instead for 
Did you mean: 

Sabertooth Z87 - Bios Clock Issue

Krait
Level 7
The basic problem is that the clock in the UEFI bios stops working on a regular basis.

I can remove the battery and it will restart (at least for a day or two) but it always stops again - I've tried 4 different batteries and the longest that the clock continued to work was 8 days.
It's only the clock that doesn't work (at least as far as I know) - all the other bios settings stay the same (except when resetting cmos ofc)
I've tried it at stock and OC'ed and it still persists in stopping, I've also tried using my older PSU (Seasonic 860 xp1) and the same result.

I suppose it's either a bios problem (bios 1205) or a MB fault but if anyone has a suggestion for me to try, in case it's neither of these, it would be most welcome.
🙂
Asus Sabertooth z87 - 4670k - Alpenfohn K2 - Corsair 16gb LP Vengeance - VTX 7970 - Arctic Cooling 7970 - DGM 27" IPS - Crucial 512gb/128gb/64gb M4 - Seagate 2TB - Xigmatek Elysium - Seasonic Platinum 860 XP2
796 Views
166 REPLIES 166

Flegma
Level 10
I have same model of MBO and maybe this is silly question but what is symptoms of frozen clock? Clock is frozen only in BIOS or both, BIOS nad Windows?

I asked this because Windows has Internet Time.
i5 4670K (no OC) on Sabertooth Z87, Asus GTX760 DC2OC, Corsair Vengeance 8GB @XMP 1600, Cooler Master M2 720W - Noctua NH-U12S CPU cooler
WD Blue 1TB (EZEX), WD Green 2TB (EARX)

Flegma wrote:
I have same model of MBO and maybe this is silly question but what is symptoms of frozen clock? Clock is frozen only in BIOS or both, BIOS nad Windows?

I asked this because Windows has Internet Time.


The clock is frozen in the BIOS and then you start to see odd behavior in the Windows clock.

Oubadah wrote:
The clock is frozen in the BIOS and then you start to see odd behavior in the Windows clock.

What odd behavior?
i5 4670K (no OC) on Sabertooth Z87, Asus GTX760 DC2OC, Corsair Vengeance 8GB @XMP 1600, Cooler Master M2 720W - Noctua NH-U12S CPU cooler
WD Blue 1TB (EZEX), WD Green 2TB (EARX)

Flegma wrote:
What odd behavior?


I first noticed it one night when I glanced at the time, continued working, then looked down at the time to see that it was still exactly the same. I remember thinking what a long minute, but it was late and I decided I must have been imagining it.

The next day I looked at the clock when it should have been ~11PM and it said 2.00AM. This time I immediately remembered this thread and guessed that the issue must extend beyond the sabertooth. I then looked in the BIOS and sure enough, the clock was static.

While the BIOS clock is frozen, the windows clock seems to fluctuate between being completely wrong and sometimes displaying what seems to be the correct time (I guess it eventually syncs with an internet clock).

hi, I bought a z87-deluxe last week.
I have the same problem. BIOS clock is frozen.
Please fix it.

Problem solved. 🙂 Now I am waiting for ASUS to send me a gift (GTX 780 ti preferable ), and then there will be full description of the process.

Is it still frozen after you flashed the bios and resetting it .

Raja
Level 13
RXweasel wrote:
My BIOS clock has frozen again 3 times after updating BIOS to 1707.

Before this, the re-flash & reset advice has kept my BIOS clock running since last August. The BIOS update to 1707 broke it again.
After the update, i've tried the re-flash and reset -solution that helped before, but in about 1-3 weeks the clock stops again until i reset it with the CMOS jumper.

Should I try to downgrade back to 1405 ?



Praz is trying to replicate the issue so please post full setup of UEFI for him to mimic.

-Raja

Hello Raja!

I have the problem where my clock doesnt work properly. And you mentioned something about a CMOS- reset and something else. I have no idea how to do these things!
Can you please specify how to? This started yesterday.

CDreier
Level 7
Okay, so I'm another one with the clock issue on the Sabertooth Z87. I'm glad to have found this forum's thread after spending much time searching elsewhere for answers. We're eagerly awaiting a solution as the problem is quite severe in the long term. Having said that, I know ASUS will find the answer and get it to us!