Anyway, Soundtap is now uninstalled and all seems perfectly fine. The reality is that you’ll see stdriver64.sys listed under any and all audio devices in your device manager, if you have Soundtap installed.Īs for other users above, I also only experienced the BSOD only when I upgraded to Cubase 6. It has nothing to do with Realtek - Realtek only features in this discussion because some google search results stdriver64.sys point to forums where Realtek was incorrectly blamed. Clearly this kind of program requires some deep under-the-hood black magic, which (I guess) is why the driver attaches to each and every sound device on your system. It is a streaming audio recorder which (if my memory serves me right) could be used to, for example, capture audio out of a streaming youtube video so that you can save it as a.
Soundtap is published by NCH software ( ) I had the same problem and (with some frustration) tracked this down to Soundtap. However, since returning to use Cubase 5 (thank goodness the upgrade leaves that intact) I have had no such problems. The reason for raising the question here is because I’ve been using Cubase 5 for a minimum of 12 hours per day, mostly 7 days a week, for the past 6 months… WITHOUT a BLIP !!! The same day that I install the Cubase 6 upgrade I get 2 or 3 blue screen crashes. Analysing the Windows dump file for my Blue Screen indicates that ‘something’ has attempted to access a protected area and has done so without handling the exception… hence the blue screen.
They are not standalone applications and a hardware call (from a software application) will be indirectly and sometimes directly interacting with such drivers. They are trained to assume if the user has any other software installed then that must be causing the problem.Īs for Blue Screen errors never being software related, that is not correct. Not a cubase with all due respect that really sounds like the kind of flippant reply one expects from front-line support.
Blue screen errors are hardware or driver related, never software.
0 kommentar(er)
