What's new

How to Install and Configure Debugging Tools

Dwarf

The Contemplator, (1963-2013)
Moderator
Post in Progress

In order to be able to analyse .dmp files, you need to install and configure the debugger package from Microsoft.

Installation

Download it from Windows Software Development Kit (SDK) for Windows 8 Consumer Preview (click on Download under Quick Details and then click Run).

You are now asked to specify the installation location. Accept the default of either C:\Program Files (x86)\Windows Kits\8.0\ (for x64 systems) or C:\Program Files\Windows Kits\8.0\ (for x86 systems) depending on whether you are using a 32-bit or 64-bit version of W8 and click on Next.

The next question is optional, it pertains to the Customer Experience Improvement Program, so click either Yes or No as appropriate and then click Next.

Accept the License Agreement by clicking Accept.

Here you can choose the feature(s) that you wish to install. We are only interested in Debugging Tools for Windows so deselect the other options and then click Install. This may take some time, so be patient. Provide Administrative Credentials to continue if the UAC prompt appears.

When the message Welcome to the Windows Software Development Kit! appears, the selected option(s) has/have been installed. Click on Close.

Configuration

Now that the tool has been downloaded and installed, it needs to be configured. Open an http://www.eightforums.com/tutorials/2754-elevated-command-prompt-open-windows-8-a.html and change to the installation folder by entering the following at the prompt:

chdir /d C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\ (for 64-bit systems)
chdir /d C:\Program Files\Windows Kits\8.0\Debuggers\x86\ (for 32-bit systems)

At the prompt, enter windbg -IA in order to register it as the default handler for the common dump file types (.DMP, .HDMP, .MDMP, .KDMP, and .WEW). Click OK on the confirmation window. This will enable the Debugger to automatically run when you click/double-click on a dump file. You can, of course, choose the manual option of clicking on File and Open Crash Dump... (or use the Ctrl+D shortcut) and then browsing to the required file.

For the tool to run correctly, it needs to be able to access certain symbols. These can be downloaded as a standalone package from Microsoft. Choose the appropriate link below in order to download them.

32-bit http://download.microsoft.com/downl...Winmain.8250.0.120217-1520.X86FRE.Symbols.msi
64-bit http://download.microsoft.com/downl...Winmain.8250.0.120217-1520.x64FRE.Symbols.msi

Once downloaded, run the installer. When it has finished computing space requirements (this may take a while), click on Next. Check the option I accept the terms in the License Agreement and then click Next. The next screen allows you to change the storage location for the symbols, or you can accept the default location that has been chosen by the installer. I recommend that you change it by clicking on Browse and then setting the destination folder to C:\Symbols\ (create this folder if it doesn't exist). Click Next and then Install to continue. The symbols will now be installed in the chosen directory. Please be patient, as this will take some time. Click Finish when prompted.

The Debugger now needs configuring in order to access these symbols, so at the command prompt enter windbg. The main program will open. Click on File and Symbol File Path … (or use the Ctrl+S shortcut). In the dialogue box that appears, enter SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols and then click OK. Close and reopen the debugger to confirm the program update. You will be prompted to Save information for workspace? when closing the Debugger, choose Yes to continue (choose this option if prompted by this prompt in the future). The program will now consult the local folder for any required symbols, and automatically contact the Symbol Server for any that aren't present locally.
 
Last edited:

My Computer

System One

  • OS
    Windows 8.1 Pro RTM x64
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Dwarf Dwf/11/2012 r09/2013
    CPU
    Intel Core-i5-3570K 4-core @ 3.4GHz (Ivy Bridge) (OC 4.2GHz)
    Motherboard
    ASRock Z77 Extreme4-M
    Memory
    4 x 4GB DDR3-1600 Corsair Vengeance CMZ8GX3M2A1600C9B (16GB)
    Graphics Card(s)
    MSI GeForce GTX770 Gaming OC 2GB
    Sound Card
    Realtek High Definition on board solution (ALC 898)
    Monitor(s) Displays
    ViewSonic VA1912w Widescreen
    Screen Resolution
    1440x900
    Hard Drives
    OCZ Agility 3 120GB SATA III x2 (RAID 0)
    Samsung HD501LJ 500GB SATA II x2
    Hitachi HDS721010CLA332 1TB SATA II
    Iomega 1.5TB Ext USB 2.0
    WD 2.0TB Ext USB 3.0
    PSU
    XFX Pro Series 850W Semi-Modular
    Case
    Gigabyte IF233
    Cooling
    1 x 120mm Front Inlet 1 x 120mm Rear Exhaust
    Keyboard
    Microsoft Comfort Curve Keyboard 3000 (USB)
    Mouse
    Microsoft Comfort Mouse 3000 for Business (USB)
    Internet Speed
    NetGear DG834Gv3 ADSL Modem/Router (Ethernet) ~4.0 Mb/sec (O2)
    Browser
    IE 11
    Antivirus
    Avast! 8.0.1497 MalwareBytes 1.75.0.1300
    Other Info
    Optical Drive: HL-DT-ST BD-RE BH10LS30 SATA Bluray
    Lexmark S305 Printer/Scanner/Copier (USB)
    WEI Score: 8.1/8.1/8.5/8.5/8.25
    Asus Eee PC 1011PX Netbook (Windows 7 x86 Starter)

GMan

Banned
This is really good for people wanting to get into doing bsod analysis on the long term. For the short term, I recommend against it. Here's why -

Say there are crashes pointing to the video driver. Now almost all people are going to say "hey, let me roll back my video driver to this version or that" and in the meanwhile, just because it said the video driver is at fault, the truth is in may cases it is very likely not to be. Only really, really old ones are usually clearly to blame.

Even experienced bsod analysts very often say "update DirectX" or similar. That's not going to help.

Then there are network cases. Take for instance Zone Alarm and its notorious 0x7f netio.sys failures (because of poor config by end user). If he/she read the dump, they would then go and revert to old network drivers instead. Not good.

Same for AVG and the like. These are just some cases out of the hundreds an experienced bsod analyst will know right away while an amateur would be running around doing all the wrong things and ending up with an even bigger problem.

lol I've seen people say things like "Microsoft expletive here" because a kernal driver keeps crashing on them and Microsoft made it.

All that being said, anyone interested in learning for the long term more so than just analyzing "his/her dump" - p.m. are welcome. :)

