error

  • Thread starter Thread starter David Black
  • Start date Start date
D

David Black

What causes the clock on my computer to run fast. I have to constantly
update to keep the time correct.
 
Thanks for the prompt reply. I am not sure how much time the clock gains in
a day because once I realize that it has gained more than a couple of minutes
I update the clock with the Internet time server.
 
Thanks for the prompt reply. I am not sure how much time the clock gains in
a day because once I realize that it has gained more than a couple of minutes
I update the clock with the Internet time server.
Click to expand...



Give me an approximate number. I don't need accuracy.
 
It appears to gain 2 minutes in about every 15 minutes or so.
Click to expand...


OK, that's a lot, and something is clearly wrong.

No guarantees, but try this:

Open a command prompt window (Start | Run | cmd) and enter the
following commands:

net stop w32time
w32tm /unregister
w32tm /register
net start w32time

It may not fix the problem, but it won't hurt anything.



 
What causes the clock on my computer to run fast.  I have to constantly
update to keep the time correct.
Click to expand...


It doesn't matter how wrong it is - if it's wrong, it's wrong.

Are you syncing off a network server?
Are you using some firewall besides the Windows firewall?
Does your CMOS time maintian accuracy?

Is your Windows Time service running and set to Automatic?

What are your time synchronization settings?

Check Start, Settings, Control Panel, Date and Time to verify setting
and perform a manual sync with your desired Internet server if that is
appropriate for you. Does that work and set your time properly?

If you syncing to a network server you will not have an Internet Time
tab. If you are not syncing to a network time server and do not have
the Internet Time tab, something else is wrong.

When XP starts, it will read the time from the CMOS first and then set
the time. The default is to sync to the designated time server every
7 days, which is usually quite sufficient if what happens before that
is working properly.

Here are the command to reregister the time service - maybe you had a
typo:

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

If that does not run without error, you have another problem.

Be sure the Windows Time service is running when you reboot.
 
It doesn't matter how wrong it is - if it's wrong, it's wrong.
Click to expand...


It certainly *does* matter. No computer clock is perfect, and they all
vary by some, usually small, amount. That's why software periodically
synchronizes it to an external clock.

The point of my asking how wrong it was to determine whether the error
falls within the expected range of errors or whether it was larger and
therefore indicative of a problem.

His was larger, and therefore clearly indicative of a problem.

Here are the command to reregister the time service - maybe you had a
typo:

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

If that does not run without error, you have another problem.
Click to expand...



And those are the same commands I posted earlier. Why did you repost
them?

If they didn't work, he very likely had a typo.
 
Hi Ken, Thanks for getting back to me. Those were not the exact commands you
sent me yesterday, they were missing the .exe. However, when I type
w32tm.exe /unregister I receive the following error message: Access is
denied, <0x80070005> Thanks for your continued help.
 
Hi Ken, Thanks for getting back to me. Those were not the exact commands you
sent me yesterday, they were missing the .exe.
Click to expand...


When you type a command, the .exe is always optional. It doesn't
matter whether it's there or not, since it's understood if it's
missing. For example, typing notepad and notepad.exe produce the same
result.
 
Thanks again for the prompt response. Can you tell me why I am receiving the
error message I am getting? Thanks in advance for your continued help.
 
Thanks again for the prompt response. Can you tell me why I am receiving the
error message I am getting? Thanks in advance for your continued help.
Click to expand...


You're welcome. Are you running as an administrator? If not, perhaps
that's why you are getting the error. Try creating a shortcut to cmd
and instead of just double-clicking it, right-click it and click "Run
as administrator."

 
I am running as Administrator

Ken Blake said:
You're welcome. Are you running as an administrator? If not, perhaps
that's why you are getting the error. Try creating a shortcut to cmd
and instead of just double-clicking it, right-click it and click "Run
as administrator."
Click to expand...
 
Back
Top