Skip to content

How to Diagnose Memory Pressure and Paging on Windows Server Print

  • 0

Applies to: Windows Server 2019, 2022 and 2025.

Memory becomes a performance fault when paging, allocation failures or application trimming affect the workload.

Monitoring should collect enough evidence to diagnose trends without overwhelming storage or exposing sensitive logs. Visit managed Windows VPS hosting.

Prerequisites

  • Know installed RAM and baseline.
  • Capture during slowdown.
  • Separate committed memory from working set.
  • Review database cache design.

Procedure

Step 1: Read OS totals

Capture visible and virtual memory.

Get-CimInstance Win32_OperatingSystem | Select TotalVisibleMemorySize,FreePhysicalMemory,TotalVirtualMemorySize,FreeVirtualMemory

Step 2: Sample counters

Measure available memory and paging.

Get-Counter '\Memory\Available MBytes','\Memory\% Committed Bytes In Use','\Memory\Pages/sec' -SampleInterval 2 -MaxSamples 15

Step 3: List processes

Sort working set and private bytes.

Get-Process | Sort WorkingSet64 -Descending | Select -First 15 Name,Id,WorkingSet64,PrivateMemorySize64

Step 4: Check page file

Review usage.

Get-CimInstance Win32_PageFileUsage

Step 5: Correlate workload

Check login, query, backup and antivirus peaks.

Verification

Use sustained trends rather than one sample.

Get-Counter '\Memory\Available MBytes','\Paging File(_Total)\% Usage' -SampleInterval 5 -MaxSamples 12

Rollback

Diagnostics are read-only. Do not disable page file or impose limits without vendor guidance.

Operational notes

Low free memory alone does not prove a problem because Windows uses RAM for cache.

Official references

For a hosted environment with setup and onboarding, explore our managed Windows VPS plans.


Was this answer helpful?

« Back