A technician is troubleshooting a Windows workstation where a desktop productivity application freezes immediately upon launch. What is the correct sequence of steps the technician should take to isolate and resolve the issue?
- 1Terminate the unresponsive application process using Task Manager.
- 2Inspect the Application log in Event Viewer to identify the faulting module name and error code.
- 3Perform a Clean Boot using System Configuration (msconfig) to isolate potential background software conflicts.
- 4Repair or reinstall the application software to restore corrupted program files.
Answer
The technician should first terminate the unresponsive process in Task Manager, review the Application log in Event Viewer for faulting module details, execute a Clean Boot to isolate background software conflicts, and finally repair or reinstall the application.
The proper troubleshooting methodology dictates stabilizing the system first by ending the unresponsive process in Task Manager, analyzing historical log data in Event Viewer to pinpoint the faulting module, using a Clean Boot to rule out third-party application interference, and finally repairing or reinstalling the application if corrupted files are confirmed.
Step-by-Step Solution
Key Concept
Standard Windows Application Crash Isolation Workflow