HD Native on Win7 - 9094 & 9129 errors

[adassumpcao]

Hi!

Well this Win 7 installation is not fresh, I had already a previous system with Cubase on it. But in terms of drivers they are the most recent Intel drivers (chipset, graphics, sata, and so on...) and NVIDIA drivers (for the NVIDIA 7200 GS). I've updated them during this process.

Also I've disabled all unneeded peripherals on the BIOS, including the extra ethernet port.

I've also check the IRQ tables on the System information. I've verified that tjhe UAD card is on IRQ 17 sharing with other peripheral, and the HD Native is on IRQ 16 sharing with the Graphics and lots of chipset stuff. I've tried to swap the Native card PCIe slots to try to manipulate the attributed IRQs but with no success, because the only port it can be switched with is the graphics card slot, and I think they must share "virtual IRQs".

This is what I've done so far.

What I can really do, is try to do a fresh win7 installation and see if it solves the problem.

What do you advice?

Thanks for the support!

[Shan]

Originally Posted by adassumpcao

Hi!

Well this Win 7 installation is not fresh, I had already a previous system with Cubase on it. But in terms of drivers they are the most recent Intel drivers (chipset, graphics, sata, and so on...) and NVIDIA drivers (for the NVIDIA 7200 GS). I've updated them during this process.

Was the system working fine prior to the NVIDIA driver updates? Some NVIDIA drivers have a history of not working well with Pro Tools over the years. Try using the default windows driver for the graphics card during your trouble shooting process and take it from there.

Shane

[adassumpcao]

No. The HD system is new. I've brought every driver up to date exactly to try to solve this problem when I first installed it!

[filosofem]

Personally, I would suggest creating a new partition for Pro Tools only. Can you post what motherboard you are running? Generally, after installing Windows 7 and SP1 (from disc if you can get it - not from Windows Update), there should only be two drivers LAN and Graphics, the rest will be installed by Windows.

Where is the Native card seated? Avid recommends seating in the second PCIe slot next to the graphics card. Meaning seat the UAD card down the line.

[adassumpcao]

I have an Abit IP-35 motherboard. I know it's an old motherboard, but I've kept it because it has been a great hardware setup for sound applications, very stable with my G-SKILL ram and Q6600 quad core CPU. No complaints so far, and usually when I have any problem is driver or software bug related.

Well, I don't have many choices to switch PCIe slots, since i'm a bit limited to the slots I can use.

I can effectively switch the HDNative card for the Graphics, which are now in this order exact, top->down. But I originally had them on the inverse order and I still had the same problems. The UAD card will have to be on the top slot because of these 3 cards it's the one that will fit the PCIE 4x slot, the others must be fitted on the PCIEXP 16x slots.

I guess my next try will be to format everything and try to install everything from scratch! :/

[adassumpcao]

AVID as launched an update to Protools (10.0.1) and a firmware update to HD Native.

For me that solved all the problems I had with -9129 errors!

I still got one specific -9129 error but that was caused by the Sans AMP plugin that maybe somehow broken and cause this error when the clip it was on had no more audio to play. Disabling DAE errors corrected this problem with no audible audio problems.

Hope it helps!

Thanks for listening AVID!!!

[filosofem]

What are your Playback Engine settings?

[jonathan jetter]

Originally Posted by adassumpcao

Hi!
...and the HD Native is on IRQ 16 sharing with the Graphics and lots of chipset stuff....

this seems to me like it could easily cause the problems you're describing.

i have my HD Native card on an IRQ that is only shared with the 1394 controller (which i'm not using anyway), and i spent 2 hours to see if i could force a -9094 error (i couldn't do it, except for Slate FG-X, which is a known issue)

edit: just read what you wrote above- glad your problem is fixed!