Frozen Time Clock in UEFI - The Fix

[Raja]

Is your motherboard suffering from the malady of a frozen time clock in UEFI?

If so try the following:

1) Reflash the latest UEFI, using EZ Flash 2 or USB BIOS flashback.

2) When the system POSTs, enter UEFI. Once in UEFI power down the motherboard. Keep the PSU attached and "on". Only the motherboard is powered off and in "standby". You will see the MB standby lights on (boards with start buttons onboard will be lit). Standby does not mean the board is actually running, standby means the board has power, but you have not pressed the power button to turn it on. Make sure the board is off before you go to the next step in this list. You will know if it is off because if you leave it for 5 seconds it should not POST~BOOT - this means it is in standby.



3) Clear CMOS (Clear RTC) for 10 seconds. This will clear the Management Engine.

4) Power up the system, enter UEFI, set the clock and then save and exit.

5) Update MEI driver to Version 9.5.14.1724 in the OS.









6 )Carry on using the system as normal.

The above steps should fix the issue.

-Raja

[ironfan]

just a quick follow up, the clock has been fine all day today.

[GregH]

Well, so far on THESE forums, seems no one has come back yet to say that they loaded 1505 and encountered a RTC stop. That's got to be a good sign.......?

Keep in mind most people only visit a forum if they have a problem to solve. No problem, no visit to the forum. So if things go quiet on this topic it is also a good sign.

[JackNaylorPE]

I haven't used it much and I am purposely avoiding all the known triggers .... such as using profiles and backing up settings to USB, stress testing, etc. I can't afford the time to do another OS reinstall or have my network backup all whacked out because file dates never change.

The fix was announced June 11 for 12 boards indicating that the fixed BIOSs would contain a notation "RTC Stop Error Cured". I haven't checked in a few days but last time I did there were no such notations. A fix for RoG boards was said to be forthcoming ... where is it ?

When i first mentioned the post in Z97 here, the answer was.... well it's only 1 board out of so many sold ..... now it's 3 plus 1 on newegg where the validity is discarded for a reason I can not determine..... newegg does verify that the posing individual did own the board in question. How many reports does there have to be before our concern is deemed legitimate ? GM made headlines for taking a similar approach recently.

I can accept any manufacturer having a problem with a product. I patiently awaited a fix until our prodding about "still no fix" has been returned with:

a) Asus telephone TS denies the problem exists and tells us everything said here is "unofficial".
b) Asus e-mail TS now responds with instructions to "call us". I guess they don't want a paper trail.
c) Three weeks after the BIOS fix was announced, there are still no BIOSs with that notation on the site.
d) Of course the fellow from newegg doesn't continue to repost .... he already returned the board for a refund.

I didn't experience the problem for 2 months after my build....I was not doing any overclocking because BIOS 1102 fudged all my previously stable OCs and kept waiting for one that would require 1.325 for a 4.5 GHz OC (1.275 worked on 0804). When I finally gave up the ghost on that, and started OCing again on 1402..... saving a now known working profile or loading a previous one would freeze the clock.

I have gone 6 weeks w/o seeing the problem and then had it happen 3 times in a day. If it's statistically insignificant, Asus should replace our boards as what is the statistical chance that we will get another affected board ?

I'm not upset about having experienced the problem.... the official denial of the problem's existence by Tech Support staff, the failure of "RoG Forum Announced Fixes"(unofficial according to Asus TS) to materialize and the immediate dismissal or every reported post of continuing problems is a pattern of behavior that puts my long standing customer loyalty to the test.

[rick66]

Updated Bios to 1505 and Kapow!!!! RTC is fixed, loaded OC profile and all is working great. Fingers crossed :cool:

[Siriusb]

Hello fellow users.

Sorry, I am new here, so please excuse any forum mistakes I do!

I have read through this thread, as I have the same problem (clock not working) with my new Maximus VII Hero MB.
But I am totally lost with how to fix it (Im 58). UEFI reflash ; CMOS Update ; OCing ..... lost!
Could someone maybe be so kind and put everything into a simple work-around for an almost OAP like me!

Thanks Siriusb (Phil)

[zeraoo98]

Siriusb wrote:
Hello fellow users.

Sorry, I am new here, so please excuse any forum mistakes I do!

I have read through this thread, as I have the same problem (clock not working) with my new Maximus VII Hero MB.
But I am totally lost with how to fix it (Im 58). UEFI reflash ; CMOS Update ; OCing ..... lost!
Could someone maybe be so kind and put everything into a simple work-around for an almost OAP like me!

