Event 2020 is logged and your Windows Server 2003-based file server stops responding

Applies to: Microsoft Windows Server 2003 Web EditionMicrosoft Windows Server 2003 Standard Edition (32-bit x86)Microsoft Windows Server 2003 Enterprise Edition (32-bit x86) More

Symptoms


Your Microsoft Windows Server 2003-based computer that functions as a file server stops responding. An event that is similar to the following event is recorded in the System log:

If you click Words in the Event Properties dialog box, you see information that is similar to the following:
Data:

0000: 00040000 00540001 00000000 c00007e4

0010: 00000000 c000009a 00000000 00000000

0020: 00000000 00000000 0000000b

Cause


This problem occurs if many files are copied and deleted from a Linux client that is running the Samba program to a mounted file share on a Windows Server 2003-based computer. During the file copy and delete operation, the Windows Server 2003-based computer leaks system paged pool memory. If the system paged pool memory is exhausted, the Windows Server 2003-based computer may stop responding. When the Windows Server 2003 computer stops responding, you must restart the computer.

Resolution


Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

No prerequisites are required.

Restart requirement

You must restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Windows Server 2003, 32-bit editions


Date Time Version Size File name
--------------------------------------------------------------
18-Oct-2004 07:20 5.2.3790.223 355,840 Srv.sys

Windows Server 2003, 64-bit editions


Date Time Version Size File name
--------------------------------------------------------------
18-Oct-2004 08:21 5.2.3790.223 994,304 Srv.sys

Status


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information


The Data Words information that is included in the event 2020 corresponds to the following error codes.
  • c00007e4 corresponds to EVENT_SRV_NO_PAGED_POOL.
  • c000009a corresponds to STATUS_INSUFFICIENT_RESOURCES.
To verify that you are experiencing the problem that is described in this article, use Task Scheduler to run the Memsnap.exe tool at certain intervals. For example, you can configure the memsnap -p c:\temp\memsnap.log command to run every hour by using Task Scheduler.


Note The Memsnap.exe tool is located in the Support\Tools folder of your Windows Server 2003 CD. The Memsnap tool records system memory usage to the Memsnap.log log file.



When you view the Memsnap.log file, locate the "Strg Nonp" tag to determine whether you have this problem.



For more information about the Memsnap.exe tool, see the Support Tools Help that is included with the Windows Server 2003 Support Tools.

Important By default, pool tagging is turned on in Windows Server 2003. Therefore, you do not have to click the Enable Pool Tagging option in the Gflags.exe tool before you use the Memsnap.exe utility.



Alternatively, you can use the Schtasks.exe tool to create, delete, query, change, run, and end scheduled tasks on a local or remote computer.
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.

For additional information about the standard terminology that is used to describe Microsoft software updates, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

References


312362 Server is unable to allocate memory from the system paged pool

244139 Windows feature allows a Memory.dmp file to be generated with the keyboard