BSOD's with EMU 1616m PCI in Windows 7 64-bit

Page: < 1234 > Showing page 2 of 4
Author
Post
Essentials Only Full Version
sdsicee
Max Output Level: -88 dBFS
  • Total Posts : 118
  • Joined: 2005/07/22 22:13:00
  • Status: offline
Re:BSOD's with EMU 1616m PCI in Windows 7 64-bit 2011/09/14 22:19:14 (permalink)
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.

-Savoy-
http://www.iceestudios.com
#31
haydn12
Max Output Level: -84 dBFS
  • Total Posts : 322
  • Joined: 2007/01/29 17:12:04
  • Status: offline
Re:BSOD's with EMU 1616m PCI in Windows 7 64-bit 2011/09/14 23:47:16 (permalink)
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
#32
Duojet
Max Output Level: -62 dBFS
  • Total Posts : 1413
  • Joined: 2003/12/06 22:02:31
  • Location: NJ, US
  • Status: offline
Re:BSOD's with EMU 1616m PCI in Windows 7 64-bit 2011/09/15 00:10:30 (permalink)
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?
post edited by Duojet - 2011/09/15 00:21:32

Intel Core2Duo e8400
Abit IP35-E
4GB Ram
Windows 7 SP1 64 Bit
EMU 1820m

DFHS2, BFD2, Battery3, Amplitube2, GuitarRig3, Kontakt4, Ampeg SVX, Line6 PodXT
#33
Spencil Splodge
Max Output Level: -89 dBFS
  • Total Posts : 57
  • Joined: 2008/03/05 04:23:28
  • Status: offline
Re:BSOD's with EMU 1616m PCI in Windows 7 64-bit 2011/09/15 04:36:08 (permalink)
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!

Sonar X1 Producer Edition
Windows 7 Home Premium 64-bit
Intel Core i7 2600K
Gigabyte H67 Motherboard
8GB RAM
EMU 1616M PCI Audio Interface
#34
Spencil Splodge
Max Output Level: -89 dBFS
  • Total Posts : 57
  • Joined: 2008/03/05 04:23:28
  • Status: offline
Re:BSOD's with EMU 1616m PCI in Windows 7 64-bit 2011/09/15 04:39:28 (permalink)
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!

Sonar X1 Producer Edition
Windows 7 Home Premium 64-bit
Intel Core i7 2600K
Gigabyte H67 Motherboard
8GB RAM
EMU 1616M PCI Audio Interface
#35
Spencil Splodge
Max Output Level: -89 dBFS
  • Total Posts : 57
  • Joined: 2008/03/05 04:23:28
  • Status: offline
Re:BSOD's with EMU 1616m PCI in Windows 7 64-bit 2011/09/15 04:46:28 (permalink)
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!

Sonar X1 Producer Edition
Windows 7 Home Premium 64-bit
Intel Core i7 2600K
Gigabyte H67 Motherboard
8GB RAM
EMU 1616M PCI Audio Interface
#36
Duojet
Max Output Level: -62 dBFS
  • Total Posts : 1413
  • Joined: 2003/12/06 22:02:31
  • Location: NJ, US
  • Status: offline
Re:BSOD's with EMU 1616m PCI in Windows 7 64-bit 2011/09/15 09:38:10 (permalink)
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?
post edited by Duojet - 2011/09/15 09:43:25

Intel Core2Duo e8400
Abit IP35-E
4GB Ram
Windows 7 SP1 64 Bit
EMU 1820m

DFHS2, BFD2, Battery3, Amplitube2, GuitarRig3, Kontakt4, Ampeg SVX, Line6 PodXT
#37
Spencil Splodge
Max Output Level: -89 dBFS
  • Total Posts : 57
  • Joined: 2008/03/05 04:23:28
  • Status: offline
Re:BSOD's with EMU 1616m PCI in Windows 7 64-bit 2011/09/15 09:58:21 (permalink)
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!

Sonar X1 Producer Edition
Windows 7 Home Premium 64-bit
Intel Core i7 2600K
Gigabyte H67 Motherboard
8GB RAM
EMU 1616M PCI Audio Interface
#38
Spencil Splodge
Max Output Level: -89 dBFS
  • Total Posts : 57
  • Joined: 2008/03/05 04:23:28
  • Status: offline
