svchost.exe is a wrapper for a bunch of services that are running on your system. This means that many, many system services are running under this one process. You can use task manager to look to see what is actually running. using 60% of your available memory could be a normal state of windows. It all depends on the memory used by each process under the service host.
Now that being said, any of the processes running can consume lots of memory when it hits a error condition.
for example, I have seen background file transfers take lots of memory, search indexes database using up all of the free memory when the database gets corrupted, broken windows updates the list gets long and the fix depends on which subprocess is using the extra memory.
you can try some generic fixes like:
start cmd.exe as an admin then run
sfc.exe /scannow
(this will windows files using a local backup copy, (often malware modifies the backup copy so it might not help))
dism.exe /online /cleanup-image /restorehealth
(this will repair your windows files, using a trusted source from the Microsoft update servers)
other common causes of this problem would not be fixed with the above commands.
for example, to fix the windows search indexer you would have to delete its database and recreate it.
to fix the windows update problems you would have to run the Microsoft windows update troubleshooter
or locate the actual download directory and delete it.
Other fixes just depend on the cause of the problem, bad spots on the hard drive might just require your system sleep to be turned off until the windows data integrity checking has a chance to complete. it start to run 5 minutes after the system goes idle. I would turn off the sleep functions and leave the system idle over night. The process attempts to scan your entire drive and find any cluster that has read errors, it then tries to read it over and over until it gets a good copy. At that point it moves the data to a new cluster and marks the old one as bad. The process can take days.
Microsoft has tools herer:
https://technet.microsoft.com/en-us/sysinternals/bb545021.aspx
the tool process explorer should be able to help to find out which subprocess is using excessive memory and help isolate the actual problem