Discussion Locked

empty system nonpaged pool

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Error in the event log: "Server unable to allocate from the system nonpaged pool because the pool was empty." The printers reported an "unexpected network problem." The exact text is "The server was unable to allocate from the system nonpaged poolbecause the pool was empty." with event ID 2019 and source SRV.

this error has been recurring every 10 days.

10 days ago, the printers stopped working, but there was nothing in the event log. Inoculan, however had crashed. I thought Inoculan was the culprit.

10 days before that, I had the same problem, but before I could do anything, I got a BSOD and well.... I wrote it off as "just one of those things."

10 days before that, the server was not responding and users could not log in. I could not open anything and a system nonpaged pool failure was noted. on that day there were power fluctuations that the UPS logged and it was "extra hot" over the weekend, so I thought that it was a combination of dirty power and heat.

There are no errors prior to the above.

From my understanding, the system nonpaged pool failure refers to inadequate system physical memory. We currently have 128 MB of system RAM. I changed the virtual RAM setting to 250 MB from 150 MB, but no good. I also changed to server optimization to "minimize memory used" from "balance". I've got 11 - 13 users, one of which is semi-retired now and the others are about 50% in Guam, so I figure that this setting is OK.

Also, I am thinking about more RAM, I'd rather know that RAM is the problem instead of just guessing and throwing $$ at the problem.

The server is a Compaq Proliant with a 350 MHz P II, 128 MB RAM (ECC I think) running Win NT 4.0 SP 6a small business server (exchange 5.5, proxy, etc.)

other than the corrupted mailbox and virus signature updates, nothing was changed prior to the start of this chain of nasty stuff.

Help!

5 replies

by pvp

*I* would want 512 MB on that server! Then I'd go with two 523 MB paging files, preferably on separate physical disks, but at least on separate partitions (one of which should be the system drive).

I have 256 MB on my _workstation_ and manage todrive it into the ground every 3-7 days!

At home I run a standalone server with only 80 MB, but there are no users but me there.

by mikel~t

You might have a bad Memory control module on your motherboard. If Compaq is worth their name, they should have some sort of diagnostics you can run on the system to diagnose hardware problems. It also might be a bad RAM module. If you had another to replace the one in question, that might verify this.

Also, making a bigger virtual memory file is a good idea, but don't put it on the system partition as recommended above. Your best bet is to put it on a drive or partition that is not hometo the system files. You'll see a decrease in performance if they are on the same drive or partition.

Blue screens are not normal...you should try and repair your NT installation ASAP so these problems don't continue.

Good luck.

Mike. ~MCSE~

This discussion is closed to new replies.