Windows 10: Memory Usage (non-paged pool) etwB

Whenever i start my pc the non-paged pool already starts at 1.7GB. I used poolmon to find out what the reason could be and it turns out there is something called "etwB" which uses 1.7GB, but it doesnt change. Now i am wondering what it is and if i could remove it.

:)

 

Large amount of Paged Pool memory usage over time


I have been fighting with this for some time and I can't figure out what it is. Over time, my Paged Pool memory usage keeps climbing until eventually I have to reboot to clear it out. It is a tough problem to search for because most people seem to have a problem with non-paged pool memory and all of those problems get included in the search results.

I have 32GB of RAM and once the paged pool reaches around 18GB or so it starts to bog down and get sluggish. And when I say 18GB, I mean 18GB with nothing open. I have my typical tray stuff, which I have tried killing, but nothing releases the RAM. I have let it climb all the way to 32GB before, but then the computer becomes useless and took about a half hour or so to shut down.

When I run Rammap it shows that paged pool is huge, and in the process list there is a process called MemCompression that has an extremely large amount of RAM in use. Not the full size of the paged pool, but definitely really big.

There are several threads talking about using Poolmon to track down processes using lots of paged or non-paged pool memory, but the process on mine that is extremely large has a tag of Se, which is tough to search for in the strings because virtually every file has Se in it somewhere.

Right now I just rebooted again, so the usage is back to "normal" (if you consider 11GB memory in use normal for just having Chrome open) and my paged pool is around 2GB or so. It will increase again by this evening, so I will get some screen grabs of the Rammap and the process list. Any other screens I can grab that might help?

 

High paged pool memory after leaving system on for quite sometime


1.2 GB Paged pool does not seem unreasonable for a system with 32 GB RAM. This value is higher for systems with large RAM sizes. In any event it is hardly likely to be the cause of your problem.

The paged and non paged memory pools are used by kernel level components such as drivers and the kernel itself. The paged pool can be paged out at the memory managers discretion while the non paged pool must remain in RAM at all times. Task Manager will not tell you how much of the paged pool is in RAM.

Memory usage in any modern OS is controlled by the system memory manager, always with the goal of maximizing overall system performance. When available memory is plentiful, as is shown in the screenshots, the memory manager will allow processes and other Windows components to use pretty much whatever memory they want without restrictions. But if there is memory pressure it is fully capable of reducing the paged pool usage to a small fraction of it's current value. But it will only do this if needed. Doing it at any other time would serve no useful purpose and would likely impair performance. Note that this is the RAM resident portion of the paged pool, not what is shown in Task Manager which would be unaffected.

High memory usage, even if it is seriously abnormal, will not impair performance unless it causes a shortage. I have seen many Internet articles that get this wrong. It is not unusual for the paged pool to grow over time. Unless there is a memory leak, and there is nothing to suggest that here, this growth will stop.

 

High paged pool memory after leaving system on for quite sometime

Oh, I see! Thanks for the clarity!

Pageable memory controlled by memory management...that makes ALOT of sense! Oh well, at least the page pool stops at 1.2gb memory so I still have plenty of ram leftover for multi-tasking purposes. For virtual memory, I left it at system managed on C:/ drive. Otherwise, I'll try to update the network drivers and nvidia drivers. I know Killer Network drivers are highly proneable for memory leaks.

Say, did Intel made an update of Intel Rapid Storage drivers for 4th Gen processors?