SVCHOST.exe using a lot of memory

  • Thread starter Thread starter smicale
  • Start date Start date
S

smicale

I am seeing a SVCHOST.exe using a about 116,360K of memory on my Vista
machine. I have ran all my ONECare antivirus/spyware tools and nothing is
coming up as a problem. I see that the Super Fetch service seems to be the
one that is hogging all this memory. When I stop that service it releases
the memory. Is this normal? What can I do to fix it? Thanks!
 
I am seeing a SVCHOST.exe using a about 116,360K of memory on my Vista
machine. I have ran all my ONECare antivirus/spyware tools and nothing is
coming up as a problem. I see that the Super Fetch service seems to be the
one that is hogging all this memory. When I stop that service it releases
the memory. Is this normal? What can I do to fix it? Thanks!
Click to expand...

There is nothing abnormal about all the SVCHOST entries you see.

Stopping any service that is running will release some memory. The
trick is to figure out which ones you need and which ones you don't
need.

You can look at Startup in MSCONFIG and disable those items one at a
time (and reboot) to see if you need all of them. And there is more:

http://www.blackviper.com/WinVista/servicecfg.htm

http://www.blackviper.com/WinVista/supertweaks.htm

Proceed with caution.
 
It appears the problem is with the SysMan service. Does this service need to
be running?
 
sysman is not a process running on my machine, it is a service. Do you think
this is still mailware or a virus?
 
smicale said:
sysman is not a process running on my machine, it is a service. Do you
think this is still mailware or a virus?
Click to expand...

A process is the same as a service so Sysman is most definitely running on
your machine. I cannot see your computer from here so I cannot guess
whether you have malware. That's why I gave you the link to malware removal
steps. If you haven't gone through the thorough steps, you have no way of
knowing whether your machine is clean. I suspect it isn't, but that's only
an educated guess based on many years of working on Windows machines.

Standard disclaimer: I can't see and test your computer myself, so these are
just suggestions based on many years of being a professional computer tech;
suggestions based on what you've written. You should not take my
suggestions as a definitive diagnosis. If you can't do the work yourself
(and there is no shame in admitting this isn't your cup of tea), take the
machine to a professional computer repair shop (not your local equivalent
of BigComputerStore/GeekSquad). If possible, have all your data backed up
before you take the machine into a shop.

Malke
 
Back
Top