If you moved around (large) files across the network prior to this happening then you're at the right address.
The first part of this post is an explanation on how to diagnose this problem and test it yourself but if you just want the solution then you can skip to the end and change the registry entry. Nothing else is needed if you're certain this applies to you.
The diagnosis
The first thing to do is verify this, ofcourse. You can do this by installing poolmon through the Windows Developer Kit.
After installing this, go to C:\Program Files (x86)\Windows Kits\8.1\Tools\x64
(change it to 8.0 or x86 if that applies in your case) and start poolmon.exe
.
Next, press P to sort by pool type and B to sort by amount of bytes.
You will now see a screen resembling this:
You can see that the big issue here is the entry with tag Wfpn
. If you have this as well then you're at the right post.
The next step is to find out what driver this is related to.
Open the command prompt (cmd.exe
) and navigate to the drivers folder with
cd c:\windows\System32\Drivers
and locate the appropriate driver:
findstr /s Wfpn *.*
This should give you something like this:
We can now see that netio.sys
is the culprit. After a quick google I came across a thread that discusses (and solves) this problem.
A user diagnosed this problem by booting in safe mode and recognizing that the issue was now solved. This meant that the problem was located in a driver that wasn't loaded. Using elimination it came to light that the Ndu.sys
driver caused this problem.
The solution
You can disable the driver by starting the registry editor (regedit.exe
) and navigating to
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Ndu
and changing the value of "Start" to "4", which will disable it.
Restart the computer and everything should work fine now (I just transferred 10GB worth of files throughout the network at 10MB/s and my memory usage didn't go beyond 35%).
This post is an accumulated answer from a few sources: