ACCESS VIOLATION OCCURRED!!!

[bobbybeck2007]

I keep getting the error message ACCESSS VIOLATION or ACCESS VIOLATION OCCURRED. It seems to be happening only when I've saved a song, close PT and come back to work on it some more. Here's my setup:

Toshiba Satellite A105-S4094
Centrino Duo Processor 1.73 GHz
1.5 Gb Ram
XP Home SP2
Pro tools 7.0
Mbox2

Heeelp!!!!

[Kris75]

Are all of your plugs PT7 ready? Have you imported any session data and chose to add the audio instead of copy it?

[bobbybeck2007]

Are all of your plugs PT7 ready? Have you imported any session data and chose to add the audio instead of copy it?

Well I use waves platinum bundle which I got back when I had PT 6.7. That's all the plug-ins i use. I never import session data. I record all my audio within pro tools. I've turned off everything digidesign says to turn off in the background etc. I thought that I finally had a setup that would actually work. Help!?!

[Kris75]

Well I use waves platinum bundle which I got back when I had PT 6.7. That's all the plug-ins i use

It's time to get WUP'ed . Check your plug in version with the ones that are compatible. I don't think your platnium bundle is. I have only gotten the access violation error twice, and both times it was traceable to plugs or adding an audio file as opposed to copying it.

[bobbybeck2007]

[/QUOTE]

It's time to get WUP'ed . Check your plug in version with the ones that are compatible. I don't think your platnium bundle is. I have only gotten the access violation error twice, and both times it was traceable to plugs or adding an audio file as opposed to copying it.

[/QUOTE]

Sorry for my slowness but what's WUP'ed? I have v5.0 and when I had my dell I never saw this problem. Oh, actually I see this more random, not just when I'm reopening a session.

[spkguitar]

You need to get the PT7 compatibility updates for your waves plugins from the waves website. If you are not already up to date, they will charge you for their Waves Update Program (WUP).

[bobbybeck2007]

wow okay that makes sense. dang...get you comin', get you goin'....BUT THANKS FOR THE HELP!

[SoundHouse]

I have the same problem on a somewhat regular basis. Most all of my sessions are imported from Mackie Mdr recorders and then overdubbed and mixed inside ProTools, but I have the same problem with the few all in the box projects that I work on. I normally have one to two instances a week with no clue anything is wrong until I reopen a previous session that was working fine. The only solution that sometimes works is to right click the session folder using windows explorer, and under properties, uncheck the read only check box. The box will be greyed out as if it's unuseable, but you can uncheck it. Then hit apply and ok. Restart protools and about half the time, the session will open. If not, I usually keep the automatic backup option going on all sessions and keep opening backup up sessions until I get to one that will open. Of course you will lose changes until the point that the working backup file was saved. I'm also using the Platinum bundle along with assorted URS, digi, Antares, and Massey plugins. All are up to date and appear to be working fine. No crashes or freezes while working on the session, only when trying to re-open one.