A technician is troubleshooting a Windows 11 workstation where a specialized financial reporting application regularly hangs during data processing and subsequently crashes. Place the following troubleshooting steps in the correct sequence to systematically isolate the hanging process, identify the failing module, eliminate software conflicts, and repair corrupted system dependencies.
- 1Analyze the process wait chain in Task Manager to determine if the unresponsive application is waiting on another process or thread.
- 2Inspect the Event Viewer Application log for Event ID 1000 entries to determine the exact faulting module and exception code.
- 3Perform a clean boot via System Configuration (msconfig) to isolate non-Microsoft services and startup programs.
- 4Run the System File Checker utility (sfc /scannow) from an elevated Command Prompt to repair corrupted system file dependencies.
Cevap
The correct troubleshooting sequence is: 1) Analyze the process wait chain in Task Manager, 2) Inspect the Event Viewer Application log for Event ID 1000 entries, 3) Perform a clean boot via System Configuration (msconfig), and 4) Run the System File Checker utility (sfc /scannow).
The correct sequence adheres to CompTIA troubleshooting best practices: start with real-time process diagnostics (Task Manager wait chain analysis), follow with historical log examination (Event Viewer Application log Event ID 1000), proceed to third-party conflict isolation (clean boot via msconfig), and conclude with system dependency repair (sfc /scannow).
Adım Adım Çözüm
Anahtar Kavram
Systematic isolation and remediation sequence for Windows application hangs and crashes using native diagnostic tools.