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.

Existing memory dump file is removed if you turn off the 'Overwrite any existing file' option in Windows 8 and Windows Server 2012


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You have a computer that is running Windows 8 or Windows Server 2012.
  • The memory dump file and the paging file are located on different volumes.

    Note By default, the memory dump file and the paging file are located on the same volume.
  • You turn off the Overwrite any existing file option for the memory dump file.
In this scenario, if a system failure occurs an even number of times, an existing memory dump file is deleted. Additionally, a .tmp file is created in the volume that holds the paging file.

Note If a system failure occurs an odd number of times, a memory dump file is created.

↑ Back to the top


Resolution

To resolve this issue, install update rollup 2862768, or install the hotfix that is described in this article. This hotfix is also available at Microsoft Update Catalog.

Update information

For more information about how to obtain update rollup 2862768, click the following article number to go to the article in the Microsoft Knowledge Base:
2862768 Windows RT, Windows 8, and Windows Server 2012 update rollup: August 2013

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

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 8 and Windows Server 2012 file information notes
Important Windows 8 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:
    VersionProductMilestoneService branch
    6.2.920 0.16xxxWindows 8 and Windows Server 2012RTMGDR
    6.2.920 0.20xxxWindows 8 and Windows Server 2012RTMLDR
  • 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 8 and 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 x86-based versions of Windows 8
File nameFile versionFile sizeDateTimePlatform
Werfault.exe6.2.9200.16659385,76809-Jul-201304:25x86
Werfault.exe6.2.9200.20767385,77609-Jul-201305:26x86
For all supported x64-based versions of Windows 8 and of Windows Server 2012
File nameFile versionFile sizeDateTimePlatform
Werfault.exe6.2.9200.16659439,48809-Jul-201306:18x64
Werfault.exe6.2.9200.20767439,48809-Jul-201308:35x64
Werfault.exe6.2.9200.16659385,76809-Jul-201304:25x86
Werfault.exe6.2.9200.20767385,77609-Jul-201305:26x86

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

Additional files for all supported x86-based versions of Windows 8
File nameUpdate-bf.mum
File versionNot Applicable
File size1,962
Date (UTC)09-Jul-2013
Time (UTC)22:24
PlatformNot Applicable
File nameUpdate.mum
File versionNot Applicable
File size1,997
Date (UTC)09-Jul-2013
Time (UTC)22:24
PlatformNot Applicable
File nameX86_112df0dbb50ef01351fa6bb5827d2977_31bf3856ad364e35_6.2.9200.20767_none_9318199d67aaa728.manifest
File versionNot Applicable
File size708
Date (UTC)09-Jul-2013
Time (UTC)22:24
PlatformNot Applicable
File nameX86_8b1b820785b9d2c65369e39aa9e5bcbc_31bf3856ad364e35_6.2.9200.16659_none_57aba3728af0f58b.manifest
File versionNot Applicable
File size708
Date (UTC)09-Jul-2013
Time (UTC)22:24
PlatformNot Applicable
File nameX86_microsoft-windows-errorreportingfaults_31bf3856ad364e35_6.2.9200.16659_none_6cd79f6b0e13384f.manifest
File versionNot Applicable
File size33,828
Date (UTC)09-Jul-2013
Time (UTC)22:24
PlatformNot Applicable
File nameX86_microsoft-windows-errorreportingfaults_31bf3856ad364e35_6.2.9200.20767_none_6d546bb6273ac15c.manifest
File versionNot Applicable
File size33,828
Date (UTC)09-Jul-2013
Time (UTC)22:24
PlatformNot Applicable
Additional files for all supported x64-based versions of Windows 8 and of Windows Server 2012
File nameAmd64_0feba595f5ad6923f1e0d8eab483183d_31bf3856ad364e35_6.2.9200.16659_none_0ec25803a67a498b.manifest
File versionNot Applicable
File size1,064
Date (UTC)09-Jul-2013
Time (UTC)22:26
PlatformNot Applicable
File nameAmd64_17414c14d6365c0811207b8729904fe6_31bf3856ad364e35_6.2.9200.20767_none_5558db5f816919a5.manifest
File versionNot Applicable
File size1,064
Date (UTC)09-Jul-2013
Time (UTC)22:26
PlatformNot Applicable
File nameAmd64_c4c5287b240710381613ba780582798b_31bf3856ad364e35_6.2.9200.20767_none_d85c298511acb25b.manifest
File versionNot Applicable
File size712
Date (UTC)09-Jul-2013
Time (UTC)22:26
PlatformNot Applicable
File nameAmd64_d9e5c573ed016b4de899853fa2ac5a15_31bf3856ad364e35_6.2.9200.16659_none_bc18df03edcb905e.manifest
File versionNot Applicable
File size712
Date (UTC)09-Jul-2013
Time (UTC)22:26
PlatformNot Applicable
File nameAmd64_microsoft-windows-errorreportingfaults_31bf3856ad364e35_6.2.9200.16659_none_c8f63aeec670a985.manifest
File versionNot Applicable
File size33,834
Date (UTC)09-Jul-2013
Time (UTC)22:26
PlatformNot Applicable
File nameAmd64_microsoft-windows-errorreportingfaults_31bf3856ad364e35_6.2.9200.20767_none_c9730739df983292.manifest
File versionNot Applicable
File size33,834
Date (UTC)09-Jul-2013
Time (UTC)22:26
PlatformNot Applicable
File nameUpdate-bf.mum
File versionNot Applicable
File size2,425
Date (UTC)09-Jul-2013
Time (UTC)22:26
PlatformNot Applicable
File nameUpdate.mum
File versionNot Applicable
File size2,467
Date (UTC)09-Jul-2013
Time (UTC)22:26
PlatformNot Applicable
File nameX86_microsoft-windows-errorreportingfaults_31bf3856ad364e35_6.2.9200.16659_none_6cd79f6b0e13384f.manifest
File versionNot Applicable
File size33,828
Date (UTC)09-Jul-2013
Time (UTC)22:26
PlatformNot Applicable
File nameX86_microsoft-windows-errorreportingfaults_31bf3856ad364e35_6.2.9200.20767_none_6d546bb6273ac15c.manifest
File versionNot Applicable
File size33,828
Date (UTC)09-Jul-2013
Time (UTC)22:26
PlatformNot Applicable

↑ Back to the top


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

↑ Back to the top

Article Info
Article ID : 2851299
Revision : 1
Created on : 1/7/2017
Published on : 8/15/2013
Exists online : False
Views : 331