Article ID: 972848 - View products that this article applies to.
Consider this scenario. You try to generate a minidump file for a .NET Framework 2.0 Service Pack 2 (SP2)-based application. The information that the file collects is not of the MiniDumpWithFullMemory type. In this scenario, you notice that it takes a long time for the file to be generated. For example, it takes several hours to generate a minidump file when you use Microsoft SharePoint. Additionally, the size of the resulting file is larger than expected.
This problem occurs because the EnumMemoryRegions method that enumerates specified areas of memory uses an incorrect size. The MiniDumpWriteDump API only calls this method if you do not use the MiniDumpWithFullMemory type in the MINIDUMP_TYPE enumeration.
Hotfix Replacement InformationThe hotfix that corresponds to KB972848 has been superseded with the hotfix KB981574, which contains all fixes that were previously included in KB972848. You should use the hotfix KB981574 to fix the issues described in KB972848. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/981574/ )The splash screen stays open longer than usual when you try to start Excel on a computer that has the .NET Framework 3.5 SP1 installed
To work around this problem, use the MiniDumpWithFullMemory type to collect information in the dump file.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about the type of information in a dump file, visit the following Microsoft Web site:
Article ID: 972848 - Last Review: August 4, 2010 - Revision: 4.0