Re: Server is unable to allocate memory from the System Paged Pool

From: Jerold Schulman (Jerry_at_jsiinc.com)
Date: 03/22/04 

Date: Mon, 22 Mar 2004 07:59:27 -0500

My guesss is a paged pool memory leak.

The following articles are returned on a search for
"paged pool" and memory and leak:

http://support.microsoft.com?kbid=260055 "OHCI1394 Driver May Cause a Memory
Leak During Asynchronous Write Operation"
http://support.microsoft.com?kbid=262386 "Non-Paged Pool Memory Leak on Master
Browser"
http://support.microsoft.com?kbid=264223 "How to Troubleshoot 'Stop 0x0000001E'
with First Parameter of 0xC0000044"
http://support.microsoft.com?kbid=272568 "Event ID 2019 or 2020 or 'Insufficient
System Resources' Error Returned When Logging On"
http://support.microsoft.com?kbid=282522 "List of Bugs Fixed in Windows 2000
Service Pack 2 [1 of 4]"
http://support.microsoft.com?kbid=282525 "List of Bugs Fixed in Windows 2000
Service Pack 2 [3 of 4]"
http://support.microsoft.com?kbid=286060 "Mapping Shared Local Printers to
Central Share Causes Server to Crash Generates Event ID 2020 from SRV"
http://support.microsoft.com?kbid=293857 "'Stop 0x0000007' Error Message Because
of a Memory Leak in the Daprotim.sys File"
http://support.microsoft.com?kbid=296265 "Windows 2000 Non-Paged Pool Is
Exhausted by Afd.sys"
http://support.microsoft.com?kbid=298193 "List of Bugs Fixed in Windows 2000
Service Pack 2 [4 of 4]"
http://support.microsoft.com?kbid=299623 "'Stop OxAB' Error Message May Be
Displayed on the Terminal Server"
http://support.microsoft.com?kbid=316102 "DFS Root Servers Leak Non-Paged Pool
Memory in Dfs.sys in Windows 2000"
http://support.microsoft.com?kbid=317249 "How to Troubleshoot Event ID 2021 and
Event ID 2022"
http://support.microsoft.com?kbid=815493 "Paged Pool Memory Leak with Increase
in Handle Count for Services.exe"
http://support.microsoft.com?kbid=830067 "Event 2020 error message when you run
WQuinn's QuotaAdvisor 4.1 build 452 or earlier on Windows 2000 Server or on
Windows NT Server"
http://support.microsoft.com?kbid=832762 "Slow system performance or your
computer stops responding because of a memory leak in paged pool memory in
Windows 2000 SP4"

On Fri, 19 Mar 2004 17:22:13 -0500, "Ricardo M. Urbano - W2K/NT4 MVP"
<rmu1@columbiaSPAM.SUCKSedu> wrote:

>We have 2 main file servers and one has a network application share for
>production apps, and the other has the same exact share name for test
>apps.
>
>Both servers have Gigabit NIC's and are running at 1000MB/full duplex.
>They are both running Windows 2000 Server, SP3. The shares are on
>~500GB hardware RAID 5 volumes.
>
>There is a particular network application folder that is nearly 5GB in
>size. On 2 separate occasions now, one of my colleagues has launched an
>xcopy from his workstation (100MB/half, fully switched network) of this
>folder from production over the corresponding folder on our "test" file
>server, and then the "source/production" file server starts to throw up
>errors when anyone tries to access any share on the server that there is
>not enough server storage to process the command and the shares become
>inaccessible.
>
>I've had to reboot the server both times. The last time, it had been up
>only about 60 days.
>
>When this happens, the server also records the following error in the
>event log several times:
>Server is unable to allocate memory from the System Paged Pool
>
>MS KB 312362 describes the error and it seems relevant, but I find it
>hard to believe that a Windows 2000 Server cannot handle such a simple
>task with it's default settings. I mean, we only have about 50
>concurrent users at any given time.
>
>Anyway, has anyone had experience with this? The article says to set
>the PoolUsageMaximum value to 40% and the PagedPoolSize value to
>0xFFFFFFFF.
>
>Are there implications to hard coding these values that I should be
>aware of?
>
>BTW, if I telnet into either server and do the same xcopy command server
>to server, no errors are generated.
>
>TIA, everyone!

Jerold Schulman
Windows: General MVP
JSI, Inc.
http://www.jsiinc.com

Relevant Pages

  • Re: Server is unable to allocate memory from the System Paged Pool
    ... My guesss is a paged pool memory leak. ... Central Share Causes Server to Crash Generates Event ID 2020 from SRV" ... WQuinn's QuotaAdvisor 4.1 build 452 or earlier on Windows 2000 Server or on ...
    (microsoft.public.windows.server.general)
  • Memory Leak issue
    ... MFC, COM dll, COM ocx, COM server, Windows static lib and windows dynamic ... It is also showing some of the memory leak in the MFC dlls. ... We are measuring the Private bytes for the application using Sysinternals ...
    (microsoft.public.vc.mfc)
  • Memory Leak Issue
    ... MFC, COM dll, COM ocx, COM server, Windows static lib and windows dynamic ... It is also showing some of the memory leak in the MFC dlls. ... We are measuring the Private bytes for the application using Sysinternals ...
    (microsoft.public.vc.debugger)
  • Re: Server is unable to allocate memory from the System Paged Pool
    ... Jerold Schulman wrote: ... > My guesss is a paged pool memory leak. ... > of a Memory Leak in the Daprotim.sys File" ... > Displayed on the Terminal Server" ...
    (microsoft.public.win2000.general)
  • Re: Server is unable to allocate memory from the System Paged Pool
    ... Jerold Schulman wrote: ... > My guesss is a paged pool memory leak. ... > of a Memory Leak in the Daprotim.sys File" ... > Displayed on the Terminal Server" ...
    (microsoft.public.windows.server.general)
Loading