My time is not staying correct. I have a CR2032 battery.
Should replacing it solve the problem and is there anything I need to do before replacing it?
Replace CMOS battery
- Krom
- DBB Database Master
- Posts: 16138
- Joined: Sun Nov 29, 1998 3:01 am
- Location: Camping the energy center. BTW, did you know you can have up to 100 characters in this location box?
- Contact:
If the CMOS battery was dead, BIOS would usually also be forgetting its settings. If the clock is just getting consistently off by exactly one or any whole number hours, check and make sure your windows timezone settings are correct. Otherwise it would be a good idea to write down all the important BIOS settings that aren't at default, then replace the battery.
- Tunnelcat
- DBB Grand Master
- Posts: 13742
- Joined: Sat Mar 24, 2007 12:32 pm
- Location: Pacific Northwest, U.S.A.
If you're not getting the time off the internet automatically, the clock could be drifting due to a dirty power signal from your power company. My XP computer keeps the time just fine since it's linked to the net for time keeping. But my older computer that doesn't have that feature runs fast all the time.
Definitely write down ALL BIOS settings BEFORE removing the battery. Krom's right, it'll save you a BIG headache.
Definitely write down ALL BIOS settings BEFORE removing the battery. Krom's right, it'll save you a BIG headache.
This is a long shot, but I wanted to share the story more than anything.
I've actually seen benignly written Windows software affect the rate of the system clock, even from a limited user's account, where this shouldn't be possible, speeding up the system clock by up to 2x as fast. I think it has something to do with buggy system calls, but I was more interested in coding around the issue than understanding it at the time. I actually ran into it developing Java code:
http://bugs.sun.com/bugdatabase/view_bu ... id=4500388
Software such as azureus has been known to trigger this issue on Windows too. I think that this could make for an interesting practical joke on a Windows admin in the right circumstances though.
I've actually seen benignly written Windows software affect the rate of the system clock, even from a limited user's account, where this shouldn't be possible, speeding up the system clock by up to 2x as fast. I think it has something to do with buggy system calls, but I was more interested in coding around the issue than understanding it at the time. I actually ran into it developing Java code:
http://bugs.sun.com/bugdatabase/view_bu ... id=4500388
Software such as azureus has been known to trigger this issue on Windows too. I think that this could make for an interesting practical joke on a Windows admin in the right circumstances though.
If you are having issues with your time in Windows, it's a fair bet that it's not you CMOS. Windows keeps time separate from your BIOS.
Also, if your battery was going out, it would be DEAD before you noticed anything. When a battery dies, you loose all the info in the BIOS as Krom stated, but when you boot, you will KNOW because it will forget what kind of drives you have and you will have to go into the CMOS and reset everything and then you will be able to get on with your bootup ... until you shut down again and you will have to repeat the process. I know this from experience.
Under normal conditions, you don't have to mess with your time settings except when you install windows. ... or unless it's a laptop and you're traveling and you want the clock to match the time zone you're in. If you have secondary software to \"keep your time updated\" ..for pete sakes, get rid of it! If there is anything that Windows Can do is keep time well.
Interesting bug Jeff, I could have some fun at work with that.
Also, if your battery was going out, it would be DEAD before you noticed anything. When a battery dies, you loose all the info in the BIOS as Krom stated, but when you boot, you will KNOW because it will forget what kind of drives you have and you will have to go into the CMOS and reset everything and then you will be able to get on with your bootup ... until you shut down again and you will have to repeat the process. I know this from experience.
Under normal conditions, you don't have to mess with your time settings except when you install windows. ... or unless it's a laptop and you're traveling and you want the clock to match the time zone you're in. If you have secondary software to \"keep your time updated\" ..for pete sakes, get rid of it! If there is anything that Windows Can do is keep time well.
Interesting bug Jeff, I could have some fun at work with that.