Stop code in the tcpip.sys driver on a computer that is running Windows Server 2008 R2: 0x000000D1

Article translations Article translations
Article ID: 2519644 - View products that this article applies to.
Expand all | Collapse all

On This Page

Symptoms

You receive a Stop error message in Tcpip.sys that resembles the following:
STOP: 0x000000D1 ( parameter1 , parameter2 , parameter3 , parameter4 )
DRIVER_IRQL_NOT_LESS_OR_EQUAL
Notes
  • The parameters in the Stop error message may vary, depending on the configuration of the computer.
  • Not all "0x000000D1" Stop errors are caused by this issue.

Cause

This issue occurs because the TCP/IP driver does not check whether a variable is NULL before accessing it.

When the TCP/IP driver accesses a variable that has a NULL value, a Stop error is generated.

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 this specific problem.

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, submit a request to 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:
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 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 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.
    Collapse this tableExpand this table
    VersionProductSR_LevelService branch
    6.1.760 0 . 20xxxWindows Server 2008 R2RTMLDR
    6.1.760 1 . 21xxxWindows Server 2008 R2SP1LDR
  • 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" 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 x64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Fwpkclnt.sys6.1.7600.20926288,12817-Mar-201105:19x64
Tcpip.sys6.1.7600.209261,892,73617-Mar-201105:19x64
Fwpkclnt.sys6.1.7601.21685288,64017-Mar-201105:06x64
Tcpip.sys6.1.7601.216851,927,55217-Mar-201105:06x64
For all supported IA-64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Fwpkclnt.sys6.1.7600.20926482,68817-Mar-201104:15IA-64
Tcpip.sys6.1.7600.209263,801,47217-Mar-201104:15IA-64
Fwpkclnt.sys6.1.7601.21685483,20017-Mar-201104:08IA-64
Tcpip.sys6.1.7601.216853,803,52017-Mar-201104:08IA-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 Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameAmd64_14a6a44a70aebd810bf38803f5edb331_31bf3856ad364e35_6.1.7600.20926_none_260b9f93049107f3.manifest
File versionNot applicable
File size706
Date (UTC)17-Mar-2011
Time (UTC)20:49
File nameAmd64_b7dfde7e91da46c02becde0fe368d564_31bf3856ad364e35_6.1.7601.21685_none_f78d159b4f809076.manifest
File versionNot applicable
File size706
Date (UTC)17-Mar-2011
Time (UTC)20:49
File nameAmd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.20926_none_0fde8a1499034adb.manifest
File versionNot applicable
File size3,838
Date (UTC)17-Mar-2011
Time (UTC)08:23
File nameAmd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7601.21685_none_11830562965b47ef.manifest
File versionNot applicable
File size3,838
Date (UTC)17-Mar-2011
Time (UTC)08:20
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameIa64_7394af9b4db16d6fedd0d8a0ba71b5f0_31bf3856ad364e35_6.1.7600.20926_none_1931da4718867560.manifest
File versionNot applicable
File size704
Date (UTC)17-Mar-2011
Time (UTC)20:49
File nameIa64_a31e0ddb5a2f9760ebcbbe9da2943c29_31bf3856ad364e35_6.1.7601.21685_none_75c1a67399e85d0b.manifest
File versionNot applicable
File size704
Date (UTC)17-Mar-2011
Time (UTC)20:49
File nameIa64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.20926_none_b3c19286e0a3e2a1.manifest
File versionNot applicable
File size3,836
Date (UTC)17-Mar-2011
Time (UTC)08:19
File nameIa64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7601.21685_none_b5660dd4ddfbdfb5.manifest
File versionNot applicable
File size3,836
Date (UTC)17-Mar-2011
Time (UTC)08:16

Properties

Article ID: 2519644 - Last Review: December 27, 2012 - Revision: 3.0
Applies to
  • Windows Server 2008 R2 Standard
  • Windows Server 2008 R2 Enterprise
  • Windows Server 2008 R2 Datacenter
  • Windows Server 2008 R2 for Itanium-Based Systems
Keywords: 
kbautohotfix kbqfe kbhotfixserver kbfix kbsurveynew kbexpertiseinter KB2519644

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com