1. #1
    jcgriff2's Avatar
    Join Date
    Feb 2012
    New Jersey Shore
    • specs System Specs
      • Manufacturer:
      • Model Number:
        HP ENVY TouchSmart 17-j130us Notebook - E8A04UA
      • Motherboard:
        HP Insyde 720265-501 6050A2549501-MB-A02
      • CPU:
        Intel Core i7-4700MQ Processor with Turbo Boost up to 3.4GHz.
      • Memory:
        12GB DDR3L SDRAM (2 DIMM)
      • Graphics:
        Intel HD graphics 4600 with up to 1792MB total graphics memory
      • Sound Card:
        Beats Audio quad speakers and two subwoofers
      • Hard Drives:
        1TB 5400RPM hard drive with HP ProtectSmart Hard Drive Protection
      • Disk Drives:
        Hitachi 500 GB SSD; 7 TB USB External
      • Power Supply:
      • Case:
      • Display:
        17.3-inch diagonal HD+ BrightView LED-backlit touchscreen display (1600 x 900)
      • Operating System:
        Windows 8.1

    Add Windbg (kd>) Commands to Program Default for Dump Files

    Most of us have Windbg set up as the default program for dump files - Register Windbg for dump files (File Associations)

    Did you know that you can also add kd commands to run by default as well?

    Simply setting up Windbg as the default program leaves Windbg at this point after double-clicking on a dump file -- waiting for you to enter additional commands at the kd> line such as !analyze -v -
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    Use !analyze -v to get detailed debugging information.
    BugCheck 50, {fffff80011b0e74d, 8, fffff80011b0e74d, 2}
    Could not read faulting driver name
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+43346 )
    Followup: MachineOwner
    I changed my default set up to include these commands -
    !analyze -v;r;kv;lmtn;lmtsmn;.bugcheck
    So, when I double-click on a dump file, all of the basic commands that I like to run do so without me having to enter them at the kd> command line.

    Try it out!

    Back up your registry first (I opted to create a system restore point).

    Maneuver to this registry key and add your default Windbg commands -

    The (Default) should look something like this (by default):
    "C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x64\windbg.exe" -z "%1"
    I added the kd commands that I mentioned above:
    "C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x64\windbg.exe" -z "%1" -c "!analyze -v;r;kv;lmtn;lmtsmn;.bugcheck"
    Double-clicking on a dump file now runs all of the commands in RED by default.

    Please note that I made these changes yesterday for the first time, so it is far from 100% tested.

    Regards. . .

    axe0 and softwaremaniac say thanks for this.

    BSOD Posting Instructions - Windows 10, 8.1, 8, 7 & Vista ` ` `Carrona Driver Reference Table (DRT)
    Sysnative Hex-Decimal-UNIX Date Conversion

    Has Sysnative Forums helped you?
    Please consider donating to help support the forum.
    Thank You!

    Microsoft MVP 2009-2015
    Windows Insider MVP 2018 - Present

    • Ad Bot



  2. #2

    Join Date
    Jul 2017
    Cambridge, UK

    Re: Add Windbg (kd>) Commands to Program Default for Dump Files

    If anyone has started to use the new WinDbg Preview which is now available from the Windows Store in W10 you might be interested to know you can still add these same commands to run automatically after double-clicking on the dump file.

    Back up your registry first or create a system restore point.

    Manoeuvre to this registry key and add your default Windbg commands to the parameters string value, adding them after the -z "%1" as previously done

    A quick way to find the key is to use Find and search for WinDbg Preview, it will be the first one found from the top of the registry entries.

    There is a clue in the name, this new version is a Preview and is being actively worked on and improved. Use the Feedback function to request any new features. I have to say that I like the more modern interface, basically it hasn't changed what I do but there appear to be some new features and my guess is this version will be updated at a faster pace than the old WinDbg.
    jcgriff2 and x BlueRobot say thanks for this.

Similar Threads

  1. Add Windbg (kd>) Commands to Program Default for Dump Files
    By jcgriff2 in forum BSOD Processing Apps Download | Information | Discussions
    Replies: 6
    Last Post: 02-25-2018, 12:18 PM
  2. Register Windbg for dump files (File Associations)
    By jcgriff2 in forum BSOD Kernel Dump Analysis Debugging Information
    Replies: 6
    Last Post: 09-04-2017, 06:08 PM
  3. OSR Online - Analyst's Perspective: 10 WinDBG Commands You Might Not Know (But Should
    By jcgriff2 in forum BSOD Kernel Dump Analysis Debugging Information
    Replies: 0
    Last Post: 11-16-2012, 09:36 PM

Log in

Log in