| UID | title | description | old-location | ms.date | keywords | ms.keywords | req.header | req.include-header | req.target-type | req.target-min-winverclnt | req.target-min-winversvr | req.kmdf-ver | req.umdf-ver | req.ddi-compliance | req.unicode-ansi | req.idl | req.max-support | req.namespace | req.assembly | req.type-library | req.lib | req.dll | req.irql | targetos | tech.root | req.typenames | f1_keywords | topic_type | api_type | api_location | api_name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
NE:d3dkmddi._DXGK_GLITCH_CAUSE |
DXGK_GLITCH_CAUSE (d3dkmddi.h) |
Enumeration that describes what caused a glitch during a SetTimingsFromVidPn call. |
display\dxgk_glitch_cause.htm |
08/25/2022 |
|
DXGK_GLITCH_CAUSE, DXGK_GLITCH_CAUSE enumeration [Display Devices], DXGK_GLITCH_CAUSE_DRIVER_ERROR, DXGK_GLITCH_CAUSE_ENCODER_RECONFIG, DXGK_GLITCH_CAUSE_MEMORY_TIMING, DXGK_GLITCH_CAUSE_METADATA_CHANGE, DXGK_GLITCH_CAUSE_MODIFIED_WIRE_USAGE, DXGK_GLITCH_CAUSE_NONE, DXGK_GLITCH_CAUSE_PIPELINE_CHANGE, DXGK_GLITCH_CAUSE_TIMING_CHANGE, _DXGK_GLITCH_CAUSE, d3dkmddi/DXGK_GLITCH_CAUSE, d3dkmddi/DXGK_GLITCH_CAUSE_DRIVER_ERROR, d3dkmddi/DXGK_GLITCH_CAUSE_ENCODER_RECONFIG, d3dkmddi/DXGK_GLITCH_CAUSE_MEMORY_TIMING, d3dkmddi/DXGK_GLITCH_CAUSE_METADATA_CHANGE, d3dkmddi/DXGK_GLITCH_CAUSE_MODIFIED_WIRE_USAGE, d3dkmddi/DXGK_GLITCH_CAUSE_NONE, d3dkmddi/DXGK_GLITCH_CAUSE_PIPELINE_CHANGE, d3dkmddi/DXGK_GLITCH_CAUSE_TIMING_CHANGE, display.dxgk_glitch_cause |
d3dkmddi.h |
Windows |
Windows |
display |
DXGK_GLITCH_CAUSE |
|
|
|
|
|
Enumeration that describes what caused a glitch during a SetTimingsFromVidPn call.
Indicates that an internal driver error caused a glitch.
Indicates that the timing requested necessitated a glitch. This cause should only be used if the OS requested a change which would always result in a glitch rather than something which could have been avoided under other circumstances.
For example, this should not be used if the driver switches to a different display pipe to support an additional path, but it should be used if the OS requests a different timing to the previous one.
Indicates that reconfiguring the display pipeline caused a glitch.
Indicates that changing graphics memory timings caused a glitch.
Indicates that changing the configuration of the encoder for a target caused a glitch.
Indicates that modifying the format of pixel data in the transport stream caused a glitch.
Indicates that changing the frame metadata caused a glitch.
Indicates that there was no glitch.