A Windows 11 workstation used for 3D rendering experiences severe system latency and frequent application crashes during heavy rendering tasks. Diagnostics show that the Paging File % Usage routinely reaches 98%, Task Manager displays high Hard Faults/sec rates, and Event Viewer logs Event ID 2004 (Resource-Exhaustion-Detector) indicating that virtual memory is depleted. Further inspection reveals that the system drive hosting pagefile.sys has less than 500 MB of remaining free space, preventing the paging file from expanding further. Which of the following initial actions should the technician take to resolve the virtual memory bottleneck and stabilize system performance?
- Modify Virtual Memory settings in System Properties to relocate the paging file to a non-system volume with ample free storage space.Cevap
- BExecute chkdsk /f /r in an elevated command prompt to clear corrupt memory address allocations inside pagefile.sys.
- CUse Event Viewer to configure a Performance Counter Alert that automatically clears physical RAM whenever Event ID 2004 is logged.
- DAccess Indexing Options in Control Panel and rebuild the Windows Search index to reduce paging file read and write operations.
Cevap
Modify Virtual Memory settings in System Properties to relocate the paging file to a non-system volume with ample free storage space.
When a Windows system experiences high Hard Faults/sec and Event ID 2004 (Resource-Exhaustion-Detector), the operating system's virtual memory capacity is depleted. Since the drive hosting pagefile.sys has less than 500 MB of free space, the paging file cannot grow to meet system demand. Moving the paging file to a drive volume with sufficient space via System Properties restores proper virtual memory functionality and stops application crashes caused by memory allocation failures.
Adım Adım Çözüm
Anahtar Kavram
Troubleshooting Windows Virtual Memory Exhaustion and Pagefile Bottlenecks