Microsoft KB Archive/927493

From BetaArchive Wiki
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

Article ID: 927493

Article Last Modified on 10/11/2007



APPLIES TO

  • Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
  • Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
  • Microsoft Windows Server 2003, Datacenter x64 Edition
  • Microsoft Windows Server 2003, Enterprise x64 Edition
  • Microsoft Windows Server 2003, Standard x64 Edition
  • Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise Edition
  • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
  • Microsoft Windows Server 2003, Web Edition
  • Microsoft Windows XP Professional x64 Edition



SYMPTOMS

Under certain circumstances in Microsoft Windows Server 2003, the heavy use of Winsock programs may exhaust the system's non-paged pool memory. 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 experience various error messages and poor performance. Additionally, the system may stop responding (hang).

CAUSE

If 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 non-paged pool memory.

RESOLUTION

This update has been superseded by another update. For more information about the replacement fix, click the following article number to view the article in the Microsoft Knowledge Base:

931311 The heavy use of Winsock programs may exhaust the "nonpaged pool memory" of a Windows Server 2003-based computer


WORKAROUND

To work around this issue, do not use MSG_OOB data in the Winsock program. Use a separate socket for urgent data.

STATUS

Microsoft 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 New file naming schema for Microsoft Windows software update packages


For more information, 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


Technical support for x64-based versions of Microsoft Windows

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

For product information about x64-based versions of Microsoft Windows Server 2003, visit the following Microsoft Web site:


Additional query words: Winx64 Windowsx64 64bit 64-bit Event ID: 2019 Afd.sys MSG_OOB

Keywords: kbbug kbfix kbqfe kbprb kbexpertiseadvanced kbhotfixserver kbwinserv2003presp2fix KB927493