A WHQL test does not finish successfully on a Windows Vista-based computer that has multiple display adapters in an LDA configuration

Consider the following scenario:

• You are running a Windows Vista-based computer that has multiple display adapters in a Linked Display Adapter (LDA) configuration.
• You use the Driver Test Manager tool on the computer to run a Windows Hardware Quality Lab (WHQL) test that includes a Logo stress subtest.

In this scenario, the Logo stress subtest triggers a Windows Display Driver Model (WDDM) aperture corruption. Therefore, the WHQL test does not finish successfully.

This problem occurs because the operating system does not correctly calculate the page offset for the end address.

Update information

The following files are available for download from the Microsoft Download Center:

Update for Windows Server 2008 for Itanium-based Systems
Download the KB948473 package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=1AA788D3-54A4-45EF-9593-69A76AF39031)

Update for Windows Server 2008 x64 Edition
Download the KB948473 package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=A22175A1-8248-4A33-B834-FC9363C9D72A)

Update for Windows Server 2008
Download the KB948473 package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=B4B39C2E-3282-4B2E-98DF-79B93F39A362)

Update for Windows Vista
Download the KB948473 package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=EDADC60B-9CAB-489E-ABAC-B18571A97313)

Update for Windows Vista for x64-based Systems
Download the KB948473 package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=CA391A5A-1133-4833-8FAC-9B9F5C983123)

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

There are no prerequisites for installing this hotfix.

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 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 Vista, x86-based versions

Windows Vista, X64 versions

Windows Vista, IA-64-based versions

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