| Previous | Next |
| ERROR_MONITOR_INVALID_USER_FRIENDLY_MONDSC_BLOCK | ERROR_MONITOR_INVALID_DETAILED_TIMING_BLOCK |
ERROR_MONITOR_NO_MORE_DESCRIPTOR_DATA
ERROR_MONITOR_NO_MORE_DESCRIPTOR_DATA means that a request for a descriptor range ran past the data that is available. It is a bounds condition, not proof that the bytes already returned are corrupt or that their format is unsupported.
Why fixed offsets are unsafe
An EDID base block is 128 bytes. Its extension flag identifies how many extension blocks follow the base block; a caller that assumes a block exists at a fixed offset can therefore request data that the monitor did not advertise.
How to narrow it down
- Record the requested offset and size together with the actual block identity and type.
- Read the base block first, honor its extension count, then fetch only available extension blocks.
- Differentiate this from
ERROR_MONITOR_NO_DESCRIPTOR, where no usable block was obtained, and from a checksum error, where a block exists but fails validation.
VESA: base-block extension flag and 128-byte checksum layout
Microsoft: raw E-EDID blocks, IDs, and types
Looking for a different code? Search another status or error code.