Nazo
2[H]4U
- Joined
- Apr 2, 2002
- Messages
- 3,672
So this is kind of a strange one. I recently reinstalled Windows 7 x64 because I wanted to switch over to UEFI (I was using CSM before and converting without using commercial software is quite a lot harder than you might think so I eventually just gave up) and it was getting a bit bogged down over time anyway. Now, nothing has changed. Exact same hardware, same software, same updates, etc etc. But for some odd reason Windows keeps deciding this USB DAC can only do 44100Hz or 48000Hz at 16-bits and absolutely nothing else. (For the record it is capable of 24/192.) I have to "uninstall" the device from device manager and tell it to delete the drivers then reinstall drivers about 15 times to get it to suddenly recognize that it is capable of more. Weirder still, it's the same drivers I used before... But then it will forget after a reboot or two (I think three is the most it ever survived.) Then once again I have to repeat the process to get it to accept that the device is capable of more. To be clear, I didn't have this problem before the reinstallation. Windows 100% understood its capabilities and never once "forgot."
I'm getting really tired of having to manually fix this and would really like a more permanent solution. Given the weirdness of this whole issue I have no clue what could even be the cause. Everything is the same including software and drivers, so there's just no explanation that makes any sense. It's not even the hardware itself because A. it worked just fine before, B. this isn't the kind of thing that failing hardware would do (even if it were old which it is not,) and C. it works fine outside of Windows in Linux or whatever. I've even used it on an Android phone with no problems getting its full capabilities (though sadly my current phone isn't working with OTG.)
Actually, with the way it "forgets" I almost wonder if it's something like Windows tries to query the device but it doesn't answer fast enough and Windows just falls back to a "safe" default or something. Might there perhaps be some way to bypass this or something if that is the case?
EDIT: Never got it to properly work on that system. As far as I can tell what it comes down to is the newer drivers just didn't get along. Unfortunately, I really didn't know what older drivers to use. I suppose someone with the patience to do it could just go through older driver archives until they found some that didn't have the problem. Since I was already planning on upgrading my system it didn't seem worth doing all that. I have since upgraded and the new system doesn't have this problem (in no small part due to only having one chipset to deal with.)
I'm getting really tired of having to manually fix this and would really like a more permanent solution. Given the weirdness of this whole issue I have no clue what could even be the cause. Everything is the same including software and drivers, so there's just no explanation that makes any sense. It's not even the hardware itself because A. it worked just fine before, B. this isn't the kind of thing that failing hardware would do (even if it were old which it is not,) and C. it works fine outside of Windows in Linux or whatever. I've even used it on an Android phone with no problems getting its full capabilities (though sadly my current phone isn't working with OTG.)
Actually, with the way it "forgets" I almost wonder if it's something like Windows tries to query the device but it doesn't answer fast enough and Windows just falls back to a "safe" default or something. Might there perhaps be some way to bypass this or something if that is the case?
EDIT: Never got it to properly work on that system. As far as I can tell what it comes down to is the newer drivers just didn't get along. Unfortunately, I really didn't know what older drivers to use. I suppose someone with the patience to do it could just go through older driver archives until they found some that didn't have the problem. Since I was already planning on upgrading my system it didn't seem worth doing all that. I have since upgraded and the new system doesn't have this problem (in no small part due to only having one chipset to deal with.)
Last edited: