Examkin

Soru

Zorluk: OrtaTroubleshooting Windows Performance and Application Crashes

A technician is troubleshooting a Windows 11 workstation where a database query utility unexpectedly closes while generating large analytical reports. Performance Monitor reveals that disk activity on the system drive is sustained at 100%, and the Average Disk Queue Length consistently exceeds 10 during the query execution, despite available physical RAM. Further inspection shows that the virtual memory paging file size was manually fixed to a minimum and maximum of 512 MB. Which of the following actions should the technician take first to resolve the application crashes?

  1. Reconfigure the system Virtual Memory settings to allow Windows to automatically manage the paging file size.Cevap
  2. B
    Execute the sfc /scannow command from an elevated Command Prompt to repair the corrupted Windows Component Store.
  3. C
    Open the Computer Management console and disable the Windows Event Log service to reduce disk queue pressure.
  4. D
    Reinstall the database application using the /3GB compatibility switch to bypass 32-bit memory allocation limits.

Cevap

Reconfigure the system Virtual Memory settings to allow Windows to automatically manage the paging file size.
Reconfiguring Virtual Memory to automatically manage the paging file size allows Windows to dynamically scale the page file according to workload demands. A restricted 512 MB paging file causes memory allocation failures and heavy disk thrashing when running resource-intensive applications, leading to abrupt application crashes.

Adım Adım Çözüm

1
Analyze performance metrics and symptom context.
High disk queue length (>10) combined with 100% disk activity indicates severe disk thrashing caused by constant swapping when memory demands exceed available space.
A fixed virtual memory page file of 512 MB restricts the system's ability to allocate additional virtual address space when running memory-intensive queries.
2
Identify the root cause of application crashes.
When the database utility demands more virtual memory than physical RAM and the restricted page file can provide, Windows fails memory allocation requests, causing the app to crash.
Windows requires sufficient paging file capacity to commit virtual memory allocations.
3
Select and apply the appropriate configuration fix.
Setting Virtual Memory back to System Managed Size allows the operating system to dynamically expand the page file as needed.
This resolves page file starvation and prevents memory allocation failure crashes during high-load processing.

Anahtar Kavram

Virtual Memory and Paging File Configuration
Bu soruyu puanla

Konular

Troubleshooting Windows Performance and Application Crashes

Bu konudan daha fazla soru