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

[Iscariah]

BoneCrusher wrote:
How did you update the ME firmware?? Within windows?? I cant get it to work in W8.1, even running cmd as admin.

Nevermind i fixed it! 😄

Yup, within Windows, using a package I got from www.station-drivers.com (see links in my post on page 8), just ran a CMD file included in the package, but the simple command line is the following:

FWUpdLcl64.exe -F ME_9.0.31.1487.bin (I'm running Win7x64)

Rebooted, cleared CMOS, installed MEI drivers, and that was it! I can send you the package via e-mail if you want.

[BoneCrusher]

Iscariah wrote:
Yup, within Windows, using a package I got from www.station-drivers.com (see links in my post on page 8), just ran a CMD file included in the package, but the simple command line is the following:

FWUpdLcl64.exe -F ME_9.0.31.1487.bin (I'm running Win7x64)

Rebooted, cleared CMOS, installed MEI drivers, and that was it! I can send you the package via e-mail if you want.

Thx mate.. i fixed it by myself... seems to be working! 😄

[Pentium4]

Can't believe mine just went again this morning, after thinking I had the problem fixed :mad: It has lasted 5 weeks before screwing up, and was working perfectly last night. I switched my pc on this morning, and the clock was 80 minutes out. Hopefully someone at Asus can address this frustrating anomaly, as apart from this one very annoying problem (and the double booting), this is one hell of a motherboard!!

[Raptor05121]

Can ASUS swap us mobos? This is getting tiresome. I have been using the above fix but the problem keeps reoccurring on my Sabertooth!

[Raja]

Praz is trying to replicate with a Sabertooth - so please post full system specs and UEFI changes if any.

[Oubadah]

Raja@ASUS wrote:
Praz is trying to replicate with a Sabertooth - so please post full system specs and UEFI changes if any.

Is there any way to dump all your current UEFI settings to a text file or something?

[Szeged]

Is this problem still happening? i sold my VI Hero motherboard a little over a month ago because of this issue, got a rampage iv black and 4930k instead, but wanted to get another haswell system. If this problem still exists my new 4770k system will not be in an asus motherboard.

[Praz]

Oubadah wrote:
Is there any way to dump all your current UEFI settings to a text file or something?

No there isn't.

[FrozenClock]

Hello...

I also suffer from this problem...

I am not too worried about it - it's just an annoyance. An annoyance I shouldn't have to deal with mind you - but to be honest I can't be bothered taking it all apart to put in a new motherboard and reactivating windows again...

That's my uneducated view on the subject at least... The only issues I have had so far is web certificates seems to be out of date and my PC warns me that everything might be a dodgy site. I just re-sync my clock with the internet time and it's okay again. I have had no other issues from a frozen BIOS clock.

I'd like the clock to be fixed with firmware of course - but is it the end of the world if it isn't fixable without hardware swap?

At the moment I have set up in Task Scheduler that when I boot up it will sync automatically if there is an internet connection (there normally will be) and then sync every 15 minutes afterwards indefinitely.

I thought the one sync per startup would allow windows to keep time but it does lose time very quickly and by large amounts.

How does Windows keep track of time when its running. I would have thought the BIOS clock would have been used for the initial "what time is it?" and then something would work in Windows to keep track and re-write the BIOS clock at the end? It appears this isn't the case since 1 sync at the start is not enough...

Cheers!

EDIT:
I have just realised the oversight in my plan - how can I trust the broken clock to know when 15 minutes is up for a re-sync? Goddamnit!

[desolator4u]

When I first got my board, the very first POST and boot into my UEFI showed a frozen clock. I followed the steps with the jumper to get it working again, but I was just doing a test run. I put it back in the box after about 30 mins, took out the CMOS battery for a few mins then reinstalled it. About a month later, I setup my new PC (only swapping board, CPU and RAM as I was upgrading from a 775 Striker Extreme) on Jan 2nd, 2014 and I have had no issues with the Clock. I have overclocked and adjusted setting in the UEFI about a 100 times since then and still no issue.

I have to say though, that I am really worried that this prob will eventually start again, as people always seem to end up coming back here to say the fix was temporary. This needs to be resolved permanently. I went through a lot of hassle and expense to get these parts shipped to Jamaica and they need to last me for years to come, as my Striker Extreme did.

FrozenClock wrote:
Hello...

I also suffer from this problem...

I am not too worried about it - it's just an annoyance. An annoyance I shouldn't have to deal with mind you - but to be honest I can't be bothered taking it all apart to put in a new motherboard and reactivating windows again...

That's my uneducated view on the subject at least... The only issues I have had so far is web certificates seems to be out of date and my PC warns me that everything might be a dodgy site. I just re-sync my clock with the internet time and it's okay again. I have had no other issues from a frozen BIOS clock.

I'd like the clock to be fixed with firmware of course - but is it the end of the world if it isn't fixable without hardware swap?

At the moment I have set up in Task Scheduler that when I boot up it will sync automatically if there is an internet connection (there normally will be) and then sync every 15 minutes afterwards indefinitely.

I thought the one sync per startup would allow windows to keep time but it does lose time very quickly and by large amounts.

How does Windows keep track of time when its running. I would have thought the BIOS clock would have been used for the initial "what time is it?" and then something would work in Windows to keep track and re-write the BIOS clock at the end? It appears this isn't the case since 1 sync at the start is not enough...

Cheers!

EDIT:
I have just realised the oversight in my plan - how can I trust the broken clock to know when 15 minutes is up for a re-sync? Goddamnit!

Awesome name, yo. This is a pretty serious issue but I still had to laugh when I saw it.
If you have a scheduled task to update the time at logon, that should be enough. Are you able to test it now? Does the time update to the correct one then no longer changes every minute?