0x0000001E Stop code error occurs on a computer that is running an IA-64-based version of Windows Server 2008 R2

Applies to: Windows Server 2008 R2 EnterpriseWindows Server 2008 R2 StandardWindows Server 2008 R2 Datacenter

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


On a computer that is running an IA-64-based version of Windows Server 2008 R2, you receive a Stop error message that resembles the following:
STOP 0x0000001E (0xffffffff80000002, parameter2, parameter3, parameter4)
  • The parameters in this Stop error message vary, depending on the configuration of the computer. However, the first parameter is 0xffffffff80000002.
  • Not all "Stop 0x0000001E" error messages are caused by this issue.
This issue occurs when the operating system handles network packets.


This issue occurs because of an error in the TCP/IP driver (Tcp/ip.sys).

The TCP/IP driver assumes that the memory that stores IP addresses is aligned. However, this assumption is not always true. Therefore, the operating system triggers the Stop code message that is mentioned in the "Symptoms" section when the memory is not aligned.


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.


To apply this hotfix, you must be running Windows Server 2008 R2.

Registry information

To use the hotfix, you do not have to change 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 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 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 IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform


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 IA-64-based versions of Windows Server 2008 R2
File nameIa64_171a01dabd1d7a5f626b2db60ee31572_31bf3856ad364e35_6.1.7600.20785_none_c9f1810e5bb96cff.manifest
File versionNot applicable
File size704
Date (UTC)20-Aug-2010
Time (UTC)18:24
PlatformNot applicable
File nameIa64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.20785_none_b37faee8e0d576a2.manifest
File versionNot applicable
File size3,782
Date (UTC)20-Aug-2010
Time (UTC)18:24
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size1,690
Date (UTC)20-Aug-2010
Time (UTC)18:24
PlatformNot applicable