DXGKDDI_SYSTEM_DISPLAY_WRITE - NtDoc
Native API online documentation, based on the System Informer
(formerly Process Hacker) phnt
headers
// dispmprt.h
DXGKDDI_SYSTEM_DISPLAY_WRITE DxgkddiSystemDisplayWrite;
VOID DxgkddiSystemDisplayWrite(
[in] PVOID MiniportDeviceContext,
[in] PVOID Source,
[in] UINT SourceWidth,
[in] UINT SourceHeight,
[in] UINT SourceStride,
[in] UINT PositionX,
[in] UINT PositionY
)
{...}
View the official Windows Driver Kit DDI referenceNo description available.
Called by the operating system to request the display miniport driver to write an image block to the display device.
Starting with Windows 8, the operating system calls this function during a bugcheck operation following a system stop error. The operating system calls this function only if the display device was previously reset through a call to DxgkDdiSystemDisplayEnable.
MiniportDeviceContext [in]A handle to a context block that is associated with a display adapter. The display miniport driver's DxgkDdiAddDevice function previously provided this handle to the Microsoft DirectX graphics kernel subsystem.
Source [in]A pointer to the start address of the source image to be written to the bugcheck screen that displays information about the system stop error.
SourceWidth [in]A UINT value that specifies the width, in units of pixels, of the specified source image.
SourceHeight [in]A UINT value that specifies the height, in units of pixels, of the specified source image.
SourceStride [in]A UINT value that specifies the number of bytes for each line of the specified source image.
PositionX [in]A UINT value that specifies the starting X coordinate that the specified source image should be written to on the display device.
PositionY [in]A UINT value that specifies the starting Y coordinate that the specified source image should be written to on the display device.
The display miniport driver must follow these guidelines when its DxgkDdiSystemDisplayWrite function is called:
The display miniport driver should use the CPU to write the image block to the frame buffer. When the system encounters a stop error, it may have been caused by a continuous timeout detection and recovery (TDR) on the display device. In that case, the graphics processing unit (GPU) might be in an unknown state.
For more information about TDR, see Timeout Detection and Recovery (TDR).
Windows kernel-mode functions might not be available while this function is being called.
DxgkDdiSystemDisplayWrite can be called at any IRQL, so it must be in nonpageable memory. DxgkDdiSystemDisplayWrite must not call any code that is in pageable memory and must not manipulate any data that is in pageable memory.
DxgkCbAcquirePostDisplayOwnership
DxgkDdiStopDeviceAndReleasePostDisplayOwnership