Microsoft-Windows-Resource-Exhaustion-Resolver

17 events across 1 channel

Event	Title	Channel	Sample
1001	The Windows Resource Exhaustion Resolver started.	Operational	Y
1002	The Windows Resource Exhaustion Resolver stopped.	Operational	Y
1003	The Windows Resource Exhaustion Resolver received a notification that the …	Operational	N
1004	The Windows Resource Exhaustion Resolver close programs UI was launched.	Operational	N
1005	The Windows Resource Exhaustion Resolver failed to start due to an error.	Operational	N
1006	The Windows Resource Exhaustion Resolver failed to stop due to an error.	Operational	N
1007	The Windows Resource Exhaustion Resolver experienced a memory allocation …	Operational	N
1008	The Windows Resource Exhaustion Resolver failed to launch the close programs UI.	Operational	N
1009	The Windows Resource Exhaustion Resolver close programs UI was closed.	Operational	N
1010	Windows could not restore the computer's virtual memory.	Operational	N
1011	Windows could not restore the computer's virtual memory because some programs …	Operational	N
1012	Windows successfully restored your computer's virtual memory.	Operational	N
1013	Windows successfully restored your computer's virtual memory without closing any …	Operational	N
1014	The Windows Resource Exhaustion Resolver received a notification to perform …	Operational	Y
1015	The Windows Resource Exhaustion Resolver received an event from the Windows …	Operational	Y
1016	Windows could not restore the computer's virtual memory.	Operational	N
1017	The Windows Resource Exhaustion Resolver resolution failure notification UI was …	Operational	N

Event ID 1001: The Windows Resource Exhaustion Resolver started.

Provider: Microsoft-Windows-Resource-Exhaustion-Resolver
Channel: Operational
Level: Informational
Task: LifecycleEvents
Opcode: Eventsloggedwhentheresourceexhaustionresolverisstarted.

Description

The Windows Resource Exhaustion Resolver started.

Message #

The Windows Resource Exhaustion Resolver started.

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Resource-Exhaustion-Resolver",
    "guid": "{91F5FB12-FDEA-4095-85D5-614B495CD9DE}",
    "event_source_name": "",
    "event_id": 1001,
    "version": 0,
    "level": 4,
    "task": 1,
    "opcode": 11,
    "keywords": -9223372036854771712,
    "time_created": "2026-05-29T06:44:06.0373204+00:00",
    "event_record_id": 4,
    "correlation": {},
    "execution": {
      "process_id": 2368,
      "thread_id": 2008
    },
    "channel": "Microsoft-Windows-Resource-Exhaustion-Resolver/Operational",
    "computer": "telemetry-DC-b.cell-b.ludus.domain",
    "security": {
      "user_id": "S-1-5-21-1006758700-2167138679-1475694448-1105"
    }
  },
  "event_data": {},
  "message": "The Windows Resource Exhaustion Resolver started."
}

Event ID 1002: The Windows Resource Exhaustion Resolver stopped.

Provider: Microsoft-Windows-Resource-Exhaustion-Resolver
Channel: Operational
Task: LifecycleEvents
Opcode: Eventsloggedwhentheresourceexhaustionresolverisstopped.

Description

The Windows Resource Exhaustion Resolver stopped.

Message #

The Windows Resource Exhaustion Resolver stopped.

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Resource-Exhaustion-Resolver",
    "event_id": 1002,
    "level": "Information",
    "task": "Lifecycle Events",
    "opcode": "Events logged when the resource exhaustion resolver is stopped.",
    "time_created": "2026-04-22T05:44:22.3054467+00:00",
    "computer": "JD-DC01-2022.ludus.domain",
    "channel": "Microsoft-Windows-Resource-Exhaustion-Resolver/Operational"
  },
  "event_data": {}
}

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

Provider: Microsoft-Windows-Resource-Exhaustion-Resolver
Channel: Operational
Task: ResolutionEvents
Opcode: Eventsloggedafterperformingtheresolutionactions

Description

The Windows Resource Exhaustion Resolver received a notification that the computer is low on virtual memory. This notification was ignored as it is no longer valid.

Message #

