Sabertooth Z87 - Bios Clock Issue

[Krait]

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.
🙂

[JackNaylorPE]

Figgah:

There were two solutions to this problem, neither of which appears to be permanent:

1. The Clear CMOS method will unfreeze the clock but it is a temporary fix. Described here:

http://rog.asus.com/forum/showthread.php?36676-Frozen-Time-Clock-in-UEFI-The-Fix

2. The 2nd method was via a BIOS upgarde which is described here (post 134):

http://rog.asus.com/forum/showthread.php?35490-Sabertooth-Z87-Bios-Clock-Issue&p=408653&viewfull=1#p...

Last I checked however, no BIOS has ever been released with the announced "RTC Stop Error Cured" annotated in the description.... there were BIOSs released the next day but they allowed you to put Devils Canon CPUs in Z87 boards....no mention of fixing the RTC Stop Error.

I have since asked Asus over a dozen times including 5 times with the Asus Loyalty Team and they just refuse to answer the question as to whether that BIOS release included a fix for this problem. The only response is an offer to RMA the board. Ever call or e-mail response I have gotten is that they were unaware of the issue until I brought it to their attention.

[NOUMAN]

Hi ! Just wanted to ask "how long would it take you (Asus) to resolve this issue?"

It has been almost a year since I am waiting for a fix. My old Post

[kdk_warhead]

Bios 1707 + 10 sec CMOS CLEAR fixed it for 236 days but now the clock is frozen.
I guess i will try the latest Bios 2103 for GryphonZ87.
(for more info se #124)

Update: Did a 10 sec CMOS CLEAR but the clock and date didn't work well in the beginning. It started to work properly after about two days. I then updated to ME 9.5.15.1730 and the Bios to 2103.

2014-10-18 Flashed Bios 2103, OK

[Nicholas_Steel]

Any chance you guys can update http://www.asus.com/au/Motherboards/SABERTOOTH_Z87/HelpDesk_Download/ to mention the newest version of the Intel Management Engine Interface software? Currently it mentions "Intel(R) Management Engine Interface V9.5.14.1724" when v9.5.15.1730 (And possibly newer, I haven't checked yet) exists and works fine (As far as I can tell, we haven't had any issues with the system since installing that unlisted version months ago)

[FZG_Immel]

Hey guys.

I am the owner of a Maximus VII ranger and I'm affected by a frozen bios clock... It messes up my windows time...

Can you pinpoint me to a solution for this ? It seems that the problem appeared when I installed the MEi for the ai suite III

Thanks a lot

[Nicholas_Steel]

Just chiming in again to confirm that the issue still does seem to be resolved for us. Windows Time Sync (Internet time) thing occasionally resyncs the Windows clock to the wrong value, we've since changed what server it syncs against so hopefully that's resolved.

There is definitely the possibility that it ISN'T resolved and the clock is being resynced using the internet each time we turn his PC on, masking the issue. I haven't really bothered to test this out, but I easily can. I actually might test it out now that I think about it. I'll disconnect his PC from the internet, leave it off for an hour or 2 and turn it on, see what the clock says.

[Nicholas_Steel]

I've tested the computer without it being connected to the internet for several hours while turned off, and still disconnected from the internet when it was eventually turned on. The clock and date in the BIOS remains correct.