Microsoft Debug Diagnostic Tool: detect Windows errors

samsul55 By samsul55, 6th Feb 2015 | Follow this author | RSS Feed
Posted in Wikinut>News>Technology

With the Microsoft Debug Diagnostic, Tool detects errors on Windows PCs and Windows servers. We introduce this brilliant free tool for professionals.

Microsoft Debug Diagnostic Tool: detect Windows errors

Administrators and advanced users who need to check for errors on Windows computers and servers often should the free Microsoft Debug Diagnostic tool (for Windows Vista, Windows 7/8 / 8.1, Windows Server 2008/2008 R2 / 2012/2012 R2, English speaking, all 32 and 64 bits).

This is a tool collection that professionals among others, supported the causes of system crashes to find out memory leaks to track to resolve fragmentation problems and repeal power brakes. We show practical examples of how to use the smart professional tool.

Configure Debug Diagnostics

Often problems are associated with the memory management of the reason, if it falls short with the performance and stability of a server or a Windows computer. Such OutofMemory problems can be solved very efficiently using the Debug Diagnostic Tool. You must first install the tool on the appropriate server, set up and then start the measurement. To do so, according to the installation as follows:

1. Start the Debug Analysis Tool.
2. Click on "Settings" (gear icon) and then "Preferences."
3. Enable the option "Save reports in relative sub folders When possible."
4. When done, click the plus sign in the "Symbol search paths to use for Analysis."
5. Add the following path: srv * c: \ symcache * http: // The exact background why you should integrate the symbols, Microsoft said in a separate Knowledge Base article.
6. Add another path to then: C: \ Program Files (x86) \ Java \ juries \ bin. This helps, for example, especially if you look for problems on Web servers and Java applications. Examine Java is a problem. You can omit this path.
7. Then go back to settings and close the tool. Your changes are saved.

Preparing the collection of data

Next step is to start the DebugDiag Collection Tool for collecting data. Again, you need to make settings so that you can perform an analysis:

1. First connect the wizard to create a measurement by clicking after the start of DebugDiag Collection "Add Rule" and then in the window that opens, click the Cancel button, because you can create your own measuring rule (opens in circumstances the wizard automatically). However, they have to carry out the possibility wizard measurements here.
2. Click on Tools \ Options and Settings.
3. Go to Folder and Search Paths \ Symbol Search Path for debugging. Make sure that the path srv * c: \ symcache * http: // is entered.
Select Manual in user dump saves folder, select a path for saving the dumps.
4. Scroll then clicks the Preferences tab and set the following options:
Include source and line information in debug logs
Use fixed initial folder for data files.
Record call stacks immediately when monitoring for leaks
5. Click "OK" and closing your window.

Detect and measure memory issues

You can then make the measurement of memory problems. Continue to use the tools DebugDiag Collectio n Proceed as follows to measure before:
1. Go to the "Processes" tab.
2. Select the process in which you suspect that he has problems with the RAM, so memory leaks or other.
3. Click the right mouse button on the process and choose Monitor For Leaks. Confirm all screens. We are shown in the column Backtracks the tracking option. The process is also now supported by Debug Diagnostic.
4. Let the process work now quite normally and perform the measurement by at least 15 minutes. Perform all actions that normally lead to a crash or problems during the process.
5. Select every few minutes from the context menu of the process, the Create Full Userdump option. Especially in case of problems or if the process uses a lot of memory or causing problems, you should create a dump. How to obtain more information.
6. After some time, you can end the tracking of the process via the context menu.

Benefit analysis of the dump files

After you create measurement data on the process, you can analyze the problems with the Debug Diagnostic Tool, using the dump files that has the tool creates.
1. Simply launch Debug Analysis.
2. Click adds Data Files.
3. Select the dump files that you have created. By default, the directory C: \ Program Files \ DebugDiag \ Logs \ mice used.
4. Select the top option for Memory Analysis Memory Pressure Analyzer.
5. Click the Start Analysis.
6. In the event a hit file to the directory \ Documents \ DebugDiag \ Reportsreportsd.7. Open the files Tobe obtained by the analysis for references to the problem.8. Even announcement problems themselves, but require many companies such as Microsoft and IT service providers, provide or offer professional support this file for their work.

Find an error on an error's servers (IIS) another

You can also find errors and problem's observers running Microsoft IIS Web server with the Debug Diagnostic Tool. To doth proceed similarly as previously described. When measuring in this area goes brucelloses:
1. Create a new collection in Debug Diagnostic monitor control. 2. You use the wizard already described that automatically appears when you start the tool. Electroshock there.
3. Is it an application pool or directly to process of IIS, you can select Internet aphthaetropicae application pool.4? Pow pool? The Web server other promoter process problems, search targeted for particular process crashes. En Monmouth be then only selected.5. Click in monitoring a process on the Advanced Configuration page (Optional) in Advanced Settings on breakpoint sand then clickAddBreakpoint.6.breakpoint.tdll!ZwTerminateProcess from the list and select in Action Type, select Full User DumpSet Action to Limit 5 and confirm with OK.7. Click saves & Close.
Save slick "Next"and give the rule Pan-American all names. Electropath which the dump files and logs files, will be stored.9. Select on the last page, select Activatethe rule now and click Finish. 10. The rule is d10. There'd in the window anon be given tetracosactide. In the active. Count column soon, number of dumps created.11.Warten what ha11. War ten then analyzes the dump analyze scribed.

All photos and images from Pixabay


Microsoft, Microsoft Debug Diagnostic, Windows 78, Windows Errors, Windows Vista

Meet the author

author avatar samsul55
I have a graduate degree in Philosophy. I love to write and to develop friendships all over the world, I hope to add you to my list of good friends.

Share this page

moderator Peter B. Giblett moderated this page.
If you have any complaints about this content, please let us know


author avatar Carol Roach
6th Feb 2015 (#)

very good article

Reply to this comment

author avatar Retired
8th Feb 2015 (#)

Excellent post!

Reply to this comment

Add a comment
Can't login?