The Windows Resource Exhaustion Resolver received a notification that the computer is low on virtual memory. This notification was ignored as it is no longer valid.

Fields #

Name	Description
`TimeSinceLastUI` UInt32
`EventGenerationTime` FILETIME
`EventType` UInt32
`DropReasonCode` UInt32
`TimesUIShown` UInt8
`MaxCommit` UInt8

Event ID 1004: The Windows Resource Exhaustion Resolver close programs UI was launched.

Provider: Microsoft-Windows-Resource-Exhaustion-Resolver
Channel: Operational
Task: UIEvents
Opcode: EventsloggedbeforeUIislaunched.

Description

The Windows Resource Exhaustion Resolver close programs UI was launched.

Message #

The Windows Resource Exhaustion Resolver close programs UI was launched.

Fields #

Name	Description
`Process_1_Name` UnicodeString
`Process_1_ID` UInt32
`Process_1_CreationTime` FILETIME
`Process_1_Version` UnicodeString
`Process_2_Name` UnicodeString
`Process_2_ID` UInt32
`Process_2_CreationTime` FILETIME
`Process_2_Version` UnicodeString
`Process_3_Name` UnicodeString
`Process_3_ID` UInt32
`Process_3_CreationTime` FILETIME
`Process_3_Version` UnicodeString
`ResolverID` UInt32
`EventGenerationTime` FILETIME

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

Provider: Microsoft-Windows-Resource-Exhaustion-Resolver
Channel: Operational
Task: LifecycleEvents
Opcode: Eventsloggedwhentheresourceexhaustionresolverisstarted.

Description

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

Message #

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

Fields #

Name	Description
`ErrorCode` UInt32

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

Provider: Microsoft-Windows-Resource-Exhaustion-Resolver
Channel: Operational
Task: LifecycleEvents
Opcode: Eventsloggedwhentheresourceexhaustionresolverisstopped.

Description

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

Message #

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

Fields #

Name	Description
`ErrorCode` UInt32

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

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

Description

The Windows Resource Exhaustion Resolver experienced a memory allocation failure.

Message #

The Windows Resource Exhaustion Resolver experienced a memory allocation failure.

Fields #

Name	Description
`RequestSize` UInt64
`ErrorCode` UInt32

Event ID 1008: The Windows Resource Exhaustion Resolver failed to launch the close programs UI.

Provider: Microsoft-Windows-Resource-Exhaustion-Resolver
Channel: Operational
Task: UIEvents
Opcode: EventsloggedafterUIislaunchedorafteranattempttolaunchtheUIismade.

Description

The Windows Resource Exhaustion Resolver failed to launch the close programs UI.

Message #

The Windows Resource Exhaustion Resolver failed to launch the close programs UI.

Fields #

Name	Description
`ErrorCode` UInt32

Event ID 1009: The Windows Resource Exhaustion Resolver close programs UI was closed.

Provider: Microsoft-Windows-Resource-Exhaustion-Resolver
Channel: Operational
Task: UIEvents
Opcode: EventsloggedafterUIislaunchedorafteranattempttolaunchtheUIismade.

Description

The Windows Resource Exhaustion Resolver close programs UI was closed.

Message #

The Windows Resource Exhaustion Resolver close programs UI was closed.

Fields #

Name	Description
`UIDisplayTime` UInt32
`UserAction` Int32
`MaxCommit` UInt8

Event ID 1010: Windows could not restore the computer's virtual memory.

Provider: Microsoft-Windows-Resource-Exhaustion-Resolver
Channel: Operational
Task: ResolutionEvents
Opcode: Eventsloggedafterperformingtheresolutionactions

Description

Windows could not restore the computer's virtual memory. To prevent information loss, save your files and close your programs.

Message #

Windows could not restore the computer's virtual memory. To prevent information loss, save your files and close your programs.

Fields #

Name	Description
`ReasonCode` UInt32
`UserAction` Int32
`MaxCommit` UInt8

Event ID 1011: Windows could not restore the computer's virtual memory because some programs could not be closed.

Provider: Microsoft-Windows-Resource-Exhaustion-Resolver
Channel: Operational
Task: ResolutionEvents
Opcode: Eventsloggedafterperformingtheresolutionactions

