| UID | title | ms.date | targetos | description | tech.root | req.construct-type | req.ddi-compliance | req.dll | req.header | req.include-header | req.kmdf-ver | req.lib | req.max-support | req.redist | req.target-min-winverclnt | req.target-min-winversvr | req.target-type | req.typenames | req.umdf-ver | req.unicode-ansi | topic_type | api_type | api_location | api_name | f1_keywords | dev_langs | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
NS:dispmprt._DXGK_DIAG_SCANOUT_BUFFER_CONTENT |
DXGK_DIAG_SCANOUT_BUFFER_CONTENT |
03/24/2020 |
Windows |
The DXGK_DIAG_SCANOUT_BUFFER_CONTENT structure provides information about the current buffer being scanned out during diagnostic data collection. |
display |
structure |
dispmprt.h |
Windows 10, version 2004 |
DXGK_DIAG_SCANOUT_BUFFER_CONTENT |
|
|
|
|
|
|
The DXGK_DIAG_SCANOUT_BUFFER_CONTENT structure provides information about the current buffer being scanned out during diagnostic data collection.
A DXGK_DIAG_DISPLAY_SCANOUT_BUFFER_CRC value.
A DXGK_DIAG_DISPLAY_SCANOUT_BUFFER_HISTOGRAM structure.
The DXGK_DIAG_SCANOUT_BUFFER_CONTENT structure is a member of the DXGK_DISPLAYSTATE_INTRUSIVE structure, which is passed in calls to DxgkDdiGetDisplayStateIntrusive during diagnostic data collection.
Drivers should use either ScanoutBufferCrc or ScanoutBufferHistogram, or both ScanoutBufferCrc and ScanoutBufferHistogram, to report to the operating system about the content of the current buffer being scanned out.
DXGK_DIAG_DISPLAY_SCANOUT_BUFFER_CRC
DXGK_DIAG_DISPLAY_SCANOUT_BUFFER_HISTOGRAM