SVCHOST.EXE(netsvc) taking up all memory on a freshly formatted system

Hello everyone. Long time lurker, first time poster. I have ran into a problem and would like to ask for some help.

I help around my office when computers go bad, and diagnose and fix. But this one has me stumped.

A lady needed some help yesterday with a very slow and laggy computer (it was literally 30 seconds behind on anything you tried to do). Well, I opened up task manager and the memory usage was 100%. The cpu usage was normal. I see that the svchost.exe (netsvc) is the culprit, but couldn't figure out how to get it to stop. We are really busy, so my boss just said give her a different computer and format that one and put all of our software back on it.

Well this morning I formatted, installed Windows 7 and stepped away to lunch. When I returned, it was exactly the same. On the desktop of a fresh format, nothing installed, the memory usage is 100% with the same exact culprit.

Could this be a hardware issue of any sort? I did a memory scan and it said it was ok. This is a Dell tower with built in NIC. Could it be going out? I wouldn't think so since the internet works fine (just very unusable due to slowness).

Any help would be greatly appreciated it. If any more info is needed I will be glad to give whatever is need. Thank you all!

See this post http://www.sevenforums.com/general-...vcs-draining-all-my-memory-2.html#post3072022, some steps may be detailed in earlier posts. Looks a bit complicated.

Thanks for the link. I did see that earlier but since I haven't downloaded any updates I didn't think it would work for me.

Also, I'm not sure if it provides any help. But if you unplug the ethernet cable, it runs fine. But literally as soon as it gets an internet connection memory usage goes to 80, 90, 100%.

Sorry to bump my own post. But this thing is still whooping me.

Okay I fixed the problem on my home based machine but for office based machines configured to use a WSUS server take a look at the following:

Strange behavior of Updates during recent installs

It looks like MS has provided a fix: KB3050265 - take a look at: https://support.microsoft.com/en-us/kb/3050265