Description

Windows could not restore the computer's virtual memory because some programs could not be closed.

Message #

Windows could not restore the computer's virtual memory because some programs could not be closed.

Fields #

Name	Description
`ReasonCode` UInt32
`UserAction` Int32
`MaxCommit` UInt8

Event ID 1012: Windows successfully restored your computer's virtual memory.

Provider: Microsoft-Windows-Resource-Exhaustion-Resolver
Channel: Operational
Task: ResolutionEvents
Opcode: Eventsloggedafterperformingtheresolutionactions

Description

Windows successfully restored your computer's virtual memory.

Message #

Windows successfully restored your computer's virtual memory.

Fields #

Name	Description
`TimesUIShown` UInt8
`UserAction` Int32

Event ID 1013: Windows successfully restored your computer's virtual memory without closing any programs.

Provider: Microsoft-Windows-Resource-Exhaustion-Resolver
Channel: Operational
Task: ResolutionEvents
Opcode: Eventsloggedafterperformingtheresolutionactions

Description

Windows successfully restored your computer's virtual memory without closing any programs.

Message #

Windows successfully restored your computer's virtual memory without closing any programs.

Fields #

Name	Description
`TimesUIShown` UInt8
`UserAction` Int32

Event ID 1014: The Windows Resource Exhaustion Resolver received a notification to perform memory leak diagnosis.

Provider: Microsoft-Windows-Resource-Exhaustion-Resolver
Channel: Operational
Level: Informational
Task: LeakDiagnosisEvents
Opcode: Eventsloggedafteranattempttolaunchtheleakdiagnoserismade.

Description

The Windows Resource Exhaustion Resolver received a notification to perform memory leak diagnosis. This notification was processed and dropped.

Message #

The Windows Resource Exhaustion Resolver received a notification to perform memory leak diagnosis. This notification was processed and dropped.

Fields #

Name	Description
`DroppedLeakDiagnosisEventInfo.ProcessImageName`
`DroppedLeakDiagnosisEventInfo.ProcessId`
`DroppedLeakDiagnosisEventInfo.ProcessCreationTime`
`DroppedLeakDiagnosisEventInfo.DropReasonCode`
`ProcessImageName`
`PID`
`CreationTime`
`DropReasonCode`

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Resource-Exhaustion-Resolver",
    "guid": "{91F5FB12-FDEA-4095-85D5-614B495CD9DE}",
    "event_source_name": "",
    "event_id": 1014,
    "version": 0,
    "level": 4,
    "task": 5,
    "opcode": 41,
    "keywords": -9223372036854759424,
    "time_created": "2026-05-29T06:44:08.0835351+00:00",
    "event_record_id": 6,
    "correlation": {
      "ActivityID": "{559E5142-CDCD-4213-BC43-A528C3D24645}"
    },
    "execution": {
      "process_id": 2368,
      "thread_id": 2008
    },
    "channel": "Microsoft-Windows-Resource-Exhaustion-Resolver/Operational",
    "computer": "telemetry-DC-b.cell-b.ludus.domain",
    "security": {
      "user_id": "S-1-5-21-1006758700-2167138679-1475694448-1105"
    }
  },
  "user_data": {
    "DroppedLeakDiagnosisEventInfo": {
      "ProcessImageName": "wsmprovhost.exe",
      "ProcessId": "5772",
      "ProcessCreationTime": "2026-05-29T06:42:05.7051460Z",
      "DropReasonCode": "16"
    }
  },
  "message": "The Windows Resource Exhaustion Resolver received a notification to perform memory leak diagnosis. This notification was processed and dropped."
}

Event ID 1015: The Windows Resource Exhaustion Resolver received an event from the Windows Resource Exhaustion Detector.

Provider: Microsoft-Windows-Resource-Exhaustion-Resolver
Channel: Operational
Level: Informational
Task: ResolutionEvents
Opcode: Eventsloggedwhendiagnosisisstarted.

Description

The Windows Resource Exhaustion Resolver received an event from the Windows Resource Exhaustion Detector.

Message #

