| Previous | Next |
| PDC_LOCK_WATCHDOG_LIVEDUMP | WVR_LIVEDUMP_REPLICATION_IOCONTEXT_TIMEOUT |
PDC_UNEXPECTED_REVOCATION_LIVEDUMP
Power Dependency Coordinator revocation live dump for PDC_UNEXPECTED_REVOCATION_LIVEDUMP
PDC_UNEXPECTED_REVOCATION_LIVEDUMP is bug check code 0x0000017D. PDC relates to Modern Standby and power dependency coordination. This live dump records a situation where an expected power dependency or activator state was revoked in an unexpected order.
How to read it in a dump
- Interpret it together with Modern Standby, power framework, device power, and platform-residency events.
- The requester, activator, and device stack that owned the dependency are the key evidence.
- A live dump can record a power-state contract problem without proving a hard system crash.
What to check
- Collect SleepStudy, power framework logs, device power logs, and the live dump.
- Check firmware, chipset, ACPI, and device driver updates on Modern Standby systems.
- Look for a driver or service that holds or drops a power dependency at the wrong time.
References
- Modern Standby platform model
- Crash dump files and live dump context
- Microsoft Bug Check Code Reference
- Analyze a kernel-mode dump with WinDbg
Dump evidence
Preserve the complete dump, the four bug-check parameters, the exact Windows build, loaded-module list, and the event timeline immediately before the stop. AllStat summarizes the condition as “this result”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.
Analysis order
- Run WinDbg
!analyze -v, then inspect the documented meaning of each parameter instead of relying only on the probably-caused-by line. - find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with pdc / unexpected / revocation / livedump.
- keep third-party filter, security, storage, graphics, and virtualization drivers in the module inventory; removing evidence before dump analysis can obscure the responsible path.
Do not repeatedly reboot a machine affected by this result before collecting the dump and event logs. Recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.
Looking for a different code? Search another status or error code.