Crash Dump files: Associate with WINDBG

[Arc]

   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.



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



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



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



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



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.



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

​

 

[Britton30]

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

 

[Arc]

Thanks Gary.

It is too short to be a tutorial ....

 

[nommy the first]

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

 

[Arc]

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.



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.

 

[nommy the first]

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;


However, when I run it from an elevated one, I get this;



Nommy

 

[Arc]

For whatever, it works the same way for me

May be my bad luck.

 

[YoYo155]

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.

"C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\windbg.exe" -IA and hitting enter.

 

[nommy the first]

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.

"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

 

[YoYo155]

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

Anyway the default install locations are:

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

 

[x BlueRobot]

The default location for the x86 version of WinDbg would be for x64 systems, that does not work on a x86 system, as seen here:

 

[YoYo155]

Yep that is true, x86 based Windows won't have the apprentices and the x86 notation.
I think it's safe to say that x64 OS's are becoming the norm (and that's a good thing IMHO).

 

[x BlueRobot]

Yep that is true, x86 based Windows won't have the apprentices and the x86 notation.
I think it's safe to say that x64 OS's are becoming the norm (and that's a good thing IMHO).

I've got a 64-bit processor, so I could purchase a Windows 7 x64 DVD, but I have no need for it at the moment.

 

[YoYo155]

The only benefit is breaking the 4GB RAM limit, if you're not using that much then you don't need to .

 

[x BlueRobot]

The only benefit is breaking the 4GB RAM limit, if you're not using that much then you don't need to .

There's more benefits than that, for example KPP

x86 systems can address more than 4GB of RAM, when you set PAE, however, Windows set licensing restrictions on the amount of RAM a system can use, due to compatibility problems with drivers.

 

[YoYo155]

There's more benefits than that, for example KPP

Some won't call it a benefit ..

 

[x BlueRobot]

There's more benefits than that, for example KPP

Some won't call it a benefit ..

Well I guess

 

[Britton30]

The only benefit is breaking the 4GB RAM limit, if you're not using that much then you don't need to .

You need to get up to date on that point.

 

[Arc]

First post edited.

 

[YoYo155]

The only benefit is breaking the 4GB RAM limit, if you're not using that much then you don't need to .

You need to get up to date on that point.

Can you elaborate please ?