You know... the problem you referring to don't need to be EMU audio card,

I think you have probelms with you MEMORY and it has nothing to do with E-MU card.. I don't know but I bet you use overclock memory mode, right?

Corsair...kingston.... are I'm wrong...?
No... I thought so... If that is so-----> there is you main problem. Set the MEMORY in default SPEED in BIOS and you problems will go away..
 
And listen... even if you do LINUX MEMORY TEST during PRE BOOT it still can fail in Windows. You MEMORY can also be damage too so that make it fail if you don't have OVERCLOCK your self the MEMORY. Check so you MEMORY isn't OVERCLOCK. Sometimes you think you have bought 1600 mhz Memory but they are just factory overclocked to 1600 mhz but the memory are only still 1333 mhz speed MEMORY. Very common in Corsair.

Best Regards
Freddie

 
I tried repeated testing over a couple days - seriously hammering the REC arm/disarm and input echo buttons like a complete idiot - no BSOD's at all...
 
Then, yesterday evening I give it some more testing and boom - a BSOD. Try it again this morning, and once again a BSOD.
 
Sorry if I got anyones hopes up about this, I was hopeful too, and I'm not even sure why it was so stable for a couple of days either... did I improve anything? I don't know. All I know is I could not make a BSOD happen for the first couple of days, no matter what I did - and I don't even know why this was.
 
The changes were to disable EIST (Speed Step), C1E, C3 and C6 power states in the BIOS. I also have core parking disabled in the OS but the BIOS changes overrule this anyhow. Keep in mind your computer will run slightly hotter when idle and will consume more power. I did also try turning off Turbo Boost technology for the hell of it, to no avail. On the plus side these changes improved latency slightly - or maybe everything is just a placebo for me these days!??

Some background info:
[</font]
[link=http://www.gearslutz.com/board/music-computers/465221-c1e-c3-c6-eist-speedstep-turbo-boost-core-parking-2.html]http://www.gearslutz.com/...st-core-parking-2.html[/link]
 
Disabling core parking in the OS:
 
[link=http://forum.cakewalk.com/tm.aspx?m=1861804</a></font></font>]http://forum.cakewalk.com.../font></font>
 
Feel free to give these changes a go and post your results.

post edited by Spencil Splodge - 2011/09/23 10:30:58

Thanks for the link drumr - I'm already posting on this site and trying to extract any help I can from it.  Mine is the latest 'BSOD' thread in 'EMU 1616M' stuff ;)

I tried repeated testing over a couple days - seriously hammering the REC arm/disarm and input echo buttons like a complete idiot - no BSOD's at all...   Then, yesterday evening I give it some more testing and boom - a BSOD.

I had the same experience with the "Disable Exclusive Mode" tweak. I could not crash it deliberately with the Arm or Input Echo buttons, and then it went down suddenly last night when inserting a soft synth. 


This is pretty much how this issue has always been for me... very unpredictable. It's often related to Input state changes that would obviously involve calling the interface driver, but then it will happen doing something seemingly unrelated. But it's always ha10kx2k.sys - the Creative/E-MU driver.


FWIW, I spent some time browsing the ProductionForums site about this a long time ago, and the only thing I came up with that I hadn't tried was the full uninstall/reinstall.


Looking hard at buying a MOTU 8Pre or the new Presonus AudioBox 1818VSL. Both have the ADAT input I need.

brundlefly

I tried repeated testing over a couple days - seriously hammering the REC arm/disarm and input echo buttons like a complete idiot - no BSOD's at all...   Then, yesterday evening I give it some more testing and boom - a BSOD.

Looking hard at buying a MOTU 8Pre or the new Presonus AudioBox 1818VSL. Both have the ADAT input I need.

...oh Lord... Good Luck with MOTU crash heaven.. Those products are not even near E-MU Audio interface..Totally different category "Home studio" products.
 
 
Great things always cost money. EMU 1616M-series are great choice., the best converters in the world for nothing..... If you still don't like it and want the same quality range and gear you should check out following products.
 
 
 
E-MU 1616M
http://www.creative.com/emu/products/product.aspx?category=505&pid=19007 
    
  
 
Focusrite Rednet Series
 
http://www.focusrite.com/products/audio_interfaces/rednet_2/
 
 
Lynx
 
http://www.lynxstudio.com/product_detail.asp?i=1
 
 
Apogee
http://www.apogeedigital.com/products/rosetta-series.php 
  
  
 
RME (weakest in this class..has not as so good converters as the rest)
 
http://www.rme-audio.de/en_products_fireface_ufx.php
 
http://www.rme-audio.de/en_products_fireface_800.php
 
http://www.rme-audio.de/en_products_hdspe_aio.php
 
 
 
 
 
 
 
Check price tag...You will see you get a lot of hardware choosing E-MU 1616M

Last post is quite old but hopefully this will help others still having issues with 1616m.

Here's what I did:
1. Disable on-board sound
2. Uninstall HDMI sound driver (on my 69xx series graphics card)
3. Install the beta drivers from 2010 located here: E-MU PCI/PCIe Windows 7 Beta Driver - June 2010 (0404/1212M/1616/1616M/1820/1820M)
4. Not sure if it changed anything but I also set E-MU PatchMix DSP to compatibility mode XP SP2

Hope this helps!
Moridin


PS the reason I use this "old" BETA driver is if you look in the wdma_emu.inf (EmuPMX_PCDrv_US_2_30_00_BETA\Binary\Drivers\wdm) of the release version and BETA you will see the release is 1 year older...seems like someone may have screwed up when packaging the released version...

BETA: EmuPMX_PCDrv_US_2_30_00_BETA - Modified Date:23 February 2010 Version: 2.12.0006.5
Release: EmuPMX_PCDrv_US_2_30_00 - Modified Date:23 February 2009 Version: 2.12.0004.5

Alas! I still get the BSODs. Almost makes want to switch to Reaper... Almost. I'm beginning to think the only fix may be a new interface.

SoundIT


Hi guys, it happens to my comp too :/ I have almost the same configuration an Spencil (Gigabyte H67 Motherboard  and i5 2500K) 


Is changing an interface the only solution? I tried everything and I guess testing it with compatibility mode , new drivers etc. won't help. EMU sucks, cause they are definitely loosing their customers (maybe me too?). It takes away your power while composing and makes you very frustrated... so, I'm wondering what is the final of this issue? Have you changed your interfaces?

Yes...changed to a Tascam US-1800 and couldn't be happier.  It feels so good doing sessions without having the feeling of walking on egg shells.

OK I skipped to the end so I may have missed this somewhere. Are your PCI slots native or bridged from the PCIe controller? The block diagram (showing PCIe to PCI bridge) in your motherboard manual or an email to Gigabyte support might clear that up if you do not know. Bridged PCI is the most common way to do it on newer motherboards, and has resulted in problems with a lot of the old PCI cards. If this is a hardware problem and no new drivers will be coming, then it may be insoluble in your present machine.

Sandmännchen


We all know that EMU is dead. Creatives only interest are new consumer soundcards. If you can grab one, i suggest to take a 1212m pcie,
Windows 8 64 bit and the latest  beta driver from 8 Aug 2012
http://support.creative.c...nDriverType=11#type_11

Yeah, ok, but does it work and if you can confirm it? Actualy EMU doesn't deserve to buy another their product but I guessI don't have much time to learn nothing more, but who knows...  Actualy I've got 1616M PCIe and its their newest driver...

No bashing, i`m using the 1616m PCIe in my actual setup. I´m very satisfied with the sound quality and the patchmix possibilities, but the driver support lacks. And yes, for the money you can`t get wrong (used 1616m PCIe here in Germany ca. 250 €) - but only if it really works in your concrete system.
Another website about EMU products: http://www.productionforu..com/viewforum.php?f=114

I have 1212m PCI. I also had BSOD (IRQ_LESS_bla-bla... & ha10kx2k.sys). Installing latest 1212m PCI-E (yes, pci-e) from emu(dot)com for win7(64) actually solved my problems =) Hope it helps:)

