How to fix corrupted memory dump effectively and efficiently
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 theBlue 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 method to do that.
Steps to fix corrupted memory dump file errors
Solution 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 check box.
- Similarly, clear the Enable heartbeat monitoring for the virtual machine check box 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 the issue.
Solution 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 cancelled, run the following Windows PowerShell command.
PS C:> (Get-ClusterResource <Object>).EmbeddedFailureAction = 1
Exit Windows PowerShell and restart your PC. This should resolve your issue for good.
Also, here are some additional resources to browse through.
- Fix: “Critical structure corruption” BSOD error in Windows 10
- The Windows Admin Center tool is now available for IT admins
- 3 of the best virtual machines for Windows 10 to use in 2019
- September 2016 build for Windows developer virtual machines out now
Have you ever tried using MS Works on Windows 10? It might be harder than you think. Even though Works has been discontinued by Microsoft, […]
Users reported on Reddit that Windows 10 v1903 disabled Windows Defender real-time protection. This is often the case when you installed another antivirus solution on […]