MOTUnation.com

Hello, I'm posting today because I am having issues installing an old MOTU 2408 running through a PCI-424e card. I currently have a working copy of Pro Tools 9.0.6 installed on a Windows 7 32-bit home brew computer. I have Sandra details posted at the end of the post.

The problem I'm having is that I cannot get Pro Tools to recognize the audio device. I keep getting the "ASIO device could not be initialized" notice. I've installed the hardware and drivers on my computer, and although I'm able to bring up the MOTU PCI-424 Audio Console menu, and it seems to be recognized by the computer, I cannot get Pro Tools to do the same. When I try to run it through Reaper, it sees the audio device, but does not record any signal. The 2408 is clearly receiving audio in the meters, but I can't seem to get it to the computer. Another note, is when I go to change the banks in the MOTU Audio Console menu, it freezes the program, and makes the cpu so sluggish it takes over 5 mintues just to open the Task Manager and force close the program. I've tried switching the PCIe slots with no difference.

I've installed the card on another Windows 7 64-bit cpu, and everything is recognized, but putting any amount of large load on the cpu's resources causes PT to become jittery, and unstable way before it should be. Apparently, this MOTU system worked prior to switching to Windows 7, but every place tells me it should work now.

To me this all sounds like a driver issue, but I've dilligently followed the instructions for installation and I'm having no luck. I'm posting this message at the Avid forum as well, as I desperately need to get this system working. Everything tells me I shouldn't have a problem with this set-up, but here I am... Thanks for any help in advance. -Chris

SiSoftware Sandra

Computer
Model : System manufacturer System Product Name
Workgroup : WORKGROUP
Host Name : Chris-PC
User : Chris

Processor
Model : AMD Athlon(tm) 64 X2 Dual Core Processor 4200+
Speed : 2.2GHz
Cores per Processor : 2 Unit(s)
Threads per Core : 1 Unit(s)
Type : Dual-Core
Integrated Data Cache : 2x 64kB, Synchronous, Write-Back, 2-way, Exclusive, 64 byte line size
L2 On-board Cache : 2x 512kB, ECC, Synchronous, Write-Back, 16-way, Exclusive, 64 byte line size

Computer
Mainboard : Asus A8V-XE
BIOS : Phoenix Technologies, LTD ASUS A8V-XE ACPI BIOS Revision 0702 09/25/2006
Bus(es) : X-Bus AGP PCI PCIe IMB USB FireWire/1394 i2c/SMBus
Multi-Processor (MP) Support : No
Multi-Processor Advanced PIC (APIC) : Yes
Total Memory : 2.75GB DDR

Chipset
Model : ASUS K8T890 CPU to PCI Bridge
Front Side Bus Speed : 2x 1GHz (2GHz)

Chipset
Model : AMD Athlon 64 / Opteron HT Hub
Front Side Bus Speed : 2x 1GHz (2GHz)
Total Memory : 3GB DDR
Channels : 2
Memory Bus Speed : 2x 157MHz (314MHz)

Memory Module(s)
Memory Module : Corsair VS512MB400 512MB DDR PC1-3200U DDR1-400 (2.5-3-3-8 2-11-0-0)
Memory Module : Corsair VS512MB400 512MB DDR PC1-3200U DDR1-400 (2.5-3-3-8 2-11-0-0)
Memory Module : Corsair VS1GB400C3 1GB DDR PC1-3200U DDR1-400 (3-3-3-8 2-11-0-0)
Memory Module : Corsair VS1GB400C3 1GB DDR PC1-3200U DDR1-400 (3-3-3-8 2-11-0-0)

Video System
Video Adapter : Radeon X1300/X1550 Series (Microsoft Corporation - WDDM) (PS3.0, VS3.0, 256MB, PCIe 1.00 x16)

Graphics Processor

Storage Devices
WDC WD800JB-22JJC0 80GB (ATA100, 8MB Cache) : 75GB (C:)
WDC WD800JB-22JJC0 80GB (ATA100, 8MB Cache) : 75GB (D:)
PIONEER DVD-RW DVR-116D (ATA66, DVD+-RW, CD-RW, 64kB Cache) : N/A (E:)
SNEJQ Q30LAJ49Q (SCSI, BD-R, HD-DVD-R, DVD+-R-DL, CD-R) : N/A (G:)

Logical Storage Devices
Hard Disk (C:) : 75GB (NTFS) @ WDC WD800JB-22JJC0 80GB (ATA100, 8MB Cache)
Studio (D:) : 75GB (NTFS) @ WDC WD800JB-22JJC0 80GB (ATA100, 8MB Cache)
3.5" 1.44MB (A:) : N/A
Optical Drive (E:) : N/A @ PIONEER DVD-RW DVR-116D (ATA66, DVD+-RW, CD-RW, 64kB Cache)
Optical Drive (G:) : N/A @ SNEJQ Q30LAJ49Q (SCSI, BD-R, HD-DVD-R, DVD+-R-DL, CD-R)

