Fast Running Clock

[Podge]

My clock has suddenly started to run very fast at times.
Suddenly it will be day/weeks/months ahead if I don't pay
attention to it. Anybody got any ideas?
Thanks guys

[JBM]

"Podge" > wrote in message
...
> My clock has suddenly started to run very fast at times.
> Suddenly it will be day/weeks/months ahead if I don't pay
> attention to it. Anybody got any ideas?
> Thanks guys

I noticed the same problem yesterday on my A7N8X Deluxe MB.
If I restart it goes back to normal until the next time.
Just installed Beyond TV 3 from Snap stream when the problem
showed up. Don't know if thats the cause or it's just a coincidence.

Jim Manning

[Alex Nichol]

Podge wrote:

>My clock has suddenly started to run very fast at times.
>Suddenly it will be day/weeks/months ahead if I don't pay
>attention to it. Anybody got any ideas?

This problem seems to happen quite often, especially with Dell
machines. Usually a steady rate of loss like 10 minutes in an hour.
And not usually an erratic effect. 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. BTW because
Windows does it this way, any troubles with the clock *while windows is
running* is definitely *not* the battery

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)


--
Alex Nichol MS MVP (Windows Technologies)
Bournemouth, U.K. (remove the D8 bit)

[Please reply to newsgroup.]

Alex Nichol wrote:

> Podge wrote:
>
>
>>My clock has suddenly started to run very fast at times.
>>Suddenly it will be day/weeks/months ahead if I don't pay
>>attention to it. Anybody got any ideas?
>
>
> This problem seems to happen quite often, especially with Dell
> machines. Usually a steady rate of loss like 10 minutes in an hour.
> And not usually an erratic effect. 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. BTW because
> Windows does it this way, any troubles with the clock *while windows is
> running* is definitely *not* the battery
>
> 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)

I have a four-month-old Dell and its clock has always been right. (It
probably helps that Windows adjusts the clock every week, but it is
right in between those times, too.)

[Please reply to newsgroup.]

Alex Nichol wrote:

> Podge wrote:
>
>
>>My clock has suddenly started to run very fast at times.
>>Suddenly it will be day/weeks/months ahead if I don't pay
>>attention to it. Anybody got any ideas?
>
>
> This problem seems to happen quite often, especially with Dell
> machines. Usually a steady rate of loss like 10 minutes in an hour.
> And not usually an erratic effect. 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. BTW because
> Windows does it this way, any troubles with the clock *while windows is
> running* is definitely *not* the battery
>
> 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)

I have a four-month-old Dell and its clock has always been right. (It
probably helps that Windows adjusts the clock every week, but it is
right in between those times, too.)

[Please reply to newsgroup.]

Alex Nichol wrote:

> Podge wrote:
>
>
>>My clock has suddenly started to run very fast at times.
>>Suddenly it will be day/weeks/months ahead if I don't pay
>>attention to it. Anybody got any ideas?
>
>
> This problem seems to happen quite often, especially with Dell
> machines. Usually a steady rate of loss like 10 minutes in an hour.
> And not usually an erratic effect. 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. BTW because
> Windows does it this way, any troubles with the clock *while windows is
> running* is definitely *not* the battery
>
> 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)

I have a four-month-old Dell and its clock has always been right. (It
probably helps that Windows adjusts the clock every week, but it is
right in between those times, too.)

[Please reply to newsgroup.]

Alex Nichol wrote:

> Podge wrote:
>
>
>>My clock has suddenly started to run very fast at times.
>>Suddenly it will be day/weeks/months ahead if I don't pay
>>attention to it. Anybody got any ideas?
>
>
> This problem seems to happen quite often, especially with Dell
> machines. Usually a steady rate of loss like 10 minutes in an hour.
> And not usually an erratic effect. 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. BTW because
> Windows does it this way, any troubles with the clock *while windows is
> running* is definitely *not* the battery
>
> 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)

I have a four-month-old Dell and its clock has always been right. (It
probably helps that Windows adjusts the clock every week, but it is
right in between those times, too.)

[Please reply to newsgroup.]

Alex Nichol wrote:

> Podge wrote:
>
>
>>My clock has suddenly started to run very fast at times.
>>Suddenly it will be day/weeks/months ahead if I don't pay
>>attention to it. Anybody got any ideas?
>
>
> This problem seems to happen quite often, especially with Dell
> machines. Usually a steady rate of loss like 10 minutes in an hour.
> And not usually an erratic effect. 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. BTW because
> Windows does it this way, any troubles with the clock *while windows is
> running* is definitely *not* the battery
>
> 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)

I have a four-month-old Dell and its clock has always been right. (It
probably helps that Windows adjusts the clock every week, but it is
right in between those times, too.)

[Please reply to newsgroup.]

Alex Nichol wrote:

