This article describes an issue in which a remote session is lost in Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1. A hotfix is available to resolve this issue. The hotfix has a prerequisite.

Symptoms

This issue occurs when multiple remote sessions are running on a remote server. In this situation, the remote server crashes, and you receive a Stop error message on the remote server that resembles the following:

STOP: 0x0000003B (parameter1, parameter2, parameter3, parameter4)


Notes

  • This Stop error indicates a SYSTEM_SERVICE_EXCEPTION issue.

  • The parameters in this Stop error message vary, and that depends on the configuration of the computer.

  • Not all "0x0000003B" Stop errors are caused by this issue.


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 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 update, you must have Service Pack 1 installed in Windows 7 or Windows Server 2008 R2.

Registry information

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

Restart requirement

You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

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 7 and Windows Server 2008 R2 file information and notes

Important 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, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    Version

    Product

    Milestone

    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, critical 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" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very 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.22887

2,387,968

27-Nov-2014

01:56

x86

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

File name

File version

File size

Date

Time

Platform

Win32k.sys

6.1.7601.22887

3,201,536

27-Nov-2014

02:02

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.22887

7,500,800

27-Nov-2014

01:41

IA-64

Additional file information

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

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

File property

Value

File name

X86_9b9f6b85311220d4a3ac2d982c6678f9_31bf3856ad364e35_6.1.7601.22887_none_7d185516c15d4a8d.manifest

File version

Not applicable

File size

694

Date (UTC)

27-Nov-2014

Time (UTC)

16:09

Platform

Not applicable

File name

X86_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.22887_none_bb3bbedf121ca620.manifest

File version

Not applicable

File size

42,145

Date (UTC)

27-Nov-2014

Time (UTC)

03:49

Platform

Not applicable

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

File property

Value

File name

Amd64_58dd85f601595f7fed6ed89e1e2db78b_31bf3856ad364e35_6.1.7601.22887_none_04c442d7c723d039.manifest

File version

Not applicable

File size

1,038

Date (UTC)

27-Nov-2014

Time (UTC)

16:09

Platform

Not applicable

File name

Amd64_826e53c3ead425c06381e35461962448_31bf3856ad364e35_6.1.7601.22887_none_f52ad3ae2919aa87.manifest

File version

Not applicable

File size

698

Date (UTC)

27-Nov-2014

Time (UTC)

16:09

Platform

Not applicable

File name

Amd64_be0bd26d20b712f43b1e8307ac064255_31bf3856ad364e35_6.1.7601.22887_none_9513d3e4fd65f911.manifest

File version

Not applicable

File size

698

Date (UTC)

27-Nov-2014

Time (UTC)

16:09

Platform

Not applicable

File name

Amd64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.22887_none_175a5a62ca7a1756.manifest

File version

Not applicable

File size

42,149

Date (UTC)

27-Nov-2014

Time (UTC)

03:50

Platform

Not applicable

File name

Wow64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.22887_none_21af04b4fedad951.manifest

File version

Not applicable

File size

4,178

Date (UTC)

27-Nov-2014

Time (UTC)

03:43

Platform

Not applicable

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

File property

Value

File name

Ia64_5ed05cf3b90e165bc3fe7548cb09052d_31bf3856ad364e35_6.1.7601.22887_none_488a78eb7704b006.manifest

File version

Not applicable

File size

1,036

Date (UTC)

27-Nov-2014

Time (UTC)

16:08

Platform

Not applicable

File name

Ia64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.22887_none_bb3d62d5121aaf1c.manifest

File version

Not applicable

File size

42,147

Date (UTC)

27-Nov-2014

Time (UTC)

03:37

Platform

Not applicable

File name

Wow64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.22887_none_21af04b4fedad951.manifest

File version

Not applicable

File size

4,178

Date (UTC)

27-Nov-2014

Time (UTC)

03:43

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

See 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?

What affected your experience?

Thank you for your feedback!

×