XP clock problem

[RonManager]

The clock on my laptop has started to play up. No matter what time I set it to, after 60 minutes, it sets back to where it started. This affects various websites, especially SkyPlayer, which freezes, causing all other open tabs to freeze.

 

Any ideas?

 

 

Also just realised it takes 80 minutes to do 60 minutes! Not gradually losing time but stopping then starting again.

Edited 8 October, 2010 by RonManager

[saint_stevo]

what time source is it sync'd to? do you have the correct DST ?

[Liquidshokk]

Sounds like the internal clock battery is on it's way out....

[saint_stevo]

if it is the CMOS then it would say on boot that the time is wrong, press F1 to continue etc

[RonManager]

what time source is it sync'd to? do you have the correct DST ?

 

It's sync'd to time.nist.gov on the internet time tab, and tells me that it is ok.

 

What is DST? If you mean GMT then yes it is calibrated to that.

[Liquidshokk]

if it is the CMOS then it would say on boot that the time is wrong, press F1 to continue etc

 

Stranger things have happened if its only playing up... but yeah sounds like it is trying to sync after 60 minutes as you say. I'll butt out.

[RonManager]

Also just realised it takes 80 minutes to do 60 minutes! Not gradually losing time but stopping then starting again.

Edited 8 October, 2010 by RonManager

[saint_stevo]

It's sync'd to time.nist.gov on the internet time tab, and tells me that it is ok.

 

What is DST? If you mean GMT then yes it is calibrated to that.

 

Try using time.windows.com, 0x1

 

Also, restart the W32time service. See what happens. Failing that, try a new CMOS (£1 max)

[RonManager]

Try using time.windows.com, 0x1

 

Also, restart the W32time service. See what happens. Failing that, try a new CMOS (£1 max)

 

I changed the sync to time.windows yesterday at 1230pm. The clock kept accurate time and I turned the laptop off at about 1am this morning, still keeping accurate time ok.

 

Turned it on this morning at 1100 and the clock read 1230pm again, as if it had reverted to yesterday's sync up time. I re-sync'd it and it is functioning ok again. So we have some sort of improvement!!

 

How do I restart the W32time service you mentioned?

[saint_stevo]

start-run

type in services.msc

 

find w32time, right click and restart (it may not be running at all, thus causing your problem!?)

[RonManager]

start-run

type in services.msc

 

find w32time, right click and restart (it may not be running at all, thus causing your problem!?)

 

Ok, done that. It was running but I've restarted it anyway. So now we play the waiting game........