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”. 예를 들어, 32비트 운영체제는 비교적 작은 주소공간 때문에 낮은 한계값을 갖는다.ģ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:ģ2비트 윈도우 서버 2003에 2GB이상의 램이 있으면 넌페이지드 풀 한계값은 256MB다.ģ2비트 윈도우 서버 2008은 2GB와 물리메모리의 75% 중 작은 값을 한계치를 갖는다.Ħ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
For example, 32-bit operating systems, with their smaller address spaces, have lower limits: 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.
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. “The server was unable to allocate from the system nonpaged pool because the pool was empty” (풀이 고갈되어 시스템 넌페이지드 풀을 할당할 수 없다) 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.
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. Luckily it was relatively easy to troubleshoot, and he's sharing the tools and techniques he used to get his servers back on track in double-quick time.īen Lye가 정기적으로 서버를 죽이는 넌페이지드 풀의 메모리릭을 찾아냈다. Troubleshooting Nonpaged and Paged Pool Errors in Windowsīen Lye uncovered a memory leak in the nonpaged pool which was crashing his servers with disquieting regularity.