|
|
You can configure RTX to extend the Windows minidump file to include information about RTX. An RTX extended Windows minidump file contains both Windows STOP Message information plus key information about the current state of the RTSS subsystem (specifically the currently running process and thread). You can then load the RTX extended Windows minidump file in WinDbg and view RTSS subsystem data.
You can configure Windows to use kernel memory dumps, complete memory dumps or small memory dumps. Kernel and complete memory dumps include RTX information, regardless of whether or not RTX extended minidump functionality has been enabled. Small memory dumps only include RTX information when RTX extended minidumps are enabled.
To determine the type and location of your Windows dump file:
The Write Debugging Information section tells you what type of dump Windows will use to capture debugging information and where the dump will be stored.
To enable RTX extended minidumps, follow the instructions in Creating an RTX Minidump in Using RTX Runtime.
Before opening the RTX extended minidump file, you must load the RTX Debugger Data Extension to get RTX symbols.
To open the dump file in WinDbg:
NOTE: You may want to obtain Microsoft Windows symbols. For more information, see http://support.microsoft.com/kb/311503.
To mine a minidump file for RTX-specific content, start with the !rtxanalyze command. This command provides information about the state of the RTX subsystem at the time Windows generated the dump file. Specifically, you can get information about the processes and threads that were active at the time of the dump. From here, you can use the process and thread IDs returned by !rtxanalyze along with the !rtxcurrentprocess and !rtxcurrentthread commands to obtain more information.
The following links provide more information about minidumps and WinDbg.
For information on crash dumps:
For information on Microsoft's Debugging Tools for Windows, including WinDbg: