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

[rforeman]

I am having the same problem with the MAXIMUS VI HERO. I went through the info in the first post of this thread and it worked till the power flicker and the PC rebooted. Now I am back to the same problem. ASUS NEEDS TO FIX THIS!!!!!!!!

[WeelyTM]

rforeman wrote:
I am having the same problem with the MAXIMUS VI HERO. I went through the info in the first post of this thread and it worked till the power flicker and the PC rebooted. Now I am back to the same problem. ASUS NEEDS TO FIX THIS!!!!!!!!

Did you try Iscariah's solution of updating the Intel ME firmware, then re-flashing bios? Did it almost a month ago, and the clock issue has not reappeared for me on my Maximus Hero (not yet anyway, knock on wood).

Here's a link to his original post

[rforeman]

WeelyTM wrote:
Did you try Iscariah's solution of updating the Intel ME firmware, then re-flashing bios? Did it almost a month ago, and the clock issue has not reappeared for me on my Maximus Hero (not yet anyway, knock on wood).

Here's a link to his original post

I have not re-flashed the bios yet. I did update the drivers. I am running the most current bios but I will re-flash it tonight.

[bern43]

rforeman wrote:
I have not re-flashed the bios yet. I did update the drivers. I am running the most current bios but I will re-flash it tonight.

The problem will just come back.

[JackNaylorPE]

WeelyTM wrote:
Did you try Iscariah's solution of updating the Intel ME firmware, then re-flashing bios? Did it almost a month ago, and the clock issue has not reappeared for me on my Maximus Hero (not yet anyway, knock on wood).

Here's a link to his original post

The reason I didn't try it is that his solution was for the Hero and I'm using the Formula. Intel ME web site says the versions are MoBo Specific.

"Some PCs may have multiple versions of the firmware available for different sizes of flash memory, or for upgradeable systems. Consult with your PC manufacturer if you are unsure about which firmware upgrade package to use. "

https://communities.intel.com/docs/DOC-5962

Just clearing CMOS had worked in the past but it sure is a PITA to re-enter 100+ of customized BIOS settings 8 different profiles.

I have been able to reproduce the problem pretty consistently:

1. Do the "fix" from 1st post.

2. Set up your Default Profile, default settings, setup boot priorities ..... Save as Profile 1

3. Try CPU level Up to 4.2 Ghz and then add 42/42 cache, save as profile 2
(The voltages are obviously low and this is not expected to be stable on most boxes but that's the idea)

4. Run RoG Real Bench Benchmark.... I fail on the Heavy Multitasking part with a STOP 0x000000124

5. Reboot and system clock frozen. Also BIOS does not display voltages to the left of the input boxes in Extreme Tweaker Menu. Setting clock to correct time seems to restore this. However, loading save OC profiles freezes the system. Clearing the CMOS does not remove the OC Profiles. So only solution I have found is to reload the BIOS w/ EZ Flash and start all over again.

[ripolo]

Same situation, here with Asus Z87-Expert, BIOS 1802, Intel MEI version 9.5.14.1724.

Windows 8.1 Pro 64b up to date.
i5-4670K
GTX 660 Ti
16GB

I flashed BIOS following OP method. But it keeps coming back. Mobo is not OC.

[clubfoot]

ripolo wrote:
Same situation, here with Asus Z87-Expert, BIOS 1802, Intel MEI version 9.5.14.1724.

Windows 8.1 Pro 64b up to date.
i5-4670K
GTX 660 Ti
16GB

I flashed BIOS following OP method. But it keeps coming back. Mobo is not OC.

Did you use the EZ flash or flash back?

[JackNaylorPE]

Well so much for my consistent duplication of the problem. After going 3 outta 4 on my 1st 4 attempts to duplicate the problem, I have since zeroed in my OC settings from 42 CPU multiplier thru 45 with steps of cache at 38, 42 and 45 and finally ending with boosting RAM to XMP. Prolly had 20 crashes in zeroing those in and haven't had bug appear as yet. As I type I worked my away up thru 46 multiplier (46 CPU Multiplier / 45 cache /\ 1600 running now) and still no re-appearance so looks like my method's ability to reproduce this error is far from as reliable as i first assumed.

EDIT: Spoke to soon within minutes of typing this, the frozen bug strikes again. This time noticed it while I was doing 8 hour Intel ETU test .... took a progress peek and the 8 hour test needed > 8 hours to finish. Last thing I did before that was save last OC profile and save to USB.

Rentered everything manually, saved the 1 profile, ran 2 hour RoG Bench test .... rebooted, clock had stopped 2 hours before

Tried loading the CMO after reloading BIOS and it freezes system. Also trashes USB.....EZ Flash will no longer read from the USB even after reformatting and replacing CAP file

[clubfoot]

Does the clock lock WITH default settings or only when you o/c? If you can get it going again with defaults, correct the time, boot into windows and run the internet time update. Use the system for a couple days WITHOUT o/c and see if it holds.

If the time holds sync,...it's your o/c!

[WeelyTM]

FWIW, mine hasn't come back since I disabled sleep and hibernate, could be related?