Re:BSOD's with EMU 1616m PCI in Windows 7 64-bit 2011/09/16 09:10:21 (permalink)
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.
post edited by Spencil Splodge - 2011/09/16 09:11:40

Sonar X1 Producer Edition
Windows 7 Home Premium 64-bit
Intel Core i7 2600K
Gigabyte H67 Motherboard
8GB RAM
EMU 1616M PCI Audio Interface
#39
Spencil Splodge
Max Output Level: -89 dBFS
  • Total Posts : 57
  • Joined: 2008/03/05 04:23:28
  • Status: offline
Re:BSOD's with EMU 1616m PCI in Windows 7 64-bit 2011/09/16 09:15:22 (permalink)
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.

Sonar X1 Producer Edition
Windows 7 Home Premium 64-bit
Intel Core i7 2600K
Gigabyte H67 Motherboard
8GB RAM
EMU 1616M PCI Audio Interface
#40
brundlefly
Max Output Level: 0 dBFS
  • Total Posts : 14250
  • Joined: 2007/09/14 14:57:59
  • Location: Manitou Spgs, Colorado
  • Status: offline
Re:BSOD's with EMU 1616m PCI in Windows 7 64-bit 2011/09/16 10:50:44 (permalink)
I have basically that same driver set. Makes sense because I'm running the same Win7 beta driver package (which behaves identically to the Vista driver BTW).

And ha10kx2k.sys is the driver identified in all my BSODs, as it is in other reports I've found on the web.  This seems to be the primary I/O driver, while many of the others are obviously involved with the onboard DSP functions, which I'm generally not using.

I am going to try to make time to uninstall and re-install everything this weekend, booting the machine with the card out of the slot at least once, and see if there is any improvement.

But as I mentioned, I do not have a recipe for reproducing BSODs on my system. I pretty much just have to wait for it to happen, though I can probably speed up the process my making a lot of I/O changes.

For refrence, my interface shows up as E-MU E-DSP on IRQ 21, shared with Intel ICH9 Family USB Universal Host Controlller - 2938, and nothing else. Also as mentioned, leaving that port disabled for a period of time did not improve stability. As a result, I don't think IRQ sharing has any bearing on this issue.

SONAR Platinum x64, 2x MOTU 2408/PCIe-424  (24-bit, 48kHz)
Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
#41
Spencil Splodge
Max Output Level: -89 dBFS
  • Total Posts : 57
  • Joined: 2008/03/05 04:23:28
  • Status: offline
Re:BSOD's with EMU 1616m PCI in Windows 7 64-bit 2011/09/16 11:16:28 (permalink)
brundlefly


For refrence, my interface shows up as E-MU E-DSP on IRQ 21, shared with Intel ICH9 Family USB Universal Host Controlller - 2938, and nothing else. Also as mentioned, leaving that port disabled for a period of time did not improve stability. As a result, I don't think IRQ sharing has any bearing on this issue.


Agreed, looks like IRQ sharing issues are ruled out.  Thanks for checking that!

Sonar X1 Producer Edition
Windows 7 Home Premium 64-bit
Intel Core i7 2600K
Gigabyte H67 Motherboard
8GB RAM
EMU 1616M PCI Audio Interface
#42
brundlefly
Max Output Level: 0 dBFS
  • Total Posts : 14250
  • Joined: 2007/09/14 14:57:59
  • Location: Manitou Spgs, Colorado
  • Status: offline
Re:BSOD's with EMU 1616m PCI in Windows 7 64-bit 2011/09/16 11:54:36 (permalink)
Well, I've made progress of sorts: I am now able to generate a blue screen with some consistency by rapidly cycling the record arming state of all tracks using the arm button in the Control Bar, or by Ctrl-clicking the arm button in an audio track. I'll have to test some more, but it does seem to happen on disarming. Sometimes nothing will happen while arming/disarming all tracks, and then I go to disarm a single one, and it blue screens.

Now that I have a somewhat reliable recipe for crashing it, I can better experiment with possible solutions.

