Fix for 'Incorrect Memory Dump' Files in Windows 7 and Windows Server 2008 R2 SP1

Microsoft has confirmed issues in which some customers running Windows 7 Service Pack 1 have come across incorrect memory dump files on their machines. "You install an x64-based version of Windows 7 SP1 or of Windows Server 2008 R2 SP1 on a computer that has the XState feature enabled. A memory dump file is generated […]

Microsoft has confirmed issues in which some customers running Windows 7 Service Pack 1 have come across incorrect memory dump files on their machines. "You install an x64-based version of Windows 7 SP1 or of Windows Server 2008 R2 SP1 on a computer that has the XState feature enabled. A memory dump file is generated on the computer.

In this scenario, the processor context is displayed incorrectly. Additionally, you receive the following error message: "A memory dump file is generated when the system crashes and a Stop error occurs," Microsoft said in KB2528507.

When you use the WinDbg command to open the memory dump file on the computer, you may found that the processor context is displayed incorrectly.

"This issue occurs because the dump generation logic saves the processor context to the dump file incorrectly on a computer that has the XState feature enabled," noted Microsoft.

Additionally, you receive the following error message:

The context is partially valid. Only x86 user-mode context is available.
The wow64exts extension must be loaded to access 32-bit state.
.load wow64exts will do this if you haven't loaded it already.

Microsoft has released a hotfix, designed to resolve this particular issue, but only this. Customers must be running Windows 7 SP1 or Windows Server 2008 R2 SP1 in the context detailed above in order to apply the hotfix.

[Source: K2528507]