Select the product you need help with
After the Terminal Services mirror driver is disconnected from a Windows Server 2008-based or Windows Vista-based remote computer, you receive a Stop error on the remote computer: "Stop error code 0x0000007E (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED)"Article ID: 958092 - View products that this article applies to. Beta InformationThis article discusses a beta release of a Microsoft product. The information in this article is provided as-is and is subject to change without notice.No formal product support is available from Microsoft for this beta product. For information about how to obtain support for a beta release, see the documentation that is included with the beta product files, or check the Web location where you downloaded the release. On This PageSYMPTOMSYou use a Terminal Services mirror driver to access a Windows Vista-based or a
Windows Server 2008-based remote computer. After you disconnect the mirror driver from the remote computer, the remote computer may crash. In this case, you receive the following error message on the remote computer:
Stop 0x0000007E (c0000005, Parameter2,
Parameter3, Parameter4)
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED CAUSEThis issue occurs because of a race condition in the Cdd.dll
file on the remote computer. This file is used to handle low-level graphics device interface (GDI)
calls. RESOLUTIONHotfix 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 the problem described in this article. 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: http://support.microsoft.com/contactus/?ws=support 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.
(http://support.microsoft.com/contactus/?ws=support)
Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page. PrerequisitesTo apply this hotfix, you must have Windows Vista Service Pack 1 or Windows Server 2008 installed on the computer.Restart requirementYou have to restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace any other previously released hotfixes.Registry informationTo use this hotfix, you do not have to make any changes to the registry.File informationThe 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 and Windows Server 2008 file information notesThe .manifest files and the .mum files that are installed in each environment are listed separately in the "Additional file information for Windows Server 2008 and for Windows Vista" section. These files and their associated .cat (security catalog) files are critical to maintaining the state of the updated component. The .cat files are signed with a Microsoft digital signature. The attributes of these security files are not listed.For all supported x86-based versions of Windows Server 2008 and Windows VistaCollapse this table
For all supported x64-based versions of Windows Server 2008 and Windows VistaCollapse this table
For all supported Itanium-based versions of Windows Server 2008Collapse this table
STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section. MORE INFORMATION
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe
Microsoft software updates
Additional file information for Windows Server 2008 and Windows VistaAdditional files for all supported x86-based versions of Windows Server 2008 and Windows VistaCollapse this table
Additional files for all supported x64-based versions of Windows Server 2008 and Windows VistaCollapse this table
Additional files for all supported Itanium-based versions of Windows Server 2008Collapse this table
PropertiesArticle ID: 958092 - Last Review: January 19, 2012 - Revision: 3.0 APPLIES TO
| Article Translations
 |
Back to the top
