Assume that you install Symantec Endpoint Protection or Forefront TMG on a Windows Vista-based or Windows Server 2008-based computer that has the hotfix that is described in Microsoft Knowledge Base (KB) article 979612 or any later version of the hotfix that contains the update of the Tcpip.sys file installed. For example, assume that you install the hotfix that is described in Microsoft KB article 2553549 on a computer that is running Windows Vista or Windows Server 2008. In these situations, the computer crashes randomly. Additionally, you receive a Stop error message that resembles the following:
This Stop error describes a DRIVER_IRQL_NOT_LESS_OR_EQUAL issue.
The parameters in this Stop error message vary, depending on the configuration of the computer.
Not all "Stop 0x000000D1" errors are caused by this issue.
The version of the Tcpip.sys file in KB 979612 is 6.0.6002.22320 (LDR Branch / V1 Package). The version of the Tcpip.sys file in KB 2553549 is 6.0.6002.22643. Therefore, the KB 2553549 contains this issue.
The specific hotfixes that contain the later update of the Tcpip.sys file are listed in the "More Information" section.
This issue occurs because Transmission Control Protocol (TCP) changes the datagram that is sent from network layer unexpectedly. When network layer sends datagram to TCP, TCP returns the datagram with the same network layer header size value. After Windows Filtering Platform (WFP) processes or inspects the value of network layer header size, TCP changes the value. However, in some code paths, TCP does not revert the value of network layer header size. Therefore, the agreement between network layer and TCP is broken.
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.
To apply this hotfix, you must be running Windows Vista Service Pack 2 (SP2) or Windows Server 2008 SP2.
For more information about how to obtain a Windows Vista service pack, click the following article number to view the article in the Microsoft Knowledge Base:
935791How to obtain the latest Windows Vista service pack
For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
968849How to obtain the latest service pack for Windows Server 2008
To apply this hotfix, you do not have to make any changes to the registry.
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
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 Vista and Windows Server 2008 file information notes
Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" 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, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
6.0.600 2. 22xxx
Windows Vista and Windows Server 2008
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 Vista and for Windows Server 2008" section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to 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 Vista and of Windows Server 2008
For all supported x64-based versions of Windows Vista and of Windows Server 2008
For all supported IA-64-based versions of Windows Server 2008
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about the hotfixes that contain the later update of the Tcpip.sys file, click the following article numbers to view the articles in the Microsoft Knowledge Base:
979612 A hotfix is available that improves TCP loopback latency and UDP latency in Windows Server 2008, Windows Server 2008 R2, Windows Vista, and Windows 7
979278 Using two Windows Filtering Platform (WFP) drivers causes a computer to crash when the computer is running Windows Vista, Windows 7, or Windows Server 2008
978338 MS10-029: Vulnerability in Windows ISATAP Component could allow spoofing
981889 A Windows Filtering Platform (WFP) driver hotfix rollup package is available for Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2
979614 Description of a reliability update for the TCP Chimney Offload feature in Windows Server 2008 and in Windows Vista
982922 Data corruption occurs when you use an IPsec NAT-T connection in Windows Vista SP2 or in Windows Server 2008 SP2
978886 MS10-058: Vulnerabilities in TCP/IP could allow elevation of privilege
2470853 IGMP v1 membership report packets are sent to incorrect destinations on a computer that is running Windows Server 2008, Windows Vista, Windows 7 or Windows Server 2008 R2
2469100 Manually added route table entries are deleted unexpectedly when you delete an additional IP address in Windows Vista, in Windows 7, in Windows Server 2008 or in Windows Server 2008 R2
2553549 All the TCP/IP ports that are in a TIME_WAIT status are not closed after 497 days from system startup in Windows Vista, in Windows 7, in Windows Server 2008 and in Windows Server 2008 R2
2563894 MS11-064: Vulnerabilities in TCP/IP Stack Could Allow Denial of Service: August 9, 2011
2569391 IPv6 DAD state does not switch back to Preferred state from Deprecated state in Windows Vista, in Windows Server 2008, in Windows 7, or in Windows Server 2008 R2
2582281 Slow failover operation if no router exists between the cluster and an application server
2588516 MS11-083: Vulnerability in TCP/IP could allow remote code execution: November 8, 2011
2621067 The first-returned IP address is incorrect when you use the getaddrinfo function on a multi-homed computer that is running Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2
2635039 The remote address field is zeroed out in a completion context when a WFP callout driver calls the FwpsPendOperation0() API in Windows Vista or in Windows Server 2008
2639793 "0x000000C2" Stop error occurs when you use IPsec on a computer that is running Windows Server 2008, Windows Vista, Windows Server 2008 R2 or Windows 7 in a network that uses IPsec NAT-T
2665809 You cannot exclude ports by using the ReservedPorts registry key in Windows Server 2008 or in Windows Server 2008 R2
2688338 MS12-032: Vulnerability in TCP/IP could allow elevation of privilege: May 8, 2012
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684Description of the standard terminology that is used to describe Microsoft software updates
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.
Additional file information
Additional file information for Windows Vista and for Windows Server 2008
Additional files for all supported x86-based versions of Windows Vista and of Windows Server 2008
Windows Server 2008 Enterprise, Windows Server 2008 Enterprise without Hyper-V, Windows Server 2008 Datacenter, Windows Server 2008 Datacenter without Hyper-V, Windows Server 2008 for Itanium-Based Systems, Windows Server 2008 Foundation, Windows Server 2008 Standard, Windows Server 2008 Standard without Hyper-V, Windows Web Server 2008 R2, Windows Vista Enterprise, Windows Vista Enterprise 64-bit Edition, Windows Vista Business, Windows Vista Business 64-bit Edition, Windows Vista Home Basic, Windows Vista Home Basic 64-bit Edition, Windows Vista Home Premium, Windows Vista Home Premium 64-bit Edition, Windows Vista Starter, Windows Vista Ultimate, Windows Vista Ultimate 64-bit Edition