Author Topic: svchosts in XP and mobile Radeon (Read 304 times)

clerick · « **on:** October 26, 2007, 10:02:56 AM »

I have been trying to streamline my system to try and squeeze every last FPS improvement i can out of it. I CTRL+ALT+DEL to see what processes were running and i noticed hat there are a lot more svchosts, some as big as 26meg, running. What exactly are they and is there a way to limit or stop them?

Also, I'm playing on my laptop through a full size monitor and am wondering which of the Omega drivers will work best for a mobile 9600/9700.

JB73 · « **Reply #1 on:** October 26, 2007, 10:23:05 AM »

http://support.microsoft.com/kb/314056

hope that helps a bit, svchost is one of those M$ things you can't really mess with.

Irwink! · « **Reply #2 on:** October 26, 2007, 01:51:06 PM »

Like the knowledge base article says, they're system services. You can still often kill some of them depending on what they are. For instance - print spool, secondary logon, etc. With XP you can construct a different hardware profile to boot with that at boot will only load the services that you choose. When you are about to play AH you could boot with the alternate profile and other times boot with the normal profile. You can also just go in to services and kill them one at a time but that gets old having to do that repeatedly. A utility called FS autostart I believe facilitates this but I never used it. I think a lot of people here do though.

M36 · « **Reply #3 on:** October 28, 2007, 06:24:03 PM »

My antivirus software picked up a "svchost" as a trojan horse I believe. And I have seen a few more also. Just a thought.

JB73 · « **Reply #4 on:** October 29, 2007, 10:29:25 AM »

Quote

Originally posted by M36
My antivirus software picked up a "svchost" as a trojan horse I believe. And I have seen a few more also. Just a thought.

you might want to look into that...

read the link I posted to "svchost" is a legitimate Microsoft Windows process.

there are other process named similar "scvhost" "svchosts" and other variations that look close but aren't that viruses and trojans hide behind. you have to pay real close attention to the file name, where it is running, and a lot of other factors. a great example is "logon.exe" vs "login.exe" one is legit, the other a virus, but that one has been known for a decade now.