Thanks Siriusb (Phil)

Hit up the 2-11 page in the manual for your motherboard, it got a step-by-step instruction on how to update/flash the BIOS. The flash of bios can brick/damage your MB if you do it wrong, so you may want to ask someone more technically skilled to do that for you. As for "work-around", there is none, otherwise the problem would be fixed long time ago, and even flashing bios with 1505 does not resolve that problem for sure. As for time setting you can do it from the OS, as it will update the RTC clock that way too (if the RCT is not stuck).

ps. Why would you need such an advanced MB in a first place if i may ask??
ps2. There is a VII discussion thread right here http://rog.asus.com/forum/forumdisplay.php?177-Maximus-VII-Motherboards

[Siriusb]

Hello zera0098.

Thanks for answering my call for help.

After thinking about everything again today, I have decided to take it back to the shop where
I bought it, as it is only a couple of weeks old. I shall give them the link to this forum and
ask them to give me a different board. As this seems to be an ongoing problem which is not being
solved by ASUS, I will change it before having to take it back every two weeks.

I updated my system to this board after reading about all the different ones and then picked
this one to get my system back up to date with the latest technics ( I had a P8P67, also from ASUS )
I also got a new graficcard ( from Geforce 560 to Geforce 770, yes you guessed ASUS ). I wasnt to
bothered that it was way over my knowledge and I wasnt going to overclock it, but I wanted a good
and fast board for my MS-flight-simulator and didn t want to keep on getting a new system every couple
of years. OK, call me stupid, but thats the way I work. On top of this, I bought a complete new
computer for my prepar3D flight-sim. I daren t tell you which board and graficcard I bought for that
and yes, all from ASUS. As I have been setting up this computer first, I haven t had the time to look
at the new one yet. I will kill myself, if the new one has the same problem!

Anyway, thanks again for your help and hoping you all get this problem sorted out. Sorry to say, I
shall be turning my back on ASUS from now on ( yes, my laptop is from ASUS too!)

cheers, SiriusB (Phil)

[Siriusb]

Hello again.

Before closing everything down and taking the computer back again tomorrow, I thought
it might be of interest to you to have the information from my system (as far as I could
find it). If you should be interested in anything else you would like to know, please post
here and possibly give me the exact information on where I can find it and how to do it
( you know, i m an OAP, not a computer guru like you, so please speak loud and clear!)

I have taken a picture of the label on the MB-Box from ASUS but dont want to print
anything out here for legal reasons, I ll just keeping it for reference.

My board : ASUS Maximus VII HERO

UEFI BIOS Version : 0401 x64
Build date : 04/23/2014
iROG1 Version RGE1-Z97-0119
iROG3 Version MKEY-Z97-0125
ME-Version : 9.1.1.1000

How I notice that something wasn t right :

After saving a file, I couldn t find it in the explorer. Thats when I noticed that the system
time/date was not right. I changed it, but later noticed that it was wrong again. I decided
to ask the guys at the shop where I updated my system to the new HERO board, but had
too much work to make it down there up to now.

I decided to live with it for now and just kept changing the time.

Later, I was flying my new PMDG Triple 7 ( one beautiful aircraft if I may say ) and suddenly
out of nowhere, the alarm bells went off in the cockpit, the plan drifted off course and passenger
oxygen went off-line (because of my loud swearing I couldn t hear the screams of my 209
passengers!) After that, the plane went into a steep dive and I dug a hole in the ground.

Today, before flying, I set the system clock to 18:30, then took off. The flight went smoothly
until exactly 19:29:59 (system), then the clock changed back to 18:30 again. After that, screams,
swearing and a big hole in the ground, again!

As you can see, once the system clock goes off-line again, the Flight Management System in
the Triple 7 goes haywire.

Obviously, keeping this board with its problems is useless to me.

So, I shall now close down this computer and see if the new one has the same problem!

I shall be taking it back tomorrow around 1pm german time, so if you would like any further
information, please post before 11am german time or send me an email : siriusb57@web.de

SiriusB (Phil)

[ironfan]

Well I spoke too soon. Clock has gone back to its bad behavior today where it gets to a certain time and then jumps back an hour.

Most disappointed 😞

[CiscoX]

ironfan wrote:
Well I spoke too soon. Clock has gone back to its bad behavior today where it gets to a certain time and then jumps back an hour.

Most disappointed 😞

Same problem after the new BIOS update (1505). The clock was still running after a restart, but the time was wrong. I didn't need to reset the BIOS this time, just change the clock and save it. Let's see when this happen again.