Windows 10: Huge memory leak in non paged pool

Hi,

I have a memory leak in my system, specifically in the non paged pool. In one or two days of usage after a restart, it fills up all of the RAM available.


Some online searches landed me on this blog: http://woshub.com/huge-memory-usage-non-paged-pool-windows/#:~:text=Install%20the%20Latest%20Versions%20of,a%20Kernel%2DMode%20Memory%20Leak


This helped me narrow down the problem for me. Using poolmon.exe, I found that "WSSL" was leaking memory. This was further associated with a file in system32 called "nFltr1.sys". Its detail read as below:


c:\windows\system32\drivers\nFltr1.sys:
Verified: Signed
Signing date: 12:27 PM 19-Mar-19
Publisher: Microsoft Windows Hardware Compatibility Publisher
Company: n/a
Description: n/a
Product: n/a
Prod version: n/a
File version: n/a
MachineType: 64-bit

Now I don't know where to go from here. I don't understand this sys file, but if I remove it, my internet stops working. I Don't know which drivers to update/downgrade to fix this issue. Any help is appreciated

:)

 

is this memory leak?

Hello RASHMIRANJAN1,

I'm an independent advisor and hope this would address your questions.

This is not a memory leak. A memory leak happens when a process or program failed to discard utilized memory when it is no longer in use. In that case, you would see a process or program consuming more and more memory over time.

I wouldn't be worried about the paged and non-paged pools as they aren't excessively large in size. The paged pool is used to store handles of kernel objects, so it is normal to have some usage there. And non-paged pool is used by kernel and drivers of the
operating system, so it is also normal for some usage there.

 

Huge non-paged pool on startup?

Hello. I just built a new computer and installed the drivers for it on w10. Everything works fine, but I have a non-paged pool of 5.7gb out of 16 on startup, and I'd like to do something about that. I checked under task manager for the non-paged pool,
but none of the programs there are taking nearly that much. I suspect it's the killer network driver, but I'd still like to confirm it. Any suggestions? Thanks!

 

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?