12.14.1  Crash Data Parameters

The crash data parameters that you need to enter vary depending on your operating system.

Windows

Table 12–1 Windows Crash Data Parameters 
Parameter
Explanation
OS Version
The version number of the failed Windows operating system
Minor Version
The NT build number (for NT 4.0, 1381; for Windows 2000, 2195)
Service Pack
The number of the Service Pack installed on the failed machine
Machine Image Type
"intel"
BugCheckCode
The number of the stop that occurred, which can be used to determine what trap occurred
BugCheckParam #1
BugCheckParam #2
BugCheckParam #3
BugCheckParam #4
The four parameters normally included with the BugCheckCode that give clues to the nature of the BugCheckCode
Failing Module
The name of the driver that failed
Failing Module Offset
The offset of the failed driver
Failing Module Timestamp
The date and time the failed driver was built
Crash Process Name
The name of the process that was running when the system crashed
Failing Routine
The name of the failing routine
Failing Routine Offset
The failing address location within the failing routine, offset from the start of the routine
Pool Information
The address within a Page or NonPage pool, depending on the stopcode
Canonical Stopcode Parameter 1
Canonical Stopcode Parameter 2
Canonical Stopcode Parameter 3
Canonical Stopcode Parameter 4
Address or status register variables (see the Kanalyze documentation for more information)
Keyword 1
Keyword 2
Keyword 3
Keyword 4
Items on the stack that point to the cause of the failure (see the Kanalyze documentation for more information)
Driver List
The Driver Name, Driver Load Address, Driver Size and Driver Date. These values are derived from the failing address information contained in the Bugcheck Parameter fields. Which Bugcheck Parameter field you use depends on the Bugcheck Code. The Driver List corresponds to the driver base address when compared to the address of the Stopcode.
Stack Trace
A list of the functions the system was executing when it crashed, with the ending line of code for each
Call Site List
Addresses taken from the Stack Trace used to identify failing areas

OpenVMS Alpha

Table 12–2 Open VMS Alpha Crash Data Parameters 
Parameter
Explanation
OS Version
The version number of the failed operating system
Crash Time
The date and time the system crash occurred
Bugcheck
The type of diagnostic check logged by the operating system
Host Name
The node on which the crash occurred
CPU Type
The model number of the failed CPU
Process Name
The name of the process active at the time of the crash
Image Name
The name of the image being executed at the time of the crash
Signal Array
The Signal Array count. The Signal Array contains the exception code, zero or more exception parameters, the PC, and the PSL.
Condition Code
The symbolic value assigned to the specific condition
Reason Mask
The longword mask
Virtual Address
The virtual address the failing instruction tried to reference
Exception PC
The instruction whose attempted execution resulted in the unexpected executive or kernel mode exception
Exception PSL
Processor Status Longword (PSL) at the time of the exception
Module Name
The name of the failed module
Module Offset
The offset of the failed module
Instruction
The failing instruction corresponding to the exception PC
Map Module
The name of the map module in use when the crash occurred
Map Offset
The beginning memory location where the map module driver resides
Caller Module
The first module identified on the stack below the failing PC
Caller Module Offset
The first module offset identified on the stack below the failing PC
Instruction M1
The instruction executed immediately before the Failing Instruction (helps to locate the Failing Instruction precisely in the code)
Instruction M2
The next-to-last instruction executed before the Failing Instruction (helps to locate the Failing Instruction precisely in the code)
Instruction P1
The first instruction that would have been executed after the Failing Instruction (helps to locate the Failing Instruction precisely in the code)
Instruction P2
The second instruction that would have been executed after the Failing Instruction (helps to locate the Failing Instruction precisely in the code)