Performance Data High Kernel Memory Utilization In PoolPaged Bytes Suspected Memory Leak

This alert condition indicates high kernel memory utilization in PoolPaged Bytes. Several factors may deplete the supply of paged pool memory. Enabling pool tagging and taking poolsnaps at different time intervals may help you to understand which driver is consuming paged pool memory. If the poolsnaps indicate that the MmSt tag (Mm section object prototype Page Table Entries (PTEs) is the largest consumer and paged pool memory has been depleted or the system is logging error event 2020, there is a high probability that there is a very large number of files that are open on a server. By default, the Memory Manager tries to trim allocated paged pool memory when the system reaches 80 of the total paged pool. Depending on the system configuration, a possible maximum paged pool memory on a computer can be 343 MB and 80 of this number is 274 MB. If the Memory Manager is unable to trim fast enough to keep up with the demand this issue can result. By tuning the Memory Manager to start the trimming process earlier (for example, when it reaches 60), it would be possible to keep up with the paged pool demand during sudden peak usage, and avoid running out of paged pool memory.

Last modified April 17, 2020