| Previous | Next |
| STATUS_MONITOR_INVALID_USER_FRIENDLY_MONDSC_BLOCK | STATUS_MONITOR_INVALID_DETAILED_TIMING_BLOCK |
STATUS_MONITOR_NO_MORE_DESCRIPTOR_DATA
The request crossed the end of the descriptor data
STATUS_MONITOR_NO_MORE_DESCRIPTOR_DATA is a bounds condition. The caller requested a descriptor region identified by an offset and size, but the monitor data available to the component does not cover that region. It is different from a malformed timing block because the operation can fail before a field is parsed.
Hot-plug and descriptor replacement make stale offsets especially dangerous. A caller that cached the size of an earlier monitor, extension chain, or descriptor set can address beyond the data associated with the current target. Re-query the current object instead of clipping the request or padding missing bytes.
What to check
- Log the requested offset, size, descriptor length, block count, and target identity.
- Re-enumerate after a hot-plug, dock reconnect, monitor power cycle, or topology change.
- Treat a short read as missing data; do not parse zero-filled or copied bytes as a real descriptor.
References
- Microsoft: WmiMonitorRawEEdidV1Block
- VESA Enhanced EDID Standard, Release A2
- Linux kernel: EDID troubleshooting and overrides
Looking for a different code? Search another status or error code.