SONAR Platinum x64, 2x MOTU 2408/PCIe-424  (24-bit, 48kHz)
Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
#43
brundlefly
Max Output Level: 0 dBFS
  • Total Posts : 14250
  • Joined: 2007/09/14 14:57:59
  • Location: Manitou Spgs, Colorado
  • Status: offline
Re:BSOD's with EMU 1616m PCI in Windows 7 64-bit 2011/09/16 12:50:43 (permalink)
Well, this is interesting... and very preliminary, but I found a suggestion on one of the threads about this problem with the 1616m suggesting to enable compatibility mode for EMUPMixDSP.exe. I started the compatibility troubleshooter, and ended up setting XP SP3 compatibility, and enabling run as Administrator. This last setting shouldn't matter because I have UAC disabled on this machine, but the first one may have had some effect, as I can't seem to generate a BSOD now after easily generating four in a row with the arming/disarming drill before making the change.

I would have sworn I tried this some time ago to no avail, but so far so good. Here's what the properties dialog looks like now:






SONAR Platinum x64, 2x MOTU 2408/PCIe-424  (24-bit, 48kHz)
Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
#44
Spencil Splodge
Max Output Level: -89 dBFS
  • Total Posts : 57
  • Joined: 2008/03/05 04:23:28
  • Status: offline
Re:BSOD's with EMU 1616m PCI in Windows 7 64-bit 2011/09/16 14:30:03 (permalink)
Exciting stuff - glad the arming/disarming trick has helped you repeat it easier.  I'm sure I tried that one before too, none the less it may well have been missed amongst all the other items I was trying...

Sonar X1 Producer Edition
Windows 7 Home Premium 64-bit
Intel Core i7 2600K
Gigabyte H67 Motherboard
8GB RAM
EMU 1616M PCI Audio Interface
#45
Freddie H
Max Output Level: -39 dBFS
  • Total Posts : 3617
  • Joined: 2007/09/21 06:07:40
  • Status: offline
Re:BSOD's with EMU 1616m PCI in Windows 7 64-bit 2011/09/16 15:39:22 (permalink)
Hi my friend!

IMPORTANT!!!

IF you use the latest version of EMU PCIe 1616M you need the latest drivers to make it work with WINDOWS 7. You find it here.

http://support.creative.com/Products/ProductDetails.aspx?catID=237&catName=Digital+Audio+Systems&subCatID=491&subCatName=Digital+Audio+System&prodID=19007&prodName=E-MU+1616M+PCIe&bTopTwenty=1&VARSET=prodfaq:PRODFAQ_19007,VARSET=CategoryID:237




IF you use the old version PCI version of EMU 1616M PCI you need to use THE BETA version to make it work with WINDOWS 7. You find it here..


http://support.creative.com/kb/ShowArticle.aspx?sid=95146&h=13



***********

It can also be good to not let the EMU 1616M card share any IRQ. Check you motherboard manual to find a free exclusive IRQ for you EMU 1616M
 
 
 
 
Best Regards
Freddie
post edited by Freddie H - 2011/09/16 15:42:23


-Highly developed spirits often encounter resistance from mediocre minds. -It really matters!
#46
Spencil Splodge
Max Output Level: -89 dBFS
  • Total Posts : 57
  • Joined: 2008/03/05 04:23:28
  • Status: offline
Re:BSOD's with EMU 1616m PCI in Windows 7 64-bit 2011/09/17 07:20:52 (permalink)
Thanks for the info Freddie H.  I'm currently using the Windows 7 BETA driver you suggest.  I've checked my motherboard manual etc. and I can't seem to find anyway to get the EMU on it's own IRQ - all I can do is switch PCI slots but it's always shared with something.  However, other people who experience this issue have found that even when the EMU has it's own IRQ the problem still persists.

I'm going to try the WinXP SP3 fix suggestion now and see if I have any luck - brundlefly, so far, seems to have had success...  fingers crossed.

Sonar X1 Producer Edition
Windows 7 Home Premium 64-bit
Intel Core i7 2600K
Gigabyte H67 Motherboard
8GB RAM
EMU 1616M PCI Audio Interface
#47
Spencil Splodge
Max Output Level: -89 dBFS
  • Total Posts : 57
  • Joined: 2008/03/05 04:23:28
  • Status: offline
