Error messages

ADM_DIO_ERROR_OCCURRED, DIOerr:PMDIOUtils::GetAVSyncOffset-failed GetAVSyncOffset lava command with status:kLFTTimeout

Exception: std::exception, what: “Bus error” in thread “Async packet processing thread”, at address  OxO

Exception: FATAL ERROPR, msg:ASSETION FAILED:ERR = = NOERR, FILE:/SNAPSHOTS/RELENG.RELENGINTEL1>1214361138/VOBS/PPG/MCTOP/PROJECTFILES....

PMDIOUtils::GetrAVSyncOffset – failed GetAVSyncOffset I ava command with status: kLFTimeout

ADM_DIO_ERROR_OCCURRED
AssyncFileOHelper::ReadStreamAsync async file system error.


I have been getting these for days.

Each time an error like this happens, first the Avid locks up..then after about 30 seconds it shows an error. If I hit quit there’s another 30 seconds and it slowly starts to save & shut down. If I then restart my DNA box and restart the system I can go back to work...for about another 1/2 hour.

I’m running Tiger on a Quad Core Intel with a DNA box using the 3.0.1 software for Tiger release. I’ve reinstalled my system (Archive & Install) and my application..twice.

This happens whether the media is on my Avid raid or external firewire drives...

I'm suspect it's a hardware problem...but I'm looking for insight.

Any thoughts out there?

                                  
><({(º>

at Filet

 This looks like it may be a problem with the Reference going to your DNA. Do you have house reference hooked up?

Sounds like corrupted projects or corrupted media to me.  I had a project awhile back that was going bannnas like what you're showing.  The followed fixed it completely.

Created a new project & moved the old bins(.avb) and project file(.avp) into it... trashed the rest.

Deleted all the pre-computes... even the ones I was using.

Deleted all the database files and rebuilt them.

Crystal clean after that...

My reference appears good.

And trashing teh databases is natural..and done again & again.

Also, no precomputes to trash as this is just in the raw cutting stage.

But I'll try creating new bins and a new project just the same...and I'll let you know! Thanks!

Well..almost a couple of weeks now and I’ve tried the whole “new project” thing...even new timelines and bins...which, I’ll admit, seems to have slowed down the issue. But still..every couple of hours..lock up. Fortunately, if I’m patient, it allows me to save. I quit, restart my DNA and open the app again.

I can say (for the moment) it seems localized to HD projects...possibly P2 card – HD projects.
                                  
><({(º>

Fish,

Where are you storing your P2 data?

I'm still thinking this is a problem with your ref. Can you disconnect it and run on internal ref for a while and see if anything changes?

Fish...You don't have a 30" Monitor connected..do you?

I have a 13" monitor connected via SDI.

I have a Wave form & Vectorscope connected to the output of my D-Beta

I have no 30" monitor connected to my system (although I'm not sure what that would do ..please enlighten me)

I can post samples ..stand by...

Don't worry. Avid just confirmed a bug caused by that monitor and I was wondering if you fell into that category.

Thanks. 

Do you have any other FW devices attached other than the DNA?

You know, I am having the exact same issues now working in an HD project.  I have been running 3.01 in NTSC projects with hardly and problems for a couple of months, and then suddenly, everything seems to fall apart in HD.  Same errors as listed above.  I am always able to save before I have to force quit (thankfully).  Yesterday, I must have crashed 25 times (of course on the day when I had 8 clients in my room).  Its starting to sound like an HD issue, doesn't it?

Sure does...

Yes I do....but I don't think its teh firewire because I don't always have them attached when it happens...but I'll try and confirm.

Don't worry. Avid just confirmed a bug caused by that monitor and I was wondering if you fell into that category.

I haven't actually been able to get an Apple 30" screen to display any signal on it through the port on the back of the HD card like I'm supposed to...never have (which hasn't been a priority but I'd really, relaly like to be able to do that.

Is that bug related to that?