I have blogged before about the Microsoft class driver for USB Audio 2.0 hardware.
If you are a hardware vendor, and you make USB Audio 2.0 hardware, you should expect your hardware to work with this driver.
If it doesn't, you may be interested in understanding why - maybe it's a bug on our end, or on your end, or perhaps a difference of interpretation in the spec.
To help shed light on these issues, we have logging in the driver that uses Event Tracing for Windows (ETW)'s Windows Software Trace Preprocessor (WPP).
For example, you could gather the logging from usbaudio2.sys into an .etl file using a Windows Performance Recorder Profile that includes this provider:
To actually read the logs, though, you need to decode them. You can decode WPP logs using a "program database" (PDB) file with full information (a so-called "private" PDB file), or using a collection of trace-format (TMF) files.
We at Microsoft have access to the private usbaudio2.pdb files, so we can decode them. And we have published a "public" usbaudio2.pdb, but it does not contain sufficient information to decode the WPP logs.
So to enable audio hardware vendors to read usbaudio2.sys logs, we are publishing the TMF Files for usbaudio2.sys. The .zip file includes TMF files for the Creators Update (AKA 1703 AKA 10.0.15063.*) and the Fall Creators Update (AKA 1709 AKA 10.0.16299.*)