"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 security

Applies To
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 Standard Windows Server 2008 Standard without Hyper-V Windows Server 2008 for Itanium-Based Systems Windows Server 2008 Foundation Windows Server 2008 Web Edition Windows Vista Business Windows Vista Business 64-bit Edition Windows Vista Enterprise Windows Vista Enterprise 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 Windows 7 Enterprise Windows 7 Home Basic Windows 7 Home Premium Windows 7 Professional Windows 7 Ultimate Windows Server 2008 R2 Datacenter Windows Server 2008 R2 Enterprise Windows Server 2008 R2 for Itanium-Based Systems Windows Server 2008 R2 Foundation Windows Server 2008 R2 Standard

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

Symptoms

Consider the following scenario:

  • You join a computer to a network. The computer is running one of the following operating systems:

    • Windows Vista
    • Windows Server 2008
    • Windows 7
    • Windows Server 2008 R2
  • The network is configured to use Internet Protocol security (IPsec) network address translation traversal (NAT-T) security.

  • You use IPsec to communicate with another computer in the network.

In this scenario, you randomly receive a Stop error message that resembles the following, and then the computer restarts:

Note

STOP 0x000000C2 (parameter1, parameter2, parameter3, parameter4)

Notes

  • This Stop error describes a BAD_POOL_CALLER issue.
  • The four parameters in this error message vary, depending on the configuration of the computer.
  • Not all "0x000000C2" Stop errors are caused by this issue.

Cause

This issue occurs because of a race condition in the Tcpip.sys driver. The Tcpip.sys driver does not handle the reference count of an object correctly. Therefore, a thread tries to free an object that was already freed by another thread, and the Windows triggers a Stop error.

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:

http:⁠//support.microsoft.com/contactus/?ws=support 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 Vista Service Pack 2 (SP2)
  • Windows Server 2008 Service Pack 2 (SP2)
  • 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 Vista service pack, click the following article number to view the article in the Microsoft Knowledge Base:

935791 How 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:

968849 How to obtain the latest service pack for Windows Server 2008

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 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.

    Version Product SR_Level Service branch
    6.0.600
    2.
    22xxx
    Windows Vista and Windows Server 2008 SP2 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 and for Windows Vista" 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 Server 2008 and of Windows Vista

File name File version File size Date Time Platform
Tcpipreg.sys 6.0.6002.22748 31,232 28-Nov-2011 13:42 x86
Tcpip.sys 6.0.6002.22748 913,280 28-Nov-2011 19:53 x86

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

File name File version File size Date Time Platform
Tcpipreg.sys 6.0.6002.22748 40,448 28-Nov-2011 13:58 x64
Tcpip.sys 6.0.6002.22748 1,423,232 28-Nov-2011 19:50 x64

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

File name File version File size Date Time Platform
Tcpipreg.sys 6.0.6002.22748 80,896 28-Nov-2011 14:03 IA-64
Tcpip.sys 6.0.6002.22748 2,968,960 28-Nov-2011 19:46 IA-64

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, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.

    Version Product SR_Level Service branch
    6.1.760
    0.
    21xxx
    Windows 7 and Windows Server 2008 R2 RTM LDR
    6.1.760
    1.
    21xxx
    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
Fwpkclnt.sys 6.1.7600.21111 187,248 21-Dec-2011 05:43 x86
Tcpip.sys 6.1.7600.21111 1,302,384 21-Dec-2011 05:44 x86
Fwpkclnt.sys 6.1.7601.21881 187,760 21-Dec-2011 06:55 x86
Tcpip.sys 6.1.7601.21881 1,303,920 21-Dec-2011 06:55 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
Fwpkclnt.sys 6.1.7600.21111 288,112 21-Dec-2011 06:32 x64
Tcpip.sys 6.1.7600.21111 1,878,896 21-Dec-2011 06:32 x64
Fwpkclnt.sys 6.1.7601.21881 288,624 21-Dec-2011 06:35 x64
Tcpip.sys 6.1.7601.21881 1,901,424 21-Dec-2011 06:35 x64

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

File name File version File size Date Time Platform
Fwpkclnt.sys 6.1.7600.21111 482,672 21-Dec-2011 05:21 IA-64
Tcpip.sys 6.1.7600.21111 3,804,528 21-Dec-2011 05:21 IA-64
Fwpkclnt.sys 6.1.7601.21881 483,184 21-Dec-2011 05:25 IA-64
Tcpip.sys 6.1.7601.21881 3,807,088 21-Dec-2011 05:25 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 Vista and for Windows Server 2008

Additional files for all supported x86-based versions of Windows Vista and of Windows Server 2008

File name X86_54788c253feb43c64308f2c4b7a9ea73_31bf3856ad364e35_6.0.6002.22748_none_4e1ead774fcacebd.manifest
File version Not applicable
File size 702
Date (UTC) 28-Nov-2011
Time (UTC) 20:00
Platform Not applicable
File name X86_9c91b4c7ee744fff6a29fac46d1e4d00_31bf3856ad364e35_6.0.6002.22748_none_1f951b94ca4a29cd.manifest
File version Not applicable
File size 717
Date (UTC) 28-Nov-2011
Time (UTC) 20:00
Platform Not applicable
File name X86_microsoft-windows-l..istry-support-tcpip_31bf3856ad364e35_6.0.6002.22748_none_886a18701bca1055.manifest
File version Not applicable
File size 4,845
Date (UTC) 28-Nov-2011
Time (UTC) 16:43
Platform Not applicable
File name X86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.0.6002.22748_none_b56af4bb7cc356bf.manifest
File version Not applicable
File size 6,762
Date (UTC) 28-Nov-2011
Time (UTC) 20:00
Platform Not applicable

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

