Windows / Modules / dps.dll

dps.dll

Associated Error Codes

Below lists error codes and symbolic names found for this module.

CodeFound inDescription
0x1000000a1011Memory tracing events
0x100000211011Timing Events
0x100000221011Scenario trigger events
0x100000231011Debug events
0x100000241011Scenario lifecycle events
0x100000251011Diagnostic Module notification events
0x3000000a1011The Diagnostic Policy Service started
0x3000000b1011A diagnostic scenario was misconfigured
0x3000000c1011A diagnostic module detected a problem
0x3000000d1011A scenario instance was dispatched for troubleshooting
0x3000000e1011A diagnostic module completed troubleshooting without setting a resolution
0x3000000f1011A diagnostic module completed troubleshooting and set an immediate resolution
0x300000101011A diagnostic module finished troubleshooting and set an queued resolution
0x300000111011A scenario instance was dispatched for resolution
0x300000121011A diagnostic module queued itself for later invocation
0x300000131011A diagnostic module completed resolution
0x300000141011The Diagnostic Policy Service was not able to instantiate a diagnostic module host
0x300000151011This event is raised when a scenario fails
0x300000161011A diagnostic module was moved to a broken state
0x300000171011Debug event
0x300000181011This event is raised at the ServiceMain for the service
0x300000191011This event is raised when the DPS signals its status as RUNNING to the SCM
0x3000001a1011This event is raised when the service receives a shutdown/stop notification from the SCM
0x3000001b1011This event is raised when the service is successfully stopped
0x3000001c1011This event is raised when DPS refreshes group policy
0x500000021011Error
0x500000031011Warning
0x500000041011Information
0x500000051011Verbose
0x700000011011Scenario Lifecycle
0x700000021011Debug task
0x700000031011DPS Initialization
0x700000041011Notification task
0x900000011011Microsoft-Windows-Diagnosis-DPS
0x900000021011Microsoft-Windows-Diagnosis-DPS/Debug
0x900000031011Microsoft-Windows-Diagnosis-DPS/Operational
0x900000041011Microsoft-Windows-Diagnosis-DPS/Analytic
0x910000011011Microsoft-Windows-Diagnosis-WDI
0x910000021011Microsoft-Windows-Diagnosis-WDI/Debug
0xb00000011011The Diagnostic Policy Service started. This event signals diagnostic modules for delayed processing after the service is initialized.
0xb00000021011The Diagnostic Policy Service started. This event signals diagnostic modules for immediate processing after the service is initialized.
0xb00000051011The scenario %1 has a configuration error or has been explicitly disabled in the WDI registry namespace. The Diagnostic Policy Service will ignore the scenario.
0xb00000641011Diagnostic module %5 (%4) detected a problem for scenario %1, instance %2, original activity ID %3.
0xb00000691011Diagnostic module %5 (%4) started troubleshooting scenario %1, instance %2, original activity ID %3.
0xb000006e1011Diagnostic module %5 (%4) finished troubleshooting scenario %1, instance %2, original activity ID %3. No resolution was set by the diagnostic module.
0xb00000731011Diagnostic module %9 (%4) finished troubleshooting scenario %1, instance %2, original activity ID %3. It set resolution %5 for user %6 in session %7 with expiration date %8. The resolution will be started immediately.
0xb00000781011Diagnostic module %9 (%4) finished troubleshooting scenario %1, instance %2, original activity ID %3. It set resolution %5 for user %6 in session %7 with expiration date %8. The resolution was queued to start later.
0xb000007d1011Diagnostic module %5 (%4) started resolving scenario %1, instance %2, original activity ID %3.
0xb000007e1011Diagnostic module %5 (%4) was queued to start later for scenario %1, instance %2, original activity ID %3.
0xb00000821011Diagnostic module %5 (%4) finished resolving scenario %1, instance %2, original activity ID %3.
0xb00000871011The Diagnostic Policy Service could not create a diagnostic module host instance for diagnostic module %6 (%5). The error code was %4. The scenario %1, instance %2, original activity ID %3 will be discarded.
0xb000008c1011The Diagnostic Policy Service encountered an error in file %1, function %2, line %3: %4.
0xb00000911011This event is raised when the SCM loads the service DLL
0xb00000961011This event is raised when the service enters a SERVICE_RUNNING state
0xb000009b1011This event is raised when the SCM signals the service to shut down.
0xb00000a01011This event is raised when the service is successfully stopped
0xb00000a51011The Diagnostic Policy Service encountered an error while handling scenario %1 with diagnostic module %6 (%5), instance %2, original activity ID %3. The error code was %4.
0xb00000aa1011Diagnostic module %6 (%4) encountered an error while handling scenario %1, instance %2, original activity ID %3. The error code was %5.
0xb00000af1011Scenario %1, instance %2, original activity ID %3 was dropped by diagnostic module %6 (%4). The error code was %5.
0xb00000b41011The Diagnostic Policy Service just refreshed the Group Policy. This event notifies the diagnostic modules about the Group Policy changes.
0xb00000b91011Diagnostic module %2 (%1) was moved into a broken state. The error code was %3.
0xb00013981011The Diagnostic Policy Service just made a heap allocation
0xb00013991011The Diagnostic Policy Service just freed a previously made heap allocation
0xb10013981011The Diagnostic Infrastructure just made a heap allocation
0xb10013991011The Diagnostic Infrastructure just freed a previously made heap allocation
65 entries