Comments on: Resources for Troubleshooting Windows Event 2019: The server was unable to allocate from the system nonpaged pool because the pool was empty http://thebackroomtech.com/2007/11/20/resources-for-troubleshooting-windows-event-2019-the-server-was-unable-to-allocate-from-the-system-nonpaged-pool-because-the-pool-was-empty/ serving up the info back room techs everywhere find interesting Sun, 07 Nov 2010 18:59:34 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Brady http://thebackroomtech.com/2007/11/20/resources-for-troubleshooting-windows-event-2019-the-server-was-unable-to-allocate-from-the-system-nonpaged-pool-because-the-pool-was-empty/#comment-436 Brady Thu, 28 Oct 2010 18:26:56 +0000 http://thebackroomtech.wordpress.com/2007/11/20/resources-for-troubleshooting-windows-event-2019-the-server-was-unable-to-allocate-from-the-system-nonpaged-pool-because-the-pool-was-empty/#comment-436 Excellent article! I was having to reboot my domain controllers once every 2 weeks and sometimes they would crash in a week. We are running provisioning server 5.6 on our DC's and replicating the images via DFS. I used this article to look at handles and found the sopeserver.exe service was slowly growing out of control. Then I found this article http://support.citrix.com/article/CTX126390 which described the exact problem I was having. After updating to Provisioning Services 5.6 SP 1 the problem has been resolved. Again thank you for posting you find for a simple solution! Excellent article!

I was having to reboot my domain controllers once every 2 weeks and sometimes they would crash in a week.
We are running provisioning server 5.6 on our DC’s and replicating the images via DFS. I used this article to look at handles and found the sopeserver.exe service was slowly growing out of control. Then I found this article http://support.citrix.com/article/CTX126390 which described the exact problem I was having. After updating to Provisioning Services 5.6 SP 1 the problem has been resolved.
Again thank you for posting you find for a simple solution!

]]> By: Leo Smith http://thebackroomtech.com/2007/11/20/resources-for-troubleshooting-windows-event-2019-the-server-was-unable-to-allocate-from-the-system-nonpaged-pool-because-the-pool-was-empty/#comment-435 Leo Smith Thu, 15 Apr 2010 13:02:19 +0000 http://thebackroomtech.wordpress.com/2007/11/20/resources-for-troubleshooting-windows-event-2019-the-server-was-unable-to-allocate-from-the-system-nonpaged-pool-because-the-pool-was-empty/#comment-435 Using task manager looking at handles I get "system" with 7,163 and dns.exe with 5,213. Looking at NP Pool dns.exe is always at the top of the list. Any suggestions? Thank you, Using task manager looking at handles I get “system” with 7,163 and dns.exe with 5,213. Looking at NP Pool dns.exe is always at the top of the list. Any suggestions?

