Nonpaged pool server issue?

[Guest]

We just started to get this message in the event log (ID 2019) and it states,
"Server was unable to allocate from the system nonpaged pool because the pool
was empty. Has anyone come across this issue? I cant seem to find any info
on it except that it may be a fairly new issue. Any suggestions would be
greatly appreciated.

 

[John John]

Do a search for ID 2019 on Microsoft or Technet you will get hits on
this. It mostly points to this:

"Event Message:

The server was unable to allocate from the system nonpaged pool because
the pool was empty.
Source Event Log Event ID Event Type
Srv System 2019 Error
Explanation:

Nonpaged pool pages cannot be pages out to the paging file, but instead
remain in main memory as long as they are allocated. An application is
probably incorrectly making system calls and using up all allocated
nonpaged pool. You might also see the following error on a local or
remote system: Not enough storage available to process this command.
User Action:

To find the application, use the Performance Monitor 4 to look at each
application's nonpaged pool allocation. As an alternative, monitor the
system with a utility such as PMON.EXE from the Windows 2000 Resource Kit."

The error might be a bit rare but far from new, there is MS
documentation on it affecting systems as early as NT3.x. Seems to be
due to faulty programing. Also, make sure that you don't have any virus
on the machine.

John