| Previous | Next |
| ERROR_GRAPHICS_START_DEFERRED | EVT_WDSMCS_S_PARAMETERS_READ |
ERROR_GRAPHICS_DEPENDABLE_CHILD_STATUS
Locate the failing graphics boundary: graphics dependable child status
ERROR_GRAPHICS_DEPENDABLE_CHILD_STATUS (0x4026243C) belongs to the graphics info layer. It marks the driver marked its child presence result as reliable for the current detection cycle, rather than a generic rendering failure. The object that owns the decision is authoritative display-child presence report.
ERROR_GRAPHICS_DEPENDABLE_CHILD_STATUS: Informational graphics results are part of WDDM control flow. For ERROR_GRAPHICS_DEPENDABLE_CHILD_STATUS, They must not automatically be surfaced as a fatal application error or translated into an unrelated Win32 code. For ERROR_GRAPHICS_DEPENDABLE_CHILD_STATUS, the built-in one-line message identifies the immediate result; diagnosis also needs the producing API, object ownership and the display generation current at the time.
Evidence that makes this result actionable
| Capture item | Why it matters for ERROR_GRAPHICS_DEPENDABLE_CHILD_STATUS |
|---|---|
| Rejected boundary | the driver marked its child presence result as reliable for the current detection cycle |
| Decisive capture | child UID, detection mechanism, timestamp, connector state and whether the result came from interrupt or poll |
| Current graph state | WDDM kernel/miniport callback and the transient object state carried by that callback |
| Supporting trace | kernel graphics ETW, callback name, child or allocation identifiers, PnP state and the first returned NTSTATUS/HRESULT |
| Object identity | authoritative display-child presence report |
For ERROR_GRAPHICS_DEPENDABLE_CHILD_STATUS, preserve the unsigned HRESULT, symbolic name, first failing API and timestamp in one record. If cleanup later fails too, keep that secondary result separately from ERROR_GRAPHICS_DEPENDABLE_CHILD_STATUS.
A controlled comparison
- Freeze the
ERROR_GRAPHICS_DEPENDABLE_CHILD_STATUSgeneration. Record child UID, detection mechanism, timestamp, connector state and whether the result came from interrupt or poll. Before diagnosingERROR_GRAPHICS_DEPENDABLE_CHILD_STATUS, do not resize, hot-plug, recreate or release the object under examination. - Run the narrow
ERROR_GRAPHICS_DEPENDABLE_CHILD_STATUScomparison. compare one detection cycle with stable connector evidence against a deliberately indeterminate cycle. During theERROR_GRAPHICS_DEPENDABLE_CHILD_STATUScomparison, keep every driver, monitor, resource format and unrelated policy unchanged. - Observe the layer after
ERROR_GRAPHICS_DEPENDABLE_CHILD_STATUS. ForERROR_GRAPHICS_DEPENDABLE_CHILD_STATUS, if the exact check passes, record the next HRESULT or visible outcome. A different downstream result shows that theERROR_GRAPHICS_DEPENDABLE_CHILD_STATUSboundary was crossed. - Repeat
ERROR_GRAPHICS_DEPENDABLE_CHILD_STATUSthrough a lifecycle transition. ForERROR_GRAPHICS_DEPENDABLE_CHILD_STATUS, exercise one relevant resize, mode switch, device recreation, hot-plug or session change and confirm that this result does not reuse stale handles.
The comparison with ERROR_GRAPHICS_UNKNOWN_CHILD_STATUS is especially useful: ERROR_GRAPHICS_UNKNOWN_CHILD_STATUS says the current presence answer cannot be relied upon. For ERROR_GRAPHICS_DEPENDABLE_CHILD_STATUS, recording both names prevents a broad “graphics error” label from merging distinct ownership, capability and lifetime problems.
Correction and proof
Use the result to update topology while retaining normal hot-plug invalidation rules. Repair of ERROR_GRAPHICS_DEPENDABLE_CHILD_STATUS is complete only when the original call succeeds or returns its documented nonfatal status and the same lifetime test remains correct after a second display transition.
- The
ERROR_GRAPHICS_DEPENDABLE_CHILD_STATUStrace identifies one producing API and one current graphics object, rather than only the final UI symptom. - The passing run changes exactly the condition described for
ERROR_GRAPHICS_DEPENDABLE_CHILD_STATUS; unrelated adapter, monitor and application state remains unchanged. - For
ERROR_GRAPHICS_DEPENDABLE_CHILD_STATUS, debug-layer, ETW or driver diagnostics no longer report the rejected authoritative display-child presence report contract during the same scenario. - The application handles recurrence of
ERROR_GRAPHICS_DEPENDABLE_CHILD_STATUSwithout an unbounded retry loop, leaked resource, duplicate composition target or stale topology handle.
Implementation notes for ERROR_GRAPHICS_DEPENDABLE_CHILD_STATUS
For ERROR_GRAPHICS_DEPENDABLE_CHILD_STATUS, log kernel graphics ETW, callback name, child or allocation identifiers, PnP state and the first returned NTSTATUS/HRESULT. When the ERROR_GRAPHICS_DEPENDABLE_CHILD_STATUS path returns a count, size, status flag or replacement object, retain it even on a nonfatal result because it can direct the next call.
A production fallback for ERROR_GRAPHICS_DEPENDABLE_CHILD_STATUS should be explicit: pause rendering, re-enumerate, rebuild one cache entry, recreate a device, or decline a protected path only when this layer calls for that action. Reinstalling every display component, deleting all caches or forcing a resolution change is not an evidence-based fix for ERROR_GRAPHICS_DEPENDABLE_CHILD_STATUS.
Technical references
- Microsoft: Graphics error codes — background for the authoritative display-child presence report boundary involved in
ERROR_GRAPHICS_DEPENDABLE_CHILD_STATUS. - Microsoft: DirectX graphics kernel subsystem — background for the authoritative display-child presence report boundary involved in
ERROR_GRAPHICS_DEPENDABLE_CHILD_STATUS. - Microsoft: Introduction to VidPNs — background for the authoritative display-child presence report boundary involved in
ERROR_GRAPHICS_DEPENDABLE_CHILD_STATUS. - Microsoft: WDDM TDR overview — background for the authoritative display-child presence report boundary involved in
ERROR_GRAPHICS_DEPENDABLE_CHILD_STATUS.
Looking for a different code? Search another status or error code.
