
- HOW TO USE POOLMON.EXE WINDOWS 10 INSTALL
- HOW TO USE POOLMON.EXE WINDOWS 10 DRIVERS
- HOW TO USE POOLMON.EXE WINDOWS 10 SOFTWARE
Once the tools are downloaded and installed, launch Process Explorer and click Options -> Symbol Configuration, point it to the dbghelp.dll file installed with the Debugging Tools, and configure Microsoft’s symbol server as the symbol file path.įigure 2 – Process Explorer Symbol Configuration (The debugging tools are required to provide access to debugging symbols.)
HOW TO USE POOLMON.EXE WINDOWS 10 INSTALL
One way to see the nonpaged pool limit on a specific system is to install the Debugging Tools for Windows, and then use Sysinternals’ Process Explorer to display the pool size. Pool size data is from Mark Russinovich and David Solomon’s book “Windows Internals, 5th Edition”, and Mark Russinovich’s blog posting “Push the Limit’s of Windows: Paged and Nonpaged Pool”.

For example, 32-bit operating systems, with their smaller address spaces, have lower limits:ģ2-bit Windows Server 2003 with 2GB or more of RAM will have a nonpaged pool limit of 256MBģ2-bit Windows Server 2008 will have a nonpaged pool limit of either 2GB or slightly more than 75% of physical memory, whichever is smallerĦ4-bit operating systems, which have a much larger address space, have higher limits:Ħ4-bit Windows Server 2003 will have a nonpaged pool of either 128GB or 40% of physical memory, whichever is smallerĦ4-bit Windows Server 2008 (or 2008 R2) will have a nonpaged pool limit of either 128GB or slightly more than 75% of physical memory, whichever is smaller The amount of memory allocated to the nonpaged pool varies, and is determined as a function of operating system, processor architecture, and physical memory size.
HOW TO USE POOLMON.EXE WINDOWS 10 DRIVERS
It is used by the kernel and also by device drivers installed on a system to store data which might be accessed in situations when page faults are not allowed. The nonpaged pool is memory which always resides in physical memory – it is never paged out. Thankfully, the error message in the event log gave us a clear indication as to why the systems were in trouble, and allowed us to troubleshoot and diagnose the problem.

Upon investigation, we found that immediately before the crash the servers would log event 2019 in the System log – “The server was unable to allocate from the system nonpaged pool because the pool was empty”. The only course of action was to power-cycle the crashed server clearly, not a good thing to do when we’re dealing with production servers.

The crashes sometimes resulted in a blue-screen, but other times resulted in a machine which responded to ping, but little else, and had a completely unresponsive console.
HOW TO USE POOLMON.EXE WINDOWS 10 SOFTWARE
I recently had an issue where, after a software change on our servers, we started to notice that some systems had become unstable and were regularly crashing.