Re:BSOD's with EMU 1616m PCI in Windows 7 64-bit 2011/09/17 14:22:56 (permalink)
brundlefly


Well, this is interesting... and very preliminary, but I found a suggestion on one of the threads about this problem with the 1616m suggesting to enable compatibility mode for EMUPMixDSP.exe. I started the compatibility troubleshooter, and ended up setting XP SP3 compatibility, and enabling run as Administrator. This last setting shouldn't matter because I have UAC disabled on this machine, but the first one may have had some effect, as I can't seem to generate a BSOD now after easily generating four in a row with the arming/disarming drill before making the change.

I would have sworn I tried this some time ago to no avail, but so far so good. Here's what the properties dialog looks like now:



How have you got on with this change?  I have tried WinXP SP3 compatibility (admin was already on) but I still get BSOD's when arming/disarming tracks.  I ran the compatibility wizard and it suggested WinXP SP2, but after trying that it also gave me BSOD's.  Just a note, using the arming/disarming method to reproduce the issue can take a variable number of repeats.  I've now gotten to the stage where I'm clicking the arm button rapidly for around 30 seconds before some BSOD's occur, other times it happens in a few clicks.
 
Hope you're having more luck with yours!  Thanks.

Sonar X1 Producer Edition
Windows 7 Home Premium 64-bit
Intel Core i7 2600K
Gigabyte H67 Motherboard
8GB RAM
EMU 1616M PCI Audio Interface
#48
brundlefly
Max Output Level: 0 dBFS
  • Total Posts : 14250
  • Joined: 2007/09/14 14:57:59
  • Location: Manitou Spgs, Colorado
  • Status: offline
Re:BSOD's with EMU 1616m PCI in Windows 7 64-bit 2011/09/17 14:27:52 (permalink)
brundlefly, so far, seems to have had success.



I've had a few setbacks, unfortunately. It doesn't seem to be sensitive to toggling the arming state, but I was able to crash it by toggling the input echo on all tracks, and twice it went down out of the blue (or maybe should I say into the blue) when switching focus from SONAR to another (non-audio) app, which closes the audio ports.


So, not much joy overall from the compatibility tweak.

SONAR Platinum x64, 2x MOTU 2408/PCIe-424  (24-bit, 48kHz)
Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
#49
Duojet
Max Output Level: -62 dBFS
  • Total Posts : 1413
  • Joined: 2003/12/06 22:02:31
  • Location: NJ, US
  • Status: offline
Re:BSOD's with EMU 1616m PCI in Windows 7 64-bit 2011/09/17 16:48:24 (permalink)
a couple suggestions -

turn off exclusive mode for the emu
make sure the sample rate in windows matches the patchmix setting (for windows sounds)

Intel Core2Duo e8400
Abit IP35-E
4GB Ram
Windows 7 SP1 64 Bit
EMU 1820m

DFHS2, BFD2, Battery3, Amplitube2, GuitarRig3, Kontakt4, Ampeg SVX, Line6 PodXT
#50
brundlefly
Max Output Level: 0 dBFS
  • Total Posts : 14250
  • Joined: 2007/09/14 14:57:59
  • Location: Manitou Spgs, Colorado
  • Status: offline
Re:BSOD's with EMU 1616m PCI in Windows 7 64-bit 2011/09/18 02:27:27 (permalink)
turn off exclusive mode for the emu



Exclusive mode?


So you don't ever get BSODs?

SONAR Platinum x64, 2x MOTU 2408/PCIe-424  (24-bit, 48kHz)
Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
#51
Spencil Splodge
Max Output Level: -89 dBFS
  • Total Posts : 57
  • Joined: 2008/03/05 04:23:28
  • Status: offline
Re:BSOD's with EMU 1616m PCI in Windows 7 64-bit 2011/09/21 10:47:44 (permalink)
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.

Sonar X1 Producer Edition
Windows 7 Home Premium 64-bit
Intel Core i7 2600K
Gigabyte H67 Motherboard
8GB RAM
EMU 1616M PCI Audio Interface
#52
datadog
Max Output Level: -89 dBFS
  • Total Posts : 75
  • Joined: 2006/05/25 00:38:10
  • Location: Meridian, Idaho
  • Status: offline
