Well, have a look in juce_win32_DirectSound.com, and there are a few things you could try. A breakpoint at the line 218 should show you what DSound call triggered the error, though if the device is sending a crazy number back, then only the people who wrote the sound driver could help decipher what it actually means…