Saturday, August 27, 2022

"0x00000050" Stop error when you try to create a virtual machine or copy a VHD or VHDX file to a SMB share in Windows Server 2012 [MS]

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


Consider the following scenario:

  • You have the Hyper-V server role installed on a computer that is running Windows Server 2012.

  • You enable performance tracing for the Server Message Block (SMB) server on the Hyper-V server. For example, you run the following command:

    wevtutil set-log Microsoft-Windows-SmbServer/Performance /e:true Note Performance tracing for the SMB server is enabled automatically when you perform certain operations.

  • You configure the Hyper-V server to store Virtual Hard Disk (VHD) or VHDX files for virtual machines on an SMB share. The SMB share is located on a remote computer.

  • You try to create a virtual machine, or you try to copy a VHD or VHDX file to the SMB share.

In this scenario, the remote computer crashes. Additionally, you receive a Stop error message that resembles the following:

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


  • This Stop error describes a PAGE_FAULT_IN_NON-PAGED_AREA issue.

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

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


This issue occurs because a certain part of the "Event Tracing for Windows" (ETW) feature is enabled. This causes a null dereference to occur when you try to create the virtual machine or copy the VHD or VHDX file to the SMB share.


This hotfix is also available at Microsoft Update Catalog

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


To apply this hotfix, you must be running Windows Server 2012.

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.

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 2012 file information notesImportant Windows 8 hotfixes and Windows Server 2012 hotfixes are included in the same packages. However, only "Windows 8" 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" 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:




    Service branch

    6.2.920 0.20 xxx

    Windows Server 2012



  • 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 2012" 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 x64-based versions of Windows Server 2012

File name

File version

File size











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

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 for Windows Server 2012

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

File name


File version

Not applicable

File size


Date (UTC)


Time (UTC)



Not applicable

File name


File version

Not applicable

File size


Date (UTC)


Time (UTC)



Not applicable

No comments:

Post a Comment

Search This Blog

(Windows Insider Program) Compatibility update for upgrading to Windows 10, Version 1903: May 1, 2019 [MS]

(Windows Insider Program) Compatibility update for upgrading to Windows 10, Version 1903: Ma...