Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Configuring the "Debugging Tools"


31 Dec 2011   #31

Windows 7 Home Premium 64 Bit OS
 
 

Don't know if the OP is still active due to date - however

Excellent tuorial

I spent a couple of hours with BSOD expert zigzag yesterday (thankyou sir)
trying to figure some of this stuff out over an IM session.

Once again I should have taken some of my own advice and come straight to the tutorials
section and I would have saved zigzag and myself somewhere in the vicinity of an hour plus we would probably both have a lot more hair!

I am about to read through every other thing I can find here at the forums in this section and
in particular, how to find information on how to decisively solve reported errors and critical events
from event viewer logs. I have worked a couple of these out in the past however I usually find it very
difficult to find specific problem related information.

Anyway - great work H2S04 - two thumbs up


My System SpecsSystem Spec
.

02 Jan 2012   #32

Windows 7/Linux
 
 

Hi All

I am trying to install the debugger package as described in this article.
From following the instructions as set out, it takes me to this page here >> Download and Install Debugging Tools for Windows

From here I see the following options for Windows 7;

Quote:
Developing for Windows 8 or Windows 7
You can install the Debugging Tools Developer Preview as part of the Windows Driver Kit Developer Preview.
Download Debugging Tools with the Windows Driver Kit Developer Preview
->> MSDN subscription and sign in required
Release Notes: Debugging Tools for Windows Developer Preview
It now appears I need a MDSN subsciption to download the debug tools! Has it now been withdrawn from the general public?
My System SpecsSystem Spec
02 Jan 2012   #33

Windows 7/Linux
 
 

Just to add I have now solved my problem. This was done by installing the SDK (Software Development Kit) and ensuring the option for installing the debug tools is checked. The 64x version of the SDK can be found here : Download: Microsoft Windows SDK 7.1 - Microsoft Download Center - Download Details

Regards.
My System SpecsSystem Spec
.


03 Jan 2012   #34

Windows 7 Pro x64
 
 

Quote   Quote: Originally Posted by Music46 View Post
Guys has the tut changed... as its 2 years old... or can we still use the above method to still debug?

Thanks
It still works. I just installed all of the Common Utilities including the Debugging Tools. However, since it is 2 years later, even though I installed as per the tutorial's instructions for a shorter program path, the SDK v7.1 installed it anyway into its default location:
"C:\Program Files\Debugging Tools for Windows (x64)\windbg.exe"

I now have the SDK v7.1 installed in 2 locations, its default above and also on my D: partition. The D: partition only has 2.5 MB's and the default above has about 41 MB's and probably about 255 MB's somewhere else on the C: O/S partition. I recommend you disregard the older tutorial's instructions regarding program location installation and simply use the default location now. This way everything is together. However, I also followed the tutorial's instructions regarding a separate Symbols folder and it already has 65 MB's so continue following that.

Many thanks to H2SO4 for posting his tutorial. Today, on my relatively new 9 month old system, I got my third BSOD in as many months. I was using BlueScreenView and it wasn't giving me enough specific information. I did get a kick out of the reproduced BlueScreen though. When you see a real MS BSOD, it gives you about 15 seconds to read it and then your system reboots. You practically need a camera to be able to study it!

WinDbg gives me accurate information. Microsoft has really improved their software. I was able to pinpoint the problem to nvlddmkm.sys, an nVidia video driver file. I will update them later. One thing I find difficult are the "kd>" commands on the bottom of the screen. I looked in the help file and I cannot find any list or explanation for them. Can someone please tell me where in the Help file these commands are located?
My System SpecsSystem Spec
25 Feb 2012   #35

windows 7 ultimate x64
 
 

When i load a specific dump file this happens , but if i get a .dmp from here the bug check seems to work fine any help thanx


Attached Thumbnails
Configuring the "Debugging Tools"-1.png   Configuring the "Debugging Tools"-2.png  
My System SpecsSystem Spec
25 Feb 2012   #36

Windows 7 - Vista
 
 

