| Previous | Next |
| ERROR_GRAPHICS_SESSION_TYPE_CHANGE_IN_PROGRESS | ERROR_MONITOR_INVALID_STANDARD_TIMING_BLOCK |
ERROR_MONITOR_INVALID_DESCRIPTOR_CHECKSUM
ERROR_MONITOR_INVALID_DESCRIPTOR_CHECKSUM means that a monitor descriptor was read, but its integrity check failed. In an EDID base block, the sum of all 128 bytes modulo 256 must be zero; the final byte is selected to make that check succeed.
How to diagnose it correctly
- Capture the descriptor again after reconnecting the display. A transient read problem and a persistently bad EDID are different faults.
- Test the direct cable path separately from a KVM, dock, receiver, or protocol converter. An intermediate device can supply stale, truncated, or malformed EDID data.
- Validate every available 128-byte block, not only the first one. A valid base block does not make a bad extension block valid.
This is not a reason to invent a display mode from the corrupted bytes. First establish a stable descriptor source, then use a known-good capture or a vendor-supplied override when one is appropriate.
VESA: EDID extension flag and checksum rules
Linux kernel documentation: EDID forwarding and bogus data
Looking for a different code? Search another status or error code.