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.

"0x0000001E" Stop error occurs intermittently in Windows 7 SP1 and Windows Server 2008 R2 SP1


View products that this article applies to.

Symptoms


A server that is running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1 crashes intermittently. Additionally, you receive a Stop error message that resembles following:
STOP: 0x0000001E (Parameter 1, Parameter 2, Parameter 3, Parameter 4)

Notes
  • This Stop error describes a KMODE_EXCEPTION_NOT_HANDLED issue.
  • The parameters in this Stop error message vary, depending on the configuration of the computer.
  • Not all "STOP: 0x0000001E" errors are caused by this issue.

↑ Back to the top


Cause

This issue occurs because of an NTFS file system memory leak issue. Specifically, when an application opens a file that has an oplock on it for modification in a transaction, NTFS will break the oplock and will leak nonpaged pool memory. This causes excessive memory usage and memory allocation failures.

↑ Back to the top


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 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, visit the following Microsoft website: 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 7 SP1 or Windows Server 2008 R2 SP1.

For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To apply this hotfix, 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.

File information

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 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:
    VersionProductMilestoneService branch
    6.1.760
    1.22xxx
    Windows 7 and Windows Server 2008 R2SP1LDR
  • 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 7 and for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. 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 nameFile versionFile sizeDateTime
Ntfs.sys6.1.7601.221231,213,29629-Sep-201216:42

For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameFile versionFile sizeDateTime
Ntfs.sys6.1.7601.221231,687,92029-Sep-201217:54

For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTime
Ntfs.sys6.1.7601.221233,558,76829-Sep-201216:48

↑ 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


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

Additional file information for Windows 7 and for Windows Server 2008 R2
File nameX86_346bed4b0261f7b13f6d2a75710f7087_31bf3856ad364e35_6.1.7601.22123_none_929468cacbf8640f.manifest
File versionNot applicable
File size692
Date (UTC)01-Oct-2012
Time (UTC)12:05
File nameX86_microsoft-windows-ntfs_31bf3856ad364e35_6.1.7601.22123_none_a8f63ff794547ce0.manifest
File versionNot applicable
File size14,508
Date (UTC)29-Sep-2012
Time (UTC)17:04

Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameAmd64_99f381d4518f6b31125943c9491e91f5_31bf3856ad364e35_6.1.7601.22123_none_2753b8cc679aa698.manifest
File versionNot applicable
File size696
Date (UTC)01-Oct-2012
Time (UTC)12:05
File nameAmd64_microsoft-windows-ntfs_31bf3856ad364e35_6.1.7601.22123_none_0514db7b4cb1ee16.manifest
File versionNot applicable
File size14,514
Date (UTC)29-Sep-2012
Time (UTC)19:34

Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File nameIa64_2bac4ae928657afee0bd67003e890f49_31bf3856ad364e35_6.1.7601.22123_none_7679182f42f0eaab.manifest
File versionNot applicable
File size694
Date (UTC)01-Oct-2012
Time (UTC)12:05
File nameIa64_microsoft-windows-ntfs_31bf3856ad364e35_6.1.7601.22123_none_a8f7e3ed945285dc.manifest
File versionNot applicable
File size14,511
Date (UTC)29-Sep-2012
Time (UTC)18:06

↑ Back to the top


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

↑ Back to the top

Article Info
Article ID : 2764302
Revision : 2
Created on : 10/27/2017
Published on : 10/27/2017
Exists online : False
Views : 344