computer clock

[Michael McNeil]

not sure where else to post this message so I thought I would try here

my computer clock runs fast for some reason

I reset up at 4 pm today and 6 hours later it is showing up as 3 pm
the following day. this has been happening for the past few days now.

I can set it up for auto update through windows or the gov site and
that will correct the problem temporarily and then it speeds up agian.

anyone ever have this problem and know how to fix it?

 

[Wayne McGlinn]

Check that you're in the correct time zone?

--
Wayne McGlinn
Brisbane, Oz

"Listen. Strange women lying in ponds distributing swords is no basis for a
system of government. Supreme executive power derives from a mandate from
the masses, not from some farcical aquatic ceremony - Dennis"

 

[MGGP]

Have you checked the motherboard manufacturer's website
for information specific to this motherboard ?

Have you changed anything in the BIOS ?

What changed between the time that the clock worked
correctly and now ?

It could be a faulty CMOS battery . . .

Have you checked Event Viewer . . . to maybe get a
clue . . .

Have you searched Google for problems with this
motherboard or system-type ?

Good Luck !

 

[Michael McNeil]

already did that.

 

[Alex Nichol]

not sure where else to post this message so I thought I would try here

my computer clock runs fast for some reason

I reset up at 4 pm today and 6 hours later it is showing up as 3 pm
the following day. this has been happening for the past few days now.

This problem seems to happen quite often - especially with Dell
machines. Usually a steady rate of loss/gain like 10 minutes in an
hour. It appears to result from a conflict with the BIOS over the
interval between 'timer interrupts'. Windows maintains the clock by
counting these, so if the interval is not the expected one, the rate is
grossly out in this manner.

Try these steps:

1. Start->Run cmd.exe
2. net stop w32time
3. w32tm.exe /unregister
4. w32tm.exe /register
5. net start w32time

(note spellings w32tm and w32time in different commands)

 

[Michael McNeil]

and this does what exactly? my machine is not a dell but rather a
custom made AMD .

this is the second time that this has happened in the past 5 months.
the first time it just cleared up on it's own.

 

[Michael McNeil]

didn't make a difference.

 

[Michael McNeil]

downloaded a program called dimension 4 to give that a try and set it
up to reconfigure every 5 minutes. So far in the past 12 hours or so
that it's been running the computer only gained 15 minutes as opposed
to 6 hours like it normally did.

Contacted a buddy of mine who's a computer techie and he said more
than likely the problem lies within the CMOS battery itself. So I am
going to replace that this week hopefully providing that I can find
one.

 

[SFB - KB3MM]

Have you checked the motherboard manufacturer's website
for information specific to this motherboard ?

Have you changed anything in the BIOS ?

What changed between the time that the clock worked
correctly and now ?

It could be a faulty CMOS battery . . .
HUH!?


Have you checked Event Viewer . . . to maybe get a
clue . . .

Have you searched Google for problems with this
motherboard or system-type ?

Good Luck !

 

[hammertown]

I have been experiencing this same problem lately. It only started
noticing this within the last week or so.

I have manually edited the windows time service parameters in the
registry to update the time every 15min from time.nist.gov Every
15min when the time service makes an update, an entry is added to the
system event log that it has reset the clock...by as little as 90sec
and sometimes as much as 130sec EVERY 15min!!! I think anything less
than 60sec won't show up in the event log.

I cant recall if I've installed any software lately but certainly not
in the last 2 weeks. The only thing I can think of is that Avast
AntiVirus has recently added a new web scanning component. Avast is
the only thing that has automatic updates enabled.

I've tried leaving the system idle at the desktop after a fresh
restart and the problem is noticed. I've left the system idle in the
bios setup and didn't notice the problem...so it must be a software
issue. The next thing I may try is booting to safemode and see if
anything changes.

D.