Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

An application or service that uses Winsock API or Winsock Kernel API may randomly stop responding in Windows Server 2008 R2 or in Windows 7


View products that this article applies to.

Not sure if this is the right fix? We've added this issue to our memory dump diagnostic which can confirm.

↑ Back to the top


Symptoms

Consider the following scenario:
  • You have a computer that is running Windows Server 2008 R2 or Windows 7.
  • An application or service uses Winsock API or Winsock Kernel API to make network connections on the computer.
In this scenario, you experience one or more of the following symptoms:
  • The application or service randomly stops responding.
  • A number of connections appear in the "CLOSE WAIT" state in netstat output and remain in this state until the system is rebooted.
  • The application or service consumes an unusually high number of handles.
  • The System process consumes an unusually high number of handles in cases where System Center Configuration Manager 2007 client push is enabled. Disabling the Client Push feature of SCCM, stops or minimizes the increase in handle count if the System process.

↑ Back to the top


Cause

This issue occurs because of a race condition in the TCP/IP driver (tcpip.sys).

↑ Back to the top


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 the problem described in this article. 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 website: 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

To apply this hotfix, you must be running one of the following operating systems:
  • Windows Server 2008 R2
  • Windows Server 2008 R2 Service Pack 1 (SP1)
  • Windows 7
  • Windows 7 Service Pack 1 (SP1)

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows 7 and Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    VersionProductMilestoneService branch
    6.1.760
    0. 20xxx
    Windows Server 2008 R2 and Windows 7RTMLDR
    6.0.760
    1. 21xxx
    Windows Server 2008 R2 and Windows 7SP1LDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows 7 and for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are very important for maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 7
File nameFile versionFile sizeDateTimePlatform
Fwpkclnt.sys6.1.7600.20882187,26417-Jan-201105:42x86
Tcpip.sys6.1.7600.208821,298,30417-Jan-201105:43x86
Fwpkclnt.sys6.1.7601.21642187,77615-Jan-201105:41x86
Tcpip.sys6.1.7601.216421,299,32815-Jan-201105:41x86
For all supported x64-based versions of Windows Server 2008 R2 and of Windows 7
File nameFile versionFile sizeDateTimePlatform
Fwpkclnt.sys6.1.7600.20882288,12817-Jan-201106:23x64
Tcpip.sys6.1.7600.208821,893,24817-Jan-201106:23x64
Fwpkclnt.sys6.1.7601.21642288,64015-Jan-201106:28x64
Tcpip.sys6.1.7601.216421,928,06415-Jan-201106:27x64
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Fwpkclnt.sys6.1.7600.20882482,68817-Jan-201105:20IA-64
Tcpip.sys6.1.7600.208823,800,96017-Jan-201105:20IA-64
Fwpkclnt.sys6.1.7601.21642483,20015-Jan-201105:19IA-64
Tcpip.sys6.1.7601.216423,802,49615-Jan-201105:19IA-64

↑ Back to the top


Status

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

↑ Back to the top


More Information

For more information about Winsock Kernel, visit the following Microsoft Developer Network (MSDN) website:For more information about software update terminology, 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

Additional file information

Additional file information for Windows Server 2008 R2 and for Windows 7

Additional files for all supported x86-based versions of Windows 7
File nameX86_0fdfdd10780d419a879ef4f39eca5d89_31bf3856ad364e35_6.1.7600.20882_none_6493058edd08a1c2.manifest
File versionNot applicable
File size702
Date (UTC)17-Jan-2011
Time (UTC)21:13
PlatformNot applicable
File nameX86_5123ae99da51860ff683763bcdfc21c5_31bf3856ad364e35_6.1.7601.21642_none_32901e7002ff247d.manifest
File versionNot applicable
File size702
Date (UTC)17-Jan-2011
Time (UTC)21:13
PlatformNot applicable
File nameX86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.20882_none_b37b0bfae0da1ec8.manifest
File versionNot applicable
File size3,834
Date (UTC)17-Jan-2011
Time (UTC)06:13
PlatformNot applicable
File nameX86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7601.21642_none_b58ca8b0dde01af0.manifest
File versionNot applicable
File size3,834
Date (UTC)15-Jan-2011
Time (UTC)06:08
PlatformNot applicable
Additional files for all supported x64-based versions of Windows Server 2008 R2 and of Windows 7
File nameAmd64_7284bed783cc23a7730ae6010ac715e7_31bf3856ad364e35_6.1.7600.20882_none_af6b2b20876e52f4.manifest
File versionNot applicable
File size706
Date (UTC)17-Jan-2011
Time (UTC)21:13
PlatformNot applicable
File nameAmd64_7afddb586db644908dc57c02639a90d1_31bf3856ad364e35_6.1.7601.21642_none_21da1e3203721710.manifest
File versionNot applicable
File size706
Date (UTC)17-Jan-2011
Time (UTC)21:13
PlatformNot applicable
File nameAmd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.20882_none_0f99a77e99378ffe.manifest
File versionNot applicable
File size3,838
Date (UTC)17-Jan-2011
Time (UTC)07:02
PlatformNot applicable
File nameAmd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7601.21642_none_11ab4434963d8c26.manifest
File versionNot applicable
File size3,838
Date (UTC)15-Jan-2011
Time (UTC)07:05
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File nameIa64_4e7c5db0811366173e72456abacea3fe_31bf3856ad364e35_6.1.7600.20882_none_4b1e883fd12a3313.manifest
File versionNot applicable
File size704
Date (UTC)17-Jan-2011
Time (UTC)21:13
PlatformNot applicable
File nameIa64_9e78ed95e3463fbe9c2d610c8afc778e_31bf3856ad364e35_6.1.7601.21642_none_7b69a5f7c475c36e.manifest
File versionNot applicable
File size704
Date (UTC)17-Jan-2011
Time (UTC)21:13
PlatformNot applicable
File nameIa64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.20882_none_b37caff0e0d827c4.manifest
File versionNot applicable
File size3,836
Date (UTC)17-Jan-2011
Time (UTC)06:48
PlatformNot applicable
File nameIa64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7601.21642_none_b58e4ca6ddde23ec.manifest
File versionNot applicable
File size3,836
Date (UTC)15-Jan-2011
Time (UTC)07:01
PlatformNot applicable
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

↑ Back to the top


Keywords: kb, kbmdd, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseadvanced

↑ Back to the top

Article Info
Article ID : 2465772
Revision : 1
Created on : 1/7/2017
Published on : 10/9/2014
Exists online : False
Views : 374