| Previous | Next |
| BUGCODE_NETADAPTER_DRIVER | TTM_WATCHDOG_TIMEOUT |
PDC_PRIVILEGE_CHECK_LIVEDUMP
Power Dependency Coordinator privilege-check live dump for PDC_PRIVILEGE_CHECK_LIVEDUMP
PDC_PRIVILEGE_CHECK_LIVEDUMP is bug check code 0x0000019F. This PDC live dump points at a privilege or authorization check in the power-dependency coordination path. It should be analyzed with Modern Standby and power-management state rather than as a normal access-denied application error.
How to read it in a dump for PDC_PRIVILEGE_CHECK_LIVEDUMP
- Identify the caller that requested or modified power dependency state.
- Check token, service, and device context if privilege information is present.
- Modern Standby and PDC event logs help explain why the check mattered.
What to check for PDC_PRIVILEGE_CHECK_LIVEDUMP
- Collect SleepStudy, power framework events, and the live dump.
- Review recent driver, service, and power-policy changes.
- Look for components attempting privileged power operations from the wrong context.
References for PDC_PRIVILEGE_CHECK_LIVEDUMP
- 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 for PDC_PRIVILEGE_CHECK_LIVEDUMP
For PDC_PRIVILEGE_CHECK_LIVEDUMP, 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 “PDC_PRIVILEGE_CHECK_LIVEDUMP”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.
Analysis order for PDC_PRIVILEGE_CHECK_LIVEDUMP
- Run WinDbg
!analyze -v, then inspect the documented meaning of each PDC_PRIVILEGE_CHECK_LIVEDUMP parameter instead of relying only on the probably-caused-by line. - For PDC_PRIVILEGE_CHECK_LIVEDUMP, find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with pdc / privilege / check / livedump.
- For PDC_PRIVILEGE_CHECK_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 PDC_PRIVILEGE_CHECK_LIVEDUMP before collecting the dump and event logs. For PDC_PRIVILEGE_CHECK_LIVEDUMP, recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.
Dump evidence for PDC_PRIVILEGE_CHECK_LIVEDUMP
For PDC_PRIVILEGE_CHECK_LIVEDUMP, 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 “PDC_PRIVILEGE_CHECK_LIVEDUMP”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.
Analysis order for PDC_PRIVILEGE_CHECK_LIVEDUMP
- Run WinDbg
!analyze -v, then inspect the documented meaning of each PDC_PRIVILEGE_CHECK_LIVEDUMP parameter instead of relying only on the probably-caused-by line. - For PDC_PRIVILEGE_CHECK_LIVEDUMP, find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with pdc / privilege / check / livedump.
- For PDC_PRIVILEGE_CHECK_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 PDC_PRIVILEGE_CHECK_LIVEDUMP before collecting the dump and event logs. For PDC_PRIVILEGE_CHECK_LIVEDUMP, 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.