Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

"0x0000003B" Stop error on a terminal server in Windows Server 2008


View products that this article applies to.

Not sure if this is the right fix? We've added this issue to our memory dump diagnostic which can confirm.

↑ Back to the top


Symptoms

Consider the following scenario:
  • You install the Terminal Services role on a computer that is running Windows Server 2008.
  • You connect to this terminal server, and then you perform some window-related operations in a terminal server session.

    For example, you open and then close some windows in the terminal server session.
In this scenario, the computer may restart unexpectedly. Additionally, you receive a Stop error message that resembles the following:
STOP 0x0000003B (parameter1, parameter2, parameter3, parameter4)
SYSTEM_SERVICE_EXCEPTION
Notes
  • The parameters in this Stop error message may vary, depending on the configuration of the computer.
  • Not all the "Stop 0x0000003B" Stop errors are caused by this issue.

↑ Back to the top


Cause

This issue occurs because the Rdpwd.sys driver does not check whether a returned list is NULL or not.

When the returned list is NULL, the Rdpwd.sys driver accesses the wrong memory location. Therefore, an access violation exception occurs.

↑ Back to the top


Resolution

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.

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, you must be running one of the following operating systems:
  • Windows Server 2008
  • Windows Server 2008 Service Pack 2 (SP2)
For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

968849 How to obtain the latest service pack for Windows Server 2008

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

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 global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2008 file information notes
Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
    VersionProductSR_LevelService branch
    6.0.600
    1.
    22xxx
    Windows Server 2008SP1LDR
    6.0.600
    2.
    22xxx
    Windows Server 2008SP2LDR
  • Service Pack 1 is integrated into the release version of Windows Server 2008. Therefore, RTM milestone files apply only to Windows Vista. RTM milestone files have a 6.0.0000.xxxxx version number.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008" section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Rdpwd.sys6.0.6002.22615180,73617-Mar-201113:29x86
For all supported x64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Rdpwd.sys6.0.6002.22615209,92017-Mar-201113:54x64
For all supported IA-64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Rdpwd.sys6.0.6002.22615475,64817-Mar-201113:54IA-64

↑ Back to the top


Status

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

↑ Back to the top


More Information

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

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows Vista and for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008
File nameX86_e8f731b7b42e2602900fa49441ea18ad_31bf3856ad364e35_6.0.6002.22615_none_21a3a6228b7b6747.manifest
File versionNot applicable
File size725
Date (UTC)17-Mar-2011
Time (UTC)17:31
File nameX86_microsoft-windows-t..dp-winstationdriver_31bf3856ad364e35_6.0.6002.22615_none_4ddfd7b0eb4a0124.manifest
File versionNot applicable
File size4,780
Date (UTC)17-Mar-2011
Time (UTC)15:30
Additional files for all supported x64-based versions of Windows Server 2008
File nameAmd64_d4e2260e326da4b2c5d87b675cd25c73_31bf3856ad364e35_6.0.6002.22615_none_a685b386b84443b1.manifest
File versionNot applicable
File size729
Date (UTC)17-Mar-2011
Time (UTC)17:31
File nameAmd64_microsoft-windows-t..dp-winstationdriver_31bf3856ad364e35_6.0.6002.22615_none_a9fe7334a3a7725a.manifest
File versionNot applicable
File size5,063
Date (UTC)17-Mar-2011
Time (UTC)15:35
Additional files for all supported IA-64-based versions of Windows Server 2008
File nameIa64_89ad9c9849c58979674cccf961325ca2_31bf3856ad364e35_6.0.6002.22615_none_e960f37efa1b3aa2.manifest
File versionNot applicable
File size727
Date (UTC)17-Mar-2011
Time (UTC)17:31
File nameIa64_microsoft-windows-t..dp-winstationdriver_31bf3856ad364e35_6.0.6002.22615_none_4de17ba6eb480a20.manifest
File versionNot applicable
File size5,060
Date (UTC)17-Mar-2011
Time (UTC)15:23

↑ Back to the top


Keywords: kb, kbmdd, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbexpertiseinter, kbsurveynew

↑ Back to the top

Article Info
Article ID : 2518298
Revision : 1
Created on : 1/7/2017
Published on : 10/9/2014
Exists online : False
Views : 151