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.

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!

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.

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:

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...

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

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.

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.

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.

a couple suggestions -

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