Home
%3CLINGO-SUB%20id%3D%22lingo-sub-871195%22%20slang%3D%22en-US%22%3EDriver%20shiproom%20measure%20for%20crashes%20in%20the%20audio%20service%2C%20including%20the%20Audio%20Device%20Graph%20Isolation%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-871195%22%20slang%3D%22en-US%22%3E%3CP%3EAudio%20drivers%20have%20long%20been%20measured%20using%20hangs%20and%20crashes%20in%20the%20Windows%20Audio%20service%20(audiosrv)%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-hardware%2Fdrivers%2Fdashboard%2Faudio-measures%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-hardware%2Fdrivers%2Fdashboard%2Faudio-measures%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3EThe%20Windows%20audio%20team%20has%20found%20a%20bug%20in%20the%20measure%20which%20causes%20it%20to%20ignore%20the%20Audio%20Device%20Graph%20Isolation%20Process%20(audiodg.exe)%2C%20which%20is%20where%20custom%20audio%20processing%20is%20done%20using%20driver-provided%20Audio%20Processing%20Objects%20(APOs.)%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3EWe%20have%20created%20a%20new%20version%20of%20the%20measure%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-hardware%2Fdrivers%2Fdashboard%2Fpercent-machines-with-at-least-one-audio-crash%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-hardware%2Fdrivers%2Fdashboard%2Fpercent-machines-with-at-least-one-audio-crash%3C%2FA%3E%20which%20includes%20crashes%20and%20hangs%20both%20in%20audiosrv%20and%20in%20audiodg.exe.%20It%20is%20currently%20being%20evaluated%20and%20will%20be%20used%20to%20make%20accept%2Freject%20decisions%20starting%20October%2015th%202019.%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3EIf%20your%20audio%20driver%20fails%20this%20measure%2C%20please%20work%20with%20your%20audio%20IHV%20to%20get%20a%20fix%20for%20the%20crash%20in%20question.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Microsoft

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-o... 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.