| Previous | Next |
| ERROR_GRAPHICS_UNASSIGNED_MODESET_ALREADY_EXISTS | ERROR_GRAPHICS_TOPOLOGY_CHANGES_NOT_ALLOWED |
ERROR_GRAPHICS_INVALID_SCANLINE_ORDERING
What Windows rejected: graphics invalid scanline ordering
Windows reports ERROR_GRAPHICS_INVALID_SCANLINE_ORDERING (0xC0262352) at the vidpn checkpoint. Here, the target mode uses an invalid progressive/interlaced ordering value. That narrows the first investigation to target signal scanline order instead of the entire GPU stack.
Validate the target signal, not the render surface
Scanline ordering belongs to the target timing and distinguishes progressive from interlaced signal forms. Preserve the complete target mode, including refresh numerator and denominator, total size and active size. Compare with a mode enumerated by the monitor/driver rather than synthesizing the enum alone. Changing the render-target format or swap-chain buffer cannot correct an invalid target signal ordering.
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.
Build a useful diagnostic record
| Capture item | Why it matters for it |
|---|---|
| Decisive capture | scanline-order enum, refresh numerator/denominator, target timing and monitor capabilities |
| 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 | target signal scanline order |
| Rejected boundary | the target mode uses an invalid progressive/interlaced ordering value |
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.
Separate state from capability
- Freeze the result generation. Record scanline-order enum, refresh numerator/denominator, target timing and monitor capabilities. Before diagnosing this result, do not resize, hot-plug, recreate or release the object under examination.
- Run the narrow this result comparison. select a timing enumerated from the target mode set. 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_FREQUENCYRANGE_CONSTRAINT is especially useful: ERROR_GRAPHICS_INVALID_MONITOR_FREQUENCYRANGE_CONSTRAINT concerns timing-range constraints. Recording both names prevents a broad “graphics error” label from merging distinct ownership, capability and lifetime problems.
Verify the repaired path
Preserve scanline ordering from validated monitor or driver timing data. 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 target signal scanline order 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 target signal scanline order 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.