828 MKII + ADAT + Cubase SX3.1 bluescreen crash

fnord · Post by **fnord** » Fri Oct 28, 2005 5:42 am

Hi everybody..

I'm having trouble with using the FW Audio Console from the Cubase VST-Audiobay. Sometimes when I change latency or the ADAT ports and close the console to get back to Cubase I get a bluescreen of death in the MFWAWAVE.SYS. Cubase.log dumps an error in the MFWAasio.drv.

This is especially disturbing because I use the Alesis AI3 ADAT I/O converter for extra eight analog inputs and outputs. After every reboot Cubase forgets about these extra ports unless I reopen the FW Audio Console and hit OK to get back and reset the VST-Inputs and -Outputs in Cubase. Suddenly the extra ADAT ports appear (until next reboot).

The problem with Cubase dropping the ADAT ports was always there and I could somehow arrange but the bluescreen crash happens since I upgraded to Cubase SX3.1.

Now for the fun part: Motu's highly praised Windows support tells me their drivers are ASIO compliant and that I need to get in touch with Steinberg. Steinberg tells me since the error occurs in the Motu drivers it's something they need to fix. My feeling tells me that Steinberg is right about this.

I can only subscribe to other postings I've read here from Motu customers who use Windows. We paid way too much money to get support like this. Motu should drop Windows and only go for Apple. The decision for "supporting" Windows is only for making extra profit. But frankly, the loss wouldn't be so bad because I can't see any Windows user every thinking about buying a Motu product again. Not with drivers like this.

Still, I'm stuck with this unit (which is basically exactly what I need) and I'd appreciate any support from other users who might have the same or similar issues.

Thanks,
fnord

cybergrass · Post by **cybergrass** » Mon Jan 16, 2006 1:50 am

I have the same Problem, how do you fix the Problem ?

fnord · Post by **fnord** » Sat Jan 28, 2006 3:47 am

I didn't.... MOTU support won't help either. They keep blaming Windows..

Smokehouse · Post by **Smokehouse** » Sun Jan 29, 2006 1:54 pm

I just started encountering the same issue of bluescreen traced back to MFWAWAVE.SYS -- after more than a year of flawless operation. And just before this started, I too had the issue of the system not recognizing the ADAT channels unless I went into the MOTU FireWire Audio Console hit OK. Unlike the other poster, I running CakeWalk Home Studio 2004 (so it's definitely NOT Steinberg/Cuebase).

So what changed recently in my system? First, I use a laptop provided by my employer, so I do not maintain a separate system for recording (as of course any purist would do.) That said, there was a Windows security update (I keep Windows very current on my system) that automatically installed on my system last week, and the company uses Cisco Security Agent (CSA) on all machines, and an updated version of that was installed last week as well. Not sure which of these two is the problem, but I'm guessing that it's one of them.

I have requested a fresh system build image for the laptop, and I will install things from the ground up. Of course, I will have to install the most current Windows patches and CSA security agent, but at least I can rule out some other random driver cruft. If the problem persists, I will ask for an older version of CSA installed. If that doesn't work, then it's Windows and we can expect to have a large number of other people complaining about this.

Please let me know if this triggers any insight into out shared problem. I'm bumming, but trying to stay positive.

Eric

fnord · Post by **fnord** » Thu Feb 02, 2006 12:04 am

Hi Smokehouse,

three is company

I'm sure there are more people out there who experience this problem (maybe some haven't noticed yet). We just have to gather up and keep bugging Motu to do something about this. It's definitely not the problem of the audio sequencer rather than something deeply hidden between Windows and the MOTU drivers. I don't think it should be our task to prove to MOTU that the problem doesn't lie entirely within our scope. But this isn't the way to go anyways because MOTU sticks with their point that it works on their SP1 reference platform so it's our problem if we're using anything else.

When MOTU support keeps getting more of these complaints support might be willing to escalate this to their engineers for their own sake. A single person will probably just get the same answer like I did: Sorry pal, why did you have to screw up your Windows. Use a fresh&clean SP1 install and it will work. Which is true but unacceptable in many justified cases.

fnord

StickS · Post by **StickS** » Sat Jul 22, 2006 2:09 am

Let's make it four. I'm also running Cubase SX3...but it's definitely not Cubase. I had it fixed at one time, unfortunately, I can't remember what I did to fix it. I do remember that I went into MSConfig and unchecked MFWAKeys under the startup Tab. But I recently loaded the 3.6.7.0 drivers and the problem started again...worse than before.

I checked my IRQs and noticed it was sharing with a wireless network card, so I moved the card to another PCI slot. I'll try to post back if it seems to work.

StickS · Post by **StickS** » Sat Jul 22, 2006 8:39 am

Simply put...NOPE.

StickS · Post by **StickS** » Sat Jul 22, 2006 4:12 pm

okay...tried the XP Firewire fix from Microsoft.com Knowledge base:
Links:
KB885222 and KB904412

In that order. I'll let ya know if that works.

StickS · Post by **StickS** » Mon Jul 24, 2006 6:32 am

That didn't work either. I tried something else also. I disabled the 1394 Network connection, that didn't work either. Still getting the blue screen of death.

