| 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.
Capture before recreating objects
| Capture item | Why it matters |
|---|---|
| What to 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 condition | the requested target ID is absent from every present path in the supplied topology |
Reproduce one variable at a time
- Capture the failing state. Record target ID, path enumeration, topology generation and monitor-child mapping.
- Add a path to the target in a disposable topology and repeat the operation.
The comparison with ERROR_GRAPHICS_SOURCE_NOT_IN_TOPOLOGY is especially useful: ERROR_GRAPHICS_SOURCE_NOT_IN_TOPOLOGY applies to the source endpoint.
Recovery contract
Derive target membership from current paths and reacquire after hot-plug.
- debug-layer, ETW or driver diagnostics no longer report the rejected VidPN target membership contract during the same scenario.
Implementation notes
Log source and target IDs, topology generation, path descriptors, pinned modes, mode-set handles and monitor timing data.
A production fallback 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.
Technical references
- Microsoft: Introduction to Video Present Networks — background for the VidPN target membership.
- 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.