PDA

View Full Version : tcpsvcs.exe at 100%


WindBlade
October 30th, 2003, 09:35 AM
Hi! After installing the latest version of NOD2.0 and rebooting my computer, my comp seem very sluggish. Looking at the processes, I discover that tcpsvcs.exe is running at 100% CPU load. Only when I disable Simple TCP/IP Services did the problem go away. I tried disablign other TCP/IP related services like TCP/IP NetBIOS Helper IPv6 Helper services but the problem still remain.

Looking at the isntallation log, NOD32 2.o seem to install Winsock 2.0 Non-IFS Service Provider Support Environment (W32IFSL.sys) into the system and I suspect that is causing the error?

Please look into he problem
Thanks
:)

Marcos
October 31st, 2003, 02:42 AM
Hello,

I recommend that you contact NOD32 support at support@nod32.com and provide more detailed information, such as what operating system you use, what service packs you have installed, information about your NOD32 (CC - NOD32 System Tools - Information), or other special programs you might have installed. Also, please let the support know if turning IMON off solves the problem.

WindBlade
October 31st, 2003, 11:10 AM
I am using Windows XP with all the latest service packs and update rollups... ..
No special programs except microsoft IPv6 installed...
turning off IMON does not solve hte problem..

Mikael Hakman
December 5th, 2003, 07:12 AM
I have the same problem after upgrading to NOD32 ver 2 on W2K Professional with all MS updates and fixes installed. Task Manager shows tcpsvcs 50% CPU and svchost 50%. DHCP does not work. W2K ipconfig /renew says:

"The following error occurred when renewing adapter Local Area Connection: An operation was attempted on something that is not a socket."

Disabling AMON and IMON doesn't help. Uninstalling NOD32 does.

Thanks/Mikael :(

Marcos
December 5th, 2003, 11:35 AM
Hi all,
a new program component update is going to be released on Monday, so I suggest that you give it a try first. If no avail, let us know either on this forum, or send a message to support.

Just to make sure, did you turn off IMON by clicking the Stop button and restarted the computer? (the same goes for AMON)

rumpstah
December 5th, 2003, 11:32 PM
I would first try running the winsockfix. A program could have either through its installation or uninstallation process corrupted the TCP/IP settings in the registry.

http://members.shaw.ca/techcd/VB_Projects/WinsockFix.zip

WindBlade
December 7th, 2003, 02:28 AM
Yeap! I STOPPED both AMONa nd IMON.. and restarted my comp thereafter..
buit seems to be no help...
I did a installation log of NOD32 and HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\Protocol_Catalog9\Catalog_Entries seems to be the problem..
what do you think?

waiting for the monday update..
:)

???
December 28th, 2004, 06:15 PM
Do you really need simple TCP/IP Services?
Look at this:

http://hardware.mcse.ms/archive91-2004-8-53029.html

On type "problem tpcsvsc" into google.

puff-m-d
December 28th, 2004, 06:23 PM
-{ Quote: "I would first try running the winsockfix. A program could have either through its installation or uninstallation process corrupted the TCP/IP settings in the registry.

http://members.shaw.ca/techcd/VB_Projects/WinsockFix.zip" }-I would again suggest you run this fix. It have solved several similar problems with NOD32. After running the fix, you may have to reactivate IMON through your contol panel....

Merlinox
January 9th, 2005, 08:39 AM
I use Win XP sp2.
I remove it from automatic services.
I read in other site it isn't important.

http://hardware.mcse.ms/archive91-2004-8-53029.html

The Kid
January 16th, 2005, 09:26 PM
I found the fix to your problem should say ours here's the link
h**p://www.spychecker.com/program/winsockxpfix.html
copy&paste

good luck

Gauthreau
January 16th, 2005, 09:39 PM
Others have had this problem as well. From what I've read - I've never experienced the problem - you can set IMON to exclude tcpsvcs.exe via - IMON >Setup>MiscellaneousTab>Exclusion>Edit and see if that does the trick for you.

Others may be able to make recommendations as to possible security risks by doing so. I am not familiar with them.


Neil