What does HRESULT 0x4026200A (ERROR_GRAPHICS_PARTIAL_DATA_POPULATED) mean?

 
Previous Next
MQ_INFORMATION_OWNER_IGNORED ERROR_GRAPHICS_SKIP_ALLOCATION_PREPARATION

ERROR_GRAPHICS_PARTIAL_DATA_POPULATED

Why this is not a generic GPU failure: graphics partial data populated

ERROR_GRAPHICS_PARTIAL_DATA_POPULATED, value 0x4026200A, is produced by graphics info when the API filled only the portion that fit and returned the size needed for the complete dataset. The investigation should stay attached to variable-length graphics query buffer and to the exact generation in which it was obtained.

The smallest evidence set

Capture itemWhy it matters
Object identityvariable-length graphics query buffer
Rejected conditionthe API filled only the portion that fit and returned the size needed for the complete dataset
What to captureinput capacity, returned required count or byte size, structure version and whether topology changed between calls
Current graph stateWDDM kernel/miniport callback and the transient object state carried by that callback
Supporting tracekernel graphics ETW, callback name, child or allocation identifiers, PnP state and the first returned NTSTATUS/HRESULT

A/B test for the exact condition

  1. Perform the sizing call, allocate the reported capacity and repeat while holding the same query context.

The comparison with ERROR_GRAPHICS_PARAMETER_ARRAY_TOO_SMALL is especially useful: ERROR_GRAPHICS_PARAMETER_ARRAY_TOO_SMALL is a hard failure for a fixed caller array.

Safe remediation

Treat partial output as incomplete and retry with the reported size, allowing for one bounded topology-change retry.

  • debug-layer, ETW or driver diagnostics no longer report the rejected variable-length graphics query buffer contract during the same scenario.

Technical references


Looking for a different code? Search another status or error code.