| Previous | Next |
| ERROR_MONITOR_INVALID_DESCRIPTOR_CHECKSUM | ERROR_MONITOR_WMI_DATABLOCK_REGISTRATION_FAILED |
ERROR_MONITOR_INVALID_STANDARD_TIMING_BLOCK
ERROR_MONITOR_INVALID_STANDARD_TIMING_BLOCK concerns the EDID standard-timing area, not the detailed timing descriptors. The base EDID contains up to eight compact two-byte standard timing entries; each encodes horizontal addressable pixels, an aspect ratio, and a refresh rate.
Why it matters
The compact representation has strict limits. Under EDID 1.4, standard timings are not used for modes wider than 2288 pixels or with field refresh rates above 123 Hz; those modes must be represented with a detailed timing or another defined timing mechanism.
What to compare
- Inspect the standard-timing entries separately from the 18-byte detailed descriptors.
- Check whether the display's preferred mode is supplied as a valid detailed timing descriptor rather than inferred from a malformed compact entry.
- Compare a raw capture from the affected path with a known-good capture of the same monitor. Do not treat a GPU control-panel mode list as proof that the EDID bytes are valid.
VESA: standard timing encodings and their limits
Microsoft: monitor WMI classes derived from descriptor data
Looking for a different code? Search another status or error code.