Select the product you need help with
The heavy use of Winsock programs may exhaust the "nonpaged pool memory" of a Windows Server 2003-based computerArticle ID: 931311 - View products that this article applies to. On This PageSYMPTOMSThe heavy use of Winsock programs may exhaust the "nonpaged pool memory" of a Microsoft Windows Server 2003-based computer. This behavior is likely to occur if the Winsock program is dealing with both "Out-of-Band (MSG_OOB) traffic" and "standard TCP traffic." In this situation, you may receive various error messages. Also, you may experience poor performance. Additionally, the system may stop responding (hang). CAUSEIf the Winsock program does not read the incoming data from Winsock, the "AfdB pool tag" may buffer more data than is optimal. This behavior may exhaust all available "nonpaged pool memory." RESOLUTIONHotfix informationA 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: http://support.microsoft.com/contactus/?ws=support 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.
(http://support.microsoft.com/contactus/?ws=support)
PrerequisitesTo apply this hotfix, the computer must be running one of the following operating systems:
Restart requirementYou must restart your computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace a previously released hotfix.File informationThe 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 item in Control Panel.Windows Server 2003, x86-based versionsCollapse this table
Windows Server 2003, x64-based versionsCollapse this table
Windows Server 2003, Itanium-based versionsCollapse this table
WORKAROUNDTo work around this problem, do not use MSG_OOB data in the Winsock program. Use a separate socket for urgent data. STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATION
For more information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base: 816915
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/816915/
)
New file naming schema for Microsoft Windows software update packages 824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates Technical support for x64-based versions of Microsoft WindowsIf your hardware came with a Microsoft Windows x64 edition already installed, your hardware manufacturer provides technical support and assistance for the Windows x64 edition. In this case, your hardware manufacturer provides support because a Windows x64 edition was included with your hardware. Your hardware manufacturer might have customized the Windows x64 edition installation by using unique components. Unique components might include specific device drivers or might include optional settings to maximize the performance of the hardware. Microsoft will provide reasonable-effort assistance if you need technical help with a Windows x64 edition. However, you might have to contact your manufacturer directly. Your manufacturer is best qualified to support the software that your manufacturer installed on the hardware. If you purchased a Windows x64 edition such as a Microsoft Windows Server 2003 x64 edition separately, contact Microsoft for technical support.For product information about Microsoft Windows XP Professional x64 Edition, visit the following Microsoft Web site: http://www.microsoft.com/windowsxp/64bit/default.mspx
For product information about x64-based versions of Microsoft Windows Server 2003, visit the following Microsoft Web site:
(http://www.microsoft.com/windowsxp/64bit/default.mspx)
http://www.microsoft.com/windowsserver2003/64bit/x64/editions.mspx
(http://www.microsoft.com/windowsserver2003/64bit/x64/editions.mspx)
PropertiesArticle ID: 931311 - Last Review: October 11, 2007 - Revision: 1.8 APPLIES TO
| Article Translations |
Back to the top
