Audio drivers have long been measured using hangs and crashes in the Windows Audio service (audiosrv) https://docs.microsoft.com/en-us/windows-hardware/drivers/dashboard/audio-measures
The Windows audio team has found a bug in the measure which causes it to ignore the Audio Device Graph Isolation Process (audiodg.exe), which is where custom audio processing is done using driver-provided Audio Processing Objects (APOs.)
We have created a new version of the measure https://docs.microsoft.com/en-us/windows-hardware/drivers/dashboard/percent-machines-with-at-least-one-audio-crash which includes crashes and hangs both in audiosrv and in audiodg.exe. It is currently being evaluated and will be used to make accept/reject decisions starting October 15th 2019.
If your audio driver fails this measure, please work with your audio IHV to get a fix for the crash in question.
Updated Sep 23, 2019
Version 1.0kevintremblay
Microsoft
Joined March 12, 2019
Hardware Dev Center
Follow this blog board to get notified when there's new activity