Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Secondary dump data is limited to 256 MB in Windows 7 and Windows Server 2008 R2


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You have a Windows 7-based or Windows Server 2008 R2-based computer that crashes.
  • A third-party driver uses a Bug Check Callback Routine to include inaccessible memory in the secondary stream.
  • The secondary dump data is very large. For example, the total size is larger than 256 megabytes (MB).
In this scenario, the Bug Check Callback Routines are no longer called as soon as the 256 MB limit is reached.

↑ Back to the top


Cause

This issue occurs because the secondary dump data only allows for 32 MB per chunk and 256 MB overall.

↑ Back to the top


Resolution

After you apply this hotfix, you can use the following DWORD registry value to increase the maximum size to 4 gigabytes (GB) (0xFFFFFFFF):

HKLM\System\CurrentControlSet\Control\CrashControl\MaxSecondaryDataDumpSize
Note Each Bug Check Callback Routine is limited to one-eighth of this value for one or more chunks. To store more than the set limit, register the Bug Check Callback Routine multiple times. The callback order is not defined.

Hotfix information

 A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1.

For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To apply this hotfix, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.
File information
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows 7 and Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    VersionProductMilestoneService branch
    6.1.760
    1.18xxx
    Windows 7 and Windows Server 2008 R2SP1GDR
    6.1.760
    1.22xxx
    Windows 7 and Windows Server 2008 R2SP1LDR
  • GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows 7 and for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 7
File nameFile versionFile sizeDateTimePlatform
Crashdmp.sys6.1.7601.1811035,17611-Mar-201312:55x86
Crashdmp.sys6.1.7601.2227735,17611-Mar-201313:10x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Crashdmp.sys6.1.7601.1811040,28011-Mar-201313:51x64
Crashdmp.sys6.1.7601.2227740,29611-Mar-201313:55x64
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Crashdmp.sys6.1.7601.1811078,68011-Mar-201312:36IA-64
Crashdmp.sys6.1.7601.2227778,69611-Mar-201312:59IA-64

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

↑ Back to the top


More Information

For more information about how to write a bug check callback routine, go to the following Microsoft website:
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Additional file information

Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7
File nameX86_d1b7c00795afb3af85d1d2b530122f35_31bf3856ad364e35_6.1.7601.22277_none_4bc5f0247437185e.manifest
File versionNot applicable
File size697
Date (UTC)12-Mar-2013
Time (UTC)05:47
PlatformNot applicable
File nameX86_e1a455c39322f161cf0e89b357a3737f_31bf3856ad364e35_6.1.7601.18110_none_1b23f693373fa65d.manifest
File versionNot applicable
File size697
Date (UTC)12-Mar-2013
Time (UTC)05:47
PlatformNot applicable
File nameX86_microsoft-windows-crashdump_31bf3856ad364e35_6.1.7601.18110_none_a790a822751bdb77.manifest
File versionNot applicable
File size2,198
Date (UTC)11-Mar-2013
Time (UTC)13:22
PlatformNot applicable
File nameX86_microsoft-windows-crashdump_31bf3856ad364e35_6.1.7601.22277_none_a7e0676b8e63d448.manifest
File versionNot applicable
File size2,198
Date (UTC)11-Mar-2013
Time (UTC)13:42
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameAmd64_38c3d983f73df16f56ed616327ad10b7_31bf3856ad364e35_6.1.7601.18110_none_ebef28a9350fc025.manifest
File versionNot applicable
File size701
Date (UTC)12-Mar-2013
Time (UTC)05:47
PlatformNot applicable
File nameAmd64_82c46c22b4e61914b96f0cf7883487c5_31bf3856ad364e35_6.1.7601.22277_none_9805128670c25bfd.manifest
File versionNot applicable
File size701
Date (UTC)12-Mar-2013
Time (UTC)05:47
PlatformNot applicable
File nameAmd64_microsoft-windows-crashdump_31bf3856ad364e35_6.1.7601.18110_none_03af43a62d794cad.manifest
File versionNot applicable
File size2,200
Date (UTC)11-Mar-2013
Time (UTC)14:15
PlatformNot applicable
File nameAmd64_microsoft-windows-crashdump_31bf3856ad364e35_6.1.7601.22277_none_03ff02ef46c1457e.manifest
File versionNot applicable
File size2,200
Date (UTC)11-Mar-2013
Time (UTC)15:11
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File nameIa64_68861f80ea4ff1f71f33959f51c99c19_31bf3856ad364e35_6.1.7601.18110_none_d1e3b4d132b4bcba.manifest
File versionNot applicable
File size699
Date (UTC)12-Mar-2013
Time (UTC)05:47
PlatformNot applicable
File nameIa64_a43442d1f19f5ed8099d640e7e1d701b_31bf3856ad364e35_6.1.7601.22277_none_14edcc40eddf2ecf.manifest
File versionNot applicable
File size699
Date (UTC)12-Mar-2013
Time (UTC)05:47
PlatformNot applicable
File nameIa64_microsoft-windows-crashdump_31bf3856ad364e35_6.1.7601.18110_none_a7924c187519e473.manifest
File versionNot applicable
File size2,199
Date (UTC)11-Mar-2013
Time (UTC)14:08
PlatformNot applicable
File nameIa64_microsoft-windows-crashdump_31bf3856ad364e35_6.1.7601.22277_none_a7e20b618e61dd44.manifest
File versionNot applicable
File size2,199
Date (UTC)11-Mar-2013
Time (UTC)13:22
PlatformNot applicable

↑ Back to the top


Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseadvanced

↑ Back to the top

Article Info
Article ID : 2826910
Revision : 1
Created on : 1/7/2017
Published on : 4/9/2013
Exists online : False
Views : 188