Windows 10: High MmSt Paged, NtfF Paged, FMfn memory usage

Ive been on the hunt for a memory leak, and it lead me to PoolMon and RamMap, my 32gb of ram is being used up while Task Manager says it shouldn't be anywhere close to 80% ram usage with whats running. I've tried to use RamMap to empty every category I could. It temporarely fixed my issue, however now that I am watching the list go up in bytes I see that these are dominating in the bytes categoryNtfF PagedMmSt PagedFMfn PagedI have absolutely no clue what these are, or what type of software these are used in or however they are related to them. Would love some help with this, when I emptied it

:)

 

Windows 10 high memory usage FMfn paged pool

Hello from several months now i have high memory usage, if i stop my PC trough shutdown i get 40% usage at next start. If i restart it it gets back to 13-14% and it climb to 60-90% until the end of the day. I have read several topics on similar issue but they didn't help. I managed to find an particular process that's responsible for the big paged poll, it's named FMfn and i found it's a Microsoft Filesystem Filter manager. I have followed the steps in this tread:

Windows 10 high memory usage (unknown reason)

When i open the stack tag, all the memory is allocated to something named "n/a"





currently the memory usage on the screenshot is 46% from witch the paged pool is 2.6 GB from a total memory of 16 GB.

It wouldn't be a big issue if when it get to 90% the PC stop to be usable and i have to restart so i can work on it again

 

Extreme Non paged memory usage on windows 10

Hello everyone,

I'm looking for a solution to fix the 20+GB non paged memory usage in Windows 10. I follow the guide what you can read on StackExchange/Superuser.

Memory:67014784K Avail:21094036K PageFlts:226108 InRam Krnl:15340K P:6250068K

Commit:123381596K Limit:159684792K Peak:153907544K Pool N:22401880K P:7611364K

Tag Type Allocs Frees Diff Bytes Per Alloc



Even Nonp 468594745 (2982) 316020338 (1867) 152574407 19529540192 ( 142720) 128

MmSt Paged 595936455 (6747) 595302774 (5836) 633681 2030382960 ( -4203200) 3204

NtfF Paged 382738233 (4974) 382312563 (2026) 425670 681072000 ( 4716800) 1600

FMfn Paged 580176714 (6360) 579415013 (4671) 761701 402281536 ( 1069168) 528

Ntff Paged 192953879 (2852) 192669861 ( 952) 284018 399897344 ( 2675200) 1408

smNp Nonp 370348 ( 0) 300619 ( 1) 69729 285609984 ( -4096) 4096


So based on this I can see the usage caused by "Even".

The problem with this I can't search on this driver because the "Even" word is widely used in drivers. "findstr /s even *.* "

Is there anyone who can help me to figure out which driver causes the problem? I got sicks from this problem, I need to restart my PC every 3 days because of this.

 

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.