Examkin

Question

Difficulty: MediumTroubleshooting Windows Performance and Application Crashes

A desktop application on a Windows workstation freezes unexpectedly during startup. As a CompTIA A+ technician, in what order should you execute the following troubleshooting steps to isolate the root cause and remediate the application crash?

  1. 1Open Event Viewer and check the Application log for Event ID 1002 or Event ID 1000 entries related to the crash.
  2. 2Open Resource Monitor and run the Analyze Wait Chain utility on the unresponsive application process.
  3. 3End the specific blocking process thread identified in the wait chain tree.
  4. 4Execute sfc /scannow from an elevated Command Prompt to inspect and repair damaged system dependencies.

Answer

The correct troubleshooting sequence begins with analyzing Event Viewer logs (Event ID 1002/1000), using Resource Monitor's Analyze Wait Chain feature to identify blocking threads, terminating the blocking process, and performing a system file repair using sfc /scannow.
CompTIA A+ troubleshooting protocol requires collecting diagnostic evidence prior to making system modifications. The technician first checks Event Viewer Application logs for Event ID 1000 (Application Error) or 1002 (Application Hang) to confirm the faulting module. Next, Resource Monitor's Analyze Wait Chain feature is used to pinpoint the exact thread or child process causing the freeze. The blocking process is then terminated to resolve the active deadlock. Finally, System File Checker (sfc /scannow) is executed to repair any underlying system file corruption.

Step-by-Step Solution

1
Examine Event Viewer Application logs for Event ID 1000 or 1002.
Determines the specific application executable, faulting module, and exception code.
Log investigation provides baseline empirical diagnostic information without altering system state.
2
Launch Resource Monitor and select Analyze Wait Chain for the application.
Discovers thread deadlocks and pinpoints which secondary process holds required resources.
Wait chain inspection isolates active process dependencies causing the freeze.
3
End the blocking child process or thread in Resource Monitor.
Clears the process deadlock and restores immediate system/application responsiveness.
Targeted termination clears the immediate hang without requiring a reboot.
4
Run sfc /scannow in an elevated Command Prompt.
Scans protected system files and replaces corrupted binaries with cached copies.
System repair ensures long-term stability and resolves corrupted OS dependency files.

Key Concept

Sequencing diagnostic and remediation steps for application hangs in Windows using Event Viewer, Resource Monitor Wait Chain analysis, and System File Checker.
Rate this question

Topics

Troubleshooting Windows Performance and Application Crashes

More questions from this topic