Examkin

Question

Difficulty: HardTroubleshooting Windows Performance and Application Crashes

A financial analyst reports that a local database reporting application frequently freezes and crashes during heavy monthly report generation on a Windows workstation. Resource Monitor indicates that during report generation, the secondary storage drive (E:) exhibits a Disk Queue Length consistently exceeding 6 with an Average Response Time above 650 ms. Place the technician's troubleshooting and resolution steps in the correct chronological order from first to last.

  1. 1Open Task Manager and Resource Monitor to inspect real-time disk process activity, active time, and response time metrics during the crash condition.
  2. 2Review the Windows Application log in Event Viewer for Event ID 1002 (AppHang) to confirm the faulting application binary and failure details.
  3. 3Run a disk integrity scan using chkdsk E: /f from an elevated command prompt to identify and correct any underlying volume corruption.
  4. 4Reconfigure the application's temporary scratch directory path to point to a high-performance primary NVMe solid-state drive.
  5. 5Re-run the report generation process while verifying Task Manager metrics to confirm disk queue lengths remain low and the application completes cleanly.

Answer

The proper troubleshooting sequence begins with observing live performance metrics in Task Manager and Resource Monitor, inspecting Event Viewer for Event ID 1002 hang logs, executing chkdsk to rule out disk file system corruption, relocating the temporary scratch directory to an NVMe SSD, and finally executing a test report to verify system stability.
Following CompTIA troubleshooting methodology, the technician must first identify the problem by observing live symptoms (inspecting Task Manager and Resource Monitor for disk queue metrics), verify historical failure details in Event Viewer (Event ID 1002 AppHang), test volume health (chkdsk), implement the solution (reconfiguring scratch path to an NVMe drive), and verify full system functionality by testing report generation.

Step-by-Step Solution

1
Identify live performance bottlenecks using Task Manager and Resource Monitor.
Discovers high disk active time, process I/O rates, and elevated disk queue lengths.
Initial troubleshooting requires gathering real-time diagnostic data directly from the running system.
2
Check the Event Viewer Application log for Event ID 1002.
Confirms the exact faulting application executable name and hang timestamp.
Correlating live metrics with system event logs confirms the precise nature of the application hang.
3
Execute chkdsk E: /f from an elevated command prompt.
Verifies file system integrity and repairs logical volume errors.
Ruling out disk corruption ensures the high response time is caused by performance limitations rather than file system damage.
4
Reconfigure application scratch paths to move temporary data onto NVMe storage.
Eliminates the mechanical disk I/O bottleneck by using high-throughput storage.
Remediating the root cause requires rehoming intensive I/O operations to adequate hardware.
5
Run a test workload and monitor performance counters.
Validates that disk queue length remains low and report generation succeeds without hangs.
CompTIA A+ methodology requires verifying full system functionality after implementing a fix.

Key Concept

CompTIA A+ Troubleshooting Methodology for Application Hangs and Disk Bottlenecks
Estimated Time:2m 0s
Rate this question

Topics

Troubleshooting Windows Performance and Application Crashes

More questions from this topic