Quote   Quote: Originally Posted by deanolfc View Post
When i load a specific dump file this happens , but if i get a .dmp from here the bug check seems to work fine any help thanx
I assume you're referring to the dump file initially loading then stopping after -
Code:
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.............
??

If so, type/ paste in the commands at the kd> command line -
Code:
!analyze -v;r;kv;lmtn
That sometimes happens to me (Windbg pausing/ waiting); not sure exactly why.

In the 6.12 version you are running, additional commands may be helpful -
Code:
!analyze -v;r;kv;lmtn;lmtsmn;!sysinfo cpuinfo;!sysinfo machineid;!sysinfo cpuspeed;!sysinfo smbios
It also appears to me that the command window is "out".

2x-click anywhere along the yellow highlighted area the red arrows are pointing to:

Regards. . .

jcgriff2
My System SpecsSystem Spec
26 Feb 2012   #37

Windows 7 Ultimate x64
 
 

JC, would you mind defining each of those debugging commands you have listed?

Quote:
r;kv;lmtn
Another thing, sometimes when debugging a dump file it'll say "timestamp for example.sys could not be loaded, symbols for example.sys could not be loaded". What does this mean, exactly? I believe I've had a few dumps that the driver in those "errors" I guess you could call them were the culprit.
My System SpecsSystem Spec
27 Feb 2012   #38

Windows 7 - Vista
 
 

Quote   Quote: Originally Posted by ePeen View Post
JC, would you mind defining each of those debugging commands you have listed?
!analyze -v - analyze command verbose mode
r - show registers
kv - display stack backtrace

List loaded modules command
lmtn
lmtsmn

t = display timestamps
n = display image name
sm = sort s by module name (default = "start" memory address)

Quote:
!analyze -v;r;kv;lmtn;lmtsmn
Those commands will list the loaded drivers twice - 1 sorted by memory address; 1 sorted by driver name

Please see - [Advanced] Principles of debugging


Quote   Quote: Originally Posted by ePeen View Post
Another thing, sometimes when debugging a dump file it'll say "timestamp for example.sys could not be loaded, symbols for example.sys could not be loaded". What does this mean, exactly? I believe I've had a few dumps that the driver in those "errors" I guess you could call them were the culprit.
Yes - 3rd party driver symbol errors usually = guilty

Microsoft OS drivers can show up with symbol errors for several different reasons
- symbol config is wrong
- the symbol file is not available from the MSDL SYM site, e.g., possibly a recent Windows Update updated the driver and it has not yet been added (happened recently with win32k.sys)
- dump is corrupted
- cracked Windows
- other...

Try .reload command

Regards. . .

John
My System SpecsSystem Spec
27 Feb 2012   #39

Windows 7 Ultimate x64
 
 

Quote   Quote: Originally Posted by jcgriff2 View Post
Quote   Quote: Originally Posted by ePeen View Post
JC, would you mind defining each of those debugging commands you have listed?
-snip-
Just what I wanted, thanks a ton!
My System SpecsSystem Spec
09 Mar 2012   #40

Windows 7 - Vista
 
 

My pleasure to try and help/ explain.

If you have not yet found the Windbg HELP file, look for debugger.chm in the Windbg installation directory, usually - c:\program files\debugging tools for windows

Or type .hh in the kd> Windbg command line.

Regards. . .

John
My System SpecsSystem Spec
Reply

 Configuring the "Debugging Tools"




Thread Tools



Similar help and support threads for2: Configuring the "Debugging Tools"
Thread Forum
Solved Error Message "Failure configuring Windows update" Windows Updates & Activation
Solved Google "More" and "Search Tools" buttons no longer working... Browsers & Mail
Windows 7 hangs at "configuring updates" at launch BSOD Help and Support
"Failure configuring updates" message - advice please! Windows Updates & Activation
What is "windows 7 debugging symbols"? General Discussion
Which Setting for "Write Debugging Information" BSOD Help and Support

Our Sites

Site Links

About Us

Find 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 08:59 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33