Well after three complete wipes and reinstalls I finally figured out what was going on - sort of. Check out this post:
http://forums.techarena.in/showthread.php?t=628241 It seems that there exists a race condition with the Auto Update program where it will call svchost and ping the CPU at 100% indefinitely. There is a hotfix available: http://support.microsoft.com/kb/916089 The hotfix didn't work for me - I just disabled the AutoUpdater Service. There is a really interesting issue however that still exists - I can't play any audio files with Mediamonkey! When I hit play it just sits there. The same files play just fine in VLC. I have tried uninstalling / reinstalling several times but still nothing. Really weird. I hate windows sometimes. -- Brian On 4/25/07, Brian Weeden <[EMAIL PROTECTED]> wrote:
I just had some network problems that have started to crop up on my home LAN. The first symptom was that it would take a while (a few seconds) to resolve all host names, sometimes up to 15 seconds. The traffic itself flowed fast like a normal cable modem but every time you went to a new site it had to stop and resolve it. This happens with all 3 machines in the house (2 XP machines and 1 Macbook). The second symptom just started occurring yesterday. I use Remote Desktop to log into a second session on my HTPC (a Windows XP box). It has always functioned fine until yesterday when it kept timing out before it could connect. I could browse files and folders on the HTPC from my machine, I could connect via VNC fine, but Remote Desktop kept timing out. Finally it connected and worked fine. The third symptom is that when it can't connect via VNC, svchost.exe is running as a Network Service on my machine and using up 70-90% of the CPU time. I know svchost is one of those key OS services that runs all the time but is there anyway to pin down exactly what it is doing? At any given time there seems to be 5 or 6 instances running, a couple as SYSTEM, a couple as NETWORK SERVICE, and a couple as LOCAL SERVICE. Originally I was thinking it was Comcast's DNS servers but the problems with the Remote Desktop are inside my router and shouldn't (AFAIK) rely on Comcast. -- Brian
