Debug Diagnostic 2 : Creating a rule in Performance mode

[Updated on Dec. 18th 2017]

Currently the latest version of Debug Diagnostic is Version 2 update 2, which can be downloaded here :

(Note : both 64bit and 32bit versions are available in this link, please download the one matching your machine.)

This version includes 2 components : Debugdiag 2 Collection and Debugdiag 2 Analysis.

Debugdiag 2 Collection is used to capture dumps, and Debugdiag 2 Analysis is used to generate automatic report.

This article will detail the action plan you can implement to create a rule in Debug Diagnostic 2 to automate a dump generation in function of some specified performance counters for your IIS server or your application.
This action plan is applicable when your "W3WP.exe" process or your application is consuming too much CPU, consuming too much memory (for managed code), is in a deadlock situation…

Action Plan

  • Run "Debugdiag 2 Collection"
  • Once the tool has been installed and executed on the IIS server, the wizard "Select Rule Type" loads
  • Choose "Performance", and then click on "Next >"

  • Choose "Performance Counters", then click on "Next >"

  • Click on "Add Perf Triggers…"
    • Select one or several counter(s) for which you want to generate a dump if a certain value is exceeded (here we'll take the example of a high CPU consumption)
    • Then click on "OK"

  • Select the counter you just have added and click on "Edit Thresholds…"
    • Here a dump will be generated if the % CPU Time is greater than 95% during 10 seconds
  • Once those parameters are configured, click on "OK", and then on "Next >"

Note: Those values are only informed as an indicator. You may need to change them depending on your scenario.

  • In the "Select Dump Targets" window
    • Click on "Add Dump Target"
    • In the "Target Type" field, choose "Web application pool" and select the Application Pool which is facing the hang issue
    • Click on "OK", and then on "Next >"

  • Set the "Configure UserDump Series" settings as followed:
    • Note 1: You may need to change these values depending on your scenario.
    • Note 2: Here, we'll generate a Full UserDump every 10 seconds. A maximum of 3 dumps will be generated.

  • Choose a name and a location for dumps file, then click on "Next >"
    • Setting those dumps on another disk than C:\ is possible
    • Please check you have enough available space disk as the dump size will be equal to the memory consumed by the process you are monitoring

  • In the window "Rule Completed", select "Activate the rule now", and then click on "Finish"
    • The rule is now configured and ready to generate dumps

  • Check the status is "Active"
    • If it's not, The "DbgSvc" service is surely not started
    • You can go in "Administrative Tools > Services" and start it
  • When a dump will be generated, you'll see the column "UserDump Count" being incremented

The dumps are located by default in "C:\Program Files\DebugDiag\Logs\Rule_Name".

We hope this article will help you out.
See you soon.
Sylvain Lecerf and Jin Wang from IIS support team of Microsoft France


Comments (6)

  1. Kiran says:

    Thanks for such a nice article!

    We've configured performance counter for our scenario (if requests in appn queue goes high, generate a dump). It works fine in local. But on server. Rule's status says completed. But no dump gets generated. We've enough disk space and rights also seems fine. Anything else to check?



  2. @ Kiran

    Hello Kiran,

    Debug Diag is based on the number of files you have in the rule folder to determine if the rule is completed or not.

    Have you informe a folder which is already containing *.dmp files?

    Hope this help


  3. Thank you for step-by-step instructions

  4. Ses says:


    This is a great article!

    I know this is an old post but I have the same issue as Kiran's. Debug Diag says the rule is completed but there is no single file in the folder. No .dmp file, like nothing in the dump folder. Any other issue that can cause this?

  5. @ Ses

    Sincerely I don't see why the rule could be completed while there's absolutely no file generated. Maybe you could try to use Debug Diag 2.0 to see if you reproduce the issue:…/details.aspx

  6. Ses says:

    Thanks for the reply! Unfortunately, I can't install debug diag 2.0 in the server, that's why i resorted in installing an old version. It's a 64 bit 2008, I'm using the correct msi but nothing's happening whenever i double click the installation file.

Skip to main content