PCI-424 Dead?

[Fury]

Apologies for running in and immediately asking for advice, but this is an odd one and others are also having the same issue here (http://www.gearslutz.com/board/music-co ... s-7-a.html" onclick="window.open(this.href);return false;) all report it began yesterday/today out of the blue.

Yesterday I found my system won't boot past initial XP splash screen just after post if either the PCI-424 is seated whilst drivers are installed

spent an hour or two last night changing PCI slots/IRQ's.. removing/reinstalling drivers via every method I know (including removing motu related driver files manually via safe mode), no dice... if the cards in, then driver installation hangs, if installing drivers first without card then inserting it after restart it's back to splash screen hang.

My machine never connects to net (so no MS update issue) and I haven't changed config at all recently I also tried reimaging my system from a ghost image taken 2 weeks ago, just to be sure it couldn't be a software issue

I refuse to believe the card is dead (not only due to what seems to be either coincidence or a chain reaction as per the gearsluts posts) but I think if it was a dead PCI424 card it probably wouldn't get to post, 2408mkIII is seeing a connection with the card (as it doesn't sit in converter mode) and windows see's it/reserves in device manager..

Just wondering if anyone else has encountered this or maybe have some advice? (unfortunaltely can't get help from MOTU as I'm in the UK, call cost is prohibitive, and I was lazy/didn't register my Interface so no online support)

[skullsession]

Strange, indeed.

Last weekend, my computer was crash-city in front of a new client. Not cool. Probably 10 crashes in a 10 hour session. But we made it through the session.

Today, I go to boot up and it hangs. Won't boot.

I removed the 424 card to see what would happen. Machine boots. So I uninstall the drivers. Reinstall the drivers. Reinstall the card. No boot.

Called MOTU this morning, and it turns out that they've had quite a few users within the last few hours call with the same problem. They're working on it, but this one's scary. They're saying it's looking like a software problem, and that a new card won't help me.

I've got another NEW client driving 4 hours this coming weekend to start a new album.

I'm....freaked out....to say the least.

[Fury]

You defo need some backup there mate it's either cancel the session or beg/borrow/steal another interface. Looks like its going to be a while in coming but fingers crossed for you, if they're saying it's a software problem (and at this stage they probably do not have a clue so will likely be talking off the top of their heads) then an earlier driver should resolve it. which is the ONE thing I haven't yet tried

[skullsession]

It's strange. I've been using this new driver for a few weeks now. It hasn't been perfect, but it's been working.

It seemed like it got progressively worse as time went on. More like the card had a physical problem that eventually led to failure.

I don't get it.

Maybe it's time for that Lynx upgrade this week.

[Fury]

Things were going well for me with the new driver I had random BSOD's with the previous quite often, normally when opening Kontakt VSTi.

I am kinda fortunate to have a RME Digiface I can use for the time being, but as you can tell I'm just as on edge about this as you, if it was outright dead I could take it.. solution buy a new card (Lynx is a goood choice btw ) but these symptoms, it's just being a big slutty tease... life's just not the same with the MOTU out of action

[Fury]

All the driver downloads related to PCI-424 have been taken down from the MOTU website... somethings happening!

[Roger Boden]

Hi everyone. I'm new here, but I've had the same problems as you guys. XPSP3/PCIx-424. I have a workaround for you all....

1. Remove 424 card
2. Power up PC
3. Set PC date to 11th Jan 2010
4. Power down
5. Re-insert card
6. Power up - voila!!

Done this on two machines in our studio. It's not ideal, but it should work until MOTU post the fixed drivers on their website....

BTW, I tried setting the system clock back to 11th June 2010, and the machine wouldn't start up again. Went through the workaround routine again and everything works fine.

Hope this helps for now.....

Sounds to me that someone has programmed a trap into the driver software - intentionally or otherwise!!

[tormenter]

Just found something on gearslutz - back dating the BIOS by a month worked to help me reboot and use the PCI-424

[Roger Boden]

Just got to remember that for the time being, May 2010 is the month after June 2010...

[skullsession]

Just got word from MOTU.

The new driver is here...

http://www.motu.com/download/download_m ... duct_id=13" onclick="window.open(this.href);return false;

[skullsession]

New driver got me running!

[Roger Boden]

New drivers work for me - for now. I'd love to know what the problem was, but in true MOTU style, there probably wasn't a problem...

I wonder how many people have re-formatted, re-installed, pulled their hair out, lost valuable clients, bought new cards on ebay, lost money over this??

Good job they don't write software for Boeing.........

[VampStudios]

Hi, im new to this forum. I had to join as you have just helped me out massively!
I was definatly one of the people who has spent all of today pulling my hair out trying to get this MOTU 424 to work!

I came into the studio this morning (11th June) and powered up the pc. It started fine but then stopped on the very pretty "windows is starting" page.

I couldnt believe it! I also have a lynx L22 2 in 2 out but i cant record drums effectively with only 2 channels. I had to cancel the days drum recording and spend hours on my hands and knees swapping around pci cards, reading forums and after a ridiculous process of elimination found it was the 424 card causing the startup problem.

Computer would boot fine without the card.
It would boot fine with the card installed but without the drivers.
But with drivers, and card both installed there was no joy at all!

Then i came across this page! The new drivers have sorted it out for me for now as well. But i cannot believe that this has happened! Its almost an attack on MOTU, am i right in thinking someone has created the drivers to fail??!

So every studio in the world woke up this morning to find that their motu wasn't working?
Its crazy! I wouldn't be surprised if lawyers get involved!!

But, thanks for helping me get my motu sorted! Was looking at the SSL Alpha link when things were looking really bad this morning! haha! But for now ill stick with the Motu and lynx!

By the way, you guys were taking about getting a lynx. Id say do it! even if its just the L22. You can sync the motu clock to it and it definatly improves the sound! Worth a look into!

Cheers
Sam From Vamp Studios

[James Steele]

New drivers work for me - for now. I'd love to know what the problem was, but in true MOTU style, there probably wasn't a problem...

I wonder how many people have re-formatted, re-installed, pulled their hair out, lost valuable clients, bought new cards on ebay, lost money over this??

Good job they don't write software for Boeing.........

Yeah... and good thing people don't die when your DAW crashes.

[Stephen Baysted]

Likewise, I powered down yesterday (first time in ages) and tried to restart and Win 7 refused to boot. Went through all the repair options, I even restored an older config, all to no avail. Then, just as I was about to nuke the Win drive, I stumbled across a post in another forum. Put the bios clock back a few days and all boots fine. Not a good 24hours...

Anyway, I'll grab the updated drivers if they're stable.

Cheers