Windows 7: Configuring the "Debugging Tools"

Thank you for this tutorial. When I tried to set up the file association (3rd step) it told me I don't have administrator privileges to do it. It also won't let me mess with the dump files in the folder. I copied one to the desktop and zipped it there, also opened it in windbg. There's no other administrator. Thanks

I'm tracking this as a noob and have only one obstacle: it doesn't like me opening files in the minidump folder. I can copy and paste them to the desktop and open them there, but it gives me grief from the minidump folder--which has a lock icon on it. How do I set this straight? Thanks

Sounds like a permissions problem. Try this Take Ownership tutorial and see if it fixes the problem.

that is really helpful.
I am using BlueScreenView on my win 7 64 bit and i will switch to windows debugger.


thanks alot.

You can also run BlueScreenView at an elevated admin level - RIGHT-click on icon, select "Run as Admin"

First, thank you guys for the work you did to put this particular page together and to continue its development. It helped me figure out my problem and resolution.

While investigating a fix to my own issue with the recommendation above, I came across a nice tool to compliment and confirm this one. It came from the following website, Blue screen of death (STOP error) information in dump files., from NirSoft, and is totally free. It helps analyze (analyse) MiniDump files.

It, just like the one in the MS WDK package, breaks down the analysis of the BSOD Memory MiniDumps, and while not creating the huge and detailed analysis of the MS tool, it creates a very succinct one and highlights the probable cause very nicely. And, does so in microseconds. It is a very simple process and extremely easy to use. I highly recommend it too.

My compliments to all you guys that contribute heavily in this forum, you make it great to know that there are great people willing to help for nothing more than the satisfaction of helping! Thank you mush!

The app from NirSoft = BlueScreenView, as mentioned by others

jcgriff2

.

Guys has the tut changed... as its 2 years old... or can we still use the above method to still debug?

Thanks

Yes it still works

This may help.

My windbg is installed in C:\Program Files\Debugging Tools for Windows (x64)

So for me worked that simple command.....