| Previous | Next |
| ERROR_GRAPHICS_INVALID_PIXELVALUEACCESSMODE | ERROR_GRAPHICS_NO_DISPLAY_MODE_MANAGEMENT_SUPPORT |
ERROR_GRAPHICS_TARGET_NOT_IN_TOPOLOGY
Interpret the result in its owning layer: graphics target not in topology
ERROR_GRAPHICS_TARGET_NOT_IN_TOPOLOGY (0xC0262340) belongs to the vidpn layer. It marks the requested target ID is absent from every present path in the supplied topology, rather than a generic rendering failure. The object that owns the decision is VidPN target membership.
Prove target membership from paths
A connected monitor or enumerated target does not automatically belong to every VidPN. Walk the candidate topology and match VidPnTargetId in each D3DKMDT_VIDPN_PRESENT_PATH. Capture the monitor child UID separately so a physical hot-plug event is not confused with logical topology membership. The controlled fix is to construct or select a path that references the target within the same candidate VidPN.
This result: VidPN handles and subobjects are generation-bound. A monitor hot-plug, docking action, session switch or mode commit can invalidate an otherwise well-formed cached object. 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.
Capture before recreating objects
| Capture item | Why it matters for it |
|---|---|
| Decisive capture | target ID, path enumeration, topology generation and monitor-child mapping |
| Current graph state | VidPN, topology, source and target mode sets, and the present path connecting them |
| Supporting trace | source and target IDs, topology generation, path descriptors, pinned modes, mode-set handles and monitor timing data |
| Object identity | VidPN target membership |
| Rejected boundary | the requested target ID is absent from every present path in the supplied topology |
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 this result.
Reproduce one variable at a time
- Freeze the result generation. Record target ID, path enumeration, topology generation and monitor-child mapping. Before diagnosing this result, do not resize, hot-plug, recreate or release the object under examination.
- Run the narrow this result comparison. add a path to the target in a disposable topology and repeat the operation. During the result comparison, keep every driver, monitor, resource format and unrelated policy unchanged.
- Observe the layer after it. for it, if the exact check passes, record the next HRESULT or visible outcome. A different downstream result shows that the boundary was crossed.
- Repeat it through a lifecycle transition. for it, exercise one relevant resize, mode switch, device recreation, hot-plug or session change and confirm that it does not reuse stale handles.
The comparison with ERROR_GRAPHICS_SOURCE_NOT_IN_TOPOLOGY is especially useful: ERROR_GRAPHICS_SOURCE_NOT_IN_TOPOLOGY applies to the source endpoint. Recording both names prevents a broad “graphics error” label from merging distinct ownership, capability and lifetime problems.
Recovery contract
Derive target membership from current paths and reacquire after hot-plug. Repair of it 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 result trace 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 it; unrelated adapter, monitor and application state remains unchanged.
- debug-layer, ETW or driver diagnostics no longer report the rejected VidPN target membership contract during the same scenario.
- The application handles recurrence of it without an unbounded retry loop, leaked resource, duplicate composition target or stale topology handle.
Implementation notes
Log source and target IDs, topology generation, path descriptors, pinned modes, mode-set handles and monitor timing data. When the 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 it 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 it.
Technical references
- Microsoft: Introduction to Video Present Networks — background for the VidPN target membership boundary involved in it.
- Microsoft: VidPN objects and interfaces
- Microsoft: Enumerating cofunctional VidPN modes
- Microsoft: Determining VidPN support
Looking for a different code? Search another status or error code.