svchost.exe (netsvcs) take me 2GB memory, what's the problem? Crazy!!

Please provide more information to enable your problem to be diagnosed.

Please restart your computer and allow 20 minutes for the system to run before uploading information. When examining Event Viewer log files many, not all, problems show in the period immediately after the computer has been booted.

Please provide a copy of your System Information file. Type System Information in the Search Box above the start Button and press the ENTER key (alternative is Select Start, All Programs, Accessories, System Tools, System Information). Select File, Export and give the file a name noting where it is located. Do not place the cursor within the body of the report before exporting the file. The system creates a new System Information file each time system information is accessed. You need to allow a minute or two for the file to be fully populated before exporting a copy. Please upload the file to your OneDrive, share with everyone and post a link here. If the report is in a language other than English, please state the language.

Please upload and share with everyone a fresh copy of your System log from your Event Viewer to your One Drive and post a link here. It helps to avoid confusion if you remove any earlier copies of the log files from your OneDrive.

To access the System log select Start, Control Panel, Administrative Tools, Event Viewer, from the list in the left side of the window expand Windows Logs and select System. Place the cursor on System, select Action from the Menu and Save All Events as (the default evtx file type) and give the file a name. Do not provide filtered files. Do not place the cursor in the list of reports before selecting Action from the menu. Do not clear logs whilst you have a continuing problem.

For help with OneDrive see paragraph 9.3:

http://www.gerryscomputertips.co.uk/MicrosoftCommunity1.htm

If you have not already done so you should start by applying one of these two discussions to your system to be sure that a known problem with Windows Update has been fixed (do this first):

There are two discussions that should help:

Windows update problems?   Read this first.

and/or

Windows 7 Update Solution

If after applying those known solutions to Windows update you still have a svchost Process that is running amok here is how you can figure out which Windows Service is causing the problem.

When you see the svchost Process running in Task Manger remember that what each Process is doing is "hosting" important Windows Services underneath it.  That is why it is called svchost - it is hosting services.  That is what is says in the description column in Task Manager:

What you want to see in Task Manger with the biggest number in the CPU column is System Idle Process which is the amount of "free time" your CPU has - the more of that the better.

There might be one Windows Service running under a svchost Processes or there might be many Windows Services running under each svchost Process that you see in Task Manager.

It is normal to see several to many svchost Process running at the same time since there are sometimes lots of Windows Services that are running on your system.  Normally the svchost Processes consume very little system resources (CPU and RAM) but sometimes one of them may appear to be running amok.

Often the problem has something to do with Windows Update and some of the "solutions" you might read about involve disabling all or parts of Windows Update and that may make the symptom of the problem go away but does not actually fix the problem.  It is much better to actually fix the problem than it is to just fix the symptom of the problem.

You might also read about a "memory leak" in svchost.exe but there is no memory leak in svchost.exe.  That idea comes from folks that don't know how to troubleshoot a svchost process that is running amok.  The problem is always something going wrong with some Windows Service that is being hosted by the svchost Process.  There is no memory leak in svchost.exe.

A Problem with Windows Update has been plaguing systems for months and one of the symptoms of the problem is a svchost Process that is running amok using too much CPU and RAM, causing systems to overheat, cooling fans spinning out of control, etc.

When you see the svchost that is running amok notice the Process ID (PID) which in this case the PID is 1088 (I choose check for updates to show some activity of 14% CPU), then right click the Process and choose Go to Services:

In this example all of the Windows Services running under PID 1088 would be highlighted already:

And there is our friend Windows Update Service (wuauserv) running under PID 1088:

But you can't see from there which service is using all the CPU or how much CPU any of the Services are using.

Next click the Performance Tab and then Resource Monitor:

In Resource Monitor click the Services tab and scroll to PID 1088 and you can see all the Services under PID 1088 and also how much CPU they are using.

In this example the Windows Update Service (wuauserv) is bouncing around looking for updates using 13-16% of CPU but on a Windows Update afflicted system it would probably be using more (and BITS would be there too).  As you can see the rest of the Services running under that svchost Process PID 1088 are using zero CPU: