| Previous | Next |
| ERROR_GRAPHICS_INVALID_COLORBASIS | ERROR_GRAPHICS_TARGET_NOT_IN_TOPOLOGY |
ERROR_GRAPHICS_INVALID_PIXELVALUEACCESSMODE
Why this is not a generic GPU failure: graphics invalid pixelvalueaccessmode
Windows reports ERROR_GRAPHICS_INVALID_PIXELVALUEACCESSMODE (0xC026233F) at the vidpn checkpoint. Here, the source mode requests a pixel-value access mode outside the accepted enum or path capability. That narrows the first investigation to source pixel access semantics instead of the entire GPU stack.
The smallest evidence set
| Capture item | Why it matters |
|---|---|
| Rejected condition | the source mode requests a pixel-value access mode outside the accepted enum or path capability |
| What to capture | access-mode enum, source mode type, format, driver-model version and private-format attributes |
| 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 pixel access semantics |
A/B test for the exact condition
- Use the access mode from a mode enumerated by the same driver and compare.
The comparison with ERROR_GRAPHICS_INCOMPATIBLE_PRIVATE_FORMAT is especially useful: ERROR_GRAPHICS_INCOMPATIBLE_PRIVATE_FORMAT reports a mismatch with the current primary private format.
Safe remediation
Preserve the complete enumerated source-mode structure instead of synthesizing one field.
- debug-layer, ETW or driver diagnostics no longer report the rejected source pixel access semantics contract during the same scenario.
Technical references
- Microsoft: Introduction to Video Present Networks — background for the source pixel access semantics.
- 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.