Skip to main content

Software  >  

MustGather: Data Collection for an application hang and system hangs on Windows

 Technote (FAQ)
 
Question
How do I collect the necessary output for support to analyze application and system hangs that occur on Microsoft Windows related to IBM Rational processes?
 
Answer

STEP 1: Identify the problem
  1. WHICH process is hanging? (Example: clearexplorer.exe, db_server.exe ....)
  2. WHAT operation was being performed when the hang occurred? (Example: shutting down GUI, performing X operation ....)
  3. HOW often do the errors occur? (Example: every night at X time, every day around X time ....)
  4. HOW many machines does this happen on? (Example: ALL, one or X number)

STEP 2: Collect relevant logs

Collect the logs from a good machine and a bad machine and compare the two for differences.

For example review technote 1131335 for more information on collecting ClearCase logs from Windows.

STEP 3: Collecting the User or Memory Dump for the hang

The following tools can be used to help collect data about application or system hangs. The instructions for each of the tools are provided below:

3a) Collecting application hangs (Send the dump file to IBM Rational Client Support for analysis)

  • Using GenMiniDump.exe (Note: GenMiniDump.zip is attached below):
    1. Place genminidump.exe and dbghelp.dll in a folder
    2. cd into that folder
    3. Run the following from cmd: genminidump.exe <PID> or genminidump.exe <Process name> Example: C:\Temp\GenMiniDump\genminidump msdev.exe
 DISCLAIMER:

All source code and/or binaries attached to this document are referred to here as "the Program". IBM is not providing program services of any kind for the Program. IBM is providing the Program on an "AS IS" basis without warranty of any kind. IBM WILL NOT BE LIABLE FOR ANY ACTUAL, DIRECT, SPECIAL, INCIDENTAL, OR INDIRECT DAMAGES OR FOR ANY ECONOMIC CONSEQUENTIAL DAMAGES (INCLUDING LOST PROFITS OR SAVINGS), EVEN IF IBM, OR ITS RESELLER, HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.


3b) Collecting System Hangs
Note: this type of crash may also be requested for an application hang by engineering.

CONFIGURE WINDOWS FOR A MEMORY DUMP:

Review MS KB article 254649 for an overview of memory dump file options for Windows Server 2003, Windows XP, and Windows 2000.

Instructions:

  1. Click Start > Settings > Control Panel and double-click System
  2. On the Advanced tab, click Settings in the Startup and Recovery section.
  3. Ensure the Write Debugging Information drop down box has Kernel memory dump selected and note the Dump File: location window as this is where the dump file(s) will be saved.
    Note:
    Only collect a complete memory dump when request by IBM Rational Client Support.
  4. Ensure Overwrite any existing file is checked.
  5. Ensure the Automatically restart box is checked.


Example Kernel memory dump screenshot (from XP):




Example Complete memory dump screenshot (from XP):


CONFIGURE STOP EVENT:

To configure the Stop Event, you will need to make a registry change on the host.

To add an entry to the registry:

  1. Click Start > Run > type: regedit

  2. Navigate to the subkey

    HKLM\System\CurrentControlSet\Services\i8024prt\Parameters

  3. Select the Parameters subkey, and then click Add Value from the Edit menu.

  4. In the Add Value dialog box, in the Value Name box type CrashOnCtrlScroll, in the Data Type box select REG_DWORD, and then click OK.

  5. Double-click the CrashOnCtrlScroll entry. In the DWORD Editor dialog box, type 1 in the Data box and then click OK.

  6. Close Regedit, and restart your computer. After the computer has restarted, you can generate a stop event.

Refer to Microsoft KB article 244139 Windows feature lets you generate a memory dump file by using the keyboard for further details.

GENERATE STOP EVENT:

Press and hold the right Ctrl key (the left Ctrl key will not allow you to generate a stop event), and then press the Scroll Lock (ScrLk) key twice.

A stop event will occur, and a stop error will be displayed with the following message:

*** STOP: 0x000000E2 (0x00000000, 0x00000000, 0x00000000, 0x00000000)

The end-user manually generated the crashdump.


After generating a stop event, the computer will be inoperable until it has been restarted. After the restart, complete functionality will be restored.


Send the dump file to IBM Rational Client Support for analysis.


Do you need more help?

For additional assistance, contact IBM Rational Client Support:
Submit a Service Request (SR)

 
Related information
Data collection for mem ref and blue screens on Windows
 
GenMiniDump.zip
 
 

Copyright and trademark information
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
Rate this page
Please take a moment to complete this form to help us better serve you.
This material provides me with the information I need.




This material is clear and easy to understand.




Did the information help you to achieve your goal?
What updates, improvements, or related information would you like to see in this document?
Your response will be used to improve our document content. Requests for assistance, if applicable, should be submitted through your normal support channel as we cannot respond from this site.
Input the verification number to submit feedback:
Document information
 Product categories:
 Software
 Software Development
 Other Software Development
 Rational Customer Support
 Diagnostic Utilities
 Operating system(s):
  Windows
 Software version:
  All Versions
 Reference #:
  1366397
 IBM Group:
 Software Group
 Modified date:
 2009-05-11

Translate My Page
 
 

Rate this page

Help us improve this page. Your response will be used to improve our document content. Requests for assistance, if applicable, should be submitted through your normal support channel as we cannot respond from this site.