Hello all!

Same issue here. Runing 2018.2 on WIN10 clean installed machine (from last week). The error shows up pretty much every time I press play after putting a locator on a multigroup clip. The resolution is DNx36 (transcoded from Sony FS7) and the audio syncronised are WAV files (4 tracks) imported in PCM (MXF) at 24bit 48khz.

Here are the APPEVENT.LOG and EVENTLOG.LOG: https://we.tl/B7e43dnobe

Hi could you finally solve this?

Could you try to create a new project and move the bins to the new one?

Regards.

     Diego

Hi all,

At one tv station over here these exceptions started popping up after updating from 2018.8 to 2018.11. Systems are on Nexis with Interplay.

Has anyone found the solution to the issue?

Thx

@All: ExceptionCode: 3221225477 is a Windows-level, not Media Composer, error. It means there's memory heap corruption. That is, there's some bad or invalid value in memory Media Composer tries to reference. Then, it crashes.

https://social.technet.microsoft.com/Forums/ie/en-US/e8bad4fa-b640-4a39-ad88-74afda3504de/possible-heap-corruption-detected-exception-code-3221225477?forum=winservergen

Causes are many, but likely include:

1. A Windows update your installed version of Media Composer wasn't ready for.

2. A Media Composer update not written for your version of Windows.

3. Using another program at the same time as Media Composer.

Try some Windows maintenance:

https://answers.microsoft.com/en-us/windows/forum/windows_7-performance/possible-heap-corruption-detected-exception-code/0657809a-a78b-48c7-9e6e-ac8ca97522c2

Then double-check the version of Windows is the exactly the same (down to the update) as the one qualified by Avid for Media Composer. (See the "README" and "What's New" PDF's.)

If your Windows and Media Composer installations are as-specified by Avid, then Avid needs to do some debugging.

Hi Isaac,

Thanks for your reply. These 2018.11 systems are running windows 10 1803 on HP z4 workstations. A fully supported config.

Hi Jeoren, all the upgraded systems are popping up those errors?

Did you try upgrading to upper or lower MC version to see what happens?

Did you try a different NExis client?

Regards.

Hi Diego,

Yes, but some systems more than others. Probably depends on the bins/workflow on the client at the specific time/day,

Nexis client is 2019.2.2 (latest). I have one system still running MC 2018.8 but I do not have enough feedback to be sure if that system does not expose the issue.

I don't think the issue is Nexis client related. Nexis client 2018.11 showed the same issue. I updated to 2019.2.2 to see if it would improve the situation but it seems it makes no difference.

This could be a MC 2018.11 compatibility issue with Access 2018.9 and might check if upgrading to Access 2018.11.1 helps.

The compatibility matrix is stating it needs to be updated.

Jeroen

Oh so it is a MC upgrade in Interplay environment.

Why don't you try to test MC in standalone and then in NEXIS Only mode, to see what happens.

Do you know the console command Workgroup Override?

Cheers!

Hi Diego,

I just decided to go 'by the book'. So updated transfer client, media indexer to 2018.11, access to 2018.11.1.

Installed correct nvidia drivers from Programfiles\Avid\Utilities\Nvidia. Deleted MCSTATE and sitesettings from Users\Public\Documents\Avid Mediacomposer\Settings and updated Blackmagic drivers to 11.0 and AJA drivers to 15.1.

After these changes tried the same opening of bins/checkins/checkouts/etc... that previously produced the error on 12 systems. (One system was left at 2018.8 with Interplay components 2018.9.  On this system justr deleted MCSTATE and site settings.) On all 12 systems a 5-10 minute test did not produce the error.

Time will tell but I get the feeling this was a site settings corruption after MC update maybe also due to the incorrect Interplay components.

It is always good advice to follow the book!.

Hope that works.

Cheers!

Hi Jeroen, I think your problem could be solved with the Media Composer release launched today, 2018.12.3.

Mentions something regarding Memory leak. Why dont you try it?

Cheers.

Hi Diego,

I also just spoke to my favorite support rep and she confirmed that this version should fix the issue(s) that are seen with interplay since 2018.9 or so.

More downloads and another >100 systems to update... starting with 25 at this site.   

Hi Jeroen.

So you are going to be bussy these days! Let us know how it was!

Good luck!

Cheers.

     Diego

Good news. 2018.12.3 has fixed the issue, and as it seems many more. One fix was obviously affecting many processes.

2018.12.3 looks like a really stable version.

Hi, We beilieve we are experiencing the same or similiar issues as yourself. We just wondered if you needed to upgrade the sever side as well as client or just the client side 2019.2.2 Nexis Software?

Has this completely resolved/improved your issues/reliability?

Regards,

Murray