I posted this in your other thread: EMU support told me that's a feature called "eggshells". All jokes aside...I have dealt with EMU support on this issue for months going in circles trying to put the blame on my computer. I also am using Windows 7 64 bit and experience the random BSODs when arming/disarming tracks. It happens a lot less in Reaper...it actually never happens in Reaper when arming/disarming tracks but will randomly happen when exporting a track or shutting down the program. Try technical support if it is even still available. Please let me know if you hear anything from them.

I'm using a 1212M which uses the same driver with maybe a BSOD every 6 months in either Win7 x64 or WinXP x64.  So in general it's been pretty stable.  Been using the Vista x64 driver, not the Win7 beta.

Jim

I'm  using an 1820m and no bsods (yet - been using win7 x64 for a couple weeks). Also, I haven't really stressed my daw and I use reaper these days more often than sonar. I had previously tried the beta, but now use the vista x64 driver and performance is identical, and i'm more comfortable using a non beta. 

have you tried disabling your antivirus? certain av apps in my experience have caused bsods in some situations. maybe try another pci slot?

Thanks for all the support and suggestions everyone.  It's interesting to see that I'm not the only one, but also that some people have a set-up/environment that works fine.

Unfortunately, most of the suggestions mentioned I have already tried to no avail - and as for trying with Reaper, I have had a similar experience to the one mentioned.  Basically, it will BSOD at a different point in time - looks like Reaper opens/closes the ASIO channels at different points in time to Sonar.  Reaper, I guess, keeps them open even when a track that uses it is disarmed whereas Sonar actually interacts with the ASIO driver while arming/disarming tracks etc.

It might be a case of finding out what's different between the set-up's that work and the ones that don't, although I'm not sure where you'd even start with that - could take forever!

sdsicee


I posted this in your other thread: EMU support told me that's a feature called "eggshells". All jokes aside...I have dealt with EMU support on this issue for months going in circles trying to put the blame on my computer. I also am using Windows 7 64 bit and experience the random BSODs when arming/disarming tracks. It happens a lot less in Reaper...it actually never happens in Reaper when arming/disarming tracks but will randomly happen when exporting a track or shutting down the program. Try technical support if it is even still available. Please let me know if you hear anything from them.

"eggshells" indeed! I'm having a similar EMU 'Tech' support experience where they are suggesting it is my set-up, although I feel it is more likely my set-up makes the issue with the driver more apparent.  I'll keep contacting them and hopefully they will continue the line of support I'm currently in the middle of, for what it's worth.  Any progress in this respect will be posted, of course!

Guitarpima


At 24/44.1, I get 1.1ms at 48 samples. At 96khz it is a little slower at 9? samples. I never bothered to check the latency. I have a project at 96 I plan on mixing some more on and I'll let you know.

That is very good performance wise - thanks for the info!

spencil, one other quick point. Not sure if this is the issue, but the new intel sandy bridge motherboards do not have native PCI support. they use a 3rd party bridge chip to support the PCI slots. This doesn't explain bsods from people not using the sandy bridge platform, but maybe it's responsible for your issue. have you checked for updated chipset drivers, including the PCI bridge chip?

I've coincidently just got a grab of all the latest drivers for my motherboard - I'm not sure whether the PCI bridge chip driver is in there, but it's everything Gigabyte had to offer.  I shall go through the task of updating everything as soon as I'm back near my DAW PC, you never know!

Thanks for the new info!

If this helps, my IRQ table is as follows:
IRQ 16 2nd generation Intel® Core™ processor family PCI Express Controller - 0101 OK
IRQ 16 E-MU E-DSP Audio Processor (WDM) OK
IRQ 16 Intel(R) Management Engine Interface OK
IRQ 16 Intel(R) 6 Series/C200 Series Chipset Family PCI Express Root Port 1 - 1C10 OK
IRQ 17 Texas Instruments 1394 OHCI Compliant Host Controller OK
IRQ 17 Intel(R) 6 Series/C200 Series Chipset Family PCI Express Root Port 6 - 1C1A OK
IRQ 18 Intel(R) 6 Series/C200 Series Chipset Family USB Enhanced Host Controller - 1C2D OK
IRQ 18 PCI standard PCI-to-PCI bridge OK
IRQ 18 Intel(R) 6 Series/C200 Series Chipset Family PCI Express Root Port 7 - 1C1C OK
IRQ 19 Intel(R) 6 Series/C200 Series Chipset Family 6 Port SATA AHCI Controller - 1C02 OK
IRQ 23 Intel(R) 6 Series/C200 Series Chipset Family USB Enhanced Host Controller - 1C26 OK
Note that I've tried switching the card amongst the 3 PCI slots I have and, if my memory serves me correctly, it went between IRQ 16, 17 and 18 depending on the slot.  I tried IRQ 17 with a disabled 1394 firewire (as well as the others) and it still blue screened, but even then it was still sharing with the "PCI Express Root Port 1" which is also on IRQ 17.  There doesn't seem to be a way of configuring it so nothing shares with it - unless anyone has any cool ideas?  I'm interested to hear, and very grateful for, any suggestions anyone may have...   Thanks.

Also, in 'Device Manager' if I go to the menu 'View->Show Hidden Devices' and then navigate the device tree to 'Non-Plug and Play Drivers' then...
 
** I identified the following drivers as being Creative/EMU **
Creative Hardware Abstract Layer Driver (ha10kx2k.sys) - NOTE: This is the one identified on the BSOD
Creative Proxy Driver (ctprxy2k.sys)
Creative SoundFont Management Device Driver (ctsfm2k.sys)
E-mu Plug-in Architecture Driver (emupia)
CT20XUT.SYS
CTAUDFX.SYS
CTEAPSFX.SYS
CTEDSPFX.SYS
CTEDSPIO.SYS
CTEDSPSY.SYS
CTERFXFX.SYS
CTEXFIFX.SYS
CTHWIUT.SYS
CTSBLFX.SYS
 
** Uninstalled all the above drivers by right clicking, pressing 'Uninstall' and rebooting the computer - none of the above drivers were present once rebooted **
** I then loaded PatchMix and the following appeared **
COMMONFX.SYS
Creative Hardware Abstract Layer Driver (ha10kx2k.sys)
Creative Proxy Driver (ctprxy2k.sys)
Creative SoundFont Management Device Driver (ctsfm2k.sys)
E-mu Plug-in Architecture Driver (emupia)
** TESTED WITH SONAR BUT BSOD STILL HAPPENS **
 
** Rebooted again and all drivers reappeared **
Creative Hardware Abstract Layer Driver (ha10kx2k.sys)
Creative Proxy Driver (ctprxy2k.sys)
Creative SoundFont Management Device Driver (ctsfm2k.sys)
E-mu Plug-in Architecture Driver (emupia)
CT20XUT.SYS
CTAUDFX.SYS
CTEAPSFX.SYS
CTEDSPFX.SYS
CTEDSPIO.SYS
CTEDSPSY.SYS
CTERFXFX.SYS
CTEXFIFX.SYS
CTHWIUT.SYS
CTSBLFX.SYS

Does this match anyone else's driver listing for the EMU 1616M PCI?  Thanks again.