Peripherals
LPC Hub Controller 1 : ASUS Standard PCI to ISA Bridge
LPC Legacy Controller 1 : ITE IT8712F
Audio Device : ASUS High Definition Audio Controller
Audio Codec : Analog Devices AD1986A sound chip
Serial Port(s) : 1
Parallel Port(s) : 1
Disk Controller : ASUS VT8251 AHCI/SATA 4-Port Controller
Disk Controller : ASUS VT82xxxx EIDE Controller (All VIA Chipsets)
USB Controller 1 : ASUS VT82xxxxx UHCI USB 1.1 Controller (All VIA Chipsets)
USB Controller 2 : ASUS VT82xxxxx UHCI USB 1.1 Controller (All VIA Chipsets)
USB Controller 3 : ASUS VT82xxxxx UHCI USB 1.1 Controller (All VIA Chipsets)
USB Controller 4 : ASUS VT82xxxxx UHCI USB 1.1 Controller (All VIA Chipsets)
USB Controller 5 : ASUS VIA VT8251 USB EHCI Controller
FireWire/1394 Controller 1 : NEC uPD72874 IEEE1394 OHCI 1.1 3-port PHY-Link Ctrlr
SMBus/i2c Controller 1 : VIA VT823x SMBus

Printers and Faxes
Printer : Microsoft XPS Document Writer (600x600, Colour)
Fax : Microsoft Shared Fax Driver (200x200)

Network Services
Network Adapter : VIA Rhine II Compatible Fast Ethernet Adapter
Wireless Adapter 1 : D-Link DWA-125 Wireless 150 USB Adapter (802.11g (ERP), TKIP, 24Mbps)

Power Management
Mains (AC) Line Status : On-Line

Operating System
Windows System : Microsoft Windows 7 Ultimate 6.01.7600
Platform Compliance : x86

Windows Experience Index
Current System : 4.1

Performance Enhancing Tips
Warning 100 : Large memory sizes should be made of Registered/Buffered memory.
Tip 2546 : Large memory modules should be ECC/Parity.
Tip 2 : Double-click tip or press Enter while a tip is selected for more information about the tip.

I had the same message when I tried to install PT 10 using 2 MOTU 1010s. Seems PT didn't like to have 2 cards in the same PC chained together. When I switched to a single PCI424 card (with a 24 I/O) the problem was solved.

The easiest and actually best way for me to check on a remote (read: your) system is if you've had BSODs in the recent past.

If you have a folder C:\Windows\Minidump with files in it, then copy the files to any other folder. Zip or rar these files then. Upload the zip or rar to Rapidshare or any other online host and paste a link here to it. I'll analyze the crashes and why they've happened, and this in turn will stabilize and perhaps perfect your system.

Basically, it is a first step troubleshooting process. Any system having BSODs must be fixed so they don't occur and the added benefit is clearing any and all driver problems should they have existed.

I'm afraid I haven't had any BSODs in the recent past. The most recent was in July of 2011. Would this still be useful?

Yeah, sure. It can't hurt. Worst case scenarios are that I'll advise to update a driver that you already did since, or to remove a driver that might have already been removed.

Since you haven't had a BSOD since July though, it's likely your machine is fairly stable but ya never know what I'll be able to see wrong by looking, still.

http://www.sendspace.com/file/b7itxq

Thanks!

Yeah, quite a few issues as it seems.

1) Sptd.sys is used by Daemon Tools and/or Alcohol. This file is not just a little bit, but extremely notorious for crashing Windows 7.

As in 100% of bsod cases, I advise to remove it using the installer/uninstaller found at the following link. While using, be careful not to choose update, but rather actually choose uninstall.

http://www.duplexsecure.com/download/SP ... 80-x86.exe" onclick="window.open(this.href);return false;


2) The following Presonus drivers are quite ancient by Win7 standards. Advise to update them:


PreSonusUsb_xfer PreSonusUsb_xfer.sys Mon Feb 18 16:53:48 2008
preSonusUsb preSonusUsb.sys Mon Feb 18 16:59:35 2008

http://www.presonus.com/" onclick="window.open(this.href);return false;

3) Very much recommend updating this wireless network driver from the manufacturer of the adapter. Wireless drivers older than Windows 7 initial release date are extremely notorious for system problems, including bsods:

netr28u netr28u.sys Thu Apr 16 23:27:09 2009

4) You guessed it - another extremely notorious file. I'm guessing you have an ASUS motherboard. So head on over to their website for your specific board. Download/install the latest ATK0110 driver available which will replace this ancient driver:


ASACPI ASACPI.sys Thu Aug 12 22:52:52 2004

If ATK0110 is not available in drivers or utilities, please let me know and we will easily figure out what to do about this.

5) Very old video driver here:

atikmdag atikmdag.sys Fri Apr 24 06:50:20 2009

Please update from here:

http://support.amd.com/us/gpudownload/w ... ng=English" onclick="window.open(this.href);return false;

(You can read the info on why this is a Vista driver, on the page. It is the correct one for you to install.)

6) Very much recommend to completely uninstall PC Safe Doctor which will in turn remove this ancient driver you don't want on the system at all:

anodlwf anodlwf.sys Fri Mar 06 05:09:51 2009


-------------

These above changes are excellent to make and your system will benefit greatly from it, regardless if they happen to fix your initial problem that you posted about.

Good luck and please keep us informed. If you run into any problems or troubles, don't sweat it. It's all good. We'll make it proper.

Actually missed one more ancient driver needing an update:

fetnd6 fetnd6.sys Thu Jun 19 07:45:41 2008

This is to your VIA ethernet (network). You can update from the following link. Check the device manager for the type if you aren't sure which it is:

http://www.via.com.tw/en/support/drivers.jsp" onclick="window.open(this.href);return false;