Unidentifyable High Memory Usage (Leak?) Please Memory Experts I Need Your Help!

Kirbyarm

Distinguished
Nov 9, 2013
298
8
18,785
Hello everyone,

I'm currently battling a problem with my computer's RAM. I have 32 GB of RAM installed and the last few days or so it has been obscenely high memory usage. As soon as I reboot the computer and the desktop is loaded I immediately open task manager and it shows 38 - 40% memory used but refuses to show what is using that memory.

In task manager, this is sorted by 'Memory':

https://i.imgur.com/oZkf4DU.png

This is the performance tab:

https://i.imgur.com/pl6c48e.png

A friend recommended checking into the RAMMap application, and this is what I see here:

https://i.imgur.com/4PmvH0F.png

It seems whatever this nonpaged pool section is, is eating almost 10 GB of RAM! From what I've read online that area is driver related and shouldn't be exceeding even 1 - 2 GB at the very most.

Further research led to me downloading and installing visual studio community 2017 so that I could then install the windows tool kits for Windows 10, to access this program called poolmon.exe

I have run that application and it shows a bluescreen with probably a hundred or more pages of data and I don't understand a single bit of it, more specifically, how I can use it to identify what is sucking all this memory out of nowhere suddenly. This machine is several years old and has never had this problem so this is a very new thing to just suddenly start happening.

Here is a screenshot of the top of the poolmon.exe screen:

https://i.imgur.com/e4nA8F1.png

Please help me figure this out! Thank you for your time.
 
Solution
This is almost always caused by a Killer LAN network card being used with WHQL drivers. There are other possible causes, but 99% of the time that's the cause. If you have that network card, install the latest drivers from the manufacturer's website and reboot.
This is almost always caused by a Killer LAN network card being used with WHQL drivers. There are other possible causes, but 99% of the time that's the cause. If you have that network card, install the latest drivers from the manufacturer's website and reboot.
 
Solution