Windows 10: Non-paged tool memory leak troubleshooting

I have come to the conclusion that I have the exact issue described in this thread:

https://www.reddit.com/r/Windows10/comments/8ex29t/nonpaged_pool_memory_leak/

However, after installing the per-requisite programs, windows powershell does not recognize

poolmon /p /b as an internal or external command. I know I have messed something up in the instructions but can't figure it out. Anyone have any ideas?
submitted by /u/lexilooks
[link] [comments]

:)

 

Windows 10, slow memory leak troubleshooting

Traces take 2x file size in RAM so it would need 14Gb of ram. That would force the vast majority of it to be paged to disk making it nearly impossible to examine. In the above trace you had 8Gb in standby lists which is a good thing. It did not look like
there was a memory leak. Memory leaks will show an ever increasing line on the trace. Yours was flat.

If it takes that long to experience the problem wouldnt an occasional reboot to free the ram fix the issue?

 

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.