Random Freeze - Is this causing it?

Problem: Computer has random freezes.

When I look in Everest I see in the event log that just before every freeze
the last entry is:

W32Time 36: The time service has not been able to synchronize the system
time for 49152 seconds because none of the time providers has been able to
provide a usable time stamp. The system clock is unsynchronized. (this was
the last time it happened)
____________________________________________________________
Prior to that:
17: Time Provider NtpClient: An error occurred during DNS lookup of the
manually configured peer 'time.windows.com,0x1'. NtpClient will try the DNS
lookup again in 60 minutes. The error was: A socket operation was attempted
to an unreachable host. (0x80072751)

System Error None 2007-03-26 16:55:15 W32Time 29: The time provider
NtpClient is configured to acquire time from one or more time sources,
however none of the sources are currently accessible. No attempt to contact a
source will be made for 59 minutes. NtpClient has no source of accurate time.

System Error None 2007-03-26 17:55:15 W32Time 17: Time Provider NtpClient:
An error occurred during DNS lookup of the manually configured peer
'time.windows.com,0x1'. NtpClient will try the DNS lookup again in 120
minutes. The error was: A socket operation was attempted to an unreachable
host. (0x80072751)

System Error None 2007-03-26 17:55:15 W32Time 29: The time provider
NtpClient is configured to acquire time from one or more time sources,
however none of the sources are currently accessible. No attempt to contact a
source will be made for 119 minutes. NtpClient has no source of accurate
time.

System Warning None 2007-03-26 18:11:07 W32Time 36: The time service has not
been able to synchronize the system time for 49152 seconds because none of
the time providers has been able to provide a usable time stamp. The system
clock is unsynchronized.
___________________________________________________________

Could this be causing the lockups? If so, how do I fix it?

I could be wrong, but I don't see any connection between time synchs and your
computer freezing.

More likely is that you have bad RAM or malware infection(s) on your
computer. I would check both.

Best Wishes,
Kurosh


"nvidiaman" wrote:

> Problem: Computer has random freezes.
>
> When I look in Everest I see in the event log that just before every freeze
> the last entry is:
>
> W32Time 36: The time service has not been able to synchronize the system
> time for 49152 seconds because none of the time providers has been able to
> provide a usable time stamp. The system clock is unsynchronized. (this was
> the last time it happened)
> ____________________________________________________________
> Prior to that:
> 17: Time Provider NtpClient: An error occurred during DNS lookup of the
> manually configured peer 'time.windows.com,0x1'. NtpClient will try the DNS
> lookup again in 60 minutes. The error was: A socket operation was attempted
> to an unreachable host. (0x80072751)
>
> System Error None 2007-03-26 16:55:15 W32Time 29: The time provider
> NtpClient is configured to acquire time from one or more time sources,
> however none of the sources are currently accessible. No attempt to contact a
> source will be made for 59 minutes. NtpClient has no source of accurate time.
>
> System Error None 2007-03-26 17:55:15 W32Time 17: Time Provider NtpClient:
> An error occurred during DNS lookup of the manually configured peer
> 'time.windows.com,0x1'. NtpClient will try the DNS lookup again in 120
> minutes. The error was: A socket operation was attempted to an unreachable
> host. (0x80072751)
>
> System Error None 2007-03-26 17:55:15 W32Time 29: The time provider
> NtpClient is configured to acquire time from one or more time sources,
> however none of the sources are currently accessible. No attempt to contact a
> source will be made for 119 minutes. NtpClient has no source of accurate
> time.
>
> System Warning None 2007-03-26 18:11:07 W32Time 36: The time service has not
> been able to synchronize the system time for 49152 seconds because none of
> the time providers has been able to provide a usable time stamp. The system
> clock is unsynchronized.
> ___________________________________________________________
>
> Could this be causing the lockups? If so, how do I fix it?
>