| Previous | Next |
| ERROR_MONITOR_NO_MORE_DESCRIPTOR_DATA | ERROR_MONITOR_INVALID_MANUFACTURE_DATE |
ERROR_MONITOR_INVALID_DETAILED_TIMING_BLOCK
ERROR_MONITOR_INVALID_DETAILED_TIMING_BLOCK concerns an 18-byte detailed timing descriptor (DTD). A DTD describes a mode with a pixel clock, active and blanking dimensions, sync offsets and pulse widths, image size, and signal flags. It is more precise than an EDID standard-timing entry.
Important validation rules
- A detailed timing descriptor cannot use a zero pixel clock; that value is reserved for a non-timing display descriptor.
- The timing must represent a mode the display supports. In EDID 1.4, the first 18-byte descriptor identifies the preferred timing mode.
- Detailed timings must precede other display-descriptor types in the four descriptor slots.
Inspect the raw 18 bytes before changing resolution settings. A malformed DTD can cause a wrong preferred mode or an incomplete mode list even when standard timing entries appear plausible.
VESA: 18-byte descriptors and detailed timing definition
Linux kernel documentation: EDID timing value representation
Looking for a different code? Search another status or error code.