turn off exclusive mode for the emu

Exclusive mode?


So you don't ever get BSODs?

Just an update - I've, errr, updated all my motherboard drivers and BIOS to the latest version and I'm still getting the BSOD.

I haven't played with 'exclusive mode' yet, but I'm fairly certain I've tried this in the past.  There was a known issue with the WDM driver which would cause a blue screen, as well as various sample rate mismatch issues.  I believe the WDM side of things was fixed in the latest BETA.  I wonder if the BSOD in the ASIO driver is the same issue as the WDM but it just ain't fixed yet??  That would be annoying.

What is "Exclusive Mode"?
I've been following this thread trying to get my system to BSOD and cannot make it crash. I'm using the E-Mu Windows7 beta driver. It just works without any problems. Arming and disarming tracks  rapidly, slowly. No noticeable delay with the button turning red either. Any other conditions to make it crash? I'll be glad to check that out. In fact, I don't think I've ever had a BSOD with my 1820m on Win7 x64.

In fact, I don't think I've ever had a BSOD with my 1820m on Win7 x64.

I hate you. 


A few other 1820m users have reported the same, so there must be an environmental factor, but I'm danged if I can figure out what it is. But I still haven't yet gotten around to the full uninstall/reinstall; that'll be the last resort.

I'm guessing "Exclusive Mode" means un-checking "Share drivers with other programs" in SONAR's audio preferences. I've tried this setting both says - usually off - and it doesn't seem to make a difference. I do not have the 1820m set as Default Device for Windows audio, system sounds are disabled, and I don't have any other apps set up to use it. But Win7 no longer has the "Don't use this device" checkbox that XP had, so... who knows.

It's good to know that some folks seem to have this working with x64, but frustrating that I can't get there. And mystifying that E-MU support has absolutely zero trouble-shooting recommendations. I always assumed this was because they know it's buggy, and there's nothing to be done about it.

LOL! Thanks Brundlefly!

That's what I thought- I've never used "Share Drivers with other programs" with Asio; just WDM but since E-Mu WDM sucks, ASIO is the only way to go with this card. I do use the onboard sound for Media Player etc. without any conflicts with the E-Mu.

I agree that it's probably system specific- maybe a combo of other apps/drivers. I do constantly update Windows with the latest patches. They have many "Compatibility" updates that who knows what they fix or do. I always image my partition with Acronis True Image before any updates.

What's ironic about the 1820m is when I first got it in late 2006, I had nothing but issues with BSOD's on my Core Two Duo E6600, Win XP32 and Sonar 7. I went back to using my Frontier Dakota/Montana setup and still use it on that same system today with no issues. Conversely, the Frontier setup never worked right on my current system with Win7 x64.

I also had numerous problems years back with an old P4 Northwood system and Sonar 5. As soon as Sonar 6 came out, all the problems went away. Many Gremelins in this DAW stuff and sometimes it's hard to pin it down.

I had nothing but issues with BSOD's on my Core Two Duo E6600, Win XP32 and Sonar 7.

Too funny. I started with virtually the same system (E6750) and was golden. I was still golden after upgrading the motherboard and CPU to the current Q9550, but as soon as I installed Win7 x64, everything went to hell in a you-know-what. 

brundlefly

In fact, I don't think I've ever had a BSOD with my 1820m on Win7 x64.

I hate you. 


A few other 1820m users have reported the same, so there must be an environmental factor, but I'm danged if I can figure out what it is. But I still haven't yet gotten around to the full uninstall/reinstall; that'll be the last resort.

I'm guessing "Exclusive Mode" means un-checking "Share drivers with other programs" in SONAR's audio preferences. I've tried this setting both says - usually off - and it doesn't seem to make a difference. I do not have the 1820m set as Default Device for Windows audio, system sounds are disabled, and I don't have any other apps set up to use it. But Win7 no longer has the "Don't use this device" checkbox that XP had, so... who knows.

It's good to know that some folks seem to have this working with x64, but frustrating that I can't get there. And mystifying that E-MU support has absolutely zero trouble-shooting recommendations. I always assumed this was because they know it's buggy, and there's nothing to be done about it.

right click on the volume icon in the task bar, click playback devices. Click the emu. Go to advanced. Uncheck "allow applications to take exclusive control....". Do the same for recording devices. 

No, I haven't gotten and BSODs. I haven't done much heavy recording though. What little I have used my daw since i upgraded to win7, hasnt caused and BSODs. I also researched many forums and alot of people have crash free operation of the 1820m and other using the vista or win7 beta driver.

Go to advanced. Uncheck "allow applications to take exclusive control....".

Interesting. Maybe Windows itself gets unhappy if an application has exclusive control...?  Thanks for the suggestion; I've not heard that one before. Trying it out now. So far so good; can't seem to make it crash with either the Arm or Input Echo buttons. Crossing my fingers.

So far so good here too! My blood pressure rises with each press of the arming and disarming expecting a BSOD! I actually prayed to God earlier today to stop this since EMU has been of no help. It is that frustrating. It happened to me 3 times today! Hopefully this is the fix!

Just recovered from a BSOD! Though it did take a lot longer than usual to trigger it. On with the quest.