Stop error 0x0000003B when you try to connect to a server by using Remote Desktop Protocol in Windows 7 or Windows Server 2008 R2

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

Symptoms

Consider the following scenario:

  • You have a computer that is running Windows 7 or Windows Server 2008 R2.

  • You use Remote Desktop Protocol (RDP) to connect to a server that is running Remote Desktop Services.


In this scenario, the server crashes, and you receive a Stop error 0x0000003B.

Resolution

Hotfix information

A supported hotfix is available from Microsoft Support. 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, go to the following Microsoft website:

http://support.microsoft.com/contactus/?ws=supportNote 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 have Service Pack 1 for Windows 7 or Windows Server 2008 R2 installed.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any previously released hotfix.

The English (United States) 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 7 and Windows Server 2008 R2 file information and notesImportant Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" 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.

    Version

    Product

    SR_Level

    Service branch

    6.1.760
    1.
    22xxx

    Windows 7 and Windows Server 2008 R2

    SP1

    LDR

  • GDR service branches contain only those fixes that are widely released to address widespread, extremely important issues. LDR service branches contain hotfixes in addition to widely released fixes.

  • 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 7 and Windows Server 2008 R2" section. MUM 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 7

File name

File version

File size

Date

Time

Platform

Win32k.sys

6.1.7601.22819

2,387,968

25-Sep-2014

00:43

x86

For all supported x64-based versions of Windows 7 and Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Win32k.sys

6.1.7601.22819

3,201,536

25-Sep-2014

00:58

x64

For all supported IA-64-based versions of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Win32k.sys

6.1.7601.22819

7,502,848

25-Sep-2014

00:37

IA-64

Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7

File name

X86_7757c382605faf33cd3368275ca2df98_31bf3856ad364e35_6.1.7601.22819_none_535fcb423dd167d4.manifest

File version

Not Applicable

File size

694

Date (UTC)

25-Sep-2014

Time (UTC)

22:15

Platform

Not Applicable

File name

X86_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.22819_none_bb896ee711e21537.manifest

File version

Not Applicable

File size

42,145

Date (UTC)

25-Sep-2014

Time (UTC)

02:17

Platform

Not Applicable

Additional files for all supported x64-based versions of Windows 7 and Windows Server 2008 R2

File name

Amd64_18cf862730bc83618c2ee3f96595ed0e_31bf3856ad364e35_6.1.7601.22819_none_7f8a5d92ae894485.manifest

File version

Not Applicable

File size

698

Date (UTC)

25-Sep-2014

Time (UTC)

22:15

Platform

Not Applicable

File name

Amd64_44ad515119cbb5e54fa81239cdb255b1_31bf3856ad364e35_6.1.7601.22819_none_b05f6383613263dd.manifest

File version

Not Applicable

File size

1,038

Date (UTC)

25-Sep-2014

Time (UTC)

22:15

Platform

Not Applicable

File name

Amd64_935ff790cc3881f299161c0af1baf152_31bf3856ad364e35_6.1.7601.22819_none_19dbb678c7067d09.manifest

File version

Not Applicable

File size

698

Date (UTC)

25-Sep-2014

Time (UTC)

22:15

Platform

Not Applicable

File name

Amd64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.22819_none_17a80a6aca3f866d.manifest

File version

Not Applicable

File size

42,149

Date (UTC)

25-Sep-2014

Time (UTC)

03:32

Platform

Not Applicable

File name

Wow64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.22819_none_21fcb4bcfea04868.manifest

File version

Not Applicable

File size

4,178

Date (UTC)

25-Sep-2014

Time (UTC)

02:02

Platform

Not Applicable

Additional files for all supported IA-64-based versions of Windows Server 2008 R2

File name

Ia64_5d082062f42c5da56da2b02248482b4f_31bf3856ad364e35_6.1.7601.22819_none_a1d438c4f79223be.manifest

File version

Not Applicable

File size

1,036

Date (UTC)

25-Sep-2014

Time (UTC)

22:15

Platform

Not Applicable

File name

Ia64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.22819_none_bb8b12dd11e01e33.manifest

File version

Not Applicable

File size

42,147

Date (UTC)

25-Sep-2014

Time (UTC)

02:01

Platform

Not Applicable

File name

Wow64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.22819_none_21fcb4bcfea04868.manifest

File version

Not Applicable

File size

4,178

Date (UTC)

25-Sep-2014

Time (UTC)

02:02

Platform

Not Applicable


Status

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

References

Learn about the terminology that Microsoft uses to describe software updates.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

×