May have solved problem, but...

[ojosbrujos7]

Hey guys. I've posted some threads here in the past few days about my computer freezing. First I didn't know what it was, but figured out it was a W32Time error in the system event checker, which I fixed, but then it continued to freeze consistently, logging something called a Netlogon error. I then opened up the computer itself and cleaned it out, cleaned the fan, and put a smaller fan on it, and it's been doing great since then. The only time it freezes is when it's left alone for a long period of time. But my question for whoever is, what can I do to keep it from freezing at all? I seem to have solved the problem, so why is it still overheating? And is it really a netlogon error or is it just registering that because it doesn't know what else to call an overheating problem?

Thanks.

[AnnMarie]

Hi ojosbrujos7. Open Event Viewer again and find the latest Netlogon error. Doubleclick on it and post back exactly what you see please.

[ojosbrujos7]

Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5719
Date: 12/23/2006
Time: 2:22:30 AM
User: N/A
Computer: ENGL-XP-GNEIK1
Description:
No Domain Controller is available for domain ADS due to the following:
There are currently no logon servers available to service the logon request. .
Make sure that the computer is connected to the network and try again. If the problem persists, please contact your domain administrator.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 5e 00 00 c0 ^..À

[AnnMarie]

Hi ojosbrujos7, because your computer is still freezing, I suspect the problem may be caused by your network adaptor. This is not my area of expertise so I am transferring your topic to the Hardware Forum for more help.

[ojosbrujos7]

Alright, thanks AnnMarie.

Well, if anyone can help, it'd be greatly appreciated.

I have some new information about the problem.

I went a couple days after doing the fan without it freezing, but now it seems to be doing it again, ever 10 or 15 minutes, no matter what I'm doing, even during startup.

The error log is still netlogon, as shown above.

I recently connected a Nintendo Wii to our wireless internet, which is on the same adaptor as this. Might that have anything to do with it?

[ojosbrujos7]

This morning it's been as bad as it ever was. I don't understand, since it seemed perfectly fine the last day or so.

[ojosbrujos7]

It seems like once it gets going it likes to freeze when I try to play any kind of file in Windows Media Player (9).