| Previous | Next |
| ERROR_GRAPHICS_ADAPTER_CHAIN_NOT_READY | ERROR_GRAPHICS_CHAINLINKS_NOT_POWERED_ON |
ERROR_GRAPHICS_CHAINLINKS_NOT_STARTED
Interpret the result in its owning layer: graphics chainlinks not started
ERROR_GRAPHICS_CHAINLINKS_NOT_STARTED (0xC0262434) belongs to the linked layer. It marks the lead start was attempted before all chain members reached started state, rather than a generic rendering failure. The object that owns the decision is linked-adapter start ordering.
Capture before recreating objects
| Capture item | Why it matters |
|---|---|
| Supporting trace | device-instance IDs, lead/chain role, PnP problem codes, Dx states and start/power IRP ordering |
| Object identity | linked-adapter start ordering |
| Rejected condition | the lead start was attempted before all chain members reached started state |
| What to capture | start IRP order, member states, timestamps and lead-start request |
| Current graph state | lead adapter, chain members and their PnP/power transitions |
Reproduce one variable at a time
- Wait for every chain member to start and then repeat the lead start.
The comparison with ERROR_GRAPHICS_ADAPTER_CHAIN_NOT_READY is especially useful: ERROR_GRAPHICS_ADAPTER_CHAIN_NOT_READY can indicate an unknown failure after enumeration.
Recovery contract
Enforce chain-before-lead startup ordering in the driver stack.
- debug-layer, ETW or driver diagnostics no longer report the rejected linked-adapter start ordering contract during the same scenario.
Technical references
- Microsoft: DirectX graphics kernel subsystem — background for the linked-adapter start ordering.
- Microsoft: WDDM architecture
- Microsoft: Display miniport driver requirements
- Microsoft: Graphics error codes
Looking for a different code? Search another status or error code.