On a computer that is running Windows Server 2003 or Windows XP, an application experiences an access violation and then crashes if the computer has more than four cores or more than four logical processors

Consider the following scenario:

• You have a computer that is running Windows Server 2003 or Windows XP.
• The computer has more than four cores or more than four logical processors installed.
• An application calls functions in the D3d9.dll library for DirectX 3D support.

In this scenario, the application experiences an access violation and then crashes.

This issue occurs because DirectX creates worker threads that are based on the number of cores or logical processors. DirectX has a global data array, and each worker thread accesses a dedicated element in that global array. However, there is a hard-coded limitation of four elements in the array. If there are more than four cores or more than four logical processors, some worker threads in DirectX try to access memory that has not been allocated. Therefore, DirectX experiences an access violation issue when it tries to create more than four worker threads.

To work around the issue, do not use more than four processors. You can use the /numproc switch in the Boot.ini file to limit the number of processors. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Hotfix information for Windows Server 2003

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

To apply this hotfix, Windows Server 2003 Service Pack 1 (SP1) or Windows Server 2003 Service Pack 2 (SP2) must be installed.

Restart requirement

You do not have to 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 item in Control Panel.

Windows Server 2003 with Service Pack 1, x86 version

Windows Server 2003 with Service Pack 2, x86 version

Windows Server 2003, x64 version

Windows Server 2003 with Service Pack 2, x64 version

Hotfix information for Windows XP

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: 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, Windows XP SP2 or Windows XP SP3 must be installed.

Restart requirement

You do not have to 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 item in Control Panel.

Windows XP Professional x64 Edition with SP1, x64 version

Windows XP Professional x64 Edition with SP2, x64 version

Windows XP with Service Pack 2, x86 version

Windows XP with Service Pack 3, x86 version

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