When a service crashes intermittently in Windows XP, little information is generated about the cause. Therefore, it may be difficult to determine what is causing the problem. This step-by-step article describes how to use "Debugging Tools for Windows" to troubleshoot intermittent service crashes.
Note To follow these steps, you must install "Debugging Tools for Windows." To obtain "Debugging Tools for Windows," visit the following Web site:
- At a command prompt, type the following commands. Press ENTER after each command.cd %systemroot%\system32
copy svchost.exe svchostdbg.exe
- In Registry Editor, click the subkey that corresponds to the name of the service that crashes. This subkey is located in the following subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
- In the details pane, right-click ImagePath, and then click Modify.
- In the path that is in the Value data box, change svchost.exe to svchostdbg.exe, and then click OK.
- Exit Registry Editor.
Note Alternatively, you can run the following command from the command prompt:sc.exe config ServiceName type= ownYou need the space between the "=" and "own". This command will cause the service to always launch in its own svchost. To revert the service back to its original state, run the following command from the command prompt:sc.exe config ServiceName type= share
- At a command prompt, type the following command, and then press ENTER: net start ServiceNameReplace ServiceName with the name of the service that crashes.
- Right-click the task bar, and then click Task Manager.
- In Windows Task Manager, click the Processes tab.
- On the View menu, click Select Columns.
- Click to select the PID (Process Identifier) check box, and then click OK.
- Locate the service in the Image Name column. Then, note the service's process identifier (PID) in the PID column.
- At a command prompt, type the following commands. Press ENTER after each command.cd \Program Files\Debugging Tools for WindowsReplace PID with the PID of the service that crashes.
adplus -p PID -crash
- Wait for the service to crash.
- After the service crashes, analyze the dump file to obtain information that can help find the cause of the issue. This information includes the last error that occurred. The dump file is located in the following folder:C:\Program Files\Debugging Tools for Windows\
Article ID: 934650 - Last Review: Oct 22, 2008 - Revision: 1