Re: Win2003 Src Std Edition

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Craig Matchan (cwigster_at_nospam.swiftdsl.com.au)
Date: 12/14/04 

Date: Tue, 14 Dec 2004 15:21:15 +1100

Hi Todd,

"Todd J Heron" <todd_heron_no_spam@hotmail.com> wrote in message
news:OZdMwtO4EHA.3756@TK2MSFTNGP14.phx.gbl...
> Do you use Norton AV? If so take a look here:

No, this server is just acting as our ADC and internal PDNS server. Apart
from that is does nothing else. The only AV application on it is Sophos.

I don't think it's running out of virtual memory, at least there were no
event logs to indicate this. I spose I could up the amount, but my guess is
that it might only extend the uptime and not fix the underlying problem.
Actually if my understanding of the nonpaged pool is correct I doubt
increasing the virtual memory sizes will help as the nonpaged pool is for
application/drivers/whatever that cannot be paged.

> 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):

Doing this now. Will minitor it for a few days to see if there are any
obvious trends.

> Method #2 (harder):
> Obtain PMON from the Resource Kit then read this article:

Yeah, I came across a reference to this on a site as well. I can only find a
reference to a Win2000 version of PMON. Would this be ok to run on Win2003
or is their a WIn2003 specific version. Been bit by version missmatches to
many times to make assumptions any more :)

> How to Use PMON to Troubleshoot Kernel Mode Memory Leaks [Q177415]
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;q177415
>
> See also:
> http://www.jsiinc.com/suba/tip0000/rh0088.htm
> http://www.jsiinc.com/subj/tip4700/rh4792.htm
> http://www.eventid.net/display.asp?eventid=2019&eventno=661&source=Srv&phase=1
>

Ahh.. didn't know about this one.

> 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

I did come across a few references to this sort of problem being due to
Intel NIC drivers, or rather certain versions, although I strongly susepct
that any driver is a candidate, but even so a few people reported that using
the latest Intel drivers fixed the issue. I can only assume the drivers have
a memory leak. I'm looking for new/updated drivers now.

Thanks for your detailed reply, it is much appreciated.

Regards (and merry xmas)

Craig

Relevant Pages