This post has been republished via RSS; it originally appeared at: Hardware Dev Center articles.
Display drivers have long been measured using ecosystem versions that measure crashes and hangs in games for the driver version being flighted (https://docs.microsoft.com/en-us/windows-hardware/drivers/dashboard/graphics-measures)
The Windows graphics team has developed three new measures, two that look at crashes and hangs in different applications on the devices receiving the driver through the current submission, and one that looks at driver rollbacks.
The first one, https://docs.microsoft.com/windows-hardware/drivers/dashboard/graphics-user-mode-crashes-edge-chromium-standard (and the ecosystem version https://docs.microsoft.com/windows-hardware/drivers/dashboard/graphics-user-mode-crashes-edge-chromium-ecosystem) look at how often Microsoft Edge Chromium crashes due to the graphics driver.
The second one, https://docs.microsoft.com/windows-hardware/drivers/dashboard/graphics-user-mode-crashes-collaboration-standard (and the ecosystem version https://docs.microsoft.com/windows-hardware/drivers/dashboard/graphics-user-mode-crashes-collaboration-ecosystem) looks at number of crashes in Display Drivers that happen in the context of the Communication and Collaboration Applications.
The last one, https://docs.microsoft.com/windows-hardware/drivers/dashboard/myriad-drivers-rolled-back-standard (and the ecosystem version at https://docs.microsoft.com/windows-hardware/drivers/dashboard/myriad-drivers-rolled-back-ecosystem), looks at whether a driver is rolled back or succeeded by another driver install (not initiated by WU) within 2 days of the installation. Such actions signal that user is having problems with a driver severe enough that they need to use a different driver.
These measures are currently being evaluated and will be used to make accept/reject decisions starting June 29, 2020.
If your display driver fails one of these measures, please work with your IHV to get a fix for the crash in question.