Windows 10: Microsoft Filesystem Filter Manager or fltMgr.sys is causing non-paged memory leak.

As soon as I noticed the non-paged memory leak I started to monitor using Poolmon.exe and the amount it uses keeps increasing as the PC runs. I then used Sigcheck cmd to get info on it and this was it:


c:\windows\system32\drivers\fltMgr.sys:

Verified: Signed

Signing date: 7:06 AM 23/07/2019

Publisher: Microsoft Windows

Company: Microsoft Corporation

Description: Microsoft Filesystem Filter Manager

Product: Microsoft« Windows« Operating System

Prod version: 10.0.18362.267

File version: 10.0.18362.267 WinBuild.160101.0800

MachineType: 64-bit

how can I fix it?

:)

 

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.

 

Memory leak issue

The term "memory leak" means that an application fails to return all its RAM to the operating system when it exits. The leftover RAM is unusable to the operating system.

Step one is to identify the application that is leaking memory. Step two is to contact the application's developers and provide as much detailed data on the memory leak as you can. For example: which processes are still in RAM after the application exits
and how much RAM they occupy. Application developers never want their applications to leak memory and they will be grateful for the details you provide, particularly if they can replicate the leak on their own computers.

 

I finally find my memory leak...


You can try find the driver one by one, by checking it on the device manager. If it is not listed on device manager, try googling it. You can check all of the *.sys files, it usually related. I have these memory leak problems before too.

What I mean is you have to find the "Nonp" one. From what I read in some articles you have to find the tags categorized as Nonpaged. not the Paged