.::i7 4770K @ 4.0GHz / Zalman CNPS9700 HSF / MSI GTX 760 OC Gaming/ ASUS Maximus VI Hero / 2x8GB Corsair 1600MHz DDR3 / XFX PRO 750W PSU / Win 7 x64 / Samsung 840 Pro 256GB, WD 1x500GB, 1x750GB, 1x1TB / Sound Blaster Z / 32" Samsung HDTV / Logitech G15 Keyboard & MX518 Mouse / X12 Headset ::.
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.
Last edited by Nicholas Steel; 03-04-2014 at 08:17 AM.
Computer specifications:
Windows 7 x64|Intel Core i7 @ 2.66GHZ|ASUS P6T Motherboard|6 gigabytes DDR3 1600 RAM|2x500GB SATA2 HDD|2TB SATA3 HDD|Auzentech XFI Forte S/C|Nvidia Geforce 560GTS Ti 2048MB PCI-E|Thermaltake 750watt Toughpower Power Supply|Thermaltake Armor+ MX case
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...l=1#post379758 which is why I did not go into greater detail on THIS thread.
Last edited by Triplexbeatz; 03-03-2014 at 11:29 PM.
i7 4770K / Corsair H105 / Asrock Z87 Extreme4 / 16GB (2x8GB) Gskill 1866MHz DDR3 / EVGA GeForce GTX 750 Ti / Corsair CX750M PSU / Win 7 x64 / Samsung 840 Pro 256GB, Seagate 2x2TB RAID0, WD Raptor 2x150GB RAID0, Seagate 1x1TB / Focusrite Saffire Pro 24 FW Audio Interface/ 23" Samsung LCD / Logitech K800 Keyboard / Kensington Expert Mouse
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!
Last edited by kdk_warhead; 10-16-2014 at 05:58 AM.
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.
My point on this issue already stated here
Hello
My MB : Z87-Pro
I have this problem I faced today was exactly I initially thought that the reason lies in the operating system until you ship the BIOS again with removing the battery for some time.
Please for your consideration of this matter, I believe that I am not the only one who suffered from that problem
Less management Must be issued a new update acres stability of Bios
Last edited by M.Elglasi; 04-28-2014 at 11:56 PM.
Any fix at this point guys?
It's becoming very frustrating...
Thanks,
Alex
Hello,
Just pitching in here; I am having the exact same issue with my ROG Maximus VI Gene motherboard.
After updating a few days ago from BIOS rev. 1302 to 1402 my RTC clock just froze.
I haven't done any overclocking on the board sporting an Intel 4770K.
I've written ASUS about this and will post here if they give me any useful advice/instructions.
Any discoveries yet?
How long are we going to have to wait for a fix? This is really bad. A BIOS clock issue come on! This is motherboard 101, never in a million years would I have thought that an ASUS premium board would have this issue. I am currently recommending to all of our clients to avoid all ASUS motherboards because of this very fundamental issue. Please please please please please fix it!
I have 3 boards with this issue in my shop and EVERY client system I built has this problem. I have tried EVERY fix in this thread, nothing works for more then a few days. Flashed BIOS, reset to factory, replaced batteries. NOTHING.