Well, unless you don't know too much about the way Windows 2000 works, you ought to know that svchost.exe is just the Service Host program, used to run & control services. This means that various services actually "reside" within each running instance of svchost.exe.
Now, I can't really tell you why a specific instance of svchost.exe is taking up all your CPU, but you can use various tools to find out which services are being run by each svchost.exe. For Win2K, you can run tlist -s (the tlist.exe can be found in the Win2K CD-ROM in \Support\Tools\Support.cab) For WinXP use the command tasklist /svc. After you know which services are being run by the svchost.exe that's eating the CPU, you can go over each one and stop them until you find the critical one.
Last updated on 2004-02-07 14:00:00 -0700, by Shalom CraimerBack to Tech Journal