> Podge wrote:
>
>
>>My clock has suddenly started to run very fast at times.
>>Suddenly it will be day/weeks/months ahead if I don't pay
>>attention to it. Anybody got any ideas?
>
>
> This problem seems to happen quite often, especially with Dell
> machines. Usually a steady rate of loss like 10 minutes in an hour.
> And not usually an erratic effect. 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. BTW because
> Windows does it this way, any troubles with the clock *while windows is
> running* is definitely *not* the battery
>
> 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)

I have a four-month-old Dell and its clock has always been right. (It
probably helps that Windows adjusts the clock every week, but it is
right in between those times, too.)

[Please reply to newsgroup.]

Alex Nichol wrote:

> Podge wrote:
>
>
>>My clock has suddenly started to run very fast at times.
>>Suddenly it will be day/weeks/months ahead if I don't pay
>>attention to it. Anybody got any ideas?
>
>
> This problem seems to happen quite often, especially with Dell
> machines. Usually a steady rate of loss like 10 minutes in an hour.
> And not usually an erratic effect. 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. BTW because
> Windows does it this way, any troubles with the clock *while windows is
> running* is definitely *not* the battery
>
> 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)

I have a four-month-old Dell and its clock has always been right. (It
probably helps that Windows adjusts the clock every week, but it is
right in between those times, too.)

[Please reply to newsgroup.]

Alex Nichol wrote:

> Podge wrote:
>
>
>>My clock has suddenly started to run very fast at times.
>>Suddenly it will be day/weeks/months ahead if I don't pay
>>attention to it. Anybody got any ideas?
>
>
> This problem seems to happen quite often, especially with Dell
> machines. Usually a steady rate of loss like 10 minutes in an hour.
> And not usually an erratic effect. 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. BTW because
> Windows does it this way, any troubles with the clock *while windows is
> running* is definitely *not* the battery
>
> 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)

I have a four-month-old Dell and its clock has always been right. (It
probably helps that Windows adjusts the clock every week, but it is
right in between those times, too.)

[Please reply to newsgroup.]

Alex Nichol wrote:

> Podge wrote:
>
>
>>My clock has suddenly started to run very fast at times.
>>Suddenly it will be day/weeks/months ahead if I don't pay
>>attention to it. Anybody got any ideas?
>
>
> This problem seems to happen quite often, especially with Dell
> machines. Usually a steady rate of loss like 10 minutes in an hour.
> And not usually an erratic effect. 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. BTW because
> Windows does it this way, any troubles with the clock *while windows is
> running* is definitely *not* the battery
>
> 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)

I have a four-month-old Dell and its clock has always been right. (It
probably helps that Windows adjusts the clock every week, but it is
right in between those times, too.)

[Please reply to newsgroup.]

Alex Nichol wrote:

> Podge wrote:
>
>
>>My clock has suddenly started to run very fast at times.
>>Suddenly it will be day/weeks/months ahead if I don't pay
>>attention to it. Anybody got any ideas?
>
>
> This problem seems to happen quite often, especially with Dell
> machines. Usually a steady rate of loss like 10 minutes in an hour.
> And not usually an erratic effect. 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. BTW because
> Windows does it this way, any troubles with the clock *while windows is
> running* is definitely *not* the battery
>
> 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)

I have a four-month-old Dell and its clock has always been right. (It
probably helps that Windows adjusts the clock every week, but it is
right in between those times, too.)

[Please reply to newsgroup.]

Alex Nichol wrote:

> Podge wrote:
>
>
>>My clock has suddenly started to run very fast at times.
>>Suddenly it will be day/weeks/months ahead if I don't pay
>>attention to it. Anybody got any ideas?
>
>
> This problem seems to happen quite often, especially with Dell
> machines. Usually a steady rate of loss like 10 minutes in an hour.
> And not usually an erratic effect. 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. BTW because
> Windows does it this way, any troubles with the clock *while windows is
> running* is definitely *not* the battery
>
> 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)

I have a four-month-old Dell and its clock has always been right. (It
probably helps that Windows adjusts the clock every week, but it is
right in between those times, too.)

[Please reply to newsgroup.]

Alex Nichol wrote:

> Podge wrote:
>
>
>>My clock has suddenly started to run very fast at times.
>>Suddenly it will be day/weeks/months ahead if I don't pay
>>attention to it. Anybody got any ideas?
>
>
> This problem seems to happen quite often, especially with Dell
> machines. Usually a steady rate of loss like 10 minutes in an hour.
> And not usually an erratic effect. 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. BTW because
> Windows does it this way, any troubles with the clock *while windows is
> running* is definitely *not* the battery
>
> 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)

I have a four-month-old Dell and its clock has always been right. (It
probably helps that Windows adjusts the clock every week, but it is
right in between those times, too.)