Bear in mind that BSODs are caused by drivers.  Buggy drivers.
 
Have you tried running the M$ Driver Verifier over the EMU drivers?
 
http://support.microsoft.com/kb/244617/en-gb
 
Have the EMU drivers gone through the WHQL testing, do you know?  The WHCK (formerly WLK) test suite is actually very good and shakes out a lot of buggy driver problems.  I'd be quite surprised if a Microsoft certified driver was buggy enough to cause BSODs.

My current motherboard, which is now discontinued, has only one PCI slot.  The rest are PCIe slots (X16, x8, 2 each and 3 X1 slots for Firewire, audio, etc.  But it screams with 32 Gb of ram.

I have been using an 1820m pci since Feb 2005. I do not recall having a BSOD directly related to the emu.  I have had sonar crash cuz of the midi driver. But not for months. Using 8.5 and X3.
 
I had some issues with midi-yoke a few years ago.  IRQ not less....
 
So, been using this interface with XP, Vista, 7, 8, and now 8.1 with all updates.
 
Currently: Windows 8.1, 1616 pcie 32 bit beta driver, 44.1 / 24 for settings.
 
I use WhoCrashed to learn which part of the driver is stealing the joy. it usually indicates the MIDI portion of the driver.
 
I remember once-upon-a-time sonar grabbed the strip names. But now I have to add the driver names to Sonar.
 
I use loopbe virtual midi cable.  I used to use loopmidi but it crashed sonar. I think this is a windows 8.1 thang.
 
However::::::
This past summer the audio was not working correctly. Was getting snaps and such. I do not remember if BS'sOD were involved. I replaced the three capacitors that were bulging and leaking and became a happy camper again.
 
Again: I have been using the 1616 pcie 32 bit beta drivers with my 1818m pci interface. And version 2.2 of patchmix. Windows 8.1 64.
 
Have not tried the 64 bit drivers.
 
Using the MIDI ports, and the ADAT ports, and the mic inputs, and some of the audio I/O ports.
 
I did make sure the emu was using a dedicated IRQ.
 
Just tried clicking all the buttons in sonar a lot, quickly, and just got a bunch of auto-saves.
 
Lately I have been having a problem with IE stealing the sound driver, even though I have all the settings to not be exclusive. This results in Sonar displaying an error. No crashes.
But sure is annoying to open the help file and lose audio I/O with sonar x3.
This does not occur with 8.5. Good thing cuz I often record from browsers into sonar.