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.

0x50 Stop error and users can't access documents on shared folders or home folders in Windows Server 2012 R2


View products that this article applies to.

This article describes an issue in which a Stop error 0x50 occurs and users can't access documents on shared folders or home folders on a Windows Server 2012 R2-based file server. A hotfix is available to fix this issue. Before you install this hotfix, see the Prerequisites section.

↑ Back to the top


Symptoms

This issue occurs when the following conditions are true:
  • You're using the Scale-out File Server (SOFS) role on a Windows Failover Cluster.
  • You use iSCSI Logical Unit Numbers (LUNs) on the cluster.
  • Distributed File Service (DFS) on cluster CSV share has the access-based enumeration (ABE) feature enabled.
  • A user tries to copy the data from one share to another, or multiple users access shares at the same time.
In this situation, you receive a "0x00000050" Stop error, indicating a PAGE_FAULT_IN_NONPAGED_AREA error on the Windows Server 2012 R2-based server.

↑ Back to the top


Resolution

To fix this issue, we've released a hotfix for Windows 8.1 or Windows Server 2012 R2.

Hotfix information

Important If you install a language pack after you install this hotfix, you must reinstall this hotfix. Therefore, we recommend that you install any language packs that you need before you install this hotfix. For more information, see Add language packs to Windows.


A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that's described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there's a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section doesn't appear, submit a request to Microsoft Customer Service and Support to get 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 don't 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: Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you don't see your language, it's because a hotfix isn't available for that language.


Prerequisites

To apply this hotfix, install update 2919355 in Windows 8.1 or Windows Server 2012 R2.

Registry information

To use the hotfix in this package, you don't 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 doesn't replace a previously released hotfix.

↑ Back to the top


File Information

The English (United States) version of this software update installs files that have the attributes that are listed in the following tables. The dates and times for these files are listed in Coordinated Universal Time (UTC). Be aware that dates and times for these files on your local computer are displayed in your local time and with your current daylight saving time bias. The dates and times may also change when you perform certain operations on the files.
Windows 8.1, Windows RT 8.1 and Windows Server 2012 R2
Notes
  • 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:
    VersionProductMilestoneService branch
    6.3.960 0.18 xxxWindows RT 8.1, Windows 8.1, and Windows Server 2012 R2RTMGDR
  • 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 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.
x64 Windows 8.1 and Windows Server 2012 R2
File nameFile versionFile sizeDateTimePlatform
Srv2.sys6.3.9600.18057676,86416-Sep-201504:34x64
Windows RT 8.1
File nameFile versionFile sizeDateTimePlatform
Srv2.sys6.3.9600.18057521,72816-Sep-201503:34Not applicable
x86 Windows 8.1
File nameFile versionFile sizeDateTimePlatform
Srv2.sys6.3.9600.18057562,68816-Sep-201503:42x86

Additional file information
x64 Windows 8.1 and Windows Server 2012 R2
File propertyValue
File nameAmd64_727a7d8d901428044d845aaa700f1a48_31bf3856ad364e35_6.3.9600.18057_none_98cda738d9a20a4f.manifest
File versionNot applicable
File size704
Date (UTC)16-Sep-2015
Time (UTC)22:18
PlatformNot applicable
File nameAmd64_microsoft-windows-smbserver-v2_31bf3856ad364e35_6.3.9600.18057_none_cace36d9ca57ee39.manifest
File versionNot applicable
File size259,948
Date (UTC)16-Sep-2015
Time (UTC)05:33
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size1,602
Date (UTC)16-Sep-2015
Time (UTC)22:18
PlatformNot applicable
Windows RT 8.1
File propertyValue
File nameArm_8f9b1f28f64a22ed18603c56e980421a_31bf3856ad364e35_6.3.9600.18057_none_9758db642d96a256.manifest
File versionNot applicable
File size700
Date (UTC)16-Sep-2015
Time (UTC)22:18
PlatformNot applicable
File nameArm_microsoft-windows-smbserver-v2_31bf3856ad364e35_6.3.9600.18057_none_6eb20dae11f79bc9.manifest
File versionNot applicable
File size259,944
Date (UTC)16-Sep-2015
Time (UTC)04:17
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size1,594
Date (UTC)16-Sep-2015
Time (UTC)22:18
PlatformNot applicable
x86 Windows 8.1
File propertyValue
File nameUpdate.mum
File versionNot applicable
File size1,594
Date (UTC)16-Sep-2015
Time (UTC)22:18
PlatformNot applicable
File nameX86_9e5245165fb7a78505eb4f79d6aa736c_31bf3856ad364e35_6.3.9600.18057_none_5cba9b5ad39bd563.manifest
File versionNot applicable
File size700
Date (UTC)16-Sep-2015
Time (UTC)22:18
PlatformNot applicable
File nameX86_microsoft-windows-smbserver-v2_31bf3856ad364e35_6.3.9600.18057_none_6eaf9b5611fa7d03.manifest
File versionNot applicable
File size259,944
Date (UTC)16-Sep-2015
Time (UTC)04:45
PlatformNot applicable

↑ 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


References

See the terminology that Microsoft uses to describe software updates.

↑ Back to the top


Keywords: kbqfe, kbsurveynew, kbexpertiseadvanced, kbfix, kbautohotfix, kbhotfixserver, kb

↑ Back to the top

Article Info
Article ID : 3093900
Revision : 1
Created on : 1/7/2017
Published on : 11/4/2015
Exists online : False
Views : 239