| Previous | Next |
| ERROR_GRAPHICS_INVALID_PRIMARYSURFACE_SIZE | ERROR_GRAPHICS_INVALID_STRIDE |
ERROR_GRAPHICS_INVALID_VISIBLEREGION_SIZE
Why this is not a generic GPU failure: graphics invalid visibleregion size
Windows reports ERROR_GRAPHICS_INVALID_VISIBLEREGION_SIZE (0xC026233B) at the vidpn checkpoint. Here, the visible rectangle is inconsistent with the primary surface or selected mode. That narrows the first investigation to source-mode visible region instead of the entire GPU stack.
The smallest evidence set
| Capture item | Why it matters |
|---|---|
| What to capture | surface dimensions, visible-region dimensions, offsets, scaling and rotation |
| 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 | source-mode visible region |
| Rejected condition | the visible rectangle is inconsistent with the primary surface or selected mode |
A/B test for the exact condition
- Use a visible region fully contained in the primary surface and compare with the rejected region.
The comparison with ERROR_GRAPHICS_INVALID_PRIMARYSURFACE_SIZE is especially useful: ERROR_GRAPHICS_INVALID_PRIMARYSURFACE_SIZE rejects the containing surface dimensions.
Safe remediation
Validate containment and transformation-adjusted dimensions before assigning the mode.
- debug-layer, ETW or driver diagnostics no longer report the rejected source-mode visible region contract during the same scenario.
Technical references
- Microsoft: Introduction to Video Present Networks — background for the source-mode visible region.
- 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.