Where to find dr.watson log file on windows 2003

However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it.

Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, see How to back up and restore the registry in Windows. Because there are several versions of Microsoft Windows, the following steps may be different on your computer.

If they are, see your product documentation to complete these steps. Click Start , click Run , type regedit. Steps three and four are optional. However, they are necessary if you want to restore the default use of Dr. Registry entries for debugger programs are located in the AeDebug key in Windows. Visual Notification If this check box is selected, a dialog box appears when a crash occurs.

For Iguana, this check box can be kept unselected, as displaying this dialog box keeps Iguana from restarting if service recovery settings are being used. If you do not dismiss this dialog box by pressing OK , it automatically disappears after 5 minutes. Sound Notification Provide audio notification when a crash occurs. This check box can normally be kept unselected. Create Crash Dump File Specifies that a crash dump file is to be created when a crash occurs.

Continue: Using Problem Reports and Solutions. Leave A Comment? Click here to cancel reply. The path of the log file created when a program crashes. The location of the dump file created when a program crashes. This specifies the number of assembly instructions to be recorded for each thread when an application error occurs. This is the maximum number of errors saved to the log file.

Specifies that the symbol table is to be dumped. Provide data for all threads. The log file is called Drwtsn This location is configurable using the Dr Watson configuration tool drwtsn This file may very well be several megabytes in size, since the log may be appended to each time Dr.

Watson handles an exception. The log is written top to bottom, so the last entry in the file is the most recent crash. Each entry starts off telling what process crashed and the basic type of crash it was:. OK - so the first thing to understand is what this information is telling us. But what you can do that sometimes helps is to find the actual fault itself.

You should find an entry similar to this:. Below that will be the stack for the faulting thread, and may point to at least basically what is causing the issue. For instance, if the stack referenced a third-party. DLL, it is very possibly the cause of the crash. So, in the following example for instance, a module called CMGR caused a crash:. Following frames may be wrong. If looking at the Drwtsn So to do this, we will need to install the Debugging Tools for Windows.

Simply install the tools using the defaults and set your symbol path to the default listed on the web page. Now comes our choice in how you wish to actually do the debug. When an application crashes, it will generally be caught by Dr.

Watson and create a dump in the same location as the Drwtsn This is the dump file we can open using the Debugging Tools for Windows. To do this, run Windbg.