|
|
Post by kensuguro on Nov 23, 2011 21:10:23 GMT
BSOD from stdriver64 seems to be a infrequent but recurring problem. I've gathered that stdriver64.sys is a file from nch soft, bundled with their soundtap or debut video capture application to record the master outs of your soundcard. Fortunately, uninstalling the application fixes the BSOD, but this is actually where the problem starts. For some reason, none of my audio devices work with asio4all. Actually, my devices don't even work with their own asio drivers. So basically, my production system's been rendered useless. There really isn't much info surrounding asio problems after uninstalling the nch soft app, but the problem seems to revolve around upper filters. www.w7forums.com/blue-screen-after-sleep-mode-t11048.htmluk.answers.yahoo.com/question/index?qid=20100504105317AAXijodstdriver64 gathers the system's audio out by intercepting signals going to the card, which makes sense that something gone wrong at that phase could interfere with asio4all. The problem is that I don't know what asio4all needs, or what sort of filter settings could break asio functionality all together.. I was wondering if anyone here had more knowledge about this. As it stands, there seems to be no way to fix the stdriver64 uninstall problem. Or more specifically, there seems to be no good way to rebuild the filter stack to pre-stdriver64 install. Fyi, the strange thing is that all my audio devices work fine as long as they are not accessed through asio. In asio4all, they all show up as "beyond logic". Any ideas? |
|
|
|
Post by ryanfarrell on Apr 24, 2012 2:05:15 GMT
Apparently this is a great mystery of our age as numerous peoples computers have been rendered useless as audio production tools due to this problem(wow, run on). I have been trying to figure this out for about a year with no results. Good luck and godspeed to you. I'll scream over the internet if I figure out a way to fix it.
|
|
|
|
Post by Ben Reaves on Jun 15, 2012 13:15:01 GMT
My best guess is that this is a fatal problem, meaning a complete re-install of Windows is required. It's a worst-case scenario, meaning I have to back up 600 GB of documents, pictures, music, games, and raw recordings/final renders to an external drive, gather all the installation files for every program I've ever installed to my computer, re-install Windows, download and install all of Dell's drivers, and then restore every file, every program, every setting to the way it was before I blew it away. Daunting doesn't seem like the right word to describe it. What's so bad about having to do this is that it's a three-to-five-day process, during which I'll have no computer.
I'm incredibly disappointed at the level of stupidity NCH stands for, given they don't fix the registry with their own installer. That's the root cause of ASIO being dead. I recommend everyone who has this problem, once you've completely reset Windows, go configure your system restore points to stay on your PC longer, so that if you ever have problems again, you can restore to when you didn't have problems. I could have fixed this problem had the restore point not reached the end of the cue and expired.
I'm sorry, but that's really what I think is going to have to happen. Back up EVERYTHING, find your installers, re-install Windows, re-install your drivers, then restore applications and files. I wish there was more forewarning about NCH software so this wouldn't happen to people again.
|
|
|
|
Post by travis on Jul 26, 2012 14:43:08 GMT
This worked for me on 64-bit Windows 7, Lenovo Y570 machine: I went to the nch software site, downloaded soundtap, and installed/uninstalled it. That didn't fix the problem, but it uninstalled soundtap (mostly). Shortly after that, I discovered a flaw in Windows 7 audio sample rate conversion, and I was made aware of this patch when discussing it on another forum: support.microsoft.com/kb/2653312 I installed the patch, and not only was the original problem fixed (as described by the original poster), but I was able to run my Realtek audio at 5.5 ms roundtrip latency when using Asio4all (measured by jumping audio in/out jacks). So yes, soundtap screwed my system audio, but ultimately, it got me looking into other things about the Windows audio stack, which led to the discovery of a Windows 7 audio flaw, and I ended up with fixed audio and lower latency with onboard sound than what my audio interface is capable of on Windows 7. Sometimes things turn out awesome.  |
|
|
|
Post by Michael Tippach on Jul 30, 2012 12:02:18 GMT
Thanks a lot for the info!
Making this sticky for a while.
|
|
|
|
Post by RainSnowHail on Oct 29, 2012 0:17:22 GMT
Actually, I've had this problem. The stupid "Beyond Logic" error that rendered my PC pretty much useless, (I had to use the DirectX options like an animal) fixed it self today.
(Not too different to the regular fix, still)
My MIDI was also broken until I applied this thing to fix the Beyond Logic error.
Open regedit, and search:
4D36E96C-E325-11CE-BFC1-08002BE10318
Once you find it, make a multi-string value, called UpperFilters.
In the data area, put these in:
stdriver
ksthunk
Close regedit, and reboot.
Install the new Realtek driver (most people who have this problem have this problem).
Follow, and run your DAW.
(I'm not sure this works for everyone, but it worked for me. I hope this helps you!)
|
|
|
|
Post by handhanzo on Nov 3, 2012 3:34:14 GMT
Actually, I've had this problem. The stupid "Beyond Logic" error that rendered my PC pretty much useless, (I had to use the DirectX options like an animal) fixed it self today. (Not too different to the regular fix, still) My MIDI was also broken until I applied this thing to fix the Beyond Logic error. Open regedit, and search: 4D36E96C-E325-11CE-BFC1-08002BE10318 Once you find it, make a multi-string value, called UpperFilters. In the data area, put these in: stdriver ksthunk Close regedit, and reboot. Install the new Realtek driver (most people who have this problem have this problem). Follow, and run your DAW. (I'm not sure this works for everyone, but it worked for me. I hope this helps you!) How does it "fix itself" and what is this "regular fix" thou speakest of? Does that regedit fix you posted fix the ASIO driver, or just the MIDI? And what is a DAW? You'll have to excuse me, I'm a n00binho to both tech-savvy stuff like this and music production in general. All I know is that Debut broke my ASIO, I can't use it with my FL Studio anymore and nothing I do fixes it. Beyond Logic. Forever Beyond Logic. And I got a new mic being shipped to me as I type this. As I said in my thread about this problem, vocals are much harder to mix in Audacity than they are in FL, and even though I installed that aforementioned "latency patch" whatever in C:\ (where it prompted me to install it) there is still clicking and popping even though I tried to optimize my DirectSound within FL's settings to minimize that. (It's most frequent when I use my "Secret Weapon", aka Autogun) So...y'all saying this can be fixed? Or am I S.O.L. (or as ASIO4ALL would apparently put it, "Beyond Logic")? |
|
|
|
Post by wimforlife on Dec 29, 2012 12:14:25 GMT
|
|
|
|
Post by pelvis on Jan 24, 2013 18:29:48 GMT
thankyou!!! i have had this problem for months and never even gave debut a thought... i read this,,, removed debut..
as soon as i started Live (ableton) asio was working and was the selected driver... thankyou guys..
|
|
|
|
Post by wimforlife on Jan 26, 2013 7:09:26 GMT
thankyou!!! i have had this problem for months and never even gave debut a thought... i read this,,, removed debut.. as soon as i started Live (ableton) asio was working and was the selected driver... thankyou guys.. man.. u lucky. how did you make it work?? Just removing Debut didnt work for me:/ ive been searching like crazy for a solution. what OS do you have? |
|
|
|
Post by handhanzo on Feb 8, 2013 23:32:41 GMT
bump because that regedit thingamabob above my last post did nathan but disable my sound completely, and I just shelled out 25 bones on a USB MIDI keyboard that won't even turn on because my sound drivers are still beyond logic.
I've done everything. I've reinstalled and uninstalled Soundtap and gutted all its registry entries from my computer entirely. I've uninstalled and reinstalled both ASIO and my Realtek HD Audio Drivers several times.
Now, please excuse me while I go slam my head in a door. Repeatedly.
|
|
|
|
Post by wimforlife on Feb 10, 2013 22:21:37 GMT
Now, please excuse me while I go slam my head in a door. Repeatedly. LOL, good idea. |
|
|
|
Post by Evan Balster on Feb 24, 2013 8:02:27 GMT
Alternate fix for people who've uninstalled SoundTap/Debut and have broken ASIO/MIDI input:
Open regedit, and search for this key:
4D36E96C-E325-11CE-BFC1-08002BE10318
Once you find it, make a multi-string value, called UpperFilters.
In the data area, put this in:
ksthunk
Find any other instances of the key above (F3 is "find next") and make sure they also have ksthunk in the UpperFilters.
Close regedit, and reboot.
This fixed both my ASIO and my MIDI controller woes.
|
|
|
|
Post by Evan Balster on Feb 24, 2013 8:06:07 GMT
As near as I can tell the cause of the issue is that SoundTap/Debut delete the UpperFilters key when uninstalled, rather than simply removing their addition to it.
ksthunk is what allows kernel streaming to intercept the audio, as is dome in ASIO4ALL's ASIO-to-kernel-streaming interface. stdriver/debutfilter perform a similar interception in order to capture audio, but make a mess of the driver stack.
|
|
|
|
Post by wimforlife on Feb 27, 2013 14:38:59 GMT
Find any other instances of the key above (F3 is "find next") and make sure they also have ksthunk in the UpperFilters. Close regedit, and reboot. This fixed both my ASIO and my MIDI controller woes. WOW i did try this regedit before but it didnt work the first time now i try again but for "other instances with the key F3" aswell and so it worked! now i have SOUND and i can RECORD AGAIN .. finally! thank you very much Evan!! OMG this is so great   |
|