Thank you,

]]> By: Simon http://thebackroomtech.com/2007/11/20/resources-for-troubleshooting-windows-event-2019-the-server-was-unable-to-allocate-from-the-system-nonpaged-pool-because-the-pool-was-empty/#comment-434 Simon Tue, 29 Dec 2009 23:16:17 +0000 http://thebackroomtech.wordpress.com/2007/11/20/resources-for-troubleshooting-windows-event-2019-the-server-was-unable-to-allocate-from-the-system-nonpaged-pool-because-the-pool-was-empty/#comment-434 Great write-up! Thanks for being thorough Julie & sharing your wisdom. Great write-up! Thanks for being thorough Julie & sharing your wisdom.

]]> By: Erik http://thebackroomtech.com/2007/11/20/resources-for-troubleshooting-windows-event-2019-the-server-was-unable-to-allocate-from-the-system-nonpaged-pool-because-the-pool-was-empty/#comment-433 Erik Fri, 13 Nov 2009 15:08:21 +0000 http://thebackroomtech.wordpress.com/2007/11/20/resources-for-troubleshooting-windows-event-2019-the-server-was-unable-to-allocate-from-the-system-nonpaged-pool-because-the-pool-was-empty/#comment-433 Nice summary, tnx Nice summary, tnx

]]> By: Len http://thebackroomtech.com/2007/11/20/resources-for-troubleshooting-windows-event-2019-the-server-was-unable-to-allocate-from-the-system-nonpaged-pool-because-the-pool-was-empty/#comment-432 Len Wed, 22 Jul 2009 00:48:18 +0000 http://thebackroomtech.wordpress.com/2007/11/20/resources-for-troubleshooting-windows-event-2019-the-server-was-unable-to-allocate-from-the-system-nonpaged-pool-because-the-pool-was-empty/#comment-432 Thank you!!! Thank you!!!

]]> By: Duncan http://thebackroomtech.com/2007/11/20/resources-for-troubleshooting-windows-event-2019-the-server-was-unable-to-allocate-from-the-system-nonpaged-pool-because-the-pool-was-empty/#comment-431 Duncan Thu, 01 May 2008 14:16:48 +0000 http://thebackroomtech.wordpress.com/2007/11/20/resources-for-troubleshooting-windows-event-2019-the-server-was-unable-to-allocate-from-the-system-nonpaged-pool-because-the-pool-was-empty/#comment-431 Thanks for these great tips I mainly used task manager in the end and it ended up being the spooler service!!!! Now I have to find out which driver is causing the service to stuff up! Thanks for these great tips I mainly used task manager in the end and it ended up being the spooler service!!!! Now I have to find out which driver is causing the service to stuff up!

]]> By: Elizabeth http://thebackroomtech.com/2007/11/20/resources-for-troubleshooting-windows-event-2019-the-server-was-unable-to-allocate-from-the-system-nonpaged-pool-because-the-pool-was-empty/#comment-430 Elizabeth Wed, 02 Jan 2008 19:12:45 +0000 http://thebackroomtech.wordpress.com/2007/11/20/resources-for-troubleshooting-windows-event-2019-the-server-was-unable-to-allocate-from-the-system-nonpaged-pool-because-the-pool-was-empty/#comment-430 Thanks again! I looked in task manager to find that "spoolsv.exe" was using up much more memory than any other program. After a google search, folks were saying to look for a defunct printer accumulating print jobs in its queue. Came to find out that a printer on the server indeed had recently been physically removed but not deleted from the printers folder was accumulating print jobs. This was causing the leak!!! Once the defunct printer was deleted out of the printers folder, the problem stopped. I can't thank you enough, really, for saving me a lot of time, aggravation, and trouble by posting how Task Manager can be used to solve the problem. Thanks again! I looked in task manager to find that “spoolsv.exe” was using up much more memory than any other program. After a google search, folks were saying to look for a defunct printer accumulating print jobs in its queue. Came to find out that a printer on the server indeed had recently been physically removed but not deleted from the printers folder was accumulating print jobs. This was causing the leak!!! Once the defunct printer was deleted out of the printers folder, the problem stopped.

I can’t thank you enough, really, for saving me a lot of time, aggravation, and trouble by posting how Task Manager can be used to solve the problem.

]]> By: Elizabeth http://thebackroomtech.com/2007/11/20/resources-for-troubleshooting-windows-event-2019-the-server-was-unable-to-allocate-from-the-system-nonpaged-pool-because-the-pool-was-empty/#comment-429 Elizabeth Wed, 02 Jan 2008 03:11:34 +0000 http://thebackroomtech.wordpress.com/2007/11/20/resources-for-troubleshooting-windows-event-2019-the-server-was-unable-to-allocate-from-the-system-nonpaged-pool-because-the-pool-was-empty/#comment-429 Thank you for taking the time to write this up! I tried many of the steps you listed; I think Task Manager will bring me the solution! Will report back. Thank you for taking the time to write this up! I tried many of the steps you listed; I think Task Manager will bring me the solution! Will report back.

]]>