Memory Problem

The size of the Nonpaged Pool depends on many factors but will typically be less then the Paged Pool. The big problem with a large Nonpaged pool is that it is, as the name implies, non pageable. Almost all other memory can be paged out at the discretion of the memory manager but the Nonpaged pool must remain in RAM at all times no matter what the memory pressure may be.

There is no way to compensate for this. The problem must be solved at it's source.

Adding more memory would only buy some time but wouldn't solve anything.

Thanks for the new responses everyone. Here is an update, I did the following;

- Uninstalled the Killer Network Drivers
- Uninstalled Killer Network Suite

After I uninstalled the Killer Network Suite my system had asked me to reboot. So I did, when it started up the drivers were back. I never had to install the 'driver only' version which I did download.

At first, I thought it was strange but I did check my memory usage and I'm down to 201mb of Non-Paged Pool & about 2gb In use while in idle. Yet now I have 2.9gb of Cached memory? I did create a restore point before uninstalling any driver, would this have impacted that in anyway?

I'll monitor the Non-Paged for another day or so and post an update.




Thanks again.

Hello Steve,

It looks like you are in great shape now with your memory, the cached figure looks normal and nothing to be worried about. Can you identify which driver was installed, I would expect it was Microsoft choosing from its own database.


Hope it continues to work well.

At first, I thought it was strange but I did check my memory usage and I'm down to 201mb of Non-Paged Pool & about 2gb In use while in idle. Yet now I have 2.9gb of Cached memory?

Only 2.9 GB of cached memory on a system with 16 GB RAM? I would like to see it much higher than that. But with a light load the system will not be able to make full use of that much memory.

A high value for cached memory is a good thing. It was low before because it was being crowded out by the Nonpaged Pool. This memory is available for use by any process and is not in any way reserved.

Quick update;

The system was in use for 7 hours today. I went from having it idle, to high performance gaming (StarCraft 2, FarCry3, Arma3, BF4) all played on max settings, I then had larger programs running and set up on different displays for most of the day (I currently have four displays). The system didn't slow down for anything and worked fine. I monitored the memory usage extremely close and never did it give me trouble.

I believe the issue is resolved for now, I'll mark it as solved and seek further help if it comes back. Uninstalling the driver, uninstalling the killer suite and then restarting to allow Microsoft to install their drivers fixed the problem for now.

For those who wanted to know which drivers my system automatically downloaded and installed below is the information for both devices;

**Killer e2400 Gigabit Ethernet Controller
Driver Provider: Rivet Networks
Driver Date: 9.22.2015
Driver Version 9.0.0.31

**Killer Wireless-n/a/ac 1535 Wireless Network Adapter
Driver Provider: Qualcomm Atheros Communications Inc
Driver Date: 9.18.2015
Driver Version 12.0.0.149

Thanks everyone.

I had the exact same issue, for now I have disabled the NDU but I'll try to play around with drivers and see if I can get it to work.
Thanks for the post