none
Unable to open Crash Dump (Windbg Win32 Error 0n87) (Dumpchk error 80070057) RRS feed

  • Question

  • I've been attempting to open a crash dump from one of our customers, but I receive the following error dialog from both 32bit and 64bit WinDbg: "Could not find the C:\[Path to Dump]\memdump.dmp Dump File, Win32 error 0n87. The parameter is incorrect." I can also see a "Could not match Dump File signature" in the command window. Using Dumpchk (both 32 & 64 bit) I get an error: "DebugClient cannot open DumpFile - error 80070057

    The dump was created using Procdump on a 32bit native application. 

    I've searched Google, but I seem to only find people who are having issues running certain commands, however I'm not able to open the dump at all.

    Is this dump file corrupted?

    Monday, November 21, 2011 10:03 PM

Answers

All replies

  • It is not a valid dump file, if the other computers has the same results after checked it.

    I think it is better to write the details steps information and send them to your customers, let them know how to capture the dump form the process using the procdump tool: http://technet.microsoft.com/en-us/sysinternals/dd996900

    Since it is not a Visual Studio Debugger problem, please try the Windows Desktop Debugging forum: http://social.msdn.microsoft.com/Forums/en-US/windbg/threads

    If there's any concern, please feel free to let me know.

    Best wishes,


    Mike Zhang[MSFT]
    MSDN Community Support | Feedback to us
    Tuesday, November 22, 2011 3:32 AM
    Moderator
  • I am writing to check the status of the issue on your side. 
    What about this problem now? 
    Would you mind letting us know the result of the suggestions?

    Mike Zhang[MSFT]
    MSDN Community Support | Feedback to us
    Thursday, November 24, 2011 11:28 AM
    Moderator
  • Hi,

    I had a similar problem, a  Win32 error 0n87, while trying to open a crash dump from a windows 8 machine, using an older version of WinDbg; updating to a newer version (in my case the one included in the wdk for win8) solved my problem;

    Best wishes,

    Tud

    Friday, June 15, 2012 9:20 AM
  • Hi,

    I had a similar problem, a  Win32 error 0n87, while trying to open a crash dump from a windows 8 machine, using an older version of WinDbg; updating to a newer version (in my case the one included in the wdk for win8) solved my problem;

    Best wishes,

    Tud

    This is the right answer. Keep your windbg updated.
    Tuesday, October 8, 2019 7:12 AM