access violation in startup of Media Composer 4

[Mickey Grant]

Here’s my specs:
Windows XP Pro, service pack 3, Media Composer 4.05, Intel Core I7 CPU 920 @ 2.67 Ghz, 4 gigs ram, Graphics card ATI Radeon HD 2600 XT (ran composer 3 just fine)

On the same system I have no problem capturing on Adobe Premiere CS4 (of course I close it when Avid open) and I can capture fine on Windows Movie Maker. I’ve been editing with Avid for over 6 years and have never run into something like this. I talked to an Avid tech last night and he thought maybe it was something wrong with my system but since I’ve now tested it on Premiere and Win Movie maker and it captures fine, I’d say my 1394 capture card is fine and the 1394 on the board are fine. Does anyone have Premiere also installed on the same drive? I wonder if there is some kind of conflict there?

[Joseph Bradley]

The problem is in the Access Violation. When it comes on write down exactly what it says and post it. There is a major problem that may be a simple fix. Let’s see.

[Mickey Grant]

I am sorry I didn’t post this, I’ve been up 3 days trying to solve problem. I fixed the access violation as it was a corrupted Aclpu file, something like that.

I can actually edit and do everything, export files, etc. I don’t think it’s my unqualified Video card which worked fine with 3.0. I think if there was a problem with the card, then when I open capture, and simply play the video in order to cue it up, it works perfect. It’s the second I hit capture that it totally crashes.

Here’s my system:
Windows XP Pro, service pack 3, Media Composer 4.05, Intel Core I7 CPU 920 @ 2.67 Ghz, 4 gigs ram, Graphics card ATI Radeon HD 2600 XT (ran composer 3 just fine)