A technician is troubleshooting a Windows 11 workstation where a critical desktop publishing application intermittently freezes during high-resolution graphics export. The technician needs to isolate the specific thread deadlock causing the freeze, restore application responsiveness without terminating the main application process if possible, and gather historical crash logs for post-incident reporting. In what order should the technician execute these troubleshooting steps?
- 1Open Task Manager and navigate to the Details tab to locate the Process ID (PID) of the unresponsive publishing application.
- 2Right-click the application process and select Analyze Wait Chain to identify any blocking child process or thread lock.
- 3Terminate the specific blocking child thread identified in the wait chain tree to release the frozen main process.
- 4Open Event Viewer and inspect the Application log for Event ID 1002 (Application Hang) entries to document faulting module details.
Cevap
The technician should first locate the application process in Task Manager's Details tab, use Analyze Wait Chain to pinpoint the blocking thread, end the blocking thread to restore responsiveness, and finally inspect Event Viewer Application logs for Event ID 1002 entries.
The correct troubleshooting sequence begins by targeting the process in Task Manager's Details tab, running Analyze Wait Chain to identify the specific thread lock, terminating the blocking child thread to safely unfreeze the application, and lastly querying Event Viewer (Event ID 1002) for root-cause diagnostic information.
Adım Adım Çözüm
Anahtar Kavram
Isolating Windows application hangs using Task Manager Analyze Wait Chain and Event Viewer logging