| Previous | Next |
| ERROR_GRAPHICS_CHAINLINKS_NOT_STARTED | ERROR_GRAPHICS_INCONSISTENT_DEVICE_LINK_STATE |
ERROR_GRAPHICS_CHAINLINKS_NOT_POWERED_ON
Interpret the result in its owning layer: graphics chainlinks not powered on
The useful interpretation of ERROR_GRAPHICS_CHAINLINKS_NOT_POWERED_ON (0xC0262435) starts at the linked boundary: the lead was powered while one or more chain members remained in a low-power state. In practical terms, inspect linked-adapter power ordering before changing application-wide graphics settings.
Capture before recreating objects
| Capture item | Why it matters |
|---|---|
| Object identity | linked-adapter power ordering |
| Rejected condition | the lead was powered while one or more chain members remained in a low-power state |
| What to capture | Dx power state per member, resume order, power IRPs and lead operation |
| Current graph state | lead adapter, chain members and their PnP/power transitions |
| Supporting trace | device-instance IDs, lead/chain role, PnP problem codes, Dx states and start/power IRP ordering |
Reproduce one variable at a time
- Resume the chain members first and repeat the lead power-up.
The comparison with ERROR_GRAPHICS_CHAINLINKS_NOT_STARTED is especially useful: ERROR_GRAPHICS_CHAINLINKS_NOT_STARTED concerns PnP start, not device power.
Recovery contract
Coordinate power transitions across the linked set and handle partial-resume rollback.
- debug-layer, ETW or driver diagnostics no longer report the rejected linked-adapter power ordering contract during the same scenario.
Technical references
- Microsoft: DirectX graphics kernel subsystem — background for the linked-adapter power ordering.
- Microsoft: WDDM architecture
- Microsoft: Display miniport driver requirements
- Microsoft: Graphics error codes
Looking for a different code? Search another status or error code.