Configuring the "Debugging Tools"

I've had to deal with the nagging workspace problem as well. Sometimes I've found if I manually go to Options and tell it to Never save for Workspace Prompts, then save Workspace As... and name it Default, that works. Probably best to do this when no dmp file is loaded and it's just a blank Windbg session. This is what has worked for me in the past, though results may vary.

Would it be possible to upload my dump files to see why I keep getting BSoD?

every couple months, my laptop returned a IRQL Less or Equal BSOD, i clean installed windows every few months.
Koolkat (tx for your tremendous help), analyze that the error was from the installation of my atheros wireless driver. i installed the driver from the CD driver that came from the notebook. and i updated the driver through that CD software as well.

i wanna learn debugging myself because i wanted to see whether my clean install still have that unclean driver installation or not. So, i wanted to know which file from the dump folder from the BSOD instruction did koolkat found my problem.

i assume its the dmp file and thats how i ended up on this thread.


Now i've read this thread and went to this link Download and Install Debugging Tools for Windows
which one should i download since there are many links available there.

the first download link available over there was this one Install Debugging Tools for Windows as part of the WDK
but since its written for windows 8 i decided to downloaded this one instead of that one
Download the Microsoft Windows SDK for Windows 7

under the second link there is another download link Download Windows Symbol Packages should i download this as well?

===
so far i have downloaded Download the Microsoft Windows SDK for Windows 7 and i got stuck on this step of this tutorial ==>
C:\debuggers>windbg.exe -IA

windbg.exe is not recognized as an internal or external command, operable program or batch file


did i download the wrong link? should i download the first link? and should i download the symbol package as well?

While the WDK for Windows 8 caters to that OS, the Debugging Tools that comes with it is the latest version of Windbg and can be installed on WinXP and above and will open any Windows crash dump from any Windows OS.

To explain Arc's method, he's telling you that your issue is that you need to first find the directory the debugger (Windbg) is installed, then open that directory in the command line and type the appropriate command to associate dump files with Windbg. You can simply navigate to the folder normally, then when you have it open, hold Shift and right click any white space in that folder and you'll have the option to "Open command window here". Then follow up with the Windbg.exe -IA.

hi mates~! tq very very much for helping me

i downloaded Download the Microsoft Windows SDK for Windows 7 instead of Install Debugging Tools for Windows as part of the WDK

okay so... from vir gnarus explanation i take it i downloadded the wrong file? since what i get from my start windows is start => all program => debuggging tools for windows x64 and microsoft windows sdk v7.1

Secondly... i wrote on my previous post that i followed the tutorial so... i did not install it at the default path, (i was following the step on post#1 which ordered me to Override the default install path and install to c:\debuggers instead

so my path is c:\debuggers.

should i return the debugging tools path to where arc tells me it should i pointed to...? how do i do that?

or is it easier to just uninstalled the 7.1 kit and download the correct 8.0 kit? how do i uninstall the 7.1 kit by the way, i cant find it on revo uninstaller or control panel.

===
sorry for the big font, did not meant to use it at all

cheers,

KP~!

so... the correct link to download is it the 1st WDK link? or SDK link or the standalone component from this link http://msdn.microsoft.com/en-us/windows/hardware/gg463009.aspx?