For a full description, see PoolMon in the WDK documentation.
This tool is included in the Windows Driver Kit (WDK). exe) helps you to isolate the features that are causing kernel memory leaks. This feature uses data from pooltag.txt, a file installed with PoolMon and with the Debugging Tools for Windows packages. PoolMon (Poolmon.exe) monitors pool memory usage by pool tag name. Same on all 3 PCs, which I can only assume is startharvester.exe. The problem might be due to a memory leak caused by an application or service that is not releasing memory correctly.
PoolMon can display the names of the Windows components and commonly used drivers that assign each pool tag.
For more information, see "Pool Tagging Requirement" in PoolMon Requirements. On Windows Server 2003 and later versions of Windows, pool tagging is permanently enabled. To use PoolMon on Microsoft Windows XP and earlier systems, you must enable pool tagging. The version of PoolMon described in this document is included in the \Tools\Other subdirectory of the Windows Driver Kit (WDK). You can also use PoolMon in each stage of testing to view the driver's patterns of allocation and free operations, and to reveal how much pool memory the driver is using at any given time. The data is grouped by pool allocation tag.ĭriver developers and testers often use PoolMon to detect memory leaks when they create a new driver, change the driver code, or stress the driver. may be impacted enough to cause a false failure, and thus a failover of the resource to the backup server.
PoolMon (poolmon.exe), the Memory Pool Monitor, displays data that the operating system collects about memory allocations from the system paged and nonpaged kernel pools, and the memory pools used for Terminal Services sessions.