How to disable BugCheck memory dumps (Win7) RRS feed

  • Question

  • I've  gone ahead and disabled memory dumps in the Startup and Recovery tab.  But for some reason on a BugCheck BSoD I still get a small memory dump in %SystemRoot%\Minidump.

    I have also double checked that the registry entry CrashDumpEnabled (in HKLM\SYSTEM\CurrentControlSet\Control\CrashControl) is set to 0.

    Is there any other way to disable minidumps?


    One more question, after rebooting from a crash (that does a memory dump) why does Windows relocate the Pagefile from its current location to a different Logical Address on the volume?

    • Changed type Carey FrischMVP Saturday, April 30, 2011 11:59 PM Is a question
    Friday, April 29, 2011 10:08 PM

All replies

  • Hi,

    According the issue , you may  set the OS debug information options via WMIC.


    Please refer the following:


    The (none) option does not record any information in a memory dump file. To specify that you do not want Windows to record information in a memory dump file by modifying the registry, set the CrashDumpEnabled DWORD value to 0. For example, type the following information at a command prompt, and then press ENTER:

    wmic recoveros set DebugInfoType = 0


    Hope that helps

    Tuesday, May 3, 2011 9:41 AM
  • Thank you for taking the time to reply, but it is ignoring this entry and still doing Minidump's.

    This is not limited to my current Windows install, this happens on All the copy's of Windows 7 x64 I have.


    This is a example of a recent crash:


    The BugCheck wrote these values to the registry:



    Wrote a 302,341 byte memory dump to:



    And put this entry in the System Event Log:

    The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000050 (0xfffff88402d79ae8, 0x0000000000000000, 0xfffff88004d2b94a, 0x0000000000000005). A dump was saved in: C:\Windows\Minidump\050511-13400-01.dmp. Report Id: 050511-13400-01.


    It doesn't seem to care that CrashDumpEnabled has a value of 0.  It writes the dump anyway (it even states that its doing a memory dump on the BlueScreen).

    Friday, May 6, 2011 12:00 AM
  • From KB886429: "In the first stage of a memory dump operation, the Session Manager Subsystem process (SMSS.exe) performs part of the Savedump tool's job before Windows creates the pagefile. SMSS examines the pagefile head block to determine whether this file is a valid memory dump file. If the memory dump file is valid, SMSS truncates the original pagefile to the size of the dump file and renames this file to Dump<var>xxx</var>.tmp. "

    Still does not answer why the memory dump settings are not respected, but it does tell me why the pagefile is recreated after a crash.

    Friday, August 12, 2011 4:47 PM