non paged pool is empty error

I have received the following error
The server was unable to allocate from the system nonpaged pool because the
pool was empty.
Any idea on how to trap which process is causing the memory to leak or be
used up. This has caused SQL Server to be unavailable. I had to reboot as a
fix
I would like to trap it before it happens again. Any way to do so ?
Using Win2K3 and SQL 2KHi Hassan
I would expect this to be a gradual therefore monitoring the memory usage
over time would possibly indicate which process is not releasing memory.
Check out
http://www.microsoft.com/technet/pr...a.mspx?mfr=true
and the perfmon counters in http://ask.support.microsoft.com/kb/133384
Also see if this applies:
http://support.microsoft.com/defaul...us;272568&sd=ee
John
"Hassan" wrote:

> I have received the following error
> The server was unable to allocate from the system nonpaged pool because th
e
> pool was empty.
> Any idea on how to trap which process is causing the memory to leak or be
> used up. This has caused SQL Server to be unavailable. I had to reboot as
a
> fix
> I would like to trap it before it happens again. Any way to do so ?
>
> Using Win2K3 and SQL 2K
>
>
>