assertion errors how to fix

[garnoil]

My system (TDM 2) Mac OsX has become very unstable. I am getting assertion errors when trying to import sound from other drives, when using the workspace, etc. I am also getting Pro-Tools crashes every time I exit Pro-Tools.

This is what I have done to try to fix the problem:

I have trashed prefs many times and it seems that as soon as I open any session, the problem soon comes back up.

I have also repair my hard drive and all of my peripheral disks.

I removes all plugins that I don't normally used.

I am on Mac osx Snow Leopard Pro-Tools 10.3 HT TDM 2
14 gigs or Ram, 8 core
Video and audio on separate drives and separate system drive.

What to do next? re0install OSX (how do I it to preserve my systems plugins and authorizations?), re-install Pro-Tools? upgrade to PT 10.3.1??

suggestions?

[Stig Eliassen]

Maybe this can help?

http://avid.force.com/pkb/articles/e...oductCategory=

Deleting Pro Tools Databases and Preferences

These are important steps in order to resolve various issues, such as assertion errors, graphic or display problems, and other intermittent issues that are not specifically hardware or compatibility related. Listed below are the paths to all the database and preference files installed by Pro Tools. Once you have deleted these files, you should empty the trash and restart your computer. These files will be recreated when Pro Tools is launched.

Pro Tools Databases

Double-click on the Macintosh HD icon on your desktop. (This would be your system drive if you have renamed it to something else.)
Go to the Library folder.
Go to the Application Support folder.
Go to the Avid folder.
Go to the Pro Tools folder.
Find the folder called Databases and drag it to your trash.
NOTE: If you are using Pro Tools HD or Complete Production Toolkit, you will want to backup your Catalogs folder before deleting the Databases folder.
Pro Tools Preferences

From the Finder, click on the 'Go' menu at the top of your screen.
Press and hold the Option key on your keyboard and choose 'Library'.
Go to the Preferences folder.
Delete the following files:
com.digidesign.ProTools.plist
com.digidesign.ProTools.plist.lockfile
DAE Prefs
DigiSetup.OSX
Pro Tools Prefs

[garnoil]

Thanks you, I will try all these steps.

[Larold]

Make sure your drives are formatted with the GUID format, also. Back them up and reformat. ProTools 10 on Intel macs like to see those drives.

[garnoil]

My drives are Mac Osx Extended Journaled. This system was working very well -for over 2 years with no major issues- but something happened and now it is really unstable. My only new software is Unveil (this is brand new so I do;t think that is the problem), and I bought a new Avid keyboard (I had to move my I-locks around as they don't physically fit in the exact same slots they were connected before).

[sunburst79]

Originally Posted by garnoil

My drives are Mac Osx Extended Journaled. This system was working very well -for over 2 years with no major issues- but something happened and now it is really unstable. My only new software is Unveil (this is brand new so I do;t think that is the problem), and I bought a new Avid keyboard (I had to move my I-locks around as they don't physically fit in the exact same slots they were connected before).

I'd be surprised if its moving the iLoks or a Avid keyboard. I'd be temped to uninstall unveil temporarily. Since that was the most recent change.

[garnoil]

Well I tried all the fixes that you suggested but I am still getting assertion errors. If I take the suspect plugin out of the plugin folder, is this good enough so that Pro-Tools won;t see it any more (it will no longer affect Pro-Tools) or do I have to actually uninstall it?

[garnoil]

May be I can send Avid my crash reports? I have the 1 year tech support that I bought when I upgrade to PT 10.

[Larold]

In Disk utility, check that the drive uses the Partition Map Scheme: GUID Partition Table, not the Apple Partition thing. That's what I meant.

[garnoil]

This is the one part od the crash report that refers to "crash" (I can post the entire report but it is huge) may be someone knows what this means?

Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x91dc6693 ecx: 0xbffff50c edx: 0x91d1dc5a
edi: 0xa019db30 esi: 0x0150c9cc ebp: 0xbffff528 esp: 0xbffff50c
ss: 0x0000001f efl: 0x00200282 eip: 0x91d1dc5a cs: 0x00000007
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
cr2: 0xa01af020