Article ID: 2509818 - View products that this article applies to.
You use a debug tool that uses the ICorDebug interface in the Microsoft .NET Framework 4 to analyze some mini-dump files. For example, you use the Microsoft Visual Studio 2010 debugger or the Microsoft .NET Framework Command-Line debugger (Mdbg.exe).
In this situation, the ICorDebug interface does not resolve managed frames on all stacks. Additionally, the Visual Studio 2010 debugger displays an error message that resembles the following:
Note This issue does not occur when you use a debugger that does not use the ICorDebug interface. For example, this issue does not occur when you use Microsoft Windows Debugger (WinDbg).
Managed module(s) not found, frames cannot be determined.
This issue occurs because the memory that stores some private data structures for the common language runtime (CLR) is missing in mini-dump files.
When the ICorDebug interface reads the memory from the mini-dump files, the managed frames cannot be converted successfully. Therefore, the issue that is mentioned in the "Symptoms" section occurs.
Hotfix informationA supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that this article describes. Apply it only to systems that are experiencing this specific problem.
To resolve this problem, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft website:
http://support.microsoft.com/contactus/?ws=supportNote In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
Important Before you apply the hotfix, you must identify which version of common language runtime (CLR) the dump file uses. To do this, open the dump file in Visual Studio. The version number is displayed at the top of the page. If the version number is 4.0.30319.235, contact Microsoft Customer Support Services to obtain the hotfix KB2607656. Otherwise, install hotfix KB2509818. If you cannot identify the CLR version, we suggest that you install both of the hotfixes.
PrerequisitesTo apply this hotfix, you must have the Microsoft .NET Framework 4 installed.
Restart requirementYou must restart the computer after you apply this hotfix if any affected files are being used.
We recommend that you close all .NET Framework applications before you apply this hotfix.
Hotfix replacement informationThis hotfix package does not replace a previously released hotfix package.
File InformationThe English (United States) version of this hotfix package uses a Microsoft Windows Installer package to install the hotfix package. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date 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.
For all supported x86-based versions of Windows XP, of Windows Server 2003, of Windows Vista, of Windows Server 2008, and of Windows 7
For all supported x64-based versions of Windows XP, of Windows Server 2003, of Windows Vista, of Windows Server 2008, of Windows 7, and of Windows Server 2008 R2
Collapse this tableExpand this table
Collapse this tableExpand this table
To work around this issue, capture a complete memory dump file instead of a mini-dump file.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Article ID: 2509818 - Last Review: October 19, 2011 - Revision: 3.0