FAQ

* Symptoms

Consider the following scenario:

• You have a computer that is running Windows 8.1 or Windows Server 2012 R2.
• The server has more than 512 gigabytes (GB) of installed memory.
• You run an application for which a memory region greater than 512 gigabytes (GB) is stressed.

In this scenario, the server encounters a Stop error 0x1A in the nt!MiUpdateWsle function.
Note This problem is observed when the system performs data intensive operations by using Microsoft SQL Server or when you use a memory stress test tool.

* Cause

This problem occurs because of an issue in virtual memory management in the operating system kernel.

* Resolution 

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 have Windows 8.1 or Windows Server 2012 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.