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.

"0x000000D1" Stop error after you install TDI drivers in Windows


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

Assume that you have a computer that is running Windows 7, Windows Server 2008 R2, or Windows Server 2008. After you install Transport Driver Interface (TDI) drivers, the computer crashes. Additionally, you receive a Stop error message that resembles the following:
Stop 0x000000D1 (Parameter1, Parameter2, Parameter3, Parameter4)
Notes

  • 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 Afd.sys file is listed as the source of this error.

↑ Back to the top


Cause

This issue occurs because a TDI endpoint structure is created and populated when a WinSock application tries to bind a socket. However, a network interrupt occurs before the TDI endpoint structure is initialized. Therefore, the Afd.sys file tries to access to uninitiated data structure, and the computer crashes.

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

Prerequisites

To apply this hotfix, you must be running Windows 7 Service Pack 1 (SP1), Windows Server 2008 R2 SP1, or Windows Server 2008 SP2.
For more information about how to obtain a Windows 7 or 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
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

Registry information

To apply this hotfix, 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:
    VersionProductMilestoneService branch
    6.1.760 1.22xxxWindows 7 and Windows 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" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very 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 nameFile versionFile sizeDateTimePlatform
Afd.sys6.1.7601.22673338,94403-May-201401:01x86
For all supported x64-based versions of Windows 7 and Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Afd.sys6.1.7601.22673496,64003-May-201401:12x64
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Afd.sys6.1.7601.226731,115,64803-May-201400:49IA-64
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.
    VersionProductSR_LevelService branch
    6.0.600
    2.
    22xxx
    Windows Server 2008SP2LDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information" 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 
File nameFile versionFile sizeDateTimePlatform
Afd.sys6.0.6002.22969273,92008-Nov-201201:57x86
For all supported x64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Afd.sys6.0.6002.22969404,99208-Nov-201202:50x64
For all supported IA-64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Afd.sys6.0.6002.22969986,11208-Nov-201201:25IA-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 7 and Windows Server 2008 R2


Additional files for all supported x86-based versions of Windows 7
File propertyValue
File nameX86_7271d6c78de2503aa89d2179c8c3289c_31bf3856ad364e35_6.1.7601.22673_none_971a7f968e23237b.manifest
File versionNot applicable
File size700
Date (UTC)03-May-2014
Time (UTC)11:45
File nameX86_microsoft-windows-winsock-core_31bf3856ad364e35_6.1.7601.22673_none_da3752aed5fe8015.manifest
File versionNot applicable
File size73,506
Date (UTC)03-May-2014
Time (UTC)06:55
Additional files for all supported x64-based versions of Windows 7 and Windows Server 2008 R2
File propertyValue
File nameAmd64_26b71a1dc63e4b3852a7dca4faf05dae_31bf3856ad364e35_6.1.7601.22673_none_fe7d9d880706afcb.manifest
File versionNot applicable
File size704
Date (UTC)03-May-2014
Time (UTC)11:45
File nameAmd64_microsoft-windows-winsock-core_31bf3856ad364e35_6.1.7601.22673_none_3655ee328e5bf14b.manifest
File versionNot applicable
File size73,510
Date (UTC)03-May-2014
Time (UTC)08:58
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File propertyValue
File nameIa64_8d8cc14e9f92a61f2d92907dda4630a0_31bf3856ad364e35_6.1.7601.22673_none_5c11bb145b31b5be.manifest
File versionNot applicable
File size702
Date (UTC)03-May-2014
Time (UTC)11:45
File nameIa64_microsoft-windows-winsock-core_31bf3856ad364e35_6.1.7601.22673_none_da38f6a4d5fc8911.manifest
File versionNot applicable
File size73,508
Date (UTC)03-May-2014
Time (UTC)08:41

Additional file information for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008
File nameX86_6122ee86e7e08033a4145c626037ff63_31bf3856ad364e35_6.0.6002.22969_none_9bd03a4057e8670c.manifest
File versionNot applicable
File size700
Date (UTC)08-Nov-2012
Time (UTC)06:38
PlatformNot applicable
File nameX86_microsoft-windows-winsock-core_31bf3856ad364e35_6.0.6002.22969_none_da20893974d980a0.manifest
File versionNot applicable
File size30,064
Date (UTC)08-Nov-2012
Time (UTC)03:21
PlatformNot applicable
Additional files for all supported x64-based versions of Windows Server 2008
File nameAmd64_19e8d48833f930dd33d7341f90acf566_31bf3856ad364e35_6.0.6002.22969_none_41b0a54385d11761.manifest
File versionNot applicable
File size704
Date (UTC)08-Nov-2012
Time (UTC)06:38
PlatformNot applicable
File nameAmd64_microsoft-windows-winsock-core_31bf3856ad364e35_6.0.6002.22969_none_363f24bd2d36f1d6.manifest
File versionNot applicable
File size30,328
Date (UTC)08-Nov-2012
Time (UTC)04:33
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008
File nameIa64_a7727a2312c00801736a8e7ebfc37617_31bf3856ad364e35_6.0.6002.22969_none_ce714d92a047bae1.manifest
File versionNot applicable
File size702
Date (UTC)08-Nov-2012
Time (UTC)06:38
PlatformNot applicable
File nameIa64_microsoft-windows-winsock-core_31bf3856ad364e35_6.0.6002.22969_none_da222d2f74d7899c.manifest
File versionNot applicable
File size30,322
Date (UTC)08-Nov-2012
Time (UTC)02:25
PlatformNot applicable

↑ Back to the top


Keywords: kb, kbmdd, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseadvanced

↑ Back to the top

Article Info
Article ID : 2781571
Revision : 1
Created on : 1/7/2017
Published on : 12/19/2014
Exists online : False
Views : 259