Open Software Solutions

When you try to upgrade the video driver on a Windows Vista-based computer, the screen may go blank. In this situation, nothing happens when you move the mouse or when you press CTRL+ALT+DELETE. If you turn off the power and then restart the computer, the desktop is displayed correctly. However, you receive an error message that states that the newly installed driver is incompatible with Windows Vista.

Back to the top

This problem occurs under the following circumstances:

•	The driver queries Windows Vista for the available system memory.
•	Windows Vista issues an incorrect value in response to this query.

Back to the top

Hotfix information

A supported hotfix is now 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 service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

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

File name	File version	File size	Date	Time	Platform
Cdd.dll	6.0.6000.20534	36,864	10-Feb-2007	02:59	x86
Dxgkrnl.sys	6.0.6000.20534	617,472	10-Feb-2007	01:57	x86
Update.mum	Not applicable	1,780	12-Feb-2007	06:16	Not applicable
X86_0af309c2114cd3c5703202c33c0a798a_31bf3856ad364e35_6.0.6000.20534_none_0126c938fe41a465.manifest	Not applicable	696	12-Feb-2007	06:16	Not applicable
X86_microsoft-windows-lddmcore_31bf3856ad364e35_6.0.6000.20534_none_aa4f845bff989336.manifest	Not applicable	8,958	12-Feb-2007	06:18	Not applicable

Windows Vista, 64-bit versions

File name	File version	File size	Date	Time	Platform
Amd64_e847462a29f0fc5392c1a0a13605ee7b_31bf3856ad364e35_6.0.6000.20534_none_f181e9749ab25533.manifest	Not applicable	700	12-Feb-2007	06:16	Not applicable
Amd64_microsoft-windows-lddmcore_31bf3856ad364e35_6.0.6000.20534_none_066e1fdfb7f6046c.manifest	Not applicable	9,223	12-Feb-2007	06:23	Not applicable
Cdd.dll	6.0.6000.20534	47,104	10-Feb-2007	04:13	x64
Dxgkrnl.sys	6.0.6000.20534	873,472	10-Feb-2007	02:19	x64
Update.mum	Not applicable	1,780	12-Feb-2007	06:16	Not applicable

Back to the top

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

Back to the top

For more information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:

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

Back to the top