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

[FZG_Immel]

Ok. Nevermind.

I did the fix indicated in page one and so far, it seems to work (except the MEI update as I don't know what and how to install it). No more frozen clock. Times in windows stays good.

We will see in the future.

[Gianpiero]

Just to inform that I tried the fix suggested on page 1 and it seems Ok.
Thanks!

[GeoCan]

It does NOT fix the problem. This is the second time in 7 months I've had to reset the BIOS. Even my first 286 build was more reliable than this board.

[Tokens210]

GeoCan wrote:
It does NOT fix the problem. This is the second time in 7 months I've had to reset the BIOS. Even my first 286 build was more reliable than this board.

The fix listed on the first pages here are known to only fix it temporarily, there is no fix for the issue as far as I've seen, that's why this threads so large lol

[Technochris]

We all know that Asus doesn't recognize the UEFI BIOS Frozen clock bug.

But no one seems to understand that if Asus has adopted this position, that's only to avoid
tons of complaints that would force them to refund or replace the countless defective motherboards they built and sold.

Yet the facts are there indeed, thousands, or even millions of users of motherboards based
Z87\Z97 chipset are affected by this bug that Asus are refusing to recognize.

Don't be naive enough to think that Asus will solve this problem, because they never will...

Instead, Asus will continue to claim that they have a Fix that solves the problem when, in fact, the problem keeps coming back without ever being resolved.

I know whereof I speak since I applied the Fix dozens and dozens of times and the bug is still coming back, time after time. I'm even forced to apply the Fix several times a day to tell you how severely my Z87-Deluxe/Quad is affected.

On my motherboard, it took 6 months before the bug appeared because during the first 6 months I ran everything at stock settings without overclocking. Even my 2133Mhz memory didn't used the XMP profile and ran at 1066Mhz instead of 2133Mhz but when I began to Overclock my CPU at 4Ghz and my memory at 2133Mhz by switching it to use the XMP profile the frozen clock problem began and never went away even if I switched everything back at stock settings and reset the BIOS over a hundred times after having flashed it each time.


Asus will continue to maintain its position until the exhaustion of our warranty period while they will miserably keep on pretending they never had such a defective motherboard between their hands to check it but the fact is they have countless warehouses fully loaded of such motherboards and they just just had to pick one of them to check it and they would quickly have seen the bug because the way it looks it seems that all the motherboards based on the Z87\Z97 chipsets are affected by this bug...


This behavior is totally unacceptable from a responsible company and we have no reason to tolerate this any longer.


So here's what I suggest:


Let's start a class action lawsuit against Asus in order to claim the refund or replacement of our motherboard affected by freezing of the UEFI BIOS clock by a new motherboard not based on neither the Z87 nor the Z97 chipset. I'm pretty sure it will be a breeze to find Lawyers to discuss this matter in court.

That's the only way to deal with such a dishonest company...

[Griiinbergs]

Hello everyone...

Not long ago i got my new system that is built with Asus Maximus VII Gene Mobo after some time ofc the clock problem showed up to the mobo itself is only 2 weeks old. U can forget about Bios battery, resetting RTC and so on that only will help for shot time (that is in my case).

So i found a rly good solution to it...

Went in yo windows services and changed Windows Time Service from manual to Auto sooo my windows sync with online time and forgets about bios clock.

[aydintr]

I bought my Maximus Gene VI like 1.5 years ago and I had the issue after 6 months. I directly sent the motherboard to Asus service. And they solved the problem somehow. At least I thought they did. After exact 1 year later -means today- the problem showed up again.

I'm about to going crazy.

[PerpetualCycle]

Did you try replacing the CMOS battery?

[Technochris]

We all know that Asus never fixed the BIOS Frozen clock problem.

The only solution they published about this is a temporary fiix which doesn't really solve the problem because no matter what you're doing the bug keeps coming back, soon or late.

However, I made a very interesting discovery lately about this bug...

If I uninstall Microsoft update Visual C++ 2005, the bug goes away and never comes back.

At lesast, this is the result I have on my Windows 7 x64 computer.

Of course, the uninstallation of this update will make you loose some minor functionnalities...

For instance, on my computer, the Logitech MX5500 keyboard can no longer display the time and date and my M-Audio KeyStation Pro88 MiDi keyboard driver can no longer be installed. However, this driver is not necessary anymore under Windows 7 x64.

In other words, there is a little trade off to pay for the uninstallation of the Microsoft Visual C++ 2005 update, but at least, you'll get a stable running computer that doesn't crash anymore because of the BIOS Frozen Clock bug...

Give it a try, who knows, it might work for you also...

[PerpetualCycle]

My mother always used to say "Never say never"