When a svchost Process seems to be running amok the usual problem is some affliction with Windows Update. Sometimes it could be malicious software that is running under one of the svchost Processes because the malware hides in places it knows you are unlikely
to "see" it unless you know where to look.
Folks try all kinds of things to "fix" the problem such as renaming important Windows files, disabling important Windows Services, etc. but that does not fix the real problem. Such actions fix the symptom of the problem and leave your system in a sometimes
crippled or vulnerable condition.
The right course of action is to fix the problem and not try to fix the symptoms of the problem.
If you have been tampering with things like the BITS or Windows Update Services you should undo that tampering and work on fixing the real problem.
Windows Update has been afflicted for many months but there is a solution that is proving to be successful in fixing the WU problems and that discussion is found in this link:
Windows Update Problems? Read this first.
There are really two important updates that need to be applied to your system and then you will need to undo any of the other adjustments you might have made - like if you have disabled the BITS or Windows Update Service, you need to undo those adjustments.
Normally the svchost Processes should be showing very little activity unless the Services they are hosting are legitimately doing something important (Windows Update or backup, etc.)... then the svchost Processe should go back to showing very little activity.
If a svchost Process is running amok it make more sense to find a fix the real problem instead of fixing the symptoms.