File name Amd64_5523788a6d97eaa05d5fc71743632d37_31bf3856ad364e35_6.0.6002.22748_none_a7a6de8e6124d886.manifest
File version Not applicable
File size 721
Date (UTC) 28-Nov-2011
Time (UTC) 20:00
Platform Not applicable
File name Amd64_ee8ef99ee182cbf17ce3a528a9a1c3e1_31bf3856ad364e35_6.0.6002.22748_none_d38f98b9f4fb336c.manifest
File version Not applicable
File size 706
Date (UTC) 28-Nov-2011
Time (UTC) 20:00
Platform Not applicable
File name Amd64_microsoft-windows-l..istry-support-tcpip_31bf3856ad364e35_6.0.6002.22748_none_e488b3f3d427818b.manifest
File version Not applicable
File size 5,122
Date (UTC) 28-Nov-2011
Time (UTC) 15:56
Platform Not applicable
File name Amd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.0.6002.22748_none_1189903f3520c7f5.manifest
File version Not applicable
File size 6,784
Date (UTC) 28-Nov-2011
Time (UTC) 20:00
Platform Not applicable

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

File name Ia64_dc5287eb47036475b4a2262f83ff5ffe_31bf3856ad364e35_6.0.6002.22748_none_7dc28d72f01d3658.manifest
File version Not applicable
File size 1,066
Date (UTC) 28-Nov-2011
Time (UTC) 20:00
Platform Not applicable
File name Ia64_microsoft-windows-l..istry-support-tcpip_31bf3856ad364e35_6.0.6002.22748_none_886bbc661bc81951.manifest
File version Not applicable
File size 5,118
Date (UTC) 28-Nov-2011
Time (UTC) 15:33
Platform Not applicable
File name Ia64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.0.6002.22748_none_b56c98b17cc15fbb.manifest
File version Not applicable
File size 6,773
Date (UTC) 28-Nov-2011
Time (UTC) 20:00
Platform Not applicable

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) 22-Dec-2011
Time (UTC) 00:00
Platform Not Applicable
File name X86_40197c1530b273e42ba78cb01a40e177_31bf3856ad364e35_6.1.7600.21111_none_b6c6c9e86ca32fec.manifest
File version Not Applicable
File size 702
Date (UTC) 22-Dec-2011
Time (UTC) 00:00
Platform Not Applicable
File name X86_a0fb3955ed6f6490e9f8a4aa7f97d63f_31bf3856ad364e35_6.1.7601.21881_none_9b1a54b0cb1d28de.manifest
File version Not Applicable
File size 702
Date (UTC) 22-Dec-2011
Time (UTC) 00:00
Platform Not Applicable
File name X86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.21111_none_b3c59712e0a26f6a.manifest
File version Not Applicable
File size 3,834
Date (UTC) 21-Dec-2011
Time (UTC) 06:06
Platform Not Applicable
File name X86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7601.21881_none_b5606c82de016bab.manifest
File version Not Applicable
File size 3,834
Date (UTC) 21-Dec-2011
Time (UTC) 07:30
Platform Not Applicable

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

File name Amd64_1b6c0a0d2c2851fe1f6dec522eb8dfa2_31bf3856ad364e35_6.1.7600.21111_none_06525b0a8a838442.manifest
File version Not Applicable
File size 706
Date (UTC) 22-Dec-2011
Time (UTC) 00:01
Platform Not Applicable
File name Amd64_ca0bef94e79c5860eb31951e273fbb88_31bf3856ad364e35_6.1.7601.21881_none_fc9bfc8620b821d8.manifest
File version Not Applicable
File size 706
Date (UTC) 22-Dec-2011
Time (UTC) 00:01
Platform Not Applicable
File name Amd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.21111_none_0fe4329698ffe0a0.manifest
File version Not Applicable
File size 3,838
Date (UTC) 21-Dec-2011
Time (UTC) 07:05
Platform Not Applicable
File name Amd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7601.21881_none_117f0806965edce1.manifest
File version Not Applicable
File size 3,838
Date (UTC) 21-Dec-2011
Time (UTC) 08:11
Platform Not Applicable
File name Update.mum
File version Not Applicable
File size 3,215
Date (UTC) 22-Dec-2011
Time (UTC) 00:01
Platform Not Applicable

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

File name Ia64_4d8b455c61161755f1a3ea5ed704fdc0_31bf3856ad364e35_6.1.7601.21881_none_4ab8eb4996168cea.manifest
File version Not Applicable
File size 704
Date (UTC) 22-Dec-2011
Time (UTC) 00:00
Platform Not Applicable
File name Ia64_f9f56d442a14ea371ac241618aee55cc_31bf3856ad364e35_6.1.7600.21111_none_2ba123660fe32bb5.manifest
File version Not Applicable
File size 704
Date (UTC) 22-Dec-2011
Time (UTC) 00:00
Platform Not Applicable
File name Ia64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.21111_none_b3c73b08e0a07866.manifest
File version Not Applicable
File size 3,836
Date (UTC) 21-Dec-2011
Time (UTC) 07:03
Platform Not Applicable
File name Ia64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7601.21881_none_b5621078ddff74a7.manifest
File version Not Applicable
File size 3,836
Date (UTC) 21-Dec-2011
Time (UTC) 08:03
Platform Not Applicable
File name Update.mum
File version Not Applicable
File size 1,947
Date (UTC) 22-Dec-2011
Time (UTC) 00:00
Platform Not Applicable