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

[Shiney2512]

diegopl2 wrote:
Hello, I have a Maximus Hero VI and I'm having the frozen clock issue.

I have applied the fix Rava show us, but after a time the issue come back. Is there any permanent solution?

Is very annoying to apply the fix every time the clock freezes. I think I should bring back the motherboard, Asus has had enough time to solve the problem and they didn't it.

+1 - I need a permanent fix asap - due to time sensitive information stored on system.

[diegopl2]

Nothing new? I need an answer to process the rma. I don't want to be doing Clear CMOS every other day.

[Chino]

Shiney2512 wrote:
+1 - I need a permanent fix asap - due to time sensitive information stored on system.

diegopl2 wrote:
Nothing new? I need an answer to process the rma. I don't want to be doing Clear CMOS every other day.

Are you guys using the CLEAR RTC jumper in the third step?

[WebMaximus]

I've been using the clear CMOS button on the rear panel of my motherboard.

[Chino]

WebMaximus wrote:
I've been using the clear CMOS button on the rear panel of my motherboard.

Use the jumper next time. That should fix this pesky problem.

[WebMaximus]

Ok, I'll try that but I thought the button would do the same thing or what is the button for? I see how depressing the button cuts the power because the ROG logo etc goes out.

[Shiney2512]

WebMaximus wrote:
Ok, I'll try that but I thought the button would do the same thing or what is the button for? I see how depressing the button cuts the power because the ROG logo etc goes out.

I've been using the button as well (formula vi board), isn't that the whole idea of the button, so you don't have to open up the case? The last time I reset the cmos, it lasted a month before the clock Focked up again!

I've got a b2 revision with the latest 904 bios, if I did rma the board, are the new boards having the same issue?

[Ray_Proudfoot]

I've looked in the manual and cannot see any reference to a jumper for my Maximus VI Gene. Does one exists?

Having spoken to tech support at Scan this morning there isn't a jumper to adjust on my VI Gene. Instead the system is powered off but with the power switch to the mobo on and the Clear RTC button is held down for a few seconds.

When the system is powered up confirmation that the BIOS was reset is displayed and pressing F1 takes you into UEFI. The clock was running and I loaded my o/clock profile.

Whether this fix sticks is debatable. Scan did it a week or so back and it didn't. If it stops again I'll look for a replacement board from another manufacturer. But I'd rather Asus sort this problem out.

[savage1987]

Just delivered a system with a M VI Hero board that's having the same issue. This is a dealbreaker if it isn't fixed in short order.

[DeterH]

Hi all, I had this same clock problem.

What worked for me was remove and re-install the MB battery, then reset the clock to the correct time. Has kept correct time now for last 4-5 days. Hope I'm addressing the correct problem here and that this helps.

Best Regards,
DeterH