Skip to content

Memory leak in Windows 8.1 with Killer E2200 and Windows Network Data Usage Monitoring

February 27, 2014

Recently upgraded to a new computer with Intel’s latest Haswell generation and Microsoft Windows 8.1. Although its performance has been stellar, a few days ago unexpectedly ran into severely degraded performance.

Saw in the Task Manager that all available memory was taken up by the Non-Paged Pool. After a system reboot the memory used by the Non-Paged Pool quickly started to increase until all memory was taken.

Looked up what information could fine online about memory leaks in Windows 8.1 and came upon this forum post in which others detailed similar experiences when using Windows 8 on hardware equipped with Qualcomm’s Killer ethernet networking products.

T_Win8_NDU_01

The actual cause of the memory leak seems to be the Windows Network Data Usage Monitoring Driver service which in combination with a Killer network driver starts to fill up the Non-Paged Pool memory.

Considering that my MSI H87-G43 Gaming motherboard is equipped with the Killer Ethernet E2200 and am using the Killer Network Manager driver, knew it had to be the same cause.

Applied the suggested fix of altering the registry key value of the “Start” entry to 4 in HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Ndu\ to disable the Windows Network Data Usage Monitor Driver from starting and after a reboot the issue seems properly solved!

40 Comments leave one →
  1. December 28, 2014 7:03 pm

    Another thing: If you’re having problems with the key not saving after restart, right click on the NDU folder, click Permissions, Advanced, then, near the top, click on the change button by owner. On the windows that comes up, type your MICROSOFT ACCOUNT EMAIL into the box (click check names if you really want to) and apply everything. Thanks for the help BTW.

  2. January 24, 2015 2:32 pm

    That worked, thanks a lot!!!!!

  3. sylvester rep permalink
    February 23, 2015 9:11 pm

    What do you have to do when you are at start from ndu? you don’t explain that

  4. February 23, 2015 10:03 pm

    @sylvester rep
    Change the value of the the registry key “Start” in HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Ndu to 4 (like in the screenshot).
    I edited the text to make it more clear.

  5. May 15, 2015 11:14 am

    I fkn love you. Been trying to fix this for ages.. thought my SSD was broken or something.

  6. SurefireMooly permalink
    May 16, 2015 6:33 am

    You are quite literally my savior right now, +1 to everything you do!

  7. May 18, 2015 8:35 pm

    thank you sooo much man !!
    i was wondering why my ram usage was at 7gb when my pc was just 2 days old lol

  8. rizkimezo permalink
    May 31, 2015 10:45 am

    Dude, I’m following the step that you mentioned. But inversely my non-paged pool memory is increasing after I disabled it ! LOL this is ridiculous. Anyone have the same problem as I am ?

  9. May 31, 2015 11:11 am

    @rizkimezo
    If you have the same symptom that your non-paged pool was increasing on Windows 8 (or 8.1) with a Qualcomm’s Killer ethernet or related networking product, then the above fix should solve it. You did reboot after changing the registry value, right?

  10. rizkimezo permalink
    May 31, 2015 5:27 pm

    I’m not quite sure whether it caused by the same problem that you have or not. Yes I did all steps that you described. this is weird haha

  11. May 31, 2015 7:15 pm

    @rizkimezo
    Another device driver could be the culprit, from what I read online, others experience similar symptoms but caused by drivers for other device drivers than Qualcomm’s Killer ethernet devices. 😦

  12. lenintoantap permalink
    July 6, 2015 1:06 pm

    wow, thank a lot. I’m amost going to reinstall windows and everyting because this problem.

  13. chase chapman permalink
    July 23, 2015 8:43 am

    mines already set to 4 and im still having this issue ive tried updating my ethernet drivers and it bugs never goes through still says im on the old version computer keeps crashing from this problem idk what to do anymore have tried everything

  14. July 26, 2015 9:19 pm

    @chase chapman
    That does sound like the driver could be the culprit then, or perhaps another device or service is filling up the non-paged memory?

  15. Lepren permalink
    August 3, 2015 12:05 am

    THANK YOU!!! I even recently updated to Windows10 and the problem carried over but after looking at your advice I think I can fix the problem now since it appears to be the same cause.

  16. August 4, 2015 3:22 pm

    I did the change owner thing so it stayed fixed after a restart and I also did the fix. But after a few days of it being fixed it suddenly jumped to %50 memory use. My non paged pool is not as high as 600mb (which used all my memory). But it is 400 on start-up and I only have 4 gigs left (%50 used). Would getting more RAM sticks fix it. I have already ordered more (to upgrade to 16 gigs) cause I want to.

  17. August 4, 2015 3:47 pm

    So I managed to get it back down. But is their a way to stop it from getting back down again? I have done the owner thing. Also I just kept redoing the fix till it worked.

  18. August 4, 2015 6:58 pm

    @Tazwin
    Could perhaps be another driver causing the non-paged memory pool to fill up or something else eating up your free RAM?

  19. August 5, 2015 1:27 am

    Ok, thanks.

  20. August 6, 2015 10:19 pm

    Also Smithy. Do you know of a way that I can find which driver is causing this problem? I have Poolmon and I have used it but I do not know how to use it.

  21. August 9, 2015 3:43 pm

    @Tazwin
    There’s DriverView from NirSoft but I don’t think it shows the actual memory consumption.
    Maybe VMMap? it’s a Windows Sysinternals application available on Microsoft technet.

  22. A lost noodle from another world permalink
    August 18, 2015 1:28 pm

    This literally saved my life bro.😀

  23. Warsplit permalink
    October 21, 2015 1:38 pm

    Thx a lot this rly helped me out, you deserve a cookie, or ten

  24. gladston permalink
    October 26, 2015 4:03 am

    Thx Thx!

  25. Bogdan permalink
    January 25, 2016 5:24 pm

    thk, really helpful !!!

  26. WIll permalink
    January 31, 2016 8:02 pm

    HOLY F*** I have had this issue for months thank you for the fix I would give you money if I saw the guy that figured this out.

  27. FilipCRO permalink
    February 10, 2016 2:47 pm

    Yep this definitely works. Had this memory leak problem on Windows 8.1 Pro x64, and now again on Windows 10 Pro x64. Disabling the ndu.sys worked. Thanks for this !

  28. Chris permalink
    February 20, 2016 5:53 pm

    Ran into this problem for the first time on Windows 10. Perhaps it’s been there before, but it’s only just now shown up after starting to use Steam in home streaming.

    I removed the Killer specific drivers and software and used Qualcomm 8161 drivers. This appeared to solve the problem, but it didn’t. However, it did dramatically reduce the problem.

    So it’s possible there are three issues:
    1. There’s a memory leak in the crummy E2200 Killer software suite.
    2. There’s a memory leak caused by the firmware… I don’t know if this is possible.
    3. The Killer NICs are shit.

    #3 is a fact.

    I’m going to give this solution a try, but I’m pretty sick of this NIC. I’ve used a lot of network cards over the years, and this is by far the worst. I’m tempted to just go out and buy an Intel card today and be done with it.

  29. February 20, 2016 7:03 pm

    @Chris
    Personally wasn’t impressed with this NIC or MSI’s H87-G43 Gaming motherboard. I’ve since switched back to Asus with an Intel NIC.

  30. February 21, 2016 10:59 pm

    @Smithy
    I have an ASRock Z87 Killer. It’s actually been a really good board. No complaints, except for the NIC. I’d definitely recommend these boards overall, but it gets harder to recommend

    My old college roommate bought an MSI board, probably similar to yours, for the 4th Gen Core processors. I remember helping him out a bit and looking at the BIOS. Typical of MSI, it was riddled with typos and spelling mistakes and had a terrible GUI. (When I used to work retail, my intro to MSI was a laptop with several spelling mistakes on the retail box and 3 spelling mistakes on the MSI sticker advertising product features/specs. The killer being these were mistakes that word spellcheck would pick up.)

    As far as I know, the board has been stable, but I don’t think it would kill MSI to hire someone with an English degree and/or someone who specializes in UX design.

    Now I’m ranting… 🙂 Thanks for the post. I’m finally getting around to trying it tonight.

  31. Lukas permalink
    February 26, 2016 12:42 pm

    THANKS ! I bought brand new MSI laptop, memory usage was at 99% after 5 minutes of doing anything on the pc, so yeah it was cause by the Killer network software. The solution presented at the top helped but not as much, so I got rid of the whole Killer Suite and installed only necessary drivers. Everything is now working just fine.

  32. richard permalink
    March 26, 2016 5:48 am

    Hiho!

    I know its an old article, but im suffering the same problem on win10 home. What i did: Deleted killer driver and app, installed driver only
    Edit that regedit value to 4. It seems something editing it back to 2 from time to time and i cant reveal what causing it.

  33. maitry permalink
    April 21, 2016 3:37 pm

    I tried above registry solution, but once it came down by that, but again nonpagedpool memory usage increased. I recently updated my all drivers, i dont know what to do

  34. Nameless Japanese permalink
    April 30, 2016 6:38 pm

    I solved the memory leak thanks to u
    ありがとう

  35. keyra permalink
    May 14, 2016 6:34 pm

    mannnnnnnnnnnnn it’s been weeks since i had this insane memory leak. i fucking love u

  36. Dustin Loftis permalink
    May 20, 2016 10:00 pm

    Shouldn’t you recommend that users look at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Ndu as ControlSet001 may not be the active copy of the registry depending on their circumstances?

  37. Tyr3al permalink
    June 7, 2016 2:36 pm

    Works for Windows 10 as well. Thank you!!!

  38. Кирилл Колесник permalink
    June 18, 2016 2:22 pm

    many thanks to you ! win 10 – okay !

  39. Johnny permalink
    July 13, 2016 1:05 pm

    This is fucking awesome, thank you !!!

  40. August 9, 2016 2:28 pm

    Seems to have done the trick, you sir are awesome. Thank you!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: