| 500 | Diagnostic Policy Service |
Diagnostic Policy Service |
| 501 | 诊断策略服务启用了 Windows 组件的问题检测、疑难解答和解决方案。如果该服务被停止，诊断将不再运行。 |
The Diagnostic Policy Service enables problem detection, troubleshooting and resolution for Windows components. If this service is stopped, diagnostics will no longer function. |
| 600 | Microsoft Corporation |
Microsoft Corporation |
| 602 | Windows Diagnostic Infrastructure Resolution 主机启用交互式解决方案解决诊断策略服务检测到的系统问题。必要时诊断策略服务在相应的用户会话中触发此任务。如果诊断策略服务未运行，则该任务也不会运行 |
The Windows Diagnostic Infrastructure Resolution host enables interactive resolutions for system problems detected by the Diagnostic Policy Service. It is triggered when necessary by the Diagnostic Policy Service in the appropriate user session. If the Diagnostic Policy Service is not running, the task will not run |
| 0x1000000A | 内存跟踪事件 |
Memory tracing events |
| 0x10000021 | 定时事件 |
Timing Events |
| 0x10000022 | 方案触发事件 |
Scenario trigger events |
| 0x10000023 | 调试事件 |
Debug events |
| 0x10000024 | 方案生命周期事件 |
Scenario lifecycle events |
| 0x10000025 | 诊断模块通知事件 |
Diagnostic Module notification events |
| 0x3000000A | 诊断策略服务已启动 |
The Diagnostic Policy Service started |
| 0x3000000B | 诊断方案配置错误 |
A diagnostic scenario was misconfigured |
| 0x3000000C | 诊断模块检测到问题 |
A diagnostic module detected a problem |
| 0x3000000D | 调度方案实例以用于故障排除 |
A scenario instance was dispatched for troubleshooting |
| 0x3000000E | 诊断模块完成了故障排除而没有设置解决方案 |
A diagnostic module completed troubleshooting without setting a resolution |
| 0x3000000F | 诊断模块完成了故障排除并设置了立即解决方案 |
A diagnostic module completed troubleshooting and set an immediate resolution |
| 0x30000010 | 诊断模块完成了故障排除并设置了排队解决方案 |
A diagnostic module finished troubleshooting and set an queued resolution |
| 0x30000011 | 调度方案实例以用于解决方案 |
A scenario instance was dispatched for resolution |
| 0x30000012 | 诊断模块将自身排队以备以后调用 |
A diagnostic module queued itself for later invocation |
| 0x30000013 | 诊断模块完成了解决方案 |
A diagnostic module completed resolution |
| 0x30000014 | 诊断策略服务无法实例化诊断模块主机 |
The Diagnostic Policy Service was not able to instantiate a diagnostic module host |
| 0x30000015 | 当解决方案失败时出现该事件 |
This event is raised when a scenario fails |
| 0x30000016 | 诊断模块被移入了故障状态 |
A diagnostic module was moved to a broken state |
| 0x30000018 | 在服务的 ServiceMain 上出现此事件 |
This event is raised at the ServiceMain for the service |
| 0x30000019 | 当 DPS 向 SCM 通知其状态为 RUNNING 时出现此事件 |
This event is raised when the DPS signals its status as RUNNING to the SCM |
| 0x3000001A | 当服务收到来自 SCM 的关闭/停止通知时出现此事件 |
This event is raised when the service receives a shutdown/stop notification from the SCM |
| 0x3000001B | 当服务成功停止时出现此事件 |
This event is raised when the service is successfully stopped |
| 0x3000001C | 当 DPS 刷新组策略时出现此事件 |
This event is raised when DPS refreshes group policy |
| 0x50000002 | 错误 |
Error |
| 0x50000003 | 警告 |
Warning |
| 0x50000004 | 信息 |
Information |
| 0x50000005 | 详细 |
Verbose |
| 0x70000001 | 方案生命周期 |
Scenario Lifecycle |
| 0x70000002 | 调试任务 |
Debug task |
| 0x70000003 | DPS 初始化 |
DPS Initialization |
| 0x70000004 | 通知任务 |
Notification task |
| 0x90000001 | Microsoft-Windows-Diagnosis-DPS |
Microsoft-Windows-Diagnosis-DPS |
| 0x90000002 | Microsoft-Windows-Diagnosis-DPS/Debug |
Microsoft-Windows-Diagnosis-DPS/Debug |
| 0x90000003 | Microsoft-Windows-Diagnosis-DPS/Operational |
Microsoft-Windows-Diagnosis-DPS/Operational |
| 0x90000004 | Microsoft-Windows-Diagnosis-DPS/Analytic |
Microsoft-Windows-Diagnosis-DPS/Analytic |
| 0x91000001 | Microsoft-Windows-Diagnosis-WDI |
Microsoft-Windows-Diagnosis-WDI |
| 0x91000002 | Microsoft-Windows-Diagnosis-WDI/Debug |
Microsoft-Windows-Diagnosis-WDI/Debug |
| 0xB0000001 | 诊断策略服务已启动。此事件在服务初始化后向诊断模块通知延迟的处理。 |
The Diagnostic Policy Service started. This event signals diagnostic modules for delayed processing after the service is initialized. |
| 0xB0000002 | 诊断策略服务已启动。此事件将发信号通知诊断模块在启动该服务后立即处理。 |
The Diagnostic Policy Service started. This event signals diagnostic modules for immediate processing after the service is initialized. |
| 0xB0000005 | 方案 %1 在 WDI 注册表命名空间中有一个配置错误或已被明确禁用。诊断策略服务将忽略该方案。 |
The scenario %1 has a configuration error or has been explicitly disabled in the WDI registry namespace. The Diagnostic Policy Service will ignore the scenario. |
| 0xB0000064 | 诊断模块 %5 (%4)检测到方案 %1 中实例 %2 的原始活动 ID %3 的问题。 |
Diagnostic module %5 (%4) detected a problem for scenario %1, instance %2, original activity ID %3. |
| 0xB0000069 | 诊断模块 %5 (%4)启动了对方案 %1 中实例 %2 的原始活动 ID %3 的故障排除。 |
Diagnostic module %5 (%4) started troubleshooting scenario %1, instance %2, original activity ID %3. |
| 0xB000006E | 诊断模块 %5 (%4)完成了对方案 %1 中实例 %2 的原始活动 ID %3 的故障排除。诊断模块没有设置解决方案。 |
Diagnostic module %5 (%4) finished troubleshooting scenario %1, instance %2, original activity ID %3. No resolution was set by the diagnostic module. |
| 0xB0000073 | 诊断模块 %9 (%4)完成了对方案 %1 中实例 %2 的原始活动 ID %3 的故障排除。它在会话 %7 中为用户 %6 设置了解决方案 %5，过期日期为 %8。将立即执行该解决方案。 |
Diagnostic 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. |
| 0xB0000078 | 诊断模块 %9 (%4)完成了对方案 %1 中实例 %2 的原始活动 ID %3 的故障排除。它在会话 %7 中为用户 %6 设置了解决方案 %5，过期日期为 %8。将该解决方案排队以备以后执行。 |
Diagnostic 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. |
| 0xB000007D | 诊断模块 %5 (%4)启动了对方案 %1 中实例 %2 的原始活动 ID %3 的解析。 |
Diagnostic module %5 (%4) started resolving scenario %1, instance %2, original activity ID %3. |
| 0xB000007E | 将诊断模块 %5 (%4)排队以备以后方案 %1 中实例 %2 的原始活动 ID %3 启动。 |
Diagnostic module %5 (%4) was queued to start later for scenario %1, instance %2, original activity ID %3. |
| 0xB0000082 | 诊断模块 %5 (%4)完成了对方案 %1 中实例 %2 的原始活动 ID %3 的解析。 |
Diagnostic module %5 (%4) finished resolving scenario %1, instance %2, original activity ID %3. |
| 0xB0000087 | 诊断策略服务无法为诊断模块 %6 (%5)创建诊断模块主机实例。错误代码为 %4。 将丢弃方案 %1 中实例 %2 的原始活动 ID %3。 |
The 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. |
| 0xB000008C | 诊断策略服务在文件 %1 中函数 %2 的第 %3 行上遇到错误: %4。 |
The Diagnostic Policy Service encountered an error in file %1, function %2, line %3: %4. |
| 0xB0000091 | 当 SCM 加载服务 DLL 时出现此事件 |
This event is raised when the SCM loads the service DLL |
| 0xB0000096 | 当服务进入 SERVICE_RUNNING 状态时出现此事件 |
This event is raised when the service enters a SERVICE_RUNNING state |
| 0xB000009B | 当 SCM 通知服务关闭时出现此事件 |
This event is raised when the SCM signals the service to shut down. |
| 0xB00000A5 | 当诊断策略服务在处理诊断模块为 %6 (%5)、实例为 %2、原始活动 ID 为 %3 的方案 %1 时，遇到错误。错误代码为 %4。 |
The 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. |
| 0xB00000AA | 当诊断模块 %6 (%4)在处理方案 %1 中实例 %2 的原始活动 ID %3 时遇到错误。错误代码为 %5。 |
Diagnostic module %6 (%4) encountered an error while handling scenario %1, instance %2, original activity ID %3. The error code was %5. |
| 0xB00000AF | 方案 %1 中实例 %2 的原始活动 ID %3 被诊断模块 %6 (%4)丢弃。错误代码为 %5。 |
Scenario %1, instance %2, original activity ID %3 was dropped by diagnostic module %6 (%4). The error code was %5. |
| 0xB00000B4 | 诊断策略服务刚刷新了组策略。该事件便通知诊断模块有关组策略更改的信息。 |
The Diagnostic Policy Service just refreshed the Group Policy. This event notifies the diagnostic modules about the Group Policy changes. |
| 0xB00000B9 | 诊断模块 %2 (%1)被移入故障状态。错误代码为 %3。 |
Diagnostic module %2 (%1) was moved into a broken state. The error code was %3. |
| 0xB0001398 | 诊断策略服务刚刚执行了堆栈分配 |
The Diagnostic Policy Service just made a heap allocation |
| 0xB0001399 | 诊断策略服务刚刚释放了以前进行的堆栈分配 |
The Diagnostic Policy Service just freed a previously made heap allocation |
| 0xB1001398 | 诊断结构刚刚执行了堆栈分配 |
The Diagnostic Infrastructure just made a heap allocation |
| 0xB1001399 | 诊断结构刚刚释放以前进行的堆栈分配 |
The Diagnostic Infrastructure just freed a previously made heap allocation |