| 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.
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.
The smallest evidence set
| Capture item | Why it matters for it |
|---|---|
| Decisive 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 boundary | the visible rectangle is inconsistent with the primary surface or selected mode |
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/B test for the exact condition
- Freeze the result generation. Record surface dimensions, visible-region dimensions, offsets, scaling and rotation. Before diagnosing this result, do not resize, hot-plug, recreate or release the object under examination.
- Run the narrow this result comparison. use a visible region fully contained in the primary surface and compare with the rejected region. 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_PRIMARYSURFACE_SIZE is especially useful: ERROR_GRAPHICS_INVALID_PRIMARYSURFACE_SIZE rejects the containing surface dimensions. Recording both names prevents a broad “graphics error” label from merging distinct ownership, capability and lifetime problems.
Safe remediation
Validate containment and transformation-adjusted dimensions before assigning the mode. 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 source-mode visible region 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 source-mode visible region 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.