| Previous | Next |
| ERROR_GRAPHICS_INCOMPATIBLE_PRIVATE_FORMAT | ERROR_GRAPHICS_INVALID_MONITOR_CAPABILITY_ORIGIN |
ERROR_GRAPHICS_INVALID_MODE_PRUNING_ALGORITHM
Locate the failing graphics boundary: graphics invalid mode pruning algorithm
Windows reports ERROR_GRAPHICS_INVALID_MODE_PRUNING_ALGORITHM (0xC0262356) at the vidpn checkpoint. Here, the selected algorithm for filtering source/target modes is not recognized. That narrows the first investigation to monitor mode-pruning policy instead of the entire GPU stack.
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.
Evidence that makes the result actionable
| Capture item | Why it matters for it |
|---|---|
| Rejected boundary | the selected algorithm for filtering source/target modes is not recognized |
| Decisive capture | algorithm enum, monitor descriptor origin, target ID and pruning callback |
| 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 | monitor mode-pruning policy |
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.
A controlled comparison
- Freeze the result generation. Record algorithm enum, monitor descriptor origin, target ID and pruning callback. Before diagnosing this result, do not resize, hot-plug, recreate or release the object under examination.
- Run the narrow it comparison. use the documented default algorithm with the same monitor modes. 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_INVALID_MONITOR_CAPABILITY_ORIGIN is especially useful: ERROR_GRAPHICS_INVALID_MONITOR_CAPABILITY_ORIGIN rejects the provenance field for monitor capability data. Recording both names prevents a broad “graphics error” label from merging distinct ownership, capability and lifetime problems.
Correction and proof
Validate the policy enum and leave driver-provided mode support data intact. 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 monitor mode-pruning policy 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 monitor mode-pruning policy 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.