Examkin

Question

Difficulty: HardWindows Administrative and System Management Tools

A user's custom database client application on a Windows 11 workstation has become completely unresponsive. A systems administrator needs to determine if the application is experiencing a thread deadlock, terminate the blocking process, and inspect the system logs for the application hang event. In what chronological order should the administrator perform the steps below?

  1. 1Launch Resource Monitor (resmon.exe) and navigate to the CPU tab.
  2. 2Right-click the unresponsive database client process and select Analyze Wait Chain.
  3. 3Select the identified blocking process thread in the Wait Chain tree and click End Process.
  4. 4Open Event Viewer (eventvwr.msc) and inspect the Application log for Application Hang entries.

Answer

The correct sequence begins by launching Resource Monitor and selecting the CPU tab, right-clicking the hung process to Analyze Wait Chain, terminating the identified blocking process thread, and finally checking the Application log in Event Viewer for event details.
The correct workflow starts by opening Resource Monitor (resmon.exe) to evaluate live CPU processes. Using 'Analyze Wait Chain' on the frozen process allows the administrator to pinpoint the exact blocking PID causing the deadlock. Ending that specific blocking process clears the lock. Finally, opening Event Viewer (eventvwr.msc) to examine the Application log allows the administrator to review the Application Hang event for underlying faulting modules.

Step-by-Step Solution

1
Open Resource Monitor and navigate to CPU process listings.
Active processes and thread data are displayed.
Resource Monitor provides advanced process interaction, including thread wait chain diagnostics that standard Task Manager views do not offer.
2
Execute the Analyze Wait Chain feature on the target process.
A window opens illustrating which child or external thread is delaying execution.
This identifies whether the application is waiting on another process PID or an external resource.
3
Terminate the blocking PID listed in the Wait Chain view.
The resource lock is released, restoring application responsiveness.
Ending only the blocking thread clears the deadlock without needing a full system reboot.
4
Open Event Viewer and check the Application log.
Event ID details regarding the Application Hang are retrieved.
Event Viewer records official system events and error codes essential for root-cause analysis and documentation.

Key Concept

Windows Resource Monitor Analyze Wait Chain and Event Viewer Application Log Diagnostics
Estimated Time:1m 30s
Rate this question

Topics

Windows Administrative and System Management Tools

More questions from this topic