Unexpected system behavior may occur when you run 32-bit programs on a computer that is running an Itanium-based version of Windows Server 2003 with Service Pack 1

Unexpected system behavior or data integrity issues may occur when you run 32-bit programs on a computer that is running an Itanium-based version of Microsoft Windows Server 2003 with Service Pack 1 (SP1). The symptoms vary depending on the 32-bit program that you run.

This problem may occur if the 32-bit program is using a version of the IA-32 Execution Layer Software driver that is earlier than version 5.3.5338.0.

The problem may occur in rare instances when specific code sequences are executed. For example, this problem may occur with code that contains either of the following:

• Interleaved integer and floating-point producer instructions
• Interleaved integer and consumer flag-related instructions

When this code is processed, a conditional jump instruction in the code can branch to an incorrect destination.

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Download information

The following file is available for download from the Microsoft Download Center:


Download the 899755 package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=EE4883BB-6B9F-4B09-A5D3-3279800BF466&displaylang=en)

Release Date: June 17, 2005

For more information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base: Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

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

Windows Server 2003 SP1

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

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 tool in Control Panel.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.