And anyone going to jump in and start analyzing 8 crash dumps, you'll need to manually download and install the symbols. Things may have changed by now, but my debugger would not access 8 symbols at all on Microsoft's server:

Download Windows Symbol Packages
 

My Computer

System One

  • OS
    8250 x86 + 7 SP1 x86 + Ubuntu 12.04 LTS x86
    CPU
    P4 3.4 GHz HT
    Motherboard
    MSI-7211
    Memory
    OCZ 2 GB DDR @ 400 MHz
    Graphics Card(s)
    HIS AGP HD 3850 Turbo Ice-Q
    Sound Card
    MOTU Traveler firewire interface
    Monitor(s) Displays
    Acer x223w
    Screen Resolution
    1680x1050
    Hard Drives
    WD Caviar Black 1 TB Sata II, WD 400 GB Sata I, WD 120 GB Sata I
    PSU
    300W generic
    Case
    Cybertron
    Keyboard
    Logitech Classic Keyboard 200, Dell RT7D20
    Mouse
    Logitech M510
    Internet Speed
    2 MByte/sec Down, 250 KByte/sec Up

zigzag3143

Banned
Symbol server has been intermittent for about 12 hours. Seems ok now.
 

My Computer

System One

  • OS
    WCP
    System Manufacturer/Model
    HP
    CPU
    2@ 4.9 Hz
    Memory
    64 gig
    Graphics Card(s)
    Nvidia 9600
    Sound Card
    integrated
    Monitor(s) Displays
    laptop
    Screen Resolution
    1440x900
    Hard Drives
    300gig internal and a bunch ext
    Cooling
    not much
    Keyboard
    Built-in
    Mouse
    Logitch Anywhere Mx wireless mouse
    Internet Speed
    50 down 1.5 up

Dave76

Team Member
VIP Member
Pro User
Nice post/tutorial, this should be a Sticky.

Good information for those that want to start BSoD analysis.
 

My Computer

System One

  • OS
    Windows 8.1 Pro x64/ Windows 7 Ult x64
    Computer type
    PC/Desktop
    System Manufacturer/Model
    76~2.0
    CPU
    Intel Core i5-3570K 4.6GHz
    Motherboard
    GIGABYTE GA-Z77X UD3H f18
    Memory
    8GB (2X4GB) DDR3 1600 CORSAIR Vengeance CL8 1.5v
    Graphics Card(s)
    Sapphire HD 7770 Vapor-X 1GB DDR5
    Sound Card
    Onboard VIA VT2021
    Monitor(s) Displays
    22" LCD Dell SP2208WFP
    Screen Resolution
    1680x1050
    Hard Drives
    Samaung 840Pro 128GB, Seagate 500GB SATA2 7200rpm 32mb, Seagate 1TB SATA2 7200rpm 32mb,
    PSU
    Corsair HX650W
    Case
    Cooler Master Storm Scout
    Cooling
    Corsair H80 w/Noctua NF P12 12cm fan, case fans 2X14cm
    Keyboard
    Logitech Wave
    Mouse
    CM Sentinel
    Internet Speed
    Abysmal
    Browser
    Opera Next
    Other Info
    Dell Venue 8Pro: Baytrail Z3740D, 2GB Ram, 64GB HDD, 8" IPS Display 1280 x 800, Active Stylus.
    Haswell laptop: HP Envy 17t-j, i7-4700MQ, GeForce 740M 2GB DDR3, 17.3" Full HD 1920x1080, 16GB RAM, Samsung 840 Pro 128GB, 1TB Hitachi 7200 HDD,
    Desktop: eSATA ports,
    External eSATA Seagate 500GB SATA2 7200rpm,

m4v3r1ck

New Member
Member
Great post / tutorial, thanks!
 

My Computer

System One

  • OS
    Windows 8 Pro x64
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Apple Mac Pro 5.1 (2012)
    CPU
    DODECA @ 2.66 GHz
    Motherboard
    MP 5.1
    Memory
    24 GB @ 1333 MHz
    Graphics Card(s)
    EVGA GTX-670-4GB-FTW-PC & ATI XT 2600 HD Mac
    Hard Drives
    Samsung 840 EVO's 500GB @ Apricorn Velocity DUO x2 PCIe
    Case
    The most beautiful IMHO
    Keyboard
    Wired
    Mouse
    Mighty Mouse
    Antivirus
    ESET Internet Security Pro
Top