3 Replies Latest reply on Dec 13, 2011 2:29 PM by Jim_Simon

    Premiere CS5.5 Crashing EXC_Crash (SIGSEGV)

    Jeremy Markowitz

      Hi, I'm running Premiere Pro 5.5.2, on a Mac Pro, Lion 10.7.2, 2x2.26ghz Quad-Core Xeon, 20gig DDR3 ECC 1066 ram, Nvidia GeForce GT 120 512mb, Blackmagic Intensity Pro PCIE.

       

      Premiere randomly crashes and closes itself while working on projects. With the Error Type "EXC_CRASH (SIGSEGV). The Premiere saves (.prproj) don't corrupt or fail to reopen. It always opens back with the only lost work being the time between saves.

       

      I had the same problem in Snow Leopoard running CS5. I've never been able to trace a root of the problem, and have re-installed the software and reformatted the HDD and reinstalled the system OS. I've been on the phone so many times with Adobe over the course of the last year, never actually resolving my issue.

       

      I've even experienced the same problem, on my Macbook Pro 10.7.2, Core 2 Duo 3.06 , 8 gig ram, Nvidia GeForce 9600m GT.

       

      I've tried everything from different user accounts, clearing caches, trashing prefs, changing ram accessibility, storing footage and or project saves on different physical drives. And of course numerous software and full system OS reinstalls mentioned above. I've encountered this problem with DVCPRO HD, XDCAM, DV and on every project I've worked on since i went to CS5. At one point I took the Mac Pro to an Apple store and they ran 3 days of stress tests on the machine and couldn't find anything wrong.

       

      All the other components of my CS5 Production Premiere suite function exceptionally, on both computers, except Premiere CS 5 or 5.5.

       

       

      So, does anyone have any thoughts?

       

      Thank you,

       

      -Jeremy

        • 1. Re: Premiere CS5.5 Crashing EXC_Crash (SIGSEGV)
          Jim_Simon Level 8

          SIGSEGV is a memory error.

           

          20GB is an odd amount of memory.  The norm is multiple of 2 and 4 (2, 4, 8, 16, 32) or multiples of 3 (3, 6, 12, 24).

           

          How many modules of what capacity do you have installed?

          • 2. Re: Premiere CS5.5 Crashing EXC_Crash (SIGSEGV)
            Jeremy Markowitz Level 1

            Hi Jim, thanks for responding.

             

            The Mac Pro came with 12 gigs of ram, and had the problem described above before it was upgraded to 20 and my Macbook Pro still has it's factory 8 gigs of ram and has this Sigsegv issue.

             

            However, here is the breakdown on the Mac Pro:

             

            Model: MacPro4,1, BootROM MP41.0081.B07, 8 processors, Quad-Core Intel Xeon, 2.26 GHz, 20 GB, SMC 1.39f5

            Graphics: NVIDIA GeForce GT 120, NVIDIA GeForce GT 120, PCIe, 512 MB

            Memory Module: DIMM 1, 4 GB, DDR3 ECC, 1066 MHz, 0x859B, 0x435435313237324241313036372E4D313846

            Memory Module: DIMM 2, 2 GB, DDR3 ECC, 1066 MHz, 0x802C, 0x31384A53463235363732415A2D3147314631

            Memory Module: DIMM 3, 2 GB, DDR3 ECC, 1066 MHz, 0x802C, 0x31384A53463235363732415A2D3147314631

            Memory Module: DIMM 4, 2 GB, DDR3 ECC, 1066 MHz, 0x802C, 0x31384A53463235363732415A2D3147314631

            Memory Module: DIMM 5, 4 GB, DDR3 ECC, 1066 MHz, 0x859B, 0x435435313237324241313036372E4D313846

            Memory Module: DIMM 6, 2 GB, DDR3 ECC, 1066 MHz, 0x802C, 0x31384A53463235363732415A2D3147314431

            Memory Module: DIMM 7, 2 GB, DDR3 ECC, 1066 MHz, 0x802C, 0x31384A53463235363732415A2D3147314631

            Memory Module: DIMM 8, 2 GB, DDR3 ECC, 1066 MHz, 0x802C, 0x31384A53463235363732415A2D3147314631

             

             

            Thanks for the help.

             

            -Jeremy

            • 3. Re: Premiere CS5.5 Crashing EXC_Crash (SIGSEGV)
              Jim_Simon Level 8

              Well, this is a tough one.  It's not a commonly reported error here in the forums, so it's likely something specific to your two machines.  And there's no way to tell if it's the application or the OS causing the error.  My thought would be to wipe the HD clean and reinstall everything from the ground up, but you say you've already done that.

               

              My next thought is that there is something running on both your systems that most users don't have running, and which is causing the fault.  Unfortunately, the best way I can think of to test that is to do another wipe and OS install, but this time checking back here in the forums before you actually install any software.  We might spot something you're installing that you don't need (the idea is to keep it to the bare basics for editing).

               

              Outside of that, the only other thing I can think of is to get all new matched memory modules.  But if that were the actual cause, I'd not expect two separate machines to be affected.