| Previous | Next |
| STATUS_GRAPHICS_NO_RECOMMENDED_FUNCTIONAL_VIDPN | STATUS_GRAPHICS_EMPTY_ADAPTER_MONITOR_MODE_SUPPORT_INTERSECTION |
STATUS_GRAPHICS_MODE_ID_MUST_BE_UNIQUE
Each mode in a mode set needs its own ID
A VidPN mode set identifies individual modes by mode IDs. This status means a new or updated mode reused an ID that another mode in the same set already uses. The timings or pixel formats may be different, but the identifier collision is enough to reject the set.
The issue often appears in synthesized virtual-display modes or in code that rebuilds a mode set after pruning. If mode IDs are assigned from array indexes, deleting or merging entries can accidentally reuse an old ID while another mode object is still present.
What to check
- Dump mode ID, resolution, refresh, scanline ordering, and pixel format for every member of the affected set.
- Assign IDs after final pruning or keep a monotonic allocator for the life of the mode set.
- Do not assume that identical timings make duplicate IDs safe; the interface requires unique identifiers.
References
- Microsoft: VidPN objects and interfaces
- Microsoft: Enumerating cofunctional VidPN source and target modes
- Microsoft: D3DKMDT display data types
Looking for a different code? Search another status or error code.