Microsoft-Windows-Resource-Exhaustion-Detector

8 events across 2 channels

Event	Title	Channel	Sample
1001	The Windows Resource Exhaustion Detector started.	Operational	Y
1002	The Windows Resource Exhaustion Detector stopped.	Operational	Y
1003	The Windows Resource Exhaustion Detector received a notification that the …	Operational	Y
1005	The Windows Resource Exhaustion Detector failed to start due to an error.	Operational	N
1006	The Windows Resource Exhaustion Detector failed to stop due to an error.	Operational	N
1007	The Windows Resource Exhaustion Detector experienced a memory allocation …	Operational	N
1008	Windows failed to diagnose a low virtual memory condition.	Operational	N
2004	Windows successfully diagnosed a low virtual memory condition.	System	Y

Event ID 1001: The Windows Resource Exhaustion Detector started.

Provider: Microsoft-Windows-Resource-Exhaustion-Detector
Channel: Operational
Level: Informational
Task: LifecycleEvents
Opcode: Eventsloggedwhentheresourceexhaustiondetectorisstarted.

Description

The Windows Resource Exhaustion Detector started.

Message #

The Windows Resource Exhaustion Detector started.

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Resource-Exhaustion-Detector",
    "guid": "{9988748E-C2E8-4054-85F6-0C3E1CAD2470}",
    "event_source_name": "",
    "event_id": 1001,
    "version": 0,
    "level": 4,
    "task": 1,
    "opcode": 11,
    "keywords": 4611686018695823360,
    "time_created": "2026-05-29T16:35:27.0273587+00:00",
    "event_record_id": 19,
    "correlation": {},
    "execution": {
      "process_id": 6740,
      "thread_id": 1744
    },
    "channel": "Microsoft-Windows-Resource-Exhaustion-Detector/Operational",
    "computer": "telemetry-DC-a.cell-a.ludus.domain",
    "security": {
      "user_id": "S-1-5-19"
    }
  },
  "event_data": {},
  "message": "The Windows Resource Exhaustion Detector started."
}

Event ID 1002: The Windows Resource Exhaustion Detector stopped.

Provider: Microsoft-Windows-Resource-Exhaustion-Detector
Channel: Operational
Level: Informational
Task: LifecycleEvents
Opcode: Eventsloggedwhentheresourceexhaustiondetectorisstopped.

Description

The Windows Resource Exhaustion Detector stopped.

Message #

The Windows Resource Exhaustion Detector stopped.

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Resource-Exhaustion-Detector",
    "guid": "{9988748E-C2E8-4054-85F6-0C3E1CAD2470}",
    "event_source_name": "",
    "event_id": 1002,
    "version": 0,
    "level": 4,
    "task": 1,
    "opcode": 12,
    "keywords": 4611686018695823360,
    "time_created": "2026-06-13T05:22:34.5121826+00:00",
    "event_record_id": 21,
    "correlation": {},
    "execution": {
      "process_id": 7064,
      "thread_id": 3936
    },
    "channel": "Microsoft-Windows-Resource-Exhaustion-Detector/Operational",
    "computer": "telemetry-DC-c.cell-c.ludus.domain",
    "security": {
      "user_id": "S-1-5-19"
    }
  },
  "event_data": {},
  "message": "The Windows Resource Exhaustion Detector stopped."
}

Event ID 1003: The Windows Resource Exhaustion Detector received a notification that the computer is low on virtual memory.

Provider: Microsoft-Windows-Resource-Exhaustion-Detector
Channel: Operational
Level: Warning
Task: ResourceExhaustionDetectionEvents
Opcode: Eventsloggedwhenaproblemisdetected.

Description

The Windows Resource Exhaustion Detector received a notification that the computer is low on virtual memory.

Message #

The Windows Resource Exhaustion Detector received a notification that the computer is low on virtual memory.

Fields #

Name	Description
`CommitLimitExhaustion.SystemCommitLimit` UInt64
`CommitLimitExhaustion.SystemCommitCharge` UInt64
`SystemCommitLimit` UInt64
`SystemCommitCharge` UInt64

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Resource-Exhaustion-Detector",
    "guid": "{9988748E-C2E8-4054-85F6-0C3E1CAD2470}",
    "event_source_name": "",
    "event_id": 1003,
    "version": 0,
    "level": 3,
    "task": 2,
    "opcode": 22,
    "keywords": 4611686018964258816,
    "time_created": "2026-04-16T22:39:06.9591433+00:00",
    "event_record_id": 42,
    "correlation": {
      "ActivityID": "{D90F99CE-E214-4F5F-8E75-C294B37738F7}"
    },
    "execution": {
      "process_id": 16248,
      "thread_id": 4636
    },
    "channel": "Microsoft-Windows-Resource-Exhaustion-Detector/Operational",
    "computer": "JD-WIN11-22H2-1.ludus.domain",
    "security": {
      "user_id": "S-1-5-18"
    }
  },
  "user_data": {
    "CommitLimitExhaustion": {
      "SystemCommitLimit": "65690025984",
      "SystemCommitCharge": "65550077952"
    }
  },
  "message": "The Windows Resource Exhaustion Detector received a notification that the computer is low on virtual memory."
}

