Update: It took a few days but it occurred again. I checked the avast! On-Access Scanner window and for "Web Shield" it reported that it last scanned
www.telegraph.co.uk had scanned 35956 and had a runtime of 3:23:39:22. I tried the "terminate" button first this time, but it did not work. The on-access scanner window appears like the provider is closed, but the process is still running in the background.
However, I did verify that I am able to use the internet again after attempting to terminate the process. While it is still running at 50/50% CPU, I am now access any site and, of course, post to this forum. One thing I will note, however, is that I am able to access computers on my local just fine even before I attempt to terminate the process. I did not try to access a web site by IP, but I can try that next time it happens. I do however typically access computers on my network via a DNS name that resolves from my router.
Since that log was talking about winsock errors, I attempted to disconnect all network devices in the Network Connections window. After doing that, the System process went back down to near 0% CPU usage. However, the ashwebsv.exe process is still using 50% of the CPU. I have a dual core machine so that is why it only uses 50%.
Update (because I don't feel like rewriting this
) -- While the System CPU is now at near 0%, my network connection seems completely dead. ((I started saving this post in a text file when I noticed this))
Update again -- TCPView is showing Ashwebsv.exe with a lot of listening connections open. all on port 12080, which is strange as I don't think it should be able to have two entries in TCPView with the same local IP and port. Here is the detail:
ashWebSv.exe:3120 TCP 127.0.0.1:12080 0.0.0.0:0 LISTENING
<<previous line repeats about 150 times>>
ashWebSv.exe:3120 TCP 127.0.0.1:12080 127.0.0.1:12720 ESTABLISHED
ashWebSv.exe:3120 TCP 127.0.0.1:12080 127.0.0.1:12722 CLOSE_WAIT
ashWebSv.exe:3120 TCP 127.0.0.1:12080 127.0.0.1:12723 CLOSE_WAIT
ashWebSv.exe:3120 TCP 127.0.0.1:12080 127.0.0.1:12721 CLOSE_WAIT
ashWebSv.exe:3120 TCP 127.0.0.1:12080 127.0.0.1:12724 CLOSE_WAIT
ashWebSv.exe:3120 TCP 127.0.0.1:12080 127.0.0.1:12726 CLOSE_WAIT
ashWebSv.exe:3120 TCP 127.0.0.1:12080 127.0.0.1:12719 CLOSE_WAIT
ashWebSv.exe:3120 TCP 127.0.0.1:12080 127.0.0.1:12735 CLOSE_WAIT
ashWebSv.exe:3120 TCP 127.0.0.1:12080 127.0.0.1:12727 CLOSE_WAIT
ashWebSv.exe:3120 TCP 127.0.0.1:12080 127.0.0.1:12728 CLOSE_WAIT
ashWebSv.exe:3120 TCP 127.0.0.1:12080 127.0.0.1:12718 CLOSE_WAIT
ashWebSv.exe:3120 TCP 127.0.0.1:12080 127.0.0.1:12733 CLOSE_WAIT
As always, the following entry is appearing quickly in the ashwebsv.ws log file:
***Server: too many winsock errors (64368). Re-listening the sockets!
***Server: accept() failed with Winsock_Error: Winsock: (10038) An operation was attempted on something that is not a socket.
The log is now at over 26000 lines. I think I might set up a 'tail -f' to cronolog to get an idea of when these entries are appearing. If they have been appearing over the last week, it may be something that has to build up over a few days to take effect.
((Edit: I did not restart my computer until after I finished the entire above post. Made a small edit to make sure it did not seem like I saw the TCPView errors after I restarted, when in-fact I saw them before I restarted.))
