Article ID: 829808
When you run the Display Compatibility Test (DCT), Microsoft Windows NetMeeting, and the Remote Desktop Sharing service at the same time on a Microsoft Windows 2000 Service Pack 4 (SP4)-based computer, stop error 0xd5 may occur in the Win32k.sys module.
Hotfix informationA 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:
PrerequisitesYou must have Windows 2000 Service Pack 3 (SP3) installed before you apply this hotfix.
Restart requirementsYou must restart your computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace any other hotfixes.
File informationThe English version of this hotfix has the file attributes (or later) 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.
Date Time Version Size File name ----------------------------------------------------------- 31-Oct-2003 18:06 5.00.2195.6824 42,256 Basesrv.dll 21-Sep-2003 00:45 5.00.2195.6824 236,304 Cmd.exe 31-Oct-2003 18:06 5.00.2195.6824 222,992 Gdi32.dll 31-Oct-2003 18:06 5.00.2195.6867 711,440 Kernel32.dll 31-Oct-2003 18:06 5.00.2195.6824 54,032 Mpr.dll 31-Oct-2003 18:06 5.00.2195.6860 334,096 Msgina.dll 31-Oct-2003 18:06 5.00.2195.6824 90,232 Rdpwd.sys 30-Sep-2003 20:56 5.00.2195.6826 5,298,176 Sp3res.dll 31-Oct-2003 18:06 5.00.2195.6869 380,176 User32.dll 31-Oct-2003 18:06 5.00.2195.6825 389,392 Userenv.dll 31-Oct-2003 03:02 5.00.2195.6869 1,628,816 Win32k.sys 21-Sep-2003 00:44 5.00.2195.6824 182,032 Winlogon.exe 31-Oct-2003 18:06 5.00.2195.6826 243,984 Winsrv.dll 31-Oct-2003 18:06 5.00.2195.6867 711,440 Kernel32.dll 31-Oct-2003 03:02 5.00.2195.6869 1,628,816 Win32k.sys 31-Oct-2003 18:06 5.00.2195.6826 243,984 Winsrv.dll
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section of this article.
For additional information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:
816915For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/816915/ )New file naming schema for Microsoft Windows software update packages
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
Contact us for more help
Connect with Answer Desk for expert help.