Crash Dump files: Associate with WINDBG

Page 1 of 3 123 LastLast

  1. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #1

    Crash Dump files: Associate with WINDBG


       Information
    This instructions are for associating crash dump files with windbg, debugging tool for windows; so that double clicking on the crash dump files will directly open it with windbg only.
       Note
    It is suggested that you install windbg in the default location. Installing it in any other location is not really needed.


    When you have WINDBG installed, if you associate the crash dumps with that program, a simple double click on a crash dump will open it with windbg directly. Here's how:
    1. Open a command prompt.

    Crash Dump files: Associate with WINDBG-1.jpg

    2. Get back to root. Simple DOS command.... cd/

    Crash Dump files: Associate with WINDBG-2.jpg

    Note that after hitting enter, you are on C prompt.

    3. Now go the the installation directory .... CD (change directory).
    The usual installation location is "C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\windbg.exe" ... so we have changed the directory to C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64

    Crash Dump files: Associate with WINDBG-3.jpg

    4. Now, the required command is .... windbg.exe -IA

    Crash Dump files: Associate with WINDBG-4.jpg

    Put the command and hit enter .... windbg will open automatically, saying this ...

    Crash Dump files: Associate with WINDBG-2013-11-05_114108.jpg

    Done. Now every double click on a single crash dump will open it in windbg directly.
    If you are not certain about your installation directory that is needed as per step 3 ..... determine it ...
    1. Go to Start > All Programs> Windows Kits> Debugging tool for windows> Windbg, and right click on it. Choose "Properties from the context menu.

    Crash Dump files: Associate with WINDBG-.jpg

    2. Look at the "target" of Windbg properties dialog. It is where the program is installed.

    Crash Dump files: Associate with WINDBG-b.jpg
    Last edited by Arc; 07 Nov 2013 at 02:00.
      My Computer


  2. Posts : 24,479
    Windows 7 Ultimate X64 SP1
       #2

    Good info Archie, I think it would be good if posted as a tutorial.
      My Computer


  3. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
    Thread Starter
       #3

    Thanks Gary.

    It is too short to be a tutorial .... :)
      My Computer


  4. Posts : 1,454
    Microsoft Windows 8.1 64-bit Professional
       #4

    Nice tut my friend!

    Another way to achieve the same is by opening an Elevated Command Prompt, pasting this ("C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\windbg.exe" -IA) and hitting enter. Maybe include this as a second option?


    Nommy
      My Computer


  5. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
    Thread Starter
       #5

    nommy the first said:
    Nice tut my friend!

    Another way to achieve the same is by opening an Elevated Command Prompt, pasting this ("C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\windbg.exe" -IA) and hitting enter. Maybe include this as a second option?


    Nommy
    Well, that is the reason behind this write-up. Have you ever tried that yourself? Here is what happens with that command.

    Crash Dump files: Associate with WINDBG-2013-11-05_230607.jpg

    If you look at what I have written in the original post, you will see that it is the same thing, but divided into two commands, as two other steps. Otherwise it will not go anywhere.

    We should not post such things that we are not totally aware of. First thing is to learn. What comes next is to practice in live threads. Then, after acquiring knowledge, experience and expertise, we should share our knowledge.

    And, a simple command prompt works as good as an elevated command prompt in this case. Command prompt does not need to elevate everywhere.
      My Computer


  6. Posts : 1,454
    Microsoft Windows 8.1 64-bit Professional
       #6

    Hmm weird.. I have tried it, and it worked perfectly fine for me.

    I see your problem though, you forgot to add the " before C:\

    When I run my command from a normal command prompt, I get this;
    Crash Dump files: Associate with WINDBG-untitled.png

    However, when I run it from an elevated one, I get this;
    Crash Dump files: Associate with WINDBG-untitled1.png


    Nommy
      My Computer


  7. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
    Thread Starter
       #7

    For whatever, it works the same way for me

    May be my bad luck.
      My Computer


  8. Posts : 3,056
    Windows 10
       #8

    Handy, Arc :).

    What Stefan suggests also works for me as well but not how he wrote it.
    The mistake is that you are looking for the x64 debugger in the x86 program files.

    nommy the first said:
    "C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\windbg.exe" -IA and hitting enter.
      My Computer


  9. Posts : 1,454
    Microsoft Windows 8.1 64-bit Professional
       #9

    YoYo155 said:
    Handy, Arc :).

    What Stefan suggests also works for me as well but not how he wrote it.
    The mistake is that you are looking for the x64 debugger in the x86 program files.

    nommy the first said:
    "C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\windbg.exe" -IA and hitting enter.
    Oops, seems I messed up during the installation
    Ah well, it works for me so no reason to change anything


    Nommy
      My Computer


  10. Posts : 3,056
    Windows 10
       #10

    Haha yeah, if it ain't broke...

    Anyway the default install locations are:

    Code:
    "C:\Program Files\Windows Kits\8.0\Debuggers\x64\windbg.exe"
    "C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x86\windbg.exe"
    :)
      My Computer


 
Page 1 of 3 123 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 09:16.
Find Us