| Previous | Next |
| ERROR_GRAPHICS_NO_DISPLAY_MODE_MANAGEMENT_SUPPORT | ERROR_GRAPHICS_CANT_ACCESS_ACTIVE_VIDPN |
ERROR_GRAPHICS_VIDPN_SOURCE_IN_USE
What Windows rejected: graphics vidpn source in use
ERROR_GRAPHICS_VIDPN_SOURCE_IN_USE, value 0xC0262342, is produced by vidpn when another display-mode-management client already owns the source. The investigation should stay attached to DMM client ownership of a VidPN source and to the exact generation in which it was obtained.
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.
Build a useful diagnostic record
| Capture item | Why it matters for it |
|---|---|
| Supporting trace | source and target IDs, topology generation, path descriptors, pinned modes, mode-set handles and monitor timing data |
| Object identity | DMM client ownership of a VidPN source |
| Rejected boundary | another display-mode-management client already owns the source |
| Decisive capture | source ID, owning DMM client, full-screen state, output mapping and acquisition/release timestamps |
| Current graph state | VidPN, topology, source and target mode sets, and the present path connecting them |
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.
Separate state from capability
- Freeze the result generation. Record source ID, owning DMM client, full-screen state, output mapping and acquisition/release timestamps. Before diagnosing this result, do not resize, hot-plug, recreate or release the object under examination.
- Run the narrow this result comparison. release the competing owner and retry without changing the topology. 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 DXGI_STATUS_GRAPHICS_VIDPN_SOURCE_IN_USE is especially useful: DXGI_STATUS_GRAPHICS_VIDPN_SOURCE_IN_USE is presentation feedback at the swap-chain layer. Recording both names prevents a broad “graphics error” label from merging distinct ownership, capability and lifetime problems.
Verify the repaired path
Serialize source ownership and release it on every transition and failure path. 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 DMM client ownership of a VidPN source 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 DMM client ownership of a VidPN source boundary involved in it.
- Microsoft: VidPN objects and interfaces — background for the DMM client ownership of a boundary involved in it.
- Microsoft: Enumerating cofunctional VidPN modes
- Microsoft: Determining VidPN support
Looking for a different code? Search another status or error code.