A technician is investigating a Windows 11 workstation where an enterprise application gradually consumes available system memory, causing severe system slowdowns after several hours of operation. In what order should the technician perform the following troubleshooting steps to identify and isolate the root cause?
- 1Launch Task Manager and Resource Monitor to inspect process memory metrics, observing Commit Charge and Working Set usage.
- 2Examine Event Viewer logs under Windows Logs > Application to inspect Event ID 1000 and Event ID 2004 fault records for process details.
- 3Launch System Configuration (msconfig), select 'Hide all Microsoft services', and disable all remaining third-party services.
- 4Restart the workstation and selectively re-enable background services to isolate the specific application service responsible for the memory leak.
Cevap
The correct troubleshooting sequence begins with monitoring active process memory metrics in Task Manager and Resource Monitor, followed by reviewing Event Viewer application logs for crash and resource exhaustion events (Event ID 1000 and 2004). Next, configure a clean boot state using System Configuration (msconfig) by hiding Microsoft services and disabling non-Microsoft services. Finally, reboot the system and incrementally re-enable services to isolate the specific application service causing the memory leak.
The standard CompTIA troubleshooting workflow for application memory leaks and crashes requires first gathering live diagnostic metrics (Task Manager/Resource Monitor), reviewing recorded log events (Event Viewer Event IDs 1000/2004), establishing a clean startup baseline (msconfig with Microsoft services hidden), and systematically testing services after a reboot to isolate the offending third-party service.
Adım Adım Çözüm
Anahtar Kavram
Methodological isolation of Windows application crashes and memory leaks