Configuring the "Debugging Tools"

yea i did that and i got windows cannot find the file path specified.

so i wrote C:\>chdir /d C:\debuggers instead.

I am here now, C:\debuggers>windbg.exe -IA
and i got that internal external command etc etc

do i need to download the proper 8.0 debugging tools btw? or the stand-alone 7.1 i've downloaded and put on the wrong path worked just as well?
I'm downloading the debugging tools part of WDK as we speak, i hope its the correct one

===
btw, i posted on my BSOD thread regarding uninstallation of driver and getting rid of asus utility, kindly check it out at your leisure

cheers,

KP

wish you a great week!!

Even if the dumps are not associated with windbg, you can open windbg, then File > Open Crash Dump and browse to the dump and open it. The result will be the same.

i tried this as well since its on post#1,, there are 2 dump file on my dump folder, when i opened 1 of them,, i got a pop up saying "executable search is:" and it doesnt open just stay that way.

when i opened the other one, i got "you dont have to correct symbols" or smthn... i cant rmmbr what.


on that note, i will try downloading your link and go from there,


cheers again,


KP~!

okay i've tried opening the crash dump file, and its already associated with dmp files, the windbg.exe -IA command works properly this time, however when i tried opening dump files, i got

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:

and that's it. also on the bottom it was written, debuggee not connected.

may i ask wht should i do now?

If you set things up correctly (which from the looks of it you did), what's happening is it's downloading all the symbol files and storing it in the folder you assigned (C:\SymCache). It will take a while, especially for the first run, so let it sit. May even take several minutes, depending on your network connection. Once it's done, the "debuggee not connected" will disappear and it'll provide the prompt and will not give any big symbol errors.

Some symbol errors are expected for drivers that are 3rd-party drivers, since they very commonly do not include symbols (nor will MS have it in their symbol server). What you'll want to worry about is when it pops up that it couldn't find symbols for Windows modules. When that happens usually it'll prompt you with a big massive message about no or incorrect symbols.

awesome, i think it takes a quite long while due to slow internet connection then.

i will post my result on the appropriate thread,

cheers for the help!!

KP