Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>There is an <a href="http://msdn.microsoft.com/en-us/library/d5zhxt22.aspx" rel="nofollow noreferrer">"how to create dump"</a> on msdn, which gives 4 ways, perhaps the third one might be worth trying in your case.</p> <ol> <li><p>While you are debugging a native process in Visual Studio, you can save a dump from the Debug menu. For more information, see <a href="http://msdn.microsoft.com/en-us/library/fk551230.aspx" rel="nofollow noreferrer">How to: Save and Open Dump Files</a>. </p></li> <li><p>If you have Just-In-Time debugging enabled, you can attach to a crashed process that is running outside the debugger, break the process, and then save a dump file. For more information, see <a href="http://msdn.microsoft.com/en-us/library/fk551230.aspx" rel="nofollow noreferrer">How to: Save and Open Dump Files</a>. </p></li> <li><p>You can create a dump by using the UserDump utility, which is part of the OEM Support Tools package. You can download a copy from <a href="http://download.microsoft.com/download/win2000srv/Utility/3.0/NT45/EN-US/Oem3sr2.zip" rel="nofollow noreferrer">http://download.microsoft.com/download/win2000srv/Utility/3.0/NT45/EN-US/Oem3sr2.zip</a>. </p></li> <li><p>You can create a dump by using the Autodump+ (AD+) utility, which is part of Microsoft Debugging Tools for Windows. You can download Debugging Tools for Windows from Windows Hardware Developer Central at <a href="http://www.microsoft.com/whdc/DevTools/Debugging/default.mspx" rel="nofollow noreferrer">http://www.microsoft.com/whdc/DevTools/Debugging/default.mspx</a>. </p></li> </ol>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload