| 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.
Evidence that makes the result actionable
| Capture item | Why it matters |
|---|---|
| Rejected condition | the selected algorithm for filtering source/target modes is not recognized |
| What to 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 |
A controlled comparison
- Use the documented default algorithm with the same monitor modes.
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.
Correction and proof
Validate the policy enum and leave driver-provided mode support data intact.
- debug-layer, ETW or driver diagnostics no longer report the rejected monitor mode-pruning policy contract during the same scenario.
Technical references
- Microsoft: Introduction to Video Present Networks — background for the monitor mode-pruning policy.
- 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.