Question

Difficulty: MediumTroubleshooting Windows Performance and Application Crashes

A user reports that a video rendering application unexpectedly closes with memory allocation errors on a Windows 11 workstation during high-load processing. Place the following troubleshooting steps in the correct logical order for a technician to isolate the root cause and resolve the performance crash.

  1. 1Open Task Manager to observe real-time physical memory and CPU utilization while reproducing the rendering task.
  2. 2Examine Event Viewer System logs to check for Resource-Exhaustion-Detector events (Event ID 2004) confirming low virtual memory.
  3. 3Navigate to System Properties > Advanced > Performance Settings to inspect the current virtual memory paging file configuration.
  4. 4Reconfigure the paging file to 'Automatically manage paging file size for all drives' and reboot the system.

Answer

The correct sequence begins by observing real-time memory usage in Task Manager, checking Event Viewer System logs for Event ID 2004 resource exhaustion entries, inspecting the paging file configuration in Advanced System Properties, and finally reconfiguring the virtual memory to be automatically managed followed by a system reboot.
The correct troubleshooting workflow follows standardCompTIA methodology: first observe live performance metrics in Task Manager during symptom reproduction, second confirm diagnostic log evidence in Event Viewer (Event ID 2004 for resource exhaustion), third inspect the relevant control tool (Paging file settings in Advanced System Properties), and fourth apply the corrective change by enabling system-managed paging file sizing and restarting.

Step-by-Step Solution

1
Monitor real-time system resource metrics in Task Manager.
Identifies immediate resource bottlenecks and confirms whether physical RAM utilization spikes to 100% during the workload.
Live diagnostic observation is the first step in verifying user-reported symptoms before modifying configuration settings.
2
Analyze historical system event logs in Event Viewer.
Locates Event ID 2004 logs generated by the Resource-Exhaustion-Detector, confirming virtual memory exhaustion.
Corroborating live observations with system logs verifies that Windows was unable to allocate virtual memory.
3
Inspect virtual memory settings in Advanced System Properties.
Reveals whether the paging file is set too low, disabled, or locked to a static custom size.
Checking configuration settings allows the technician to pinpoint misconfigured paging parameters causing the crash.
4
Apply virtual memory remediation and restart the computer.
Enables Windows to dynamically expand the page file on disk as memory demand increases during rendering operations.
Reconfiguring to system-managed paging file size directly resolves virtual memory allocation limits.

Key Concept

Troubleshooting Virtual Memory Exhaustion and Application Performance Crashes
Rate this question