[ntp:questions] Windows time question.
nomail at example.com
Thu Apr 21 13:36:46 UTC 2011
DaveB <g8kbv at uko2.co.uk> wrote:
> In article <slrniqt8ck.do1.nomail at xs8.xs4all.nl>, nomail at example.com
>> DaveB <g8kbv at uko2.co.uk> wrote:
>> > but as above, sometimes the pool server that responds seems to do
>> > something odd, and kill (or seriously destabilize) W32Time as a result.
>> > At least, looking in the system error and info logs, after recovering
>> > from a lockup, it's related to W32Time going bad, not long after first
>> > boot of the day.
>> What do you mean with "a lockup"?
>> Is your entire machine locking up? that is not normal.
>> Is the W32Time simply losing sync and declaring the timeserver as
>> unresponsive? That is normal. It is just the build quality of W32Time,
>> it seems you have to live with it.
>> (or install another time service when you don't like it)
> "Lockup" as in not even the mouse cursor moves, nor keyboard lights
> follow the shift lock buttons etc. Esentialy, something goes into a
> tight closed loop so even the BIOS doesnt get a look in, while the cpu
> cooler does a paint stripper impression!.
> I ran MEMTEST86 the other night, and Spinrite last night, neither found
> any problems with the memory or disk systems.
> After a forced shutdown and cold boot (plus hot coffee while it sorts
> itself out) if I look in the event logs, the last "event" is W32Time
> error'ing for some reason.
> Yes, it is not normal!
I think it is most likely that W32Time is not the cause.
Probably something else is going haywire (e.g. the network card) and
W32Time notices there is a problem shortly before the system crashes
More information about the questions