System clock pauses while computer is off.

[MtSeldon]

When i boot the system , i see that the clock is the same as i shut down the computer ,tough computer is still connected to power and psu isn't off, i can see the motherboard leds.

First thing comes to mind is the motherboard battery but this motherboard is like 3 months old. Asus ROG maximus VI Hero. And wouldn't all the settings reset if it was the battery?

Any idea what could be the cause?

 

[John Connor]

Could be a faulty board. I would reset CMOS and see if that changes any thing.

 

[Drummerdude]

easiest test is to replace battery, regardless of age

 

[tidy]

.

 

[John Connor]

Why I go Gigabyte. LOL!

 

[tidy]

.

 

[Morbus]

Happened to me on a ONE MONTH old Asus Z87-A.

Naturally I didn't think it'd be the CMOS battery, so I didn't even bother. Tried everything else, nothing changed it.

End result: it wasn't the battery, obviously, but something got borked in the BIOS and all I needed to do was take the battery out for a couple of minutes. Everything went back to working perfectly.

Of course, if that doesn't work for you (which I must say it's a VERY RARE occurrence, from what I can tell), it's possible your boards quartz clock got fried or something, so you need to RMA it. But that's like finding an unicorn, really.

 

[Lonyo]

http://answers.microsoft.com/en-us/...how-do-i/3ad0278b-370d-416d-867a-534729ca7d32

Set up Windows to sync the time more frequently so that when you're actually using the PC the time is up to date without having to do it manually.
It's a bit of a hacky workaround, rather than solving the underlying problem, but better than nothing if it's an Asus issue they won't solve.
If you set it to "on workstation unlock" from the dropdown, that means every time you resume/start up it should update.

 

[crashtech]

^ That is a cool way to ensure high clock accuracy, though as mentioned it's a kludgy way to fix a hardware/firmware problem.

 

[MtSeldon]

I just used the clear cmos jumper , and problem seems to be fixed.

But i lost respect for Asus. Those threads on Asus forum starts from August , and the problem still hasnt been solved.

 

[tidy]

.

 

[Morbus]

Don't expect it to last.

I know when the problem happened without a doubt: on a full system format, back on January.

It's been going strong since then, no problems whatsoever.

 

[MtSeldon]

it happened after a full system format in my case too. Maybe i wont happen again.

 

[tidy]

.

 

[Morbus]

I seem to remember installing it and having a lot of problems. Can't remember how I installed it and what the problems were, but I'm pretty certain I don't have it installed...

 

[MtSeldon]

I installed it via a installer.
I'm not sure what it does. Should we not install it ?

 

[tidy]

.

 

[Morbus]

So you installed it during the 'full system format' that you believe triggered the issue?

Indeed, that may have been the case.

Although, if I recall correctly, I uninstalled the drivers and the problem persisted, and then I removed the battery and it fixed the issue, no windows reinstall necessary.

Of course, my theory that you don't need to install something if you don't know what it's for still stands strong. If something's not working correctly, THEN you need to consider installing drivers or updating the bios or whatever. Not before that.

 

[tidy]

.

 

[sm625]

Usually when you have a dead battery, the system clock reverts to date of manufacture when power is lost. I've never seen one simply pause.

 

[justrandomguy]

replace battery