Event ID 1005: The Windows Resource Exhaustion Detector failed to start due to an error.

Provider: Microsoft-Windows-Resource-Exhaustion-Detector
Channel: Operational
Task: LifecycleEvents
Opcode: Eventsloggedwhentheresourceexhaustiondetectorisstarted.

Description

The Windows Resource Exhaustion Detector failed to start due to an error.

Message #

The Windows Resource Exhaustion Detector failed to start due to an error.

Fields #

Name	Description
`ErrorCode` UInt32

Event ID 1006: The Windows Resource Exhaustion Detector failed to stop due to an error.

Provider: Microsoft-Windows-Resource-Exhaustion-Detector
Channel: Operational
Task: LifecycleEvents
Opcode: Eventsloggedwhentheresourceexhaustiondetectorisstopped.

Description

The Windows Resource Exhaustion Detector failed to stop due to an error.

Message #

The Windows Resource Exhaustion Detector failed to stop due to an error.

Fields #

Name	Description
`ErrorCode` UInt32

Event ID 1007: The Windows Resource Exhaustion Detector experienced a memory allocation failure.

Provider: Microsoft-Windows-Resource-Exhaustion-Detector
Channel: Operational
Task: LifecycleEvents
Opcode: Eventsloggedafteramemoryallocation.

Description

The Windows Resource Exhaustion Detector experienced a memory allocation failure.

Message #

The Windows Resource Exhaustion Detector experienced a memory allocation failure.

Fields #

Name	Description
`RequestSize` UInt64
`ErrorCode` UInt32

Event ID 1008: Windows failed to diagnose a low virtual memory condition.

Provider: Microsoft-Windows-Resource-Exhaustion-Detector
Channel: Operational
Task: ResourceExhaustionDiagnosisEvents
Opcode: Containstheresultsofthediagnosis.

Description

Windows failed to diagnose a low virtual memory condition.

Message #

Windows failed to diagnose a low virtual memory condition.

Fields #

Name	Description
`ErrorCode` UInt32

Event ID 2004: Windows successfully diagnosed a low virtual memory condition.

Provider: Microsoft-Windows-Resource-Exhaustion-Detector
Channel: System
Level: Warning
Task: ResourceExhaustionDiagnosisEvents
Opcode: Containstheresultsofthediagnosis.

Description

Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: () consumed bytes, () consumed bytes, and () consumed bytes.

Message #

Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: %21 (%22) consumed %24 bytes, %28 (%29) consumed %31 bytes, and %35 (%36) consumed %38 bytes.

Fields #

