- Memory dumps are an excellent way for developers to troubleshoot various Windows 10 errors.
- Memory dumps can become corrupted, and the data displayed by them can become unusable.
- Corrupted memory dumps can eventually lead to Blue Screen of Death errors.
- For more great troubleshooting guides, visit our dedicated Windows 10 Errors page.
It isn’t every day that you come across a corrupted memory dump file But when you do, you will rue your luck you did. That is for the simple reason that the condition renders your PC virtually unusable and should explain why it is called the Blue Screen of Death.
Another reason corrupted memory dump file is quite uncommon is that it will come to haunt you in some specialized scenarios — like when you have a virtual machine operating within a cluster environment on a Windows Server 2012 or Windows Server 2008 R2 platform.
Also, the reason the corrupted memory dump file is generated is that the option Enable heartbeat monitoring for the virtual machine is selected in the virtual machine.
With this setting enabled, the clustered virtual machine gets reset after a minute even though the clustered virtual machine needs more than a minute to write the memory dump.
As such, one easy solution to set things right here is to set the Enable heartbeat monitoring for the virtual machine to the disabled state. Listed below are the methods to do that.
How do I fix corrupted memory dump file errors?
1. Change the setting via GUI
- For this, open Failover Cluster Manager first and click on Roles.
- Search for the virtual machine resource and click on the Resources
- Under Resources tab, right-click on the virtual machine.
- Click on Properties and select the Settings
- There under Heartbeat Setting, clear the Enable automatic recovery for application health monitoring checkbox.
- Similarly, clear the Enable heartbeat monitoring for the virtual machine checkbox and then click OK for the setting to take effect.
This should help prevent the generation of the corrupted memory dump file from being generated though there is another way to deal with the issue.
2. Change the setting via Windows PowerShell
- Start Windows PowerShell.
- You do this by right-clicking on Start and selecting Windows PowerShell (Admin).
- Alternately, you can simply type PowerShell in the Cortana search box, right-click on the Windows PowerShell app shown and select Run as administrator.
- Type the Windows PowerShell command: PS C:> Get-ClusterResource.
- This will reveal the virtual machine name.
- Next, type the following command:
- PS C:> Get-ClusterResource <VirtualMachineName> | Get-ClusterParameter CheckHeartbeat
- This will reveal if Enable heartbeat monitoring for the virtual machine and Enable automatic recovery for application health monitoring are both selected.
- You will know both are selected if the CheckHeartbeat value is shown as 1.
- Type the following Windows PowerShell command to set CheckHeartbeat value to 0.
- PS C:> Get-ClusterResource <VirtualMachineName> | Set-ClusterParameter CheckHeartbeat 0
- However, just in case you’d like only the Enable automatic recovery for application health monitoring option to be canceled, run the following Windows PowerShell command:
- PS C:> (Get-ClusterResource <Object>).EmbeddedFailureAction = 1
- Exit Windows PowerShell and restart your PC.
FAQ: Learn more about Memory Dumps and their issues
- What is a Memory Dump?
A memory dump can be defined as a process in which the components of memory are displayed and stored in case of a system or an application crash.
- What is a Corrupted Memory Dump?
A Corrupted Memory Dump appears when the system can’t provide you with a working Memory Dump, as the data itself becomes corrupted. When that happens, Memory Dump files may appear.
- Are corrupted memory dumps severe?
These error messages are in the fatal system error category, and they will usually end up providing you with BSoD messages. Check out this article to see how you can fix such error messages.
By following the steps mentioned above, you should be able to get rid of any corrupted memory dumps that may be plaguing your system.
Let us know which of the solutions worked best for you by leaving us a message in the comments section below.
Editor’s Note: This post was originally published in December 2018 and has been since revamped and updated in March 2020 for freshness, accuracy, and comprehensiveness.