Re: clock's inaccuracy

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: NobodyMan (none_at_none.net)
Date: 04/22/04


Date: Wed, 21 Apr 2004 22:41:59 -0400

On Wed, 21 Apr 2004 15:42:29 -0700, "Adam Turner"
<adturner@email.uophx.edu> wrote:

>
> "Ken Blake, MVP" <kblake@this.is.an.invalid.domain> wrote in message news:OzmJer%23JEHA.556@TK2MSFTNGP10.phx.gbl...
> In news:%230ftEa%23JEHA.2660@TK2MSFTNGP09.phx.gbl,
> Adam Turner <adturner@email.uophx.edu> typed:
>
> > The bios battery needs to be replaced
>
>
> No, when he says "at random," he presumably means that he loses
> time while the computer is running. Before anyone whose clock is
> running slow rushes out to buy a new battery, he should first
> take note of whether he is losing time while the computer is
> running or while it's powered off. If it's while powered off, the
> problem *is* very likely the battery. But if it's while running,
> it can *not* be the battery.
>
> If the clock loses time while running, 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
>
> --
> Ken Blake - Microsoft MVP Windows: Shell/User
> Please reply to the newsgroup
>
>
> > "marco" <anonymous@discussions.microsoft.com> wrote in
> message
> > news:267f01c427e4$5c1010c0$a101280a@phx.gbl...
> > I have XP Pro on a new hp compaq, P IV, 512 RAM, but the
> > clock shows severals minutes ago, at ramdom. I 've seen
> > this behaviour on at least another identical machine
> > here. It's there a hardware issue or it is XP?
>...and out of curiosity Ken, what will stopping the clock and starting it again resolve?
>
>Wouldn't the result be the same from a cold boot?
>Adam Turner

Kens' advice doesn't stop the clock. It stops the time service then
restarts it. The clock still runs during the process. The time
service and the clock aren't the same thing.



Relevant Pages

  • Re: W32time event id 36
    ... >The time service has not been able to synchronize the system time for ... The system clock is unsynchronized. ... >as a message is logged in the event viewer when the clocks are ... net start w32time ...
    (microsoft.public.windowsxp.general)
  • Re: W32time event id 36
    ... >>The time service has not been able to synchronize the system time for ... The system clock is unsynchronized. ... >>as a message is logged in the event viewer when the clocks are ... net start w32time ...
    (microsoft.public.windowsxp.general)
  • Re: Windows Time unstable at synchronising?
    ... Looking at the data, the clock was close to atomic time for two synch periods, then started to diverge at each "synch" event, with larger and larger step changes. ... Why did W32time start to move the clock away from a settled, ... uses the RTC when the ...
    (microsoft.public.windowsxp.general)
  • Re: Windows Time unstable at synchronising?
    ... Why did W32time start to move the clock away from a settled, ... this using hourly synch periods, so I wouldn't grow too old waiting for the ... Is there a common hardware characteristic, ...
    (microsoft.public.windowsxp.general)
  • W32TIME errors : PC clock can not sync ...
    ... the: time.windows.com and time.nist.gov servers. ... I've added the 128.250.36.3 server to the clock and my clock get sync fine ... Event Source: W32Time ... Time Provider NtpClient: An error occurred during DNS lookup of the manually ...
    (microsoft.public.windowsxp.general)