Sign in with Microsoft
Sign in or create an account.
Hello,
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.

Important Your computer may crash after you apply the hotfix that is dated April 22, 2011. And you receive DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) error in the memory dump file. To resolve the issue, install the hotfix that is dated January 11, 2013.

Symptoms

When you connect to back-end databases by using a Windows Test Technologies (WTT) application on a computer that is running Windows 7 or Windows Server 2008 R2, you may receive an error message that resembles the following:

A transport-level error has occurred when receiving results from the server.

Provider: TCP Provider

Error: 0 - The semaphore timeout period has expired.

Notes

  • The WTT application uses an IPsec connection to the back-end databases.

  • This issue recovers after you retry the connection several times.

Cause

This issue occurs because the packet size of all successive IPsec traffic is larger than the original link maximum transmission unit (MTU). When this issue occurs, the operating systems have to complete the Transmission Control Protocol (TCP) handshake in clear text before the IPsec main mode and the quick mode security associations (SAs) are established.

TCP queries the maximum segment size (MSS) to use for each TCP segment and subtracts the IPsec overhead when the TCP handshake occurs or when changes occur later in the network. Then, the main mode or the quick mode process is complete (it takes 63 seconds to complete, according to the RFC). And, the encapsulation mode of the main mode or quick mode SAs that are established at first for the TCP session are updated to ESP encapsulation mode. Unfortunately, the network does not consider the mid-stream traffic that is updated from clear text to ESP encapsulation to be changes, and the current MSS is not updated. Therefore, all successive mid-stream traffic that is IPsec-secured cannot travel in the network layer.

Note When two computers start a TCP session for some unicast traffic, the initial TCP handshake may complete in clear text before the necessary main mode and quick mode negotiations are complete. This behavior occurs if one or both of the computers use a boundary policy such as the IPsec request inbound mode. Both main mode and quick mode SAs must be established before a TCP session can be secured by using the appropriate encapsulation method.

Resolution

This hotfix is also available at Microsoft Update Catalog.

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:

http://support.microsoft.com/contactus/?ws=supportNote 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 7

  • Windows 7 Service Pack 1 (SP1)

  • Windows Server 2008 R2

  • Windows Server 2008 R2 Service Pack 1 (SP1)

For more information about how to obtain a Windows 7 or a Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

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:

    Version

    Product

    Milestone

    Service branch

    6.1.760
    0.21xxx

    Windows 7 and Windows Server 2008 R2

    RTM

    LDR

    6.1.760
    1.22xxx

    Windows 7 and Windows Server 2008 R2

    SP1

    LDR

  • 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 Server 2008 R2 and for Windows 7" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. 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 name

File version

File size

Date

Time

Platform

Netio.sys

6.1.7601.22215

240,488

11-Jan-2013

12:34

x86

Fwpkclnt.sys

6.1.7600.21422

187,240

11-Jan-2013

12:44

x86

Tcpip.sys

6.1.7600.21422

1,303,912

11-Jan-2013

12:44

x86

Fwpkclnt.sys

6.1.7601.22215

187,752

11-Jan-2013

12:34

x86

Tcpip.sys

6.1.7601.22215

1,308,520

11-Jan-2013

12:34

x86

For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Netio.sys

6.1.7601.22215

376,664

11-Jan-2013

13:34

x64

Fwpkclnt.sys

6.1.7600.21422

287,576

11-Jan-2013

13:47

x64

Tcpip.sys

6.1.7600.21422

1,876,824

11-Jan-2013

13:47

x64

Fwpkclnt.sys

6.1.7601.22215

288,088

11-Jan-2013

13:33

x64

Tcpip.sys

6.1.7601.22215

1,901,400

11-Jan-2013

13:34

x64

For all supported IA-64-based versions of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Netio.sys

6.1.7601.22215

711,000

11-Jan-2013

12:34

IA-64

Fwpkclnt.sys

6.1.7600.21422

482,152

11-Jan-2013

12:48

IA-64

Tcpip.sys

6.1.7600.21422

3,811,176

11-Jan-2013

12:48

IA-64

Fwpkclnt.sys

6.1.7601.22215

482,136

11-Jan-2013

12:34

IA-64

Tcpip.sys

6.1.7601.22215

3,821,912

11-Jan-2013

12:34

IA-64

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 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 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7

File name

Update.mum

File version

Not Applicable

File size

2,773

Date (UTC)

11-Jan-2013

Time (UTC)

18:56

Platform

Not Applicable

File name

X86_772ef2ae306e7d6ce2c27660597041ee_31bf3856ad364e35_6.1.7600.21422_none_d5ad0c299d550f24.manifest

File version

Not Applicable

File size

702

Date (UTC)

11-Jan-2013

Time (UTC)

18:56

Platform

Not Applicable

File name

X86_9fe892571c7353ca774f18418c006c3a_31bf3856ad364e35_6.1.7601.22215_none_d8cb17f6658863cf.manifest

File version

Not Applicable

File size

1,054

Date (UTC)

11-Jan-2013

Time (UTC)

18:56

Platform

Not Applicable

File name