Re:BSOD's with EMU 1616m PCI in Windows 7 64-bit 2011/09/21 11:02:36 (permalink)
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.

datadog
http://www.518music.com

i7 920, Gigabyte GA-EX58-UD3R, Mushkin DDR3 1600, ATI Radeon HD 5450, RME Fireface UFX, UAD2's, Windows7 x64, Sonar X3C x64, Reaper 4 x64, Studio One Pro V2.61 x64, NI Komplete 6, Waves v9 Gold, SSL Bundle x64.
#53
brundlefly
Max Output Level: 0 dBFS
  • Total Posts : 14250
  • Joined: 2007/09/14 14:57:59
  • Location: Manitou Spgs, Colorado
  • Status: offline
Re:BSOD's with EMU 1616m PCI in Windows 7 64-bit 2011/09/21 11:58:23 (permalink)
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.

SONAR Platinum x64, 2x MOTU 2408/PCIe-424  (24-bit, 48kHz)
Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
#54
datadog
Max Output Level: -89 dBFS
  • Total Posts : 75
  • Joined: 2006/05/25 00:38:10
  • Location: Meridian, Idaho
  • Status: offline
Re:BSOD's with EMU 1616m PCI in Windows 7 64-bit 2011/09/21 12:24:36 (permalink)
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.

datadog
http://www.518music.com

i7 920, Gigabyte GA-EX58-UD3R, Mushkin DDR3 1600, ATI Radeon HD 5450, RME Fireface UFX, UAD2's, Windows7 x64, Sonar X3C x64, Reaper 4 x64, Studio One Pro V2.61 x64, NI Komplete 6, Waves v9 Gold, SSL Bundle x64.
#55
brundlefly
Max Output Level: 0 dBFS
  • Total Posts : 14250
  • Joined: 2007/09/14 14:57:59
  • Location: Manitou Spgs, Colorado
  • Status: offline
Re:BSOD's with EMU 1616m PCI in Windows 7 64-bit 2011/09/21 13:27:08 (permalink)
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. 




SONAR Platinum x64, 2x MOTU 2408/PCIe-424  (24-bit, 48kHz)
Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
#56
Duojet
Max Output Level: -62 dBFS
  • Total Posts : 1413
  • Joined: 2003/12/06 22:02:31
  • Location: NJ, US
  • Status: offline
Re:BSOD's with EMU 1616m PCI in Windows 7 64-bit 2011/09/21 19:51:10 (permalink)
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.




post edited by Duojet - 2011/09/21 19:55:37

Intel Core2Duo e8400
Abit IP35-E
4GB Ram
Windows 7 SP1 64 Bit
EMU 1820m

DFHS2, BFD2, Battery3, Amplitube2, GuitarRig3, Kontakt4, Ampeg SVX, Line6 PodXT
#57
brundlefly
Max Output Level: 0 dBFS
  • Total Posts : 14250
  • Joined: 2007/09/14 14:57:59
  • Location: Manitou Spgs, Colorado
  • Status: offline
Re:BSOD's with EMU 1616m PCI in Windows 7 64-bit 2011/09/21 21:33:47 (permalink)
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.

SONAR Platinum x64, 2x MOTU 2408/PCIe-424  (24-bit, 48kHz)
Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
#58
sdsicee
Max Output Level: -88 dBFS
  • Total Posts : 118
  • Joined: 2005/07/22 22:13:00
  • Status: offline
Re:BSOD's with EMU 1616m PCI in Windows 7 64-bit 2011/09/21 21:47:19 (permalink)
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!

-Savoy-
http://www.iceestudios.com
#59
sdsicee
Max Output Level: -88 dBFS
  • Total Posts : 118
  • Joined: 2005/07/22 22:13:00
  • Status: offline
Re:BSOD's with EMU 1616m PCI in Windows 7 64-bit 2011/09/21 21:51:44 (permalink)
Just recovered from a BSOD! Though it did take a lot longer than usual to trigger it. On with the quest.

-Savoy-
http://www.iceestudios.com
#60
Page: < 1234 > Showing page 2 of 4
Jump to:
© 2025 APG vNext Commercial Version 5.1