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.
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!
Read More:
- Browser performance tool
- NVIDIA NVML Driver/library version mismatch
- Linux c running error killed
- Windows 10 startup item repair an operating system wasn’t found
- Ethernet Cable vs. Telephone Cable: Which Is Your Option?
- Kvm internal error: process exited :cannot set up guest memory ‘pc.ram‘:Cannot allocate memory
- Win10 must be optimized after installation to solve 100% disk occupation
- How to disable Network Manager on Linux
- Some problems about startup
- Wireless network solution of deepin Linux network card driver (manual) installation
- Windows Realtek USB wireless network card boot failure Rtlihvs. DLL module stop problem
- Matlab shows license manager error – 103
- ARP – s in win7 (ARP binding under win7)
- [Solved] kubelet Startup Error: cannot find network namespace for the terminated container
- The solution of OpenGL not displaying normally in win7 system
- Bcdboot command line parameter options
- Error 1500. Another program is in progress. You must complete another installation before continuing with this installation.
- How to solve runtime error r6016
- Android ADB command adb devices error: protocol fault (no status)
- This error may also indicate that the docker daemon is not running.