X86_microsoft-windows-netio-infrastructure_31bf3856ad364e35_6.1.7601.22215_none_592d55762cac7e90.manifest

File version

Not Applicable

File size

2,540

Date (UTC)

11-Jan-2013

Time (UTC)

12:59

Platform

Not Applicable

File name

X86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.21422_none_b3bbcd22e0a99c27.manifest

File version

Not Applicable

File size

3,834

Date (UTC)

11-Jan-2013

Time (UTC)

13:06

Platform

Not Applicable

File name

X86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7601.22215_none_b5affaf2ddc53827.manifest

File version

Not Applicable

File size

3,834

Date (UTC)

11-Jan-2013

Time (UTC)

13:01

Platform

Not Applicable

Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

File name

Amd64_0811608c1cf91ce06b0b126a1b93d606_31bf3856ad364e35_6.1.7601.22215_none_abbef7b2926824fa.manifest

File version

Not Applicable

File size

1,060

Date (UTC)

11-Jan-2013

Time (UTC)

18:56

Platform

Not Applicable

File name

Amd64_24884c43489febf8afded71874ee5d4b_31bf3856ad364e35_6.1.7601.22215_none_80d85124aa54c3f8.manifest

File version

Not Applicable

File size

712

Date (UTC)

11-Jan-2013

Time (UTC)

18:56

Platform

Not Applicable

File name

Amd64_af823d71ed07851f28c41336817f1536_31bf3856ad364e35_6.1.7601.22215_none_69b2d91b3570c3af.manifest

File version

Not Applicable

File size

1,414

Date (UTC)

11-Jan-2013

Time (UTC)

18:56

Platform

Not Applicable

File name

Amd64_e4250fc8c41c65ef7dcf2403b4822036_31bf3856ad364e35_6.1.7600.21422_none_c1ea0c49b430bdd2.manifest

File version

Not Applicable

File size

706

Date (UTC)

11-Jan-2013

Time (UTC)

18:56

Platform

Not Applicable

File name

Amd64_microsoft-windows-netio-infrastructure_31bf3856ad364e35_6.1.7601.22215_none_b54bf0f9e509efc6.manifest

File version

Not Applicable

File size

2,542

Date (UTC)

11-Jan-2013

Time (UTC)

14:01

Platform

Not Applicable

File name

Amd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.21422_none_0fda68a699070d5d.manifest

File version

Not Applicable

File size

3,838

Date (UTC)

11-Jan-2013

Time (UTC)

14:13

Platform

Not Applicable

File name

Amd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7601.22215_none_11ce96769622a95d.manifest

File version

Not Applicable

File size

3,838

Date (UTC)

11-Jan-2013

Time (UTC)

14:05

Platform

Not Applicable

File name

Update.mum

File version

Not Applicable

File size

4,059

Date (UTC)

11-Jan-2013

Time (UTC)

18:56

Platform

Not Applicable

File name

Wow64_microsoft-windows-netio-infrastructure_31bf3856ad364e35_6.1.7601.22215_none_bfa09b4c196ab1c1.manifest

File version

Not Applicable

File size

1,166

Date (UTC)

11-Jan-2013

Time (UTC)

12:45

Platform

Not Applicable

Additional files for all supported IA-64-based versions of Windows Server 2008 R2

File name

Ia64_33feb5022fba2b3de5db53014d602ac0_31bf3856ad364e35_6.1.7600.21422_none_046d916ea3d0b587.manifest

File version

Not Applicable

File size

704

Date (UTC)

11-Jan-2013

Time (UTC)

18:56

Platform

Not Applicable

File name

Ia64_9ae8c2056cff4c7fd7a7c09eb8102cdc_31bf3856ad364e35_6.1.7601.22215_none_1be9ba88a13f1f2d.manifest

File version

Not Applicable

File size

1,411

Date (UTC)

11-Jan-2013

Time (UTC)

18:56

Platform

Not Applicable

File name

Ia64_microsoft-windows-netio-infrastructure_31bf3856ad364e35_6.1.7601.22215_none_592ef96c2caa878c.manifest

File version

Not Applicable

File size

2,541

Date (UTC)

11-Jan-2013

Time (UTC)

13:55

Platform

Not Applicable

File name

Ia64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.21422_none_b3bd7118e0a7a523.manifest

File version

Not Applicable

File size

3,836

Date (UTC)

11-Jan-2013

Time (UTC)

14:09

Platform

Not Applicable

File name

Ia64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7601.22215_none_b5b19ee8ddc34123.manifest

File version

Not Applicable

File size

3,836

Date (UTC)

11-Jan-2013

Time (UTC)

13:58

Platform

Not Applicable

File name

Update.mum

File version

Not Applicable

File size

1,947

Date (UTC)

11-Jan-2013

Time (UTC)

18:56

Platform

Not Applicable

File name

Wow64_microsoft-windows-netio-infrastructure_31bf3856ad364e35_6.1.7601.22215_none_bfa09b4c196ab1c1.manifest

File version

Not Applicable

File size

1,166

Date (UTC)

11-Jan-2013

Time (UTC)

12:45

Platform

Not Applicable

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!

×