Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.

Dismiss

Event 2019 - "The server was unable to allocate from the system nonpaged pool because the pool was empy" - Can you help me ?

85 views

Skip to first unread message

Javier

unread,

Oct 12, 2005, 4:33:12 PM10/12/05

am the network administrator of a country wide net. with 5 branches. I
have 2 windows 2003 servers in each branch.

In the last june, one of my remote DC Server started to show the event
2019, and then stoped servinng all the network services. We restarted the
server every 6 hours until reformated.

Now I start having the same problem in another DC server in other
branch. I will format it the next weekend.

I was looking for information about this in the newsgroups and in the
microsoft support site and I only found something related with macaffe
Antivirus. We don´t use any macaffe product.

Do you have any suggestion about that ? Do you know another case like
this ?

I am very happy with Windows 2003 & Exchange 2003 BUT I really don´t
want to reformat the servers every 6 months

Thanks in advance

Javier

Todd J Heron

unread,

Oct 12, 2005, 7:18:58 PM10/12/05

Do you use Norton AV? If so take a look here:

http://support.microsoft.com/default.aspx?scid=kb;en-us;272568&sd=ee

If not, you have some sort of kernel driver memory leak. This is especially
true if this error is accompanied in the System Event Log by Event ID: 2019,
"The server was unable to allocate from the system nonpaged pool because the
pool was empty". The memory leak can be identified by using one of the two
following methods:

Method #1 (easy):
Open Task Manager, and under

View->Select Columns

choose Virtual Memory Size.

Click on the column header to sort by VM usage. If the application isn't
freeing memory, this value will continue climbing until the system exhausts
the available memory, which causes the System Process - Out of Virtual
Memory dialog. Also look at Task Manager Processes > Mem Delta. A
consistently positive value here also indicates a memory leak. The only way
to free the memory would be to kill the process.

Method #2 (harder):
Obtain PMON from the Resource Kit then read this article:
How to Use PMON to Troubleshoot Kernel Mode Memory Leaks [Q177415]
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q177415

Memtriage from windows 2003 resource kit may help to find the leak:
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/techref/en-us/Default.asp?url=/Resources/Documentation/windowsserv/2003/all/techref/en-us/memtriage.asp

------------------------

If you wish to conduct none of the above tests, then simply update all
drivers on the system, starting with the NIC drivers. Reports I have seen
in the field indicate using the latest Intel NIC drivers fixed this problem.

I have also seen a confirmed report in the field which stated that
unisntalling Promise Array Managment software resolved the problem. The
version of PAM was 3.2.1 Build 13.

And see if maybe the crypserve.exe proces is running and try stopping it.

--
Todd J Heron, MCSE
Windows Server 2003/2000/NT; CCA
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights

"Javier" <jvil...@elsitio.net> wrote in message
news:eQtzIw2z...@TK2MSFTNGP09.phx.gbl...

0 new messages