Memory leak, Ndu.sys and Netio.sys problem

[Darth Persson]

Hello,

I am having problems with a huge, and constant, non paged memory pool of 6.1-6.2 GB out of 8GB memory, even directly after start-up/reboot.

I have googled for solutions and found a couple that seemed to work for most people with this problem - but nothing has worked for me.
I have Windows 10, MSI Z87-G45 motherboard with Killer Ethernet, 8GB ram.

Using poolmon.exe I can see that the problem lies with "Wfpn" (5.614.457.920 bytes) and "NDNB" (701.800.720 bytes), which seem to correspond to the drivers Ndu.sys and Netio.sys.

The three common solutions I have found on the internet are:

1) Disabling Ndu from start-up using the "sc config ndu start= disabled" command, and also changing the "Start" value to 4 in regedit in HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Ndu;

2) Updating my Killer drivers. Only the driver for Win 7 works now. When I try to install the driver for Win 10 it says the device cannot start (code 10). But with Win 7 driver at least I can connect properly to the internet;

3) Uninstalling all Killer software, and reinstalling only the drivers.

I tried all but nothing helped.

What can I do? Could buying a different network card help?

 

[Lutfij]

1| Try installing your Killer drivers in compatibility mode:
Right click installer>Properties>Compatibility tab>Windows 7/8[from drop down menu]
2| Memory leaks can happen from a corruption in OS' files. Have a go with repair install.
3| Make sure your BIOS alongside your device drivers as well as your GPU drivers up to date. Use this guide to reinstall your GPU driver.

 

[Darth Persson]

Thank you for the quick answer! I will try these suggestions as soon as I can. Concerning the driver in compatibility mode, since it's only a driver file - how do I "install" it in compatibility mode? Is it only possible if the driver comes as an installer?

 

[Darth Persson]

I never had the time to try this out, but a Win 10 update was installed during the last 24h and it seems to have solved the problem. Now for the first time since the problem occurred a few weeks back, non-paged memory pool is down to normal again at 150 MB.