lock-up after dialing-up

[Guest]

When we dial-up our internet connection we cannot open ANY programms. When
I look on task manager (which has to be started before connecting) the
programms show up on the "processes" tab, but never make it over to the
"applications" tab. This makes it impossible to properly reset the machine as
logonui.exe has to run to shut down windows. So when it locks we have to hit
the reset button (I still live in fear of the Blue Screen of Death days).

Running "netsh winsock reset" and resetting the machine a couple of times
will help to get things running correctly, but only once. This is an
unacceptable work around as we have multiple people in the house connecting
at various times during the day. If someone connects and disconnects, we
must go through this process again.

I have ran the xpnetdiag.exe (again started before connecting) when it is
locked up and it reports that it cannot find a network adapter. This kind of
goes along with the strange glitch of IE or OE telling me that I am not
connected to the internet and would I like to connect now. When I answer
yes, it will sometimes work.

I have ran multiple virus scans with nothing bad popping up.

There is a svchost.exe with a PID of 880 that has a lot of activity
immediately after connection. I forget how, but I traced that back to the
Remote Procedure Call service. This service, it seems, is depended on by
everyother service. If I terminate that svchost, all the frozen programms
that I had attempted to run pop up. But everything gets kind of screwy and I
end up resetting any way. (Yes, I know its bad to terminate services this
way!)

If the machine is locked up, even if I disconnect, it stays in this state.

 

[Patrick Keenan]

When we dial-up our internet connection we cannot open ANY programms. When
I look on task manager (which has to be started before connecting) the
programms show up on the "processes" tab, but never make it over to the
"applications" tab. This makes it impossible to properly reset the machine as
logonui.exe has to run to shut down windows. So when it locks we have to hit
the reset button (I still live in fear of the Blue Screen of Death days).

Running "netsh winsock reset" and resetting the machine a couple of times
will help to get things running correctly, but only once. This is an
unacceptable work around as we have multiple people in the house connecting
at various times during the day. If someone connects and disconnects, we
must go through this process again.

I have ran the xpnetdiag.exe (again started before connecting) when it is
locked up and it reports that it cannot find a network adapter. This kind of
goes along with the strange glitch of IE or OE telling me that I am not
connected to the internet and would I like to connect now. When I answer
yes, it will sometimes work.

I have ran multiple virus scans with nothing bad popping up.

There is a svchost.exe with a PID of 880 that has a lot of activity
immediately after connection. I forget how, but I traced that back to the
Remote Procedure Call service. This service, it seems, is depended on by
everyother service. If I terminate that svchost, all the frozen programms
that I had attempted to run pop up. But everything gets kind of screwy and I
end up resetting any way. (Yes, I know its bad to terminate services this
way!)

If the machine is locked up, even if I disconnect, it stays in this state.

Task Manager won't tell you what's actually using svchost. Get Process
Explorer, which *can* show you the processes in question, and run it first,
and select Show Process Tree. Arrange the windows so you can see the CPU
load column. This should give you another clue.

http://www.sysinternals.com/Utilities/ProcessExplorer.html

HTH
-pk

 

[Guest]

wauclt.exe (a.k.a. Windows Auto Update) showed up under the svchost right
after I connected and then everything locked up. I killed the wauclt.exe
process and about 30 seconds later it popped up again and everything began to
work. Also, there was a WMI service that opened in a different svchost when
the I connected also.

So is Windows Auto Update locking up my system? I tried turning it off
before but, it didn't help.