In case it helps...
If the original problem = "...Yes it's very slow & CPU goes up to %100 svchost.exe services.exe run up to 30 to 60% CPU..." check out: http://www.howtogeek.com/howto/windows-vista/what-is-svchostexe-and-why-is-it-running/ . It applies regardless the Windows version you're running -- it's just maybe easier in win7/8, harder in XP because of the info available in Task Mgr... Note that in win7, Task Mgr.'s View menu -> Select Columns lets you display the full path to the file for each running process, making it tons more useful.
If/when a problem shows up when you run one or more apps, Sysinternals Process Explorer gives you loads of info, selecting Firefox for example, right click -> Properties. One example: Win7's Media Center was giving me all sorts of high CPU usage etc., & a quick look in Task Mgr showed the receiver service as the culprit. Fired up Process Explorer, checked the properties for that exe file, went to the Threads tab, & I could see the LAV Filters popping up & dying repeatedly in the thread list. Closed Process Explorer, Media Center, that service through Task Mgr. 1st, then using Admin Tools -> Services [works better for me closing it via that 2-step], renamed the folder for the LAV Filters, fired up Media Center, problem solved [actually turns out it was just that version of the LAV Filters, but that's another short story].
Note that finding info on any individual file/file name is a bit hit or miss on-line -- there are loads of sites that insert the name you searched for into standard, boilerplate text, presenting you with a generated web site with little if any real value. If/when I'm trying to find something out about a file I'll try Google/Bing, but I mainly look for hits from sites like MSDN or referencing a software company. If I have a copy of that file [search your hard drive(s)] if the file's properties don't show much, Nirsoft has a couple of utilities that may give more info, like at least a company name. Where it shows up, assuming it does show up when you search your drives, can tell you something -- hidserv.dll for example shows up on this rig under Windows\WinSxS [among other places], which tells me it's something installed by apps/drivers rather than coming with Windows. Using Find in Sysinternals' Process Explorer leads me to an instance of svchost.exe, which also shows my pen & tablet drivers as well as Windows 7 Pen & Touch Interface Component. Right click that svchost instance, selecting properties, & Process Explorer shows me all sorts of info, including network activity (none). If OTOH I don't have a copy of a file anywhere on my drives, if a device or app isn't working I'll look at their setup files, expanding them with Universal Extractor to see what's included. I can also open/mount Paragon backup images & take a look there, copying/extracting files as needed if one a file has for some reason gone missing.
------------
Separately, If you suspect malware the worst stuff can hide pretty well & disable your anti-malware software too. The way some of that stuff works is to insert code in or on the 1st hard drive track -- the track that contains info to make the disk bootable -- & that code tells Windows not to recognize or even see certain files... if Windows can't see whatever files then no anti-virus software can either. This malware also disables AV software, opening the door for lesser malware infections -- in fact some of this malware even looks for & disables lesser malware so it doesn't tip you off with more obvious symptoms, so you don't go looking for the source of those problems & possibly stumble on, find the heavy duty malware too. While certain of the malware files may be made invisible to Windows, something still has to be inserted in Windows to start/run those files -- that portion of the malware is often disguised as a driver or service. Some anti-virus software companies have boot disc apps that scan drives without running Windows or anything else off the hard drive, trying to match files stored on that drive to known malware file patterns or signatures. You can also boot to a WinPE-type disc/USB stick & run AV software scans using AV apps that were installed to that WinPE-type mini-OS, &/or use portable &/or on-line AV software to scan your drives. Kaspersky has their TDSSKiller available for free download, & it's supposed to find just this sort of malware while you're running Windows.
Still, it can be Very difficult to find & more difficult to remove. You can read about ways people, often experts have found & overcome malware by following links & browsing the forums at the Sysinternals site at microsoft.com. Personally I've always recommended using one of Paragon's backup apps to back up that first disk track, regardless whether you use Paragon's software to create disc images or not -- that way if something infects that 1st track you can very easily boot to a CD/USB stick & restore it, & since that 1st track rarely changes [usually only when you add an OS], that 1st track backup can be useful for a very long time... it's well worth the time & effort to create it.
--------------
RE: Files not found...
Happens... In a typical Windows install software adds entries in the registry to start whatever, & later when you uninstall that software, &/or when that software is updated, files may be removed but the registry entries are left in place. Since the files aren't there they can't start anyway, so in this situation the only downside is they can add up to create registry bloat, making the registry larger than it has to be. More serious, at least potentially, are left over drivers... Drivers are a special kind of software that lets an app or apps talk to your hardware. And drivers are more prone to cause crashes & BSODs than anything else. Worse, they can be difficult, sometimes even impossible to remove/uninstall -- that's why I'm hesitant to recommend Sysinternals' Autoruns unless you know how to & can restore an ERUNT registry backup when Windows won't start... clearing the wrong checkbox in Autoruns can break Windows *Permanently* otherwise, making a [Repair?] re-install necessary. Unless a driver has an uninstall shortcut &/or entry in Add/Remove Programs -or- Programs and Features [xp/win7], either leave it alone or make sure you can restore the registry & then uncheck it in Autoruns. There are driver removal apps that use their own records of what should be removed from the hard drive & in the registry, though they're usually only available for certain driver set ups, & can be far from perfect -- again make sure you can put things back if Windows won't start.
That said, [un]installing less well written apps may remove drivers or other files that you need, malware may remove/rename them, crashes can damage files etc. If Windows will run & the missing/damaged files are for a driver, re-install the driver -- if they're for an app, reinstall that. If Windows won't run, restore a backup, try replacing the files with a copy/paste after booting to a CD/USB stick, or try a Windows Repair Install. The most common examples I've seen are poorly written VB [Visual Basic] apps... VB apps use a common runtime -- rather than being completely self contained, they rely on & use other files that are commonly shared by all the VB apps you've installed. Sometimes uninstalling an app will remove shared files -- with VB common/shared files are often relocated from the system folder to the program's folder, so when you remove the app you remove the shared file(s). If/when that happens & you have other VB software that won't run, [re]install the VB runtime [downloadable from microsoft.com], or find the pre-existing copy of the shared file(s) in the system folder & register them with Windows [Google/Bing for directions], or add what you need to the system folder & register that file or files.
Now, Files Not Found in Autoruns...
Autoruns lists the results of all sorts of registry entries, showing you what apps, files, drivers, services etc. start with Windows, & it also shows you the file name & its location for every item in its list. If the file name listed in the registry can't be found where that registry entry says it should be, Autoruns tells you the file's not found. Every item/line Autoruns lists has a checkbox next to it -- clearing that checkbox moves the referenced registry entry into a "AutorunsDisabled" sub-key -- checking the box moves the entry back to where it used to be. Clearing a checkbox in Autoruns then is best used as a temporary, maybe a diagnostic step. If Autoruns reports a file's not found, *& you don't need that file*, [after backup] find every reference to that file in the registry & delete those references, & possibly the entire keys holding those references -- by adding a sub-key, clearing a checkbox in Autoruns makes the registry a tiny bit bigger [that adds up if you clear enough checkboxes], & if/when a key has several lines, removing just the line with the file name leaves a lot of garbage untouched [good luck finding those keys to delete them later since without the file name you can't easily search for them]. Getting rid of the useless registry entry also eliminates that line in Autoruns, making its list smaller, keeping it as manageable as possible. Autoruns doesn't look at, represent the entire registry either -- that's not its job. For files that do exist, unchecking the box in Autoruns may or may not work -- if the file is critical, you may have just broken one or more apps or Windows, Plus, files are often referenced at more than one place in the registry. Drivers & other files are often started in a couple of places, & mentioned in a couple/few more, but Autoruns will often show you just 1, single entry -- clearing that checkbox may not disable that file, or it may break the way that file works rather than totally disabling it.
So... in practice unchecking the box in Autoruns for an app that's set to autostart with Windows, is one way to keep that app from starting, but it may not be the only or best or fastest way to do that. If the file's started in the registry run keys, via the Start Menu, or listed in Admin Tools -> Services, removing them there can be faster, take less time than waiting for Autoruns to build its lists -- e.g. I've set favorites in regedit for the Run keys, & you can right-click -> delete an entry in a blink of an eye. You can try disabling a driver or other file(s) in Autoruns by clearing the box, but if it kills Windows you have to reboot into something else to restore a registry backup, & as above, clearing the box may not actually disable that file -- if you can re-name the file by sticking a "_" at the front of the file's name, & Windows won't start, it's a slight bit easier to boot into something else & rename the file back as it was [the "_" just puts it at the top of the list in Windows' Explorer so it's quicker to find]. If after renaming a file & rebooting everything works OK, then you can delete the file & registry entries referencing it. Once thing I've found handy in Autoruns, If you want to get rid of the registry entries for a driver file, right click that line in Autoruns to jump to that entry in the registry with Regedit, *then search for additional keys/values* with the same name [& separately the file name], deleting those.
----------
RE: Monitoring apps...
I often have Task Mgr. running, minimized to the Taskbar, but I mainly use it if it seems a download's stalled [check the networking tab], or if something like a setup or copy is taking too long, I'll look to see if my AV software is causing the delay. If I'm rendering video or something taking a bit of horsepower, or reading/writing a lot to an external drive, I'll fire up HWMonitor & check temps from time to time -- to me it's like keeping an eye on the gauges in your car rather than waiting for the idiot light... the main reason is that if something breaks I might catch it earlier so there's less damage, but it also allows me to spot troublesome trends, like a fan starting to go bad causing higher load temps.
Beyond my McAfee AV software suite I don't constantly run anything to monitor changes, like an addition to the registry run keys, because that only happens in 2 cases, if I'm adding/updating software or if there's malware involved. If I'm adding software I'm certainly aware of it, & in the case of malware, I trust my AV software & figure I'll deal with any infection it misses if/when it happens... the odds are greater my AV stuff will catch whatever, so that's the model I use as the basis for how I work. I go with the odds. Some people might consider that a bit silly, but you don't [or shouldn't anyway] buy a house for 10x what you can afford based on the hope you'll win the lottery tomorrow -- you go with the odds & don't spend the lottery winnings until you have them. My wife & I take reasonable precautions like backing up & being careful what we download &/or open, but anything beyond that [going against the odds] I consider impractical. When the kids were young I severely limited what they could do, then as they got older gave them the old PC(s) when we upgraded -- I'd help out when/if they needed it, & kept an eye on what they used the PC(s) for, but for the most part if they broke it they fixed it. They learned about consequences & that taught them to be responsible.
