Windows 10: High paged pool memory after leaving system on for quite sometime

Last time I kinda made a thread about high-non paged pool usage, but now I had like a high-paged pool usage and somehow it kinda increases while my system is in use. For drivers, I think I have Intel Rapid Storage technology, wacom tablet drivers, killer network drivers, and nvidia drivers. While I saw the new updates on the network and nvidia drivers, I can't be sure if there's a new driver for intel storage technology and wacom tablet drivers since I had a 4th gen i7 cpu and a 10 year old tablet. Plus, I notice a quite a performane drop every time I played some games such as WoW and TF2 and I think it may be related to the memory leak but I'm not sure. Is there any other tools to find out the culprit of this?

Would be appreciated to help this. Thanks! *Smile

These were taken while I was playing WoW.

:)

 

System memory and compressed memory, interrupts of the system

I may have found a possible solution to the high memory usage;

Did some more research and found this solution which could be attritubed to a memory leak on non-paged-pool.

To Fix Memory Leaks on Non-Paged-Pool:

Changed the registry value instead of using Autoruns:

Window + R then type regedit to open the registry editor.

From that look for this: "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Ndu"

Change the Start value to "4" (for disable).

This reduced the memory usage from ~4GB to around 2.3GB which seems to be more inline with acceptable memory usage. This might not work for everyone though.

Source: High Memory Usage? - [Solved] - CPUs - Tom's Hardware

 

fltmgr.sys causing very high paged pool memory use since Win10 Creator Update

Hello,

Any news regarding this?

Is there any special reason why the Blizzard Application is behaving that way?

Any solution for it?

Is anyone else experiencing this?

Where is the problem? Blizzard Application or Windows side?

Thank you,

Cristian

 

You have about 25GB of free memory in that screenshot. Where do you suspect a leak?

 

I suspect a leak when I saw it at 1.2gb of paged pool memory. Is it normal for a paged pool memory to do this? I mean, what is the normal range for a page-pool and non-page pool? I mean this might be the reason behind the fps drops in WoW during raids (I know its a CPU limit thing but last time I rebooted I had no fps drops).


Off-topic: Ugh...I hate when it deletes my message when editing on my mobile phone. *Sad

 

The paged pool is used by the Windows kernel and drivers. I would expect usage to go up when you're doing anything that goes through a driver - this includes network activity, graphics, audio, etc.

You would have to get a screenshot of the task manager while you see the fps drops to draw any conclusions. But at only 1.2GB out of 32GB I doubt that paged pool usage is the cause.

 

Ah....was paged pool the same as non-paged pool or am I missing something?

Yeah, I'll grab some screenshots of Task Manager for that. Here are couple of pics of the task manager when the fps drops. Note that these pics were taken during the first 2 boss encounters in Antorus raid (looking for raid mode). The fps drops kinda ranges from 33 fps to 50 fps during the fights since I'm using vertical sync. Out of combat was at steady 60fps. It may seem a bit vague, but at least I can show something. *Smile

While I was checking on the system settings in WoW, I'd realized that the lightning quality was set to custom. I think it might be from the 7.3.5 patch that caused this. Shortly, I reverted back high settings and somehow I may see some improvements but needs more testing. That lightning quality in custom changes some lightning settings a bit darker. Hopefully I'll test some more of it when I had more time tomorrow. *Smile

 

They are not the same (the paged pool contains pageable memory, the non-paged pool contains non-pageable memory). But they're both used by drivers.

 

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.

 

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?