Name	Description
`MemoryExhaustionInfo.SystemInfo`
`MemoryExhaustionInfo.PagedPoolInfo`
`MemoryExhaustionInfo.NonPagedPoolInfo`
`MemoryExhaustionInfo.ProcessInfo`
`MemoryExhaustionInfo.ExhaustionEventInfo`
`SystemCommitLimit` UInt64
`SystemCommitCharge` UInt64
`ProcessCommitCharge` UInt64
`PagedPoolUsage` UInt64
`PhysicalMemorySize` UInt64
`PhysicalMemoryUsage` UInt64
`NonPagedPoolUsage` UInt64
`TotalProcesses` UInt32
`PagedPoolTag_1` UnicodeString
`PagedPoolUsed_1` UInt64
`PagedPoolTag_2` UnicodeString
`PagedPoolUsed_2` UInt64
`PagedPoolTag_3` UnicodeString
`PagedPoolUsed_3` UInt64
`NonPagedPoolTag_1` UnicodeString
`NonPagedPoolUsed_1` UInt64
`NonPagedPoolTag_2` UnicodeString
`NonPagedPoolUsed_2` UInt64
`NonPagedPoolTag_3` UnicodeString
`NonPagedPoolUsed_3` UInt64
`Process_1_Name` UnicodeString
`Process_1_ID` UInt32
`Process_1_CreationTime` FILETIME
`Process_1_CommitCharge` UInt64
`Process_1_HandleCount` UInt32
`Process_1_Version` UnicodeString
`Process_1_TypeInfo` UInt32
`Process_2_Name` UnicodeString
`Process_2_ID` UInt32
`Process_2_CreationTime` FILETIME
`Process_2_CommitCharge` UInt64
`Process_2_HandleCount` UInt32
`Process_2_Version` UnicodeString
`Process_2_TypeInfo` UInt32
`Process_3_Name` UnicodeString
`Process_3_ID` UInt32
`Process_3_CreationTime` FILETIME
`Process_3_CommitCharge` UInt64
`Process_3_HandleCount` UInt32
`Process_3_Version` UnicodeString
`Process_3_TypeInfo` UInt32
`Process_4_Name` UnicodeString
`Process_4_ID` UInt32
`Process_4_CreationTime` FILETIME
`Process_4_CommitCharge` UInt64
`Process_4_HandleCount` UInt32
`Process_4_Version` UnicodeString
`Process_4_TypeInfo` UInt32
`Process_5_Name` UnicodeString
`Process_5_ID` UInt32
`Process_5_CreationTime` FILETIME
`Process_5_CommitCharge` UInt64
`Process_5_HandleCount` UInt32
`Process_5_Version` UnicodeString
`Process_5_TypeInfo` UInt32
`Process_6_Name` UnicodeString
`Process_6_ID` UInt32
`Process_6_CreationTime` FILETIME
`Process_6_CommitCharge` UInt64
`Process_6_HandleCount` UInt32
`Process_6_Version` UnicodeString
`Process_6_TypeInfo` UInt32
`EventGenerationTime` FILETIME

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Resource-Exhaustion-Detector",
    "guid": "{9988748E-C2E8-4054-85F6-0C3E1CAD2470}",
    "event_source_name": "",
    "event_id": 2004,
    "version": 0,
    "level": 3,
    "task": 3,
    "opcode": 33,
    "keywords": -9223372036317904896,
    "time_created": "2026-04-16T22:39:06.9814264+00:00",
    "event_record_id": 5418,
    "correlation": {
      "ActivityID": "{D90F99CE-E214-4F5F-8E75-C294B37738F7}"
    },
    "execution": {
      "process_id": 16248,
      "thread_id": 4636
    },
    "channel": "System",
    "computer": "JD-WIN11-22H2-1.ludus.domain",
    "security": {
      "user_id": "S-1-5-18"
    }
  },
  "user_data": {
    "MemoryExhaustionInfo": {
      "SystemInfo": "656900259846555007795261190393856120709120032205066240156272230401239695360223",
      "PagedPoolInfo": "MmSt148571376FMfn58098272NtfF49017600",
      "NonPagedPoolInfo": "smNp82804736smCB54226944Icp 46162896",
      "ProcessInfo": "claude.exe52522026-03-26T03:41:52.3826450Z519886643204052.1.77.065claude.exe185402026-04-16T02:13:26.1655552Z27885936643522.1.110.066vmmemCmZygote59402026-03-23T23:22:08.9372426Z52380057600.0.0.067explorer.exe91762026-03-23T23:22:08.2885971Z4591124481135110.0.22621.5983136Code.exe112282026-04-07T21:45:04.7807727Z2143969284641.114.0.0144Code.exe147802026-04-07T21:45:00.2928051Z1896325124851.114.0.0152",
      "ExhaustionEventInfo": "2026-04-05T13:16:09.5921292Z"
    }
  },
  "message": "Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: claude.exe (5252) consumed 51988664320 bytes, claude.exe (18540) consumed 2788593664 bytes, and vmmemCmZygote (5940) consumed 523800576 bytes."
}

Provenance

Where this provider's schema came from, and which Windows build it was observed on. Windows can change a provider's event schema between builds, so use this to judge whether it matches the build you collect from.

ETW provider GUID 9988748e-c2e8-4054-85f6-0c3e1cad2470

Defined in radardt.dll, which carries the event manifest.

Observed on:

WS2022-20348.4893, schema read from the registered manifest, binary version 10.0.20348.1, captured 2026-06-02
Win11-26200.6584, schema read from the registered manifest, binary version 10.0.26100.1, captured 2026-06-02

`j` / `k`	Scroll down / up
`d` / `u`	Half-page down / up
`gg` / `G`	Top / bottom
`h` / `l`	History back / forward
`f`	Follow link (`Shift` = new tab)
`/`	Focus search
`?`	Toggle this help
`↑` / `↓`	Navigate search results
`Enter`	Open highlighted result
`Esc`	Close results / dialog

