Examkin

Soru

Zorluk: Çok zorTroubleshooting Windows Performance and Application Crashes

A Windows 11 workstation hosting an analytics database client experiences severe system unresponsiveness and application freezes during large dataset exports. A technician analyzes Resource Monitor and observes that the Average Disk Queue Length on the system volume continuously exceeds 14, Disk Active Time remains at 100%, and memory utilization reaches 95% with high Page Faults/sec. Windows System logs display Event ID 2004 (Resource-Exhaustion-Detector), indicating that the system low virtual memory threshold was reached because the pagefile size was manually pinned to a small static limit. Which TWO of the following actions should the technician perform to diagnose and resolve this performance issue?

  1. Modify the Virtual Memory performance settings in System Properties to enable system-managed paging file size on the primary drive.Cevap
  2. Use Task Manager or Performance Monitor to identify and terminate or reconfigure the specific application process causing excessive committed memory usage.Cevap
  3. C
    Execute the command chkdsk C: /r /f in an elevated Command Prompt to purge corrupt virtual memory pages from the disk swap space.
  4. D
    Open Disk Management and convert the primary system partition from a Basic Disk to a Dynamic Disk layout to expand physical memory capacity.

Cevap

The technician should adjust the Virtual Memory configuration to automatically manage the paging file size and use Task Manager or Performance Monitor to locate and isolate the application process driving high memory commit charge.
Event ID 2004 (Resource-Exhaustion-Detector) alongside high disk queue length and 100% active disk time signifies severe disk thrashing caused by memory pagination constraints. Allowing Windows to automatically manage the pagefile size removes the artificial memory ceiling. Concurrently, using Task Manager or Performance Monitor allows the technician to locate and address the specific process responsible for the high commit charge.

Adım Adım Çözüm

1
Analyze system telemetry and event logs.
High Average Disk Queue Length combined with high Page Faults/sec and Event ID 2004 indicates that physical RAM is exhausted and the static pagefile is preventing virtual memory expansion, causing disk thrashing.
When RAM and the pagefile fill up completely, Windows cannot fulfill memory commit requests, leading to application freezes and severe disk I/O bottlenecks.
2
Adjust Virtual Memory configuration in Windows System Properties.
Setting the paging file size to system-managed allows Windows to allocate sufficient disk space dynamically as memory commit demand increases.
This prevents virtual memory exhaustion errors and relieves disk queue bottlenecks.
3
Identify resource-heavy processes using performance analysis tools.
Checking Task Manager (Details tab) or Performance Monitor isolates the specific analytics thread or application leak responsible for consuming system memory.
Isolating the culprit process allows targeted remediation such as restarting the service, updating the application, or adjusting batch processing settings.

Anahtar Kavram

Windows Virtual Memory and Pagefile Management under Resource Exhaustion (Event ID 2004)
Bu soruyu puanla

Konular

Troubleshooting Windows Performance and Application Crashes

Bu konudan daha fazla soru