Soru

Zorluk: OrtaTroubleshooting Windows Performance and Application Crashes

A technician is troubleshooting a Windows 11 workstation where a custom line-of-business inventory application frequently freezes during database synchronization. Place the following diagnostic and remediation steps in the correct sequential order to analyze the active frozen state, inspect crash logs, review system stability history, and repair operating system files.

  1. 1Open Task Manager, locate the unresponsive inventory application process, right-click it, and select Analyze Wait Chain to check for blocked threads or process dependencies.
  2. 2Open Event Viewer and navigate to Windows Logs > Application to examine Event ID 1002 (Application Hang) details and identify the faulting module name.
  3. 3Launch Reliability Monitor to check the system stability index and correlate application crash dates with recently installed Windows updates or hardware drivers.
  4. 4Open Command Prompt with elevated administrator privileges and run sfc /scannow to locate and repair corrupted system files.

Cevap

The correct troubleshooting order begins with analyzing the active process wait chain in Task Manager, followed by inspecting Event Viewer application hang logs, checking Reliability Monitor for system change history, and finally running System File Checker to repair corrupted operating system files.
The correct troubleshooting sequence follows the standard CompTIA methodology: gather live diagnostic data first (Task Manager Analyze Wait Chain), review application event log specifics (Event Viewer Event ID 1002), review timeline correlation with recent updates (Reliability Monitor), and perform file integrity repair (sfc /scannow).

Adım Adım Çözüm

1
Analyze the active process state using Task Manager's Analyze Wait Chain feature.
Identifies if the application process is blocked by another process or thread.
Immediate live diagnostic tools take priority when an application is currently frozen.
2
Examine Event Viewer Application logs for Event ID 1002.
Provides exact faulting module names and failure signatures.
Detailed application log analysis clarifies specific technical error codes.
3
Review Reliability Monitor trends.
Correlates the onset of crashes with software or driver installations.
Evaluating environmental changes helps isolate external factors causing the performance degradation.
4
Execute sfc /scannow in an elevated Command Prompt.
Scans and repairs damaged operating system files and libraries.
System repair commands should be run after diagnosing and establishing the likely root cause.

Anahtar Kavram

Methodological Troubleshooting of Windows Performance and Application Hangs
Bu soruyu puanla