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

[virge]

I believe you, and doubt Asus' claim that they can't replicate this problem. At any rate, they won't ever put any real attempt at fixing this
problem until it starts to hurt their wallet. Incentive for a big company is always spelt money. However, is everyone who has this problem
using a 4770K CPU? I wonder if it is CPU related.

[Daronis38]

Virge.... I feel your pain as I have tried to get to the bottom of this problem in this and another thread (Hero Time Clock Problem) and after Raja and Praz tried to blame me for not sending them my MB and complaining about the little problem they deleted all my posts of protest along with many other customers who complained....
Obviously its a huge cover up and they have no intention of addressing the problem... Google this problem and you will see it covers many different models of Asus Mb's with the Z87 chipset..... Haven't seen any other Mfg's of Z87 with the same problem though...
I have used or sold well over 200 Asus MB's but my Hero VI will be the last for me or any of my clients....
BTW.... it's been known by Asus for over 10 months.. and I even dealt with Asus Tech (Nov 15, 2013) and he said it needed a new cmos chip but the source he sent me to at Asus Estore said they weren't available(Dec 10, 2013).....In 26 years of being Network Consultant and Tech I never encountered this issue with any MB's....
I hope you get to read this post before they delete it like they did my other posts..... Best Luck....

PS. I keep copies of all my posts however I'm not here to cause problems for Raja or Praz as I believe they are just doing what they are told... Just came here to motivate someone to resolve issue..

[virge]

Daronis38 wrote:
Virge.... I feel your pain as I have tried to get to the bottom of this problem in this and another thread (Hero Time Clock Problem) and after Raja and Praz tried to blame me for not sending them my MB and complaining about the little problem they deleted all my posts of protest along with many other customers who complained....
Obviously its a huge cover up and they have no intention of addressing the problem... Google this problem and you will see it covers many different models of Asus Mb's with the Z87 chipset..... Haven't seen any other Mfg's of Z87 with the same problem though...
I have used or sold well over 200 Asus MB's but my Hero VI will be the last for me or any of my clients....
BTW.... it's been known by Asus for over 10 months.. and I even dealt with Asus Tech (Nov 15, 2013) and he said it needed a new cmos chip but the source he sent me to at Asus Estore said they weren't available(Dec 10, 2013).....In 26 years of being Network Consultant and Tech I never encountered this issue with any MB's....
I hope you get to read this post before they delete it like they did my other posts..... Best Luck....

PS. I keep copies of all my posts however I'm not here to cause problems for Raja or Praz as I believe they are just doing what they are told... Just came here to motivate someone to resolve issue..

I agree with you about Raja and Praz. I think they are just doing what they are told. Also the fact that they delete negative comments about the facts is appalling. It tells me that Asus is indeed trying to hide this serious problem. Logically I have to believe that ultimately this has to be a software problem, or the wrong mix of hardware, such as memory modules etc. Why I say this is because it seems this problem presents itself over their other Z87 boards. I also don't believe it is a chipset problem either, because if other manufacturers who use the Z87 chipset with no issues such as this , then it has to be an Asus specific issue. Are ALL their Z87 boards having these problems, or just the ROG edition motherboards?

It looks like the king of the hill for so long is beginning to falter. I think their crown has slid down over their eyes, and they can't see their customers anguish. This reminds me of GM in the car industry. GM disregarded the quality of their product, and look what happened to them. Maybe this is the beginning of a downward trend for Asus. Now it seems to me that Gigabyte is looking much more appealing. I am sure this post will also be promptly deleted, but maybe you might get in here soon enough before they do. best regards.

[EasyEE1]

Good day sirs. I just had my rig in the shop to have the bios updated and the cmos reset due to the frozen clock issue. (rather have a pro do it) My tech told me not to use the sleep function anymore for shutdown because it could put the MOBO into standby mode and cause the clock issue to reappear. Is this true?
Secondly, now that these updates and resets are done is this a permanent fix or is there a chance the issue will return?

Thank you for your time.

[Tokens210]

EasyEE1 wrote:
Good day sirs. I just had my rig in the shop to have the bios updated and the cmos reset due to the frozen clock issue. (rather have a pro do it) My tech told me not to use the sleep function anymore for shutdown because it could put the MOBO into standby mode and cause the clock issue to reappear. Is this true?
Secondly, now that these updates and resets are done is this a permanent fix or is there a chance the issue will return?

Thank you for your time.

Its almost a guarantee that it'll reappear, when and how long itll last are the questions

My bios clock only worked during setup of my PC, then for awhile, probly at least a month it was frozen and kept throwing windows clock off

I fixed the windows clock so its never wrong anymore, then a few weeks later all on its own the bios clock started ticking along again

Currently the clock unfroze itself and has been ticking for a few weeks now

I shut down the PC everynight when I'm finished with it, and typically I don't allow it to fall asleep while I'm using it but it has from time to time

[sh9168]

Raja, I too had this issue come up on my Z87 Sabertooth which I purchased back in January 2014. After reading your post at the beginning of the thread I was able to fix the issue per your directions. Thank you for the clear directions. As some others have had the issue return, I will monitor my clock and if this issue returns I will contact you about letting you test with my board. (I live in the US). Thanks again

Steve

[Powellellogram]

Sorry, but these instructions are awful for a relatively novice user of Computers. I just built my first computer and am new to all of this stuff, and this doesn't give a deep enough explanation of each step.

The problem I'm having is that the BIOS clock is stuck between the 7-9pm, and I was convinced it was a dead CMOS battery. Every time I try to find out how to fix it without buying a new battery (the mobo is a few weeks old!!) I'm directed here, but I don't understand the steps.

[zeraoo98]

Okay i can explain...

Do you want to just reset clock so they work for a while? (Reset settings in BIOS, easy way)

or

Flash BIOS with newest Firmware and hope that problem fixes itself (not for sure)

[ironfan]

It's been almost two weeks now and so far the clock is still ticking 🙂

[zeraoo98]

Did you flash to 1505? Or did you apply some other fix?