Compartir a través de

Why does my !runaway command not work

  • Artículo

This article has been moved to its new home here: https://benperk.github.io/msdn/2012/2012-07-why-does-my-runaway-command-not-work.html

Sometimes when I execute: !runaway in WinDbg I receive the following error:

ERROR:
!runaway: extension exception 0x80004002.  "Unable to get thread times - dumps may not have time information"

The error message says it all, but how do you fix it.  In my case ProcDump was used to create the dump and it appears that the information required to execute this statement is not collected.  However you can collect this information using ProcDump if you copy the dbghelp.dll which is installed with the Debugging Tools for Windows into the same directory as the procdump.exe.  Or add the path to the dbghelp.dll to your system path.  Then, when you create the memory dump, it will include the information provided when you execute the !runaway command.

Be sure to take note of the bit mode.  This means if you are taking a memory dump on a 64bit machine use the 64bit dgbhelp.dll and use the 32bit dbghelp.dll for a 32bit memory dump.

Comments

  • Anonymous
    January 06, 2014
    Created dump of x64 process using task manager. When I exec !runaway getting same error. ERROR: !runaway: extension exception 0x80004002.   "Unable to get thread times - dumps may not have time information"  Any ideas how i might be able to resolve this?

  • Anonymous
    July 29, 2015
    The reason is because PROCDUMP does not save that information because the dbghelp.dll is not always present.  Copy the dbghelp.dll into the same directory as PROCDUMP, then capture the memory dump.  This should resolve the issue.

  • Anonymous
    September 29, 2015
    Getting the same error when running !runaway in WinDbg with SOS on a process dump produced in x64 Task Manager rather than PROCDUMP. ERROR: !runaway: extension exception 0x80004002.    "Unable to get thread times - dumps may not have time information" Process is verified as x64 Windows running x64 process from Debug Diag.  Could this also be a issue with dbghelp.dll?  Any ideas on how to get this working?

    • Anonymous
      September 15, 2016
      Hi All,I am also getting same issue, Please let me know if !runaway works for you. Thanks.