Microsoft-Windows-Kernel-WDI

14 events across 3 channels

Event ID	Title	Channel
32	The Scenario Event Mapper started a scenario for provider %1 (event ID %2) with …	Analytic
33	The Scenario Event Mapper stopped a scenario for provider %1 (event ID %2) with …	Analytic
34	An in-flight scenario from provider %1 (event ID %2) timed out and was stopped …	Analytic
35	The Scenario Event Mapper was unable to start a new scenario for provider %1 …	Debug
36	The Scenario Event Mapper was unable to start a scenario for provider %1 (event …	Debug
37	The Scenario Event Mapper was unable to stop a scenario for provider %1 (event …	Debug
38	The Scenario Event Mapper is configured with more than the maximum number of …	Operational
39	The Scenario Event Mapper is configured with more than the maximum number of …	Operational
40	The Scenario Event Mapper is configured with more than the maximum number of end …	Operational
41	The Scenario Event Mapper is configured with more than the maximum number of …	Operational
42	The Scenario Event Mapper is configured with an unsupported scenario.	Operational
43		Operational
44		Operational
45		Operational

Event ID 32 — The Scenario Event Mapper started a scenario for provider %1 (event ID %2) with %4 context providers.

Provider: Microsoft-Windows-Kernel-WDI
Channel: Analytic

Message

The Scenario Event Mapper started a scenario for provider %1 (event ID %2) with %4 context providers.  The context logger dropped event count was %3.

Fields

Name	Description
`ProviderID`	—
`EventID`	—
`DroppedEventCount`	—
`ActionCount`	—
`SemActions`	—

Event ID 33 — The Scenario Event Mapper stopped a scenario for provider %1 (event ID %2) with %4 context providers.

Provider: Microsoft-Windows-Kernel-WDI
Channel: Analytic

Message

The Scenario Event Mapper stopped a scenario for provider %1 (event ID %2) with %4 context providers.  The context logger dropped event count was %3.

Fields

Name	Description
`ProviderID`	—
`EventID`	—
`DroppedEventCount`	—
`ActionCount`	—
`SemActions`	—

Event ID 34 — An in-flight scenario from provider %1 (event ID %2) timed out and was stopped automatically by the Scenario Event Mapper.

Provider: Microsoft-Windows-Kernel-WDI
Channel: Analytic

Message

An in-flight scenario from provider %1 (event ID %2) timed out and was stopped automatically by the Scenario Event Mapper.

Fields

Name	Description
`ProviderID`	—
`EventID`	—

Event ID 35 — The Scenario Event Mapper was unable to start a new scenario for provider %1 (event ID %2) because the maximum number of scenarios are already in f...

Provider: Microsoft-Windows-Kernel-WDI
Channel: Debug

Message

The Scenario Event Mapper was unable to start a new scenario for provider %1 (event ID %2) because the maximum number of scenarios are already in flight.

Fields

Name	Description
`ProviderID`	—
`EventID`	—
`ScenarioCount`	—
`ScenarioInflightItems`	—

Event ID 36 — The Scenario Event Mapper was unable to start a scenario for provider %1 (event ID %2).

Provider: Microsoft-Windows-Kernel-WDI
Channel: Debug

Message

The Scenario Event Mapper was unable to start a scenario for provider %1 (event ID %2).  The error code was %3.

Fields

Name	Description
`ProviderID`	—
`EventID`	—
`NTStatus`	—

Event ID 37 — The Scenario Event Mapper was unable to stop a scenario for provider %1 (event ID %2).

Provider: Microsoft-Windows-Kernel-WDI
Channel: Debug

Message

The Scenario Event Mapper was unable to stop a scenario for provider %1 (event ID %2).  The error code was %3.

Fields

Name	Description
`ProviderID`	—
`EventID`	—
`NTStatus`	—

Event ID 38 — The Scenario Event Mapper is configured with more than the maximum number of scenarios.

Provider: Microsoft-Windows-Kernel-WDI
Channel: Operational

Message

The Scenario Event Mapper is configured with more than the maximum number of scenarios.  The scenario for provider %1 (event ID %2) will be ignored.

Fields

Name	Description
`ProviderID`	—
`EventID`	—

Event ID 39 — The Scenario Event Mapper is configured with more than the maximum number of context providers for the scenario with provider %1 (event ID %2).

Provider: Microsoft-Windows-Kernel-WDI
Channel: Operational

Message

The Scenario Event Mapper is configured with more than the maximum number of context providers for the scenario with provider %1 (event ID %2).  The scenario will be ignored.

Fields

Name	Description
`ProviderID`	—
`EventID`	—

Event ID 40 — The Scenario Event Mapper is configured with more than the maximum number of end events for the scenario with provider %1 (event ID %2).

Provider: Microsoft-Windows-Kernel-WDI
Channel: Operational

Message

The Scenario Event Mapper is configured with more than the maximum number of end events for the scenario with provider %1 (event ID %2).  The scenario will be ignored.

Fields

Name	Description
`ProviderID`	—
`EventID`	—

Event ID 41 — The Scenario Event Mapper is configured with more than the maximum number of providers.

Provider: Microsoft-Windows-Kernel-WDI
Channel: Operational

Message

The Scenario Event Mapper is configured with more than the maximum number of providers.  The provider %1 will be ignored.

Fields

Name	Description
`ProviderID`	—

Event ID 42 — The Scenario Event Mapper is configured with an unsupported scenario.

Provider: Microsoft-Windows-Kernel-WDI
Channel: Operational

Message

The Scenario Event Mapper is configured with an unsupported scenario. The scenario for provider %1 (event ID %2) encountered error code %3 and will be ignored.

Fields

Name	Description
`ProviderID`	—
`EventID`	—
`NTStatus`	—

Event ID 43 —

Provider: Microsoft-Windows-Kernel-WDI
Channel: Operational

Fields

Name	Description
`SqmType`	—
`SqmSid`	—

Event ID 44 —

Provider: Microsoft-Windows-Kernel-WDI
Channel: Operational

Fields

Name	Description
`SqmSessionGuid`	—
`SqmID`	—
`SqmType`	—
`SqmDWORDDatapointValue`	—

Event ID 45 —

Provider: Microsoft-Windows-Kernel-WDI
Channel: Operational

Fields

Name	Description
`SqmSessionGuid`	—
`SqmID`	—
`SqmType`	—
`SqmStreamRowLength`	—
`SqmStreamRow`	—