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

[desolator4u]

CDreier wrote:
EDIT: I realize this is a technical forum, not a complaint site. But I've got to say this clock issue is becoming a real annoyance. It has repercussions in almost every aspect of my daily computing; time stamps on financial spreadsheets and programs, logbooks, verification of the time emails are sent and received, on and on. I trust this is THE thread to find out the latest on what's being done to fix the problem. By the way, I notice this thread began on August first of last year. There's been no resolution and we're now going into March! This is a concern. Thanks.

^^^

[Praz]

Hello

Those screenshot point to a ME issue.

[adonisx4]

also having the same problem

[Nicholas_Steel]

Thanks everyone. We found this thread after experiencing the same issue of the RTC stalling whenever the computer was switched off, after upgrading the BIOS. The solution of simply resetting the BIOS via the Jumper Pins appears to have worked great (It's been numerous days/weeks now).

I like to imagine that the newer BIOS simply doesn't recognize some of the values that the older BIOS was using for various settings and the Jumper Pins completely erases the old configuration files allowing for completely fresh, fully compatible files to be generated.

[Fredericksburg]

Thanks Praz for the tip. I completely uninstalled AI3 for the time being. I'm at the point (not just due to this problem, but it's about that time...) to where I'm going to clear, reflash, and then reformat, and reinstall (windows, all drivers etc.) for a fresh start (fingers crossed). Just waiting for some free time.

Nicholas Steel

I like to imagine that the newer BIOS simply doesn't recognize some of the values that the older BIOS was using for various settings and the Jumper Pins completely erases the old configuration files allowing for completely fresh, fully compatible files to be generated.

Time will tell whether or not it comes back like some here claim must happen. I am starting to wonder which BIOS version they are using. Maybe your theory explains why one user said a recent BIOS upgrade "broke" it again.

I did find a somewhat hilarious consequence of this broken clock thingy, an small upside if you will (glass half-full..): several time-based software trials and demos couldn't figure out how much time had passed since I started using the software, and so therefore it now appears that the trials seem to stay open indefinitely... heh... one of them even informed me though a little periodic popup that it couldn't tell how much time had passed since I started my trial and urged me to make sure that "such-and-such-trial-monitoring-service" was running... as if I was actually going to take the time and go troubleshoot around to make sure that the service responsible for cutting me off after I'd hit 10 hours or whatever was running properly, haha!

[Nicholas_Steel]

Fredericksburg wrote:
Time will tell whether or not it comes back like some here claim must happen. I am starting to wonder which BIOS version they are using. Maybe your theory explains why one user said a recent BIOS upgrade "broke" it again.

Well, the theory is based on the fact that the motherboard uses a UEFI BIOS which is essentially an operating system, which is vastly more complex (code wise) then the low level BIOS that we're used to.

It's not too surprising that early motherboards supporting UEFI are prone to problems, I imagine it will be a year or 2 before motherboard manufacturers become completely comfortable with the new system and develop methods of avoiding this kind of thing in the future.

[Triplexbeatz]

The fact this this issue is still ongoing....well, frankly.... it worries me. That's in addition to being frustrated, pissed off, stuck with an expensive sub operational system, and at a loss for a bunch of cash and time spent chasing the issue and reading page after page of the same issue, the same fix, and the same re-occurrences. Did I mention infuriating?

My board isn't a Sabertooth or a RoG for that matter, but it boasts the same Z87 chipset, and a majority of the same features on Premium boards.
Same issue as everyone else. Specs below.

EDIT:
FYI I posted here> http://rog.asus.com/forum/showthread.php?36676-Frozen-Time-Clock-in-UEFI-The-Fix&p=379758&viewfull=1... which is why I did not go into greater detail on THIS thread.

[kdk_warhead]

System install September 2013

Problem with clock started late January 2014.

Symptom: system clock changes irrationally (usually a couple of hours). Date changes a couple of days.

System:
MB: Gryphon Z87
CPU: 4770k (no OC)
Mem: G.Skill Ares Low Profile 2x4Gb DDR 1866Mhz
GPU: 6970

CPU & GPU water cooled.

Bios: 1504 (Date 10/03/2013) until 2014-02-20

Loaded optimized default 2014-10-18, same problem.

Updated bios: 1707 (Date 12/13/2013) 2014-02-21, 4 hours later clock shows approximately the same as after flashing.

2014-02-21 22:00 noticed that the clock was stuck in bios (entered bios during startup). Did a 10 sec CMOS CLEAR (MB).
This started the clock but it was of by about one our (how can the computer now the time and date after a CMOS CLEAR . Maybe the intel I217-V took set the time from a NSA time server (spooky..).

2014-03-09 17 days and still working fine.

I might get the problem back but at least I know what works for me... (10 sec CMOS CLEAR).

2014-03-12 20 Days and still working fine.
2014-04-04 35 Days and still working fine.
2014-04-17 48 Days and still working fine.
2014-05-11 79 Days and still working fine.
2014-10-15 236 Days and the problem is back! Frozen Clock.

I guess I will try the latest bios for my MB. Strange that there is no final solution for this yet!

[KevinMillican]

My Z87 Pro motherboard developed an identical problem with the RTC after just under 3 months use.
Whilst I could get it replaced/refunded by the retailer, the hassle of reworking my PC and uncertainty of whether this would just go wrong again on a replacement, means that I prefer to workaround this issue.
I have done so successfully using the NTP service software on this site:-
http://www.meinbergglobal.com/english/sw/ntp.htm
You have to turn off the Windows internet time updates to get this to work properly but it's completely unobtrusive once set up.
Overall this works better anyhow because my Windows clock is never out by more than a second now, except for the initial login screen.

[Dorosh]

My point on this issue already stated here