Stop error 0x0000003B when a client computer uses multiple monitors that have different DPI/PPI settings

Van toepassing op
Windows 8.1 Windows 8.1 Enterprise Windows 8.1 Pro Windows Server 2012 R2 Datacenter Windows Server 2012 R2 Standard

Symptoms

Assume that you're using a computer that's running Windows 8.1 or Windows Server 2012 R2 and that uses multiple monitors. If the monitors have DPI/PPI settings that differ from one another, you may receive a Stop error message that resembles the following:

Note

****STOP 0x0000003B (parameter1parameter2parameter3parameter4) SYSTEM_SERVICE_EXCEPTION (3b)

      

Cause

This problem occurs because of an issue in Win32k. The driver makes an incorrect assumption that all the cursors are the same type. When certain cursor events are triggered, the Stop error may occur.

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

Prerequisites

To apply this hotfix, you must be running Windows 8.1.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any previously released hotfix.

File information

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 8.1 and Windows Server 2012 R2 file information and notesImportant Windows 8.1 and Windows Server 2012 R2 hotfixes are included in the same packages. However, only "Windows 8.1" 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 8.1" 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.3.960 0.17 xxx Windows 8.1 and Windows Server 2012 R2 RTM GDR
  • 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 8.1 and Windows Server 2012 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 8.1

File name File version File size Date Time Platform
Win32k.ptxml Not Applicable 4,213 21-Aug-2013 23:39 Not Applicable
Win32k.sys 6.3.9600.17084 3,498,496 28-Mar-2014 06:41 x86

For all supported x64-based versions of Windows 8.1 and Windows Server 2012 R2

File name File version File size Date Time Platform
Win32k.ptxml Not Applicable 4,213 22-Aug-2013 06:44 Not Applicable
Win32k.sys 6.3.9600.17084 4,191,744 28-Mar-2014 06:41 x64
Wow64_win32k.ptxml Not Applicable 4,213 21-Aug-2013 23:39 Not Applicable

For all supported ARM-based versions of Windows 8.1

File name File version File size Date Time Platform
Win32k.ptxml Not Applicable 4,213 21-Aug-2013 23:33 Not Applicable
Win32k.sys 6.3.9600.17084 3,078,656 28-Mar-2014 06:41 Not Applicable

Additional file information

Additional file information for Windows 8.1

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

File name X86_dffe0cecb9b1712e572b1802e66ff81c_31bf3856ad364e35_6.3.9600.17084_none_c92f7b087e7011c6.manifest
File version Not Applicable
File size 694
Date (UTC) 30-Mar-2014
Time (UTC) 01:27
Platform Not Applicable
File name X86_microsoft-windows-win32k_31bf3856ad364e35_6.3.9600.17084_none_4d9321c7b620812a.manifest
File version Not Applicable
File size 125,412
Date (UTC) 28-Mar-2014
Time (UTC) 14:14
Platform Not Applicable

Additional files for all supported x64-based versions of Windows 8.1 and Windows Server 2012 R2

File name Amd64_1e8ebce65c3a3befb8d7f9dc67743736_31bf3856ad364e35_6.3.9600.17084_none_f3c5e8701bc947ba.manifest
File version Not Applicable
File size 698
Date (UTC) 30-Mar-2014
Time (UTC) 01:38
Platform Not Applicable
File name Amd64_d7c30b59dcaca9b6166730ab5bbb3281_31bf3856ad364e35_6.3.9600.17084_none_5431d0af6a701ef4.manifest
File version Not Applicable
File size 698
Date (UTC) 30-Mar-2014
Time (UTC) 01:38
Platform Not Applicable
File name Amd64_microsoft-windows-win32k_31bf3856ad364e35_6.3.9600.17084_none_a9b1bd4b6e7df260.manifest
File version Not Applicable
File size 125,416
Date (UTC) 29-Mar-2014
Time (UTC) 02:54
Platform Not Applicable
File name Wow64_microsoft-windows-win32k_31bf3856ad364e35_6.3.9600.17084_none_b406679da2deb45b.manifest
File version Not Applicable
File size 124,683
Date (UTC) 28-Mar-2014
Time (UTC) 14:13
Platform Not Applicable

Additional files for all supported ARM-based versions of Windows 8.1

File name Arm_9b601bdeabd3678e475974ac0242b906_31bf3856ad364e35_6.3.9600.17084_none_afe6df08cd0c6ebd.manifest
File version Not Applicable
File size 694
Date (UTC) 30-Mar-2014
Time (UTC) 01:27
Platform Not Applicable
File name Arm_microsoft-windows-win32k_31bf3856ad364e35_6.3.9600.17084_none_4d95941fb61d9ff0.manifest
File version Not Applicable
File size 125,412
Date (UTC) 28-Mar-2014
Time (UTC) 09:07
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.