| 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 診斷基礎結構解決方案主機可以對診斷原則服務偵測到的系統問題啟用互動式解決方案。必要時，便會由適當使用者工作階段中的診斷原則服務觸發。如果診斷原則服務並未執行，將不會執行該工作 |
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，原始活動識別碼 %3 發生問題。 |
Diagnostic module %5 (%4) detected a problem for scenario %1, instance %2, original activity ID %3. |
| 0xB0000069 | 診斷模組 %5 (%4) 開始疑難排解狀況 %1，例項 %2，原始活動識別碼 %3。 |
Diagnostic module %5 (%4) started troubleshooting scenario %1, instance %2, original activity ID %3. |
| 0xB000006E | 診斷模組 %5 (%4) 完成疑難排解狀況 %1，例項 %2，原始活動識別碼 %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，原始活動識別碼 %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，原始活動識別碼 %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，原始活動識別碼 %3。 |
Diagnostic module %5 (%4) started resolving scenario %1, instance %2, original activity ID %3. |
| 0xB000007E | 對於狀況 %1，例項 %2，原始活動識別碼 %3，診斷模組 %5 (%4) 已進入佇列稍後啟動。 |
Diagnostic module %5 (%4) was queued to start later for scenario %1, instance %2, original activity ID %3. |
| 0xB0000082 | 診斷模組 %5 (%4) 完成解決狀況 %1，例項 %2，原始活動識別碼 %3。 |
Diagnostic module %5 (%4) finished resolving scenario %1, instance %2, original activity ID %3. |
| 0xB0000087 | 診斷原則服務無法針對診斷模組 %6 (%5) 建立診斷模組主機例項。錯誤碼是 %4。將會丟棄狀況 %1，例項 %2，原始活動識別碼 %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) 處理狀況 %1，例項 %2，原始活動識別碼 %3 時發生錯誤。錯誤碼是 %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，原始活動識別碼 %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 | 診斷模組 %6 (%4) 丟棄狀況 %1，例項 %2，原始活動識別碼 %3。錯誤碼是 %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 |