A technician is troubleshooting an enterprise accounting application that periodically freezes and crashes on a Windows 11 workstation. Arrange the troubleshooting steps in the correct order to systematically identify and isolate the root cause of the application crash.
- 1Inspect the Windows Event Viewer Application log for Event ID 1000 to identify the faulting application name, faulting module, and exception code.
- 2Open Resource Monitor and select Analyze Wait Chain on the application process to see if it is waiting for another process or thread to respond.
- 3Use System Configuration (msconfig) to disable all non-Microsoft services and startup programs, creating a clean boot state.
- 4Restart the workstation and launch the application to test whether the crash still occurs without third-party background applications.
Answer
The correct sequence is: First, inspect the Event Viewer Application log for Event ID 1000 to gather crash details; second, open Resource Monitor and analyze the wait chain for process locks; third, perform a clean boot via System Configuration; fourth, restart and test the application in the isolated clean boot state.
Troubleshooting Windows application crashes requires a methodical progression from non-intrusive log inspection to active environmental isolation. First, inspecting Event Viewer for Event ID 1000 provides details about the faulting module. Second, using Resource Monitor's Analyze Wait Chain checks for active process blocks or deadlocks. Third, using System Configuration (msconfig) to disable non-Microsoft services establishes a controlled clean boot baseline. Finally, restarting and running the application in this clean boot environment confirms whether background software conflicts were the cause.
Step-by-Step Solution
Key Concept
Windows Application Troubleshooting and Diagnostic Isolation Workflow