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.

You receive a stop error after you enable the RequireinClearout mode on an IPv6 network on 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:

  • A computer is running Windows Server 2008 R2 or Windows 7.
  • The IPSec tunnel is configured on a network by using IPv6 transition technologies, such as Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) or IPv6 over IPv4 (6to4).
  • The RequireinClearout mode is enabled on the IPSec tunnel.

    Note This option is only valid on computers that are running Windows 7 or Windows Server 2008 R2.
In this scenario, the computer restarts unexpectedly and you receive the following error message:

0x000000D1 (parameter1, parameter2, parameter3, parameter4)
DRIVER_IRQL_NOT_LESS_OR_EQUAL


Notes
  • The four parameters in this error message vary. This depends on the configuration of the computer.
  • Not all " 0x000000D1" Stop error codes are caused by this problem.

↑ Back to the top


Cause

When an outgoing clear text packet is sent by using the IPSec tunnel, an access violation occurs. This behavior triggers the error message that is mentioned in the "Symptoms" section.

↑ 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 Web site: 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, the computer must be running one of the following operating systems:
  • Windows Server 2008 R2
  • Windows 7

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfix.

File information

The 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 2008 R2 and Windows 7 file information note
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows Server 2008 R2 and of Windows 7
File nameFile versionFile sizeDateTimePlatform
Fwpkclnt.sys6.1.7600.16385187,47214-Jul-200901:20x86
Tcpip.sys6.1.7600.205641,285,20802-Nov-200907:08x86
For all supported x64-based versions of Windows Server 2008 R2 and of Windows 7
File nameFile versionFile sizeDateTimePlatform
Fwpkclnt.sys6.1.7600.16385288,33614-Jul-200901:47x64
Tcpip.sys6.1.7600.205641,897,56002-Nov-200907:46x64
For all supported Itanium-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Fwpkclnt.sys6.1.7600.16385482,89614-Jul-200901:58IA-64
Tcpip.sys6.1.7600.205643,774,53602-Nov-200906:30IA-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 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 Server 2008 R2 and of Windows 7

File nameFile versionFile sizeDateTimePlatform
Package_for_kb977067_rtm~31bf3856ad364e35~x86~~6.1.2.0.mumNot Applicable1,94703-Nov-200920:05Not Applicable
X86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.20564_none_b392a6b4e0c8221f.manifestNot Applicable3,78003-Nov-200920:07Not Applicable
Additional files for all supported x64-based versions of Windows Server 2008 R2 and of Windows 7

File nameFile versionFile sizeDateTimePlatform
Amd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.20564_none_0fb1423899259355.manifestNot Applicable3,78403-Nov-200920:09Not Applicable
Package_for_kb977067_rtm~31bf3856ad364e35~amd64~~6.1.2.0.mumNot Applicable2,18103-Nov-200920:05Not Applicable
Additional files for all supported Itanium-based versions of Windows Server 2008 R2

File nameFile versionFile sizeDateTimePlatform
Ia64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.20564_none_b3944aaae0c62b1b.manifestNot Applicable3,78203-Nov-200920:05Not Applicable
Package_for_kb977067_rtm~31bf3856ad364e35~ia64~~6.1.2.0.mumNot Applicable1,68303-Nov-200920:05Not Applicable


↑ Back to the top


References

For more information about the RequireinClearout mode, visit the following Microsoft Web site:

↑ Back to the top


Keywords: kbmdd, kbautohotfix, kbqfe, kbexpertiseinter, kbhotfixserver, kbsurveynew, kb

↑ Back to the top

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