Windows detected a significant memory pressure and indicates consumer processes.
Source of event
Microsoft-Windows-Resource-Exhaustion-Detector — Performance category.
Possible causes
- Memory leak
- Insufficient RAM
- Too much, applications or VM
- Unsuited File Page
Verifications to be carried out
- Read the processes cited….
- Control RAM and commit….
- Observer the evolution over time…
Commands
Get-WinEvent -FilterHashtable @{LogName='System'; Id=2004} -MaxEvents 20Key takeaways
An Event ID must always be interpreted with its source, its full message, its timing and the context of the system. The same number may exist in several providers of events.