ID: Q189867
The information in this article applies to:
- Windows NT
Crash dumps from some Compaq computers might cause the Microsoft Windows Debugger, WinDbg.Exe 5.0.1719.1, to crash.
Some Compaq systems install a tool called CPQDbg.exe. This tool generates user-mode application crash dumps. In some cases, the User.dmp generated by CPQDbg.exe is corrupt. When you use WinDbg.exe versions 5.0.1719.1 or earlier to analyze this dump file, it might crash.
CPQDbg.exe is a middleware tool that is installed in Compaq's Insight Manager (CIM) software on some Compaq systems. CPQDbg.exe is located in %SystemRoot%\System32\Cpqdbg.exe on some Compaq servers. When CIM is being installed, it reads the value found under AEDebug\Debuggers. Then it writes this value to a key under HKLM\System\CurrentControlSet\Services\CPQMgmt called "Apptrap". CIM then replaces the existing AEDebug\Debugger string with the CPQDbg string. When an application crashes, this CIM software tries to generate an SNMP trap to forward to the CIM Management Console. It then passes the fault to the debugger listed under the Apptrap value. For Windows NT, the default debugger is normally Dr. Watson, DRWtsn32.exe. In some cases, CPQDbg interactions create a corrupt dump file.
If you have installed CPQDbg.exe and dump files are not being generated properly, uninstall CPQDbg.exe. Restore DRWtsn32.exe as the default Windows NT debugger as follows:
1. At a command prompt, navigate to the directory containing DRWtsn32.exe.
2. Type the following text:
drwtsn32.exe -i
Microsoft is researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
You can download the latest build of Windbg from the following Web site:
http://www.microsoft.com/msdn/sdk/windbg.htm
Keywords : kb3rdparty kbnokeyword kbSDKPlatform
Issue type : kbprbLast Reviewed: January 6, 1999