Do you use the latest ASIO4ALL version
2.14? This is an updated version that includes a "Workaround for a bug in Windows 10 Creators Update: USB audio capture would not work any more (red exclamation mark, distorted sound, ...)". Maybe this also applies for USB audio render.
Besides, could you show a picture of your ASIO4ALL configuration like
this one? Does the "WDM Device List" state "24Bits" for "Out"?
If I am not mistaken you did not install any device specific WDM driver. So, which driver does Windows really use? Its own internal Microsoft/Thesycon USB 2.0 driver (usbaudio2.sys)? Or the correct device specific Schiit driver (which seems to be
this one) that Windows may have installed from Windows Update? Or a previously installed (and now incorrect) driver? I think there is a chance that ASIO4ALL on your system somehow does not use the driver that WASAPI uses.
It may also be that you have unveiled a yet undiscovered bug in ASIO4ALL. In that case the developer Michael Tippach would certainly help.
Also,
in the introduction of Schiit's test report they write "If you still have significantly different results, please contact
[email protected] with a copy of your results so we can bring back your product and check it against our standard." It would be interesting to know which ASIO driver they actually used. I think they would tell you if you showed them your results with the same 28k$ audio analyzer.
Overall I think it is worth seeking for the reason of this discrepancy (and finding a solution for it) as this device seems to be the first seriously engineered DAC from Schiit
.
By the way, the 100 Hz spikes and its overtones are certainly the result of truncation from 24 to 16 bits (as you already mentioned). This is the spectrum of an undithered 24-bit full scale 1 kHz sine:
View attachment 16066
Here is the result of converting that signal to 16 bits with simple truncation, that is, no dither and no noise shaping:
View attachment 16067
This looks like the spectrum you recorded with your APx.