| Previous | Next |
| STATUS_MONITOR_UNKNOWN_DESCRIPTOR_FORMAT | STATUS_MONITOR_INVALID_STANDARD_TIMING_BLOCK |
STATUS_MONITOR_INVALID_DESCRIPTOR_CHECKSUM
Capability bytes failed integrity validation
STATUS_MONITOR_INVALID_DESCRIPTOR_CHECKSUM means that the descriptor was read but failed its integrity check. An EDID base or extension block is 128 bytes, and the checksum protects the block as a unit; a parser should not promote its timings, identity fields, or range data after that check fails.
This is not normally repaired by changing a Windows display setting. The failure can originate in monitor firmware, DDC/AUX transport, a cable or converter, a KVM, or a driver path that forwards corrupted bytes. A raw capture taken through more than one path is more useful than a screenshot of the selected resolution.
What to check
- Keep the exact 128-byte blocks and calculate the checksum per block, not over a concatenated capture.
- Compare direct and intermediary connection paths to localize where the bytes change.
- Do not edit a system-wide override until the bad block and the intended replacement are documented.
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.