Soru

Zorluk: OrtaTroubleshooting Windows Performance and Application Crashes

A technician is troubleshooting a Windows 11 workstation where a custom background processing service slowly degrades overall system performance over several hours of execution until the system becomes unresponsive. During performance monitoring, physical RAM utilization reaches 98%, and disk activity spikes significantly. The technician suspects that a memory leak in the service is consuming available RAM and forcing the operating system into heavy virtual memory paging. Which TWO of the following metrics or administrative tool views would best help the technician confirm this diagnosis? (Select TWO.)

  1. Monitoring the Commit Charge and Private Working Set of the service process over time to verify continuous memory accumulationCevap
  2. Checking the Hard Faults/sec metric in Resource Monitor under the Memory tab to confirm RAM saturation is causing heavy page file accessCevap
  3. C
    Using Event Viewer to inspect the Security log for Event ID 4624 logon events related to the background service account
  4. D
    Executing the command `chkdsk /f` from an elevated command prompt to repair corrupted page file sectors on the hard drive

Cevap

Monitoring the process's Commit Charge and Private Working Set over time, along with checking the Hard Faults/sec metric in Resource Monitor, confirms a memory leak and excessive virtual memory paging.
Monitoring process memory counters (Commit Charge and Private Working Set) shows continuous unreleased memory allocation typical of a memory leak. Inspecting Hard Faults/sec in Resource Monitor verifies that RAM exhaustion is causing heavy read/write activity to the page file on disk, leading to system slowness.

Adım Adım Çözüm

1
Analyze memory allocation metrics for the suspected process over time.
Confirm whether the process continuously increases its Private Working Set and Commit Charge without releasing memory.
A memory leak is characterized by unreleased RAM allocations that grow over the runtime of an application.
2
Examine system-wide memory thrashing indicators in Resource Monitor.
Observe high Hard Faults/sec under the Memory tab as physical RAM is exhausted.
When RAM fills completely, the OS actively swaps memory pages to disk (pagefile.sys), resulting in elevated hard fault counts and severe I/O degradation.

Anahtar Kavram

Identifying memory leaks and virtual memory paging using process memory counters and Hard Fault metrics.
Bu soruyu puanla