The Windows Resource Exhaustion Resolver received an event from the Windows Resource Exhaustion Detector.

Fields #

Name	Description
`EventInfo.Event`
`Event`

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-Resource-Exhaustion-Resolver",
    "guid": "{91F5FB12-FDEA-4095-85D5-614B495CD9DE}",
    "event_source_name": "",
    "event_id": 1015,
    "version": 0,
    "level": 4,
    "task": 3,
    "opcode": 21,
    "keywords": -9223372036854767616,
    "time_created": "2026-05-29T06:44:06.0374855+00:00",
    "event_record_id": 5,
    "correlation": {
      "ActivityID": "{559E5142-CDCD-4213-BC43-A528C3D24645}"
    },
    "execution": {
      "process_id": 2368,
      "thread_id": 2008
    },
    "channel": "Microsoft-Windows-Resource-Exhaustion-Resolver/Operational",
    "computer": "telemetry-DC-b.cell-b.ludus.domain",
    "security": {
      "user_id": "S-1-5-21-1006758700-2167138679-1475694448-1105"
    }
  },
  "user_data": {
    "EventInfo": {
      "Event": "4"
    }
  },
  "message": "The Windows Resource Exhaustion Resolver received an event from the Windows Resource Exhaustion Detector."
}

Event ID 1016: Windows could not restore the computer's virtual memory.

Provider: Microsoft-Windows-Resource-Exhaustion-Resolver
Channel: Operational
Task: ResolutionEvents
Opcode: Eventsloggedafterperformingtheresolutionactions

Description

Windows could not restore the computer's virtual memory.

Message #

Windows could not restore the computer's virtual memory.

Fields #

Name	Description
`ErrorCode` UInt32
`ResolutionAttempted` UInt8

Event ID 1017: The Windows Resource Exhaustion Resolver resolution failure notification UI was closed.

Provider: Microsoft-Windows-Resource-Exhaustion-Resolver
Channel: Operational
Task: ResolutionEvents
Opcode: Eventsloggedafterperformingtheresolutionactions

Description

The Windows Resource Exhaustion Resolver resolution failure notification UI was closed.

Message #

The Windows Resource Exhaustion Resolver resolution failure notification UI was closed.

Fields #

Name	Description
`UIDisplayTime` UInt32
`UserAction` Int32
`MaxCommit` UInt8

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 91f5fb12-fdea-4095-85d5-614b495cd9de

Defined in radarrs.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-Resolver

Event ID 1001: The Windows Resource Exhaustion Resolver started.

Description

Message #

Example Event #

Event ID 1002: The Windows Resource Exhaustion Resolver stopped.

Description

Message #

Example Event #

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

Description

Message #

Fields #

Event ID 1004: The Windows Resource Exhaustion Resolver close programs UI was launched.

Description

Message #

Fields #

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

Description

Message #

Fields #

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

Description

Message #

Fields #

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

Description

Message #

Fields #

Event ID 1008: The Windows Resource Exhaustion Resolver failed to launch the close programs UI.

Description

Message #

Fields #

Event ID 1009: The Windows Resource Exhaustion Resolver close programs UI was closed.

Description

Message #

Fields #

Event ID 1010: Windows could not restore the computer's virtual memory.

Description

Message #

Fields #

Event ID 1011: Windows could not restore the computer's virtual memory because some programs could not be closed.

Description

Message #

Fields #

Event ID 1012: Windows successfully restored your computer's virtual memory.

Description

Message #

Fields #

Event ID 1013: Windows successfully restored your computer's virtual memory without closing any programs.

Description

Message #

Fields #

Event ID 1014: The Windows Resource Exhaustion Resolver received a notification to perform memory leak diagnosis.

Description

Message #

Fields #

Example Event #

Event ID 1015: The Windows Resource Exhaustion Resolver received an event from the Windows Resource Exhaustion Detector.

Description

Message #

Fields #

Example Event #

Event ID 1016: Windows could not restore the computer's virtual memory.

Description

Message #

Fields #

Event ID 1017: The Windows Resource Exhaustion Resolver resolution failure notification UI was closed.

Description

Message #

Fields #

Provenance

Downloads