What does HRESULT 0x4026243A (ERROR_GRAPHICS_START_DEFERRED) mean?

 
Previous Next
ERROR_GRAPHICS_POLLING_TOO_FREQUENTLY ERROR_GRAPHICS_DEPENDABLE_CHILD_STATUS

ERROR_GRAPHICS_START_DEFERRED

Why this is not a generic GPU failure: graphics start deferred

Windows reports ERROR_GRAPHICS_START_DEFERRED (0x4026243A) at the graphics info checkpoint. Here, adapter start was postponed because a prerequisite state transition had not completed. That narrows the first investigation to display-adapter PnP start scheduling instead of the entire GPU stack.

The smallest evidence set

Capture itemWhy it matters
Object identitydisplay-adapter PnP start scheduling
Rejected conditionadapter start was postponed because a prerequisite state transition had not completed
What to capturedevice instance, PnP problem code, parent and dependency states, power transition and start-attempt order
Current graph stateWDDM kernel/miniport callback and the transient object state carried by that callback
Supporting tracekernel graphics ETW, callback name, child or allocation identifiers, PnP state and the first returned NTSTATUS/HRESULT

A/B test for the exact condition

  1. Capture the failing state. Record device instance, PnP problem code, parent and dependency states, power transition and start-attempt order.
  2. Observe a normal boot/start trace and compare with the sequence that triggers deferral.

The comparison with ERROR_GRAPHICS_LEADLINK_START_DEFERRED is especially useful: ERROR_GRAPHICS_LEADLINK_START_DEFERRED is specific to the lead member of a linked-adapter chain.

Safe remediation

Let the prerequisite transition complete and remove ordering defects in the driver or device stack.

  • debug-layer, ETW or driver diagnostics no longer report the rejected display-adapter PnP start scheduling contract during the same scenario.

Implementation notes

Technical references


Looking for a different code? Search another status or error code.