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.

Stop error when a registry management problem occurs on a Windows Server 2008 or Windows Vista SP1-based computer: "0x0000007E"


View products that this article applies to.

Symptoms

On a computer that is running Windows Vista Service Pack 1 (SP1) or Windows Server 2008, you receive the following Stop error message:
STOP 0x0000007E (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED)

Notes
  • The first parameter is 0xc0000005. Other three parameters in this Stop error message may vary, depending on the configuration of the computer.
  • Not all "0x0000007E" Stop error messages are caused by this problem.
Additionally, the following event is logged in the System log:

Source: Microsoft-Windows-WER-SystemErrorReporting
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xc0000005, <address>, <address>, <address>). A dump was saved in: <file path>.

↑ Back to the top


Cause

This problem occurs because the registry management module does not manage mapped views in memory correctly. Therefore, a view is freed even though it is being mapped. Any access to this freed view will cause the system to trigger stop code 0x0000007E.

↑ 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 this specific problem. 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 Web site: 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.

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the �Hotfix Request� page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.

Prerequisites

To apply this hotfix, you must have Windows Vista Service Pack 1 (SP1) or Windows Server 2008 installed.

Restart requirement

You have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

Registry information

To use this hotfix, you do not have to make any changes to the registry.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Server 2008 and Windows Vista file information note

The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately . 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 (attributes not listed) are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows Server 2008 and of Windows Vista
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Ntkrnlpa.exe6.0.6001.223663,600,86402-Feb-200906:01Not Applicable
Ntoskrnl.exe6.0.6001.223663,548,64002-Feb-200906:01Not Applicable
For all supported x64-based versions of Windows Server 2008 and Windows Vista
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Ntoskrnl.exe6.0.6001.223664,691,44002-Feb-200906:47x64
For all supported Itanium-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Ntoskrnl.exe6.0.6001.223669,491,93602-Feb-200905:37IA-64

↑ 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, 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 Vista and for Windows Server 2008

Additional files for all supported x86-based versions of Windows Vista and of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Package_for_kb965494_client_1~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,36702-Feb-200919:02Not Applicable
Package_for_kb965494_client~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,43102-Feb-200919:02Not Applicable
Package_for_kb965494_sc_0~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42102-Feb-200919:02Not Applicable
Package_for_kb965494_sc~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42302-Feb-200919:02Not Applicable
Package_for_kb965494_server_0~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42502-Feb-200919:02Not Applicable
Package_for_kb965494_server~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,43102-Feb-200919:02Not Applicable
Package_for_kb965494_winpesrv_0~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42202-Feb-200919:02Not Applicable
Package_for_kb965494_winpesrv~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42902-Feb-200919:02Not Applicable
X86_microsoft-windows-os-kernel_31bf3856ad364e35_6.0.6001.22366_none_6c7f246bcd6bec30.manifestNot Applicable17,80602-Feb-200906:28Not Applicable
Additional files for all supported x64-based versions of Windows Vista and of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Amd64_microsoft-windows-os-kernel_31bf3856ad364e35_6.0.6001.22366_none_c89dbfef85c95d66.manifestNot Applicable16,51202-Feb-200907:14Not Applicable
Package_for_kb965494_client_1~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,37502-Feb-200919:02Not Applicable
Package_for_kb965494_client~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43902-Feb-200919:02Not Applicable
Package_for_kb965494_sc_0~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,42902-Feb-200919:02Not Applicable
Package_for_kb965494_sc~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43102-Feb-200919:02Not Applicable
Package_for_kb965494_server_0~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43302-Feb-200919:02Not Applicable
Package_for_kb965494_server~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43902-Feb-200919:02Not Applicable
Package_for_kb965494_winpesrv_0~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43002-Feb-200919:02Not Applicable
Package_for_kb965494_winpesrv~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43702-Feb-200919:02Not Applicable
Additional files for all supported Itanium-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Ia64_microsoft-windows-os-kernel_31bf3856ad364e35_6.0.6001.22366_none_6c80c861cd69f52c.manifestNot Applicable16,81902-Feb-200906:13Not Applicable
Package_for_kb965494_sc_0~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,42502-Feb-200919:02Not Applicable
Package_for_kb965494_sc~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,42602-Feb-200919:02Not Applicable
Package_for_kb965494_server_0~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,42902-Feb-200919:02Not Applicable
Package_for_kb965494_server~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,43402-Feb-200919:02Not Applicable
Package_for_kb965494_winpesrv_0~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,42602-Feb-200919:02Not Applicable
Package_for_kb965494_winpesrv~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,43302-Feb-200919:02Not Applicable

↑ Back to the top


Keywords: kbexpertiseinter, kbautohotfix, kbfix, kbsurveynew, kbqfe, KB965494

↑ Back to the top

Article Info
Article ID : 965494
Revision : 2
Created on : 10/7/2011
Published on : 10/7/2011
Exists online : False
Views : 423