Generic Host Process for Win32 Service has to close

[Robin]

I found several viruses and deleted them all. Scanned my
computer several times with different software and nothing
is being detected anymore, however I keep getting the
above error message and when I check the contents of the
error report I see this:
signature
szAppName : svchost.exe szAppVer : 5.1.2600.0
szModName : unknown
szModVer : 0.0.0.0 offset : 00000000

and
technical info:
C:\DOCUME~1\ROBINB~1\LOCALS~1\Temp\WER1EF.tmp.dir00
\svchost.exe.mdmp
C:\DOCUME~1\ROBINB~1\LOCALS~1\Temp\WER1EF.tmp.dir00
\appcompat.txt

When I send the error report I am sent to the wormblaster
page, saying I may be infected. Any suggestions?

By the way none of my programs close when this happens but
I am having trouble with iexplorer

 

[Mary Sauer]

Do you have anti-virus software? If so, go to the manufacturer's web site and do a
virus scan. You will know for sure what virus you are dealing with and how to get rid
of it. If you are being directed to the wormblaster page then obviously you need to
use the removal tool.

 

[Robin]

Yes as I said, I have antivirus software, I also found a
couple of great online scanners and all say I have no more
viruses or worms. That's why I am confused as to why I
keep getting the error messages. I also have a firewall
on my system, so anything I did have was taken care of
already by the antivirus software.

Thanks for the reply though.

-----Original Message-----
Do you have anti-virus software? If so, go to the

manufacturer's web site and do a

virus scan. You will know for sure what virus you are

dealing with and how to get rid

 

[Guest]

I started getting the same error message this morning. I was trying to setup a home network...had a problem and rebooted and now this message keeps coming up. Also the system is much slower now for some reason. I'll run the virus thing on it and see if that works.

 

[Guest]

I had the same Generic host process error for win32, I read all the boards and finally saw an entry about a problem with a visioneer scanner causing the problem, I unhooked my scanner and the problem seems to be solved. No more error messages.