Page 1 of 1

Computer Clock keeping the time wrong

Posted: 2004-06-04 12:21am
by Alyeska
Several times now I have noticed that my computer clock is not keeping good time. I've fixed it and a couple weeks later its gone bad again. Any ideas whats wrong?

Posted: 2004-06-04 12:28am
by Alyeska
And now the little devil just reset itself back to the right time all on its own...

Posted: 2004-06-04 12:44am
by DPDarkPrimus
Computer clocks aren't worth much, sometimes. Get a watch. :P

Posted: 2004-06-04 12:44am
by Gandalf
Are you using "PrecisionTime" or any program such as that?

Re: Computer Clock keeping the time wrong

Posted: 2004-06-04 12:49am
by Kamakazie Sith
Alyeska wrote:Several times now I have noticed that my computer clock is not keeping good time. I've fixed it and a couple weeks later its gone bad again. Any ideas whats wrong?
CMOS battery...

Posted: 2004-06-04 01:15am
by DPDarkPrimus
Seriously... computer clocks are no more accurate than the $4 watches you can buy at Wal-Mart.

Posted: 2004-06-04 01:23am
by phongn
Yeah, check the battery on your motherboard, it might be dying.

Posted: 2004-06-04 01:38am
by Kamakazie Sith
DPDarkPrimus wrote:Seriously... computer clocks are no more accurate than the $4 watches you can buy at Wal-Mart.
I've never had a problem....I mean after a year I notice a discrepancy but nothing major.

Posted: 2004-06-04 02:29am
by Faram
Check if you have the right timezone and if the autoadjust clock is on

Posted: 2004-06-04 04:33am
by The Wookiee
Alyeska wrote:And now the little devil just reset itself back to the right time all on its own...
Depending on what OS you have your clock can autosync itself to USNO time, I think.

Posted: 2004-06-04 08:37am
by InnocentBystander
Try this software! I don't use it and only found it 8 seconds ago, but I'm sure it works fine.
Cesium Clock Sync Program

Posted: 2004-06-04 09:32am
by Saberslash
InnocentBystander wrote:Try this software! I don't use it and only found it 8 seconds ago, but I'm sure it works fine.
Cesium Clock Sync Program
My friend uses that program, it is wonderful, and it works. I'm gonna get it myself now.

Posted: 2004-06-04 01:19pm
by Vertigo1
Solution: Go to nearest Radio Shack and buy new 3V Lith-Ion watch battery (CR2032 if memory serves) and replace old one. Your system must be really old because rarely do I ever see these things go down unless its been off for years. They get recharged by your computer's power supply when you turn it back on. However, you can only recharge the suckers so many times so.....

Posted: 2004-06-04 01:29pm
by Alyeska
Well the time is off again. But here is the interesting bit. Whenever the time is off, its exactly 10 minutes fast.

Posted: 2004-06-04 02:45pm
by Crayz9000
Better yet... get a program called NetTime. It's an NTP client like PrecisionTime, but doesn't include spyware (last time I checked, PrecisionTime was a Gator bundle...)

Posted: 2004-06-04 02:47pm
by Vertigo1
Crayz9000 wrote:Better yet... get a program called NetTime. It's an NTP client like PrecisionTime, but doesn't include spyware (last time I checked, PrecisionTime was a Gator bundle...)
Or just leave "Windows Time" service enabled if you're running Win2000 or later.

Posted: 2004-06-04 02:51pm
by Alyeska
When the clock is off it is always exactly ten minutes fast.

Posted: 2004-06-04 02:51pm
by Stormbringer
Alyeska wrote:Well the time is off again. But here is the interesting bit. Whenever the time is off, its exactly 10 minutes fast.
If you're computer's cluttered and Windows rot has set in that'll affect them. I had the same problem on mine before I reformated it.

Posted: 2004-06-04 02:54pm
by Vertigo1
Alyeska wrote:When the clock is off it is always exactly ten minutes fast.
Is it off in the BIOS as well, or just in windows?

Posted: 2004-06-04 03:25pm
by General Zod
i had a similar problem awhile back. Turns out somehow this spyware bit called clocksync had attached itself to my computer without my knowledge, and was fucking with my clock's settings. a quick ad-aware scan revealed it. Removed the clocksync, and everything worked smoothly after that. Maybe it's a similar issue?