`type:`	`events` / `rules` / `providers`
`vendor:`	`sigma` / `elastic` / `splunk` / `kusto` / `chronicle` (vendor name alone also works: `sigma:`, `kql:`, `secops:`…)
`tactic:`	TA-id, slug, or name: `credential_access`, `TA0006`
`technique:`	technique or sub-technique ID: `T1003`, `T1003.001` (alias `tech:`)
`severity:`	`critical` / `high` / `medium` / `low` / `informational` (alias `sev:`)
`risk_score`	Numeric comparison on the Elastic risk score (0 to 100): `risk_score>50`, `risk_score<=20`, `risk_score=99` (alias `risk`; Elastic rules only)
`stages:`	Rules with exactly N pipeline stages
`correlation:`	`single_event` / `sequence` / `alternatives` / `alternatives_cross_log` / `all_required` / `correlated`
`with:`	Co-occurrence event-id; stacks (`with:4624 with:4769`) to require all, while a comma list in one occurrence (`with:4624,4769`) is an either-or group. Implies multi-event
`like:`	Structural neighbors of a rule slug (equivalents + subsumption stricter / broader): `like:comsvcs_lsass_memory_dump-splunk-sysmon`
`groupby:`	Entity-grouping substring match against `group_by_keys`: `groupby:user`, `groupby:host`
`uses:`	Rules whose predicate tree touches the field (any kind, any value): `uses:CommandLine`
`excludes:`	Rules with top-level `not()` clauses on the field (FP whitelists): `excludes:ParentImage`
`field:` / `value:`	Predicate search; narrows rule cards to those with a matching leaf and drives the indicator tier. Unquoted = substring, wildcards allowed (`value:mimikatz`)
`indicator:`	Shorthand for `field:F value:V`: `indicator:Image=*\powershell.exe`
`kind:`	Filter by predicate kind. Narrows rule cards to those carrying a matching predicate leaf (`vendor:elastic kind:cidr_match`) and drives the indicator tier: `contains` / `starts_with` / `ends_with` / `regex` / `cidr` / `eq` / `in` … (operator aliases `op:`/`match:`)
`has:` / `no:`	`sample`, `field`, `notes`, `refs`, `trace`, `thirdparty`, `rule`, `pattern`, `timewindow`, `threshold`, `newterms`, `sigma`/`elastic`/`splunk`/`kusto`/`chronicle`
`-op:val`	Exclude matches; works on most operators but not `type:`/`like:`/`has:`/`no:` (use `no:<flag>` to exclude a rule flag): `tactic:execution -vendor:splunk`. Standalone `-kind:`/`-field:`/`-value:` drop every rule carrying a matching predicate leaf (`type:rules -kind:is_null`)
`field:"…"` / `value:"…"`	Quoted value = anchored exact match (also allows spaces): `value:"net user"`
`a,b`	Comma = OR inside one operator (`vendor:sigma,elastic`, `severity:high,critical`); repeating a facet merges the same way. `field:`/`value:` never split (literal commas)
`vendors:` / `stage:`	Singular and plural spellings fold to the canonical operator and value: `tactics:` = `tactic:`, `type:event` = `type:events`, `correlation:sequences` = `correlation:sequence`, `has:thresholds` = `has:threshold`
`"quoted phrase"`	Exact-match a multi-word phrase (free text)

Microsoft-Windows-Resource-Exhaustion-Detector

Event ID 1001: The Windows Resource Exhaustion Detector started.

Description

Message #

Example Event #

Event ID 1002: The Windows Resource Exhaustion Detector stopped.

Description

Message #

Example Event #

Event ID 1003: The Windows Resource Exhaustion Detector received a notification that the computer is low on virtual memory.

Description

Message #

Fields #

Example Event #

Event ID 1005: The Windows Resource Exhaustion Detector failed to start due to an error.

Description

Message #

Fields #

Event ID 1006: The Windows Resource Exhaustion Detector failed to stop due to an error.

Description

Message #

Fields #

Event ID 1007: The Windows Resource Exhaustion Detector experienced a memory allocation failure.

Description

Message #

Fields #

Event ID 1008: Windows failed to diagnose a low virtual memory condition.

Description

Message #

Fields #

Event ID 2004: Windows successfully diagnosed a low virtual memory condition.

Description

Message #

Fields #

Example Event #

Provenance

Downloads

Keyboard shortcuts

Search operators