WTF MOTU, I thought new drivers were supposed to be an improvement? As much as I love my 828mkii, this is getting a bit ridiculus.

StickS · Post by **StickS** » Wed Jul 26, 2006 6:28 am

Alrighty, it's been a couple of days now since my last little experiment, and it hasn't crashed. This is what I did:

Turned off the 828mkii.

I uninstalled the drivers using the Add/Remove Programs in the Control Panel.

Then I ran RegEdit (using the Run in the Start menu). This is the Registry Edit program. I highly suggest that you save your current Registry as you can really screw up your system.

Next, using the Find tool (under Edit) I searched for MOTU and deleted every key that referred to MOTU (deleted the folder)

Then I did the same thing after searching for 828mkii

Then I rebooted and loaded the newest 828mkii drivers. I did get an error once, so I uninstalled and reinstalled the drivers, I'm not sure if this will happen to everyone.

Rebooted and turned the 828mkii back on while rebooting

I had to go to the hardware manager and "update drivers" for all the MOTU stuff.

Disabled MFWAKeys in Task Manager since I'm not using a footswitch or anything (ran MSConfig and disabled it in the Startup tab also)

It's been two days and no Bluescreen...If it happens again, I'll post up

StickS707 · Post by **StickS707** » Fri Oct 13, 2006 6:09 am

I forget why, but I had to reload XP (unrelated to the MOTU problem). I ended up not putting Norton Internet Security on the system (yes, this is my main system for now...I'm a hobbyist, sue me

). All was good, until I decided to put NOrton back on. Now I get intermittent restarts. Sooo, I think I'll do my previous fix and if that doesn't work, I'll unload Norton.

mke52 · Post by **mke52** » Fri Oct 13, 2006 8:40 am

Well fnord, you were much more polite in you thread that I was. I am just sick & tired of this useless product!

I have the same problem with the Traveler and it is suerly not a cubase problem. The issue is with Windows. I also tried loading the updates for firewire; it improved a little but not much. I no longer have blue screens but I get clock problems: crackles and periodic sound gaps with high frequency whistles.

The thing that drives me crazy is that there are a lot of windows users that don't have this problem so it must be related to the configuration.

One thing you can do is go into the contro panel/system/hardware/device manager and check your firewire device for conflicts with other hw you might have.
Obviously I am assuming you have a Texas Intruments chip on your firewire card although I brought one (the second one) and it doesn't even work with the recomended chip.
I have also been told thatthe MOtu drivers tend to get along better with XP pro rather than home edition and that the poor sound card seems to be allergic to SP2.

I'm also thinking of buying a cashmere blanket so my poor little motu won't catch a cold.
Oh, one last thing; wait until mid November to do your tests; we're moving into Scorpio and motu is just not compatible with that sign.

I joke not to despair. I'm presently -880 euros and no soundcard.

fnord · Post by **fnord** » Sat Oct 21, 2006 2:34 am

Yeah- I can pretty much relate to this. After reading all of these stories my conclusion was to save up money for either a RME Fireface or a Mac Pro and never ever thinking about buying a Motu product again. (Still saving

Regarding the problem, I am surviving somehow after digging here and there not really knowing or understanding what helped it. Windows repair install, cleaning the registry, trying some related hotfixes - whatever. (I'm still with the Adaptec Firewire card with the TI chipset.) I don't think these a definite way to fix these issues except for really getting into the drivers which none of us can do. RME proved it can be done even under Windows. So all I can recommend is don't waste your precious time and rather make precious music

fnord

Airstorm · Post by **Airstorm** » Sun Oct 22, 2006 1:31 am

I have been plagued with blue screen crashes to the point of not doing anything creative for fear of losing it. although in my case... I am using the 2408Mk3 with PCIe 424. Tried the whole reinstall-the-drivers routine & everything else I can think of. I knew I was in trouble when I opened the box & saw that they included some nice studio software with the system.... If you had a MAC! I won't buy another product from this company. It's really a shame too, because the sound quality and connectability are stellar.

System:
AMD FX55 processor
ABIT MB, Nvidia chipset with 1.5G DDR memory
Windows XP pro, SP2 (although I haven't let it update since March)

I have noticed that it seems to happen when MIDI is somehow involved, like when I reset a MIDI device in Cubase. For that I am using a Marian Marc 8 PCI card, so I don't know if that might not be the problem, although I don't think so. The logs show MOTU files & memory errors that say something like "IRQ not less than or equal to...." I've checked for conflicts & swapped stuff around (both hardware & software), & I have the Windows HAL installed as a regular PC so it doesn't do the automatic interrupt selection. Hopefully something gets resolved soon, or I might suggest that people start contacting the Better Business Bureau. Maybe that will get their attention.

Regards, Storm.

P.S. Anyone notice there is not a single reference to blue screen crashes anywhere on their website? Hmmm.

GearNostalgia · Post by **GearNostalgia** » Tue Oct 24, 2006 12:55 pm

Airstorm. That sounds serious. I was this close to getting a Motu 8pre before I read your post. I have an AMD and Athlon system and I definitely don't need blue screen crashes, hope this get sorted out soon or I am just forced to go with another brand.