PROBLEMS WITH MOTU 828 mkII FIREWIRE & WINDOWS

[egutierrez]

Hi everyone, I recently purchased an used Motu 828 mkII Firewire interface, and it worked perfectly in the beginning with my PCI VIA Chipset firewire interface card, but suddenly it started crashing (MOTU and computer). After reading some posts, I decided to buy a new firewire card with Texas Instruments chipset... so I did, and now I'm working with a Lacie with TI.

It started working correctly, but after a couple or three weeks, it started with the same problem: the card crashes, and the computer crashes too. I'm working with Windows XP and SP3.

As a curiosity, if I power my MOTU on when the computer is working, it blocks the CPU use for a couple of minutes or three. If I switch the MOTU before powering the computer on, it doesn't happen... but in both cases, I'm having the same "crashing" problems...

Can anyone help me ?? Thank you very much in advance... Cheers from Spain.

Emilio.

[XYZ]

I assume you have updated to the latest FW card drivers, I assume you have the latest MOTU driver.

Did you check

the event viewer [both application and system]? Sometimes this can tell you what Windows doesn't like. I used to insist on a clean event viewer window, this would seem to get me a more reliable and robust install.

[apefist]

I'm using the MKii Firewire on XP64 and Windows won't recognize the Firewire connection. Whenever I try to open one of the FW interfaces MOTU installs, it says there isn't anything there, EVEN though it's plainly there in my device manager. Also, when I try to open a file in my DAW, when I go to change the driver to Motu FW 64, it says nothing is connected. I've been dealing with this for the whole day today when I should have been recording something by now. I'm using the latest (March 2009) drivers for the MKii Firewire, I'm running XP64 which in the driver specs it says that's fine. What the heck? This is extremely frustrating, and I'm about to return the stupid thing and buy an equally frustrating (as far as drivers go) M-Audio product because at least they make no effort to claim they will ever be up-to-date on drivers. MOTU did the whole press release and everything, then when it's crunch time...uh...nothing...

Help?

[XYZ]

What does the event viewer look like? Did you try a different cable? Try power cycling the 828?

Yes, I'm with you about being frustrated with this type of thing. I've quelled my lust for the latest and greatest and now I wait for 2 revisions of OSes, Drivers, etc before I upgrade, unless there is a feature I just can't live without [and since I'm living without it now...].

Anyway, that won't help you today.

Some more ideas are to create another clean test account and try using it, and try installing it from that account. Won't take long, and if it works you have isolated your problem.

[Mark S]

for mkII units, I wouldn't use anything later than the 3.6.7.x drivers. They are stable and made for this hardware. Later ones will work but will double your latency and won't give you the lower buffer settings of that driver. (I have a via chipset in my computer too)

My pre mkIII hardware will crash my system too but only if I turn it off before shutting down the system.

I also do not recommend sp3.

Having said all that, I think I would opt for a clean install of Windows with a careful step by step with your hardware to see if something is conflicting (and a list of your system would be helpful here too.)

[Mark S]

I'm using the MKii Firewire on XP64 and Windows won't recognize the Firewire connection. Whenever I try to open one of the FW interfaces MOTU installs, it says there isn't anything there, EVEN though it's plainly there in my device manager. Also, when I try to open a file in my DAW, when I go to change the driver to Motu FW 64, it says nothing is connected. I've been dealing with this for the whole day today when I should have been recording something by now. I'm using the latest (March 2009) drivers for the MKii Firewire, I'm running XP64 which in the driver specs it says that's fine. What the heck? This is extremely frustrating, and I'm about to return the stupid thing and buy an equally frustrating (as far as drivers go) M-Audio product because at least they make no effort to claim they will ever be up-to-date on drivers. MOTU did the whole press release and everything, then when it's crunch time...uh...nothing...

Help?

since you are using a 64 bit os i would start a new thread for this one.