Premiere Pro and AME crashes hole iMac

Hello together
today I set up my brandnew iMac 27 with 3.4 ghz i7 and GeForce GTX 680XM. Now i tried to render some importet projects (stored on my drobo) and premiere pro and Media Encoder crashes a few times my hole system. I have to mention, that I did the GPU-Hack for the Cuda acceleration.
But I tried it also without GPU-acceleration and just in this moment my hole Mac crashes again while rendering after 1-2 minutes.
below is one of the error-reports:
Interval Since Last Panic Report: 35 sec
Panics Since Last Report:          2
Anonymous UUID:                    3ADC0CCC-8C3E-34D3-152C-289AF67D7662
Tue Feb 12 17:26:19 2013
panic(cpu 6 caller 0xffffff80046b7e75): Kernel trap at 0xffffff80046a3722, type 14=page fault, registers:
CR0: 0x0000000080010033, CR2: 0x0000008000000038, CR3: 0x000000001a1a304d, CR4: 0x00000000001606e0
RAX: 0x0000000000000000, RBX: 0xffffff803b078860, RCX: 0x0000000000000000, RDX: 0x0000008000000000
RSP: 0xffffff839405bb40, RBP: 0xffffff839405bb90, RSI: 0x0000000000000060, RDI: 0x0000000000582d43
R8: 0x0000000000000000, R9: 0x0000000000000001, R10: 0x0000000000fd2000, R11: 0x0000000000000246
R12: 0xffffff8022ae3b40, R13: 0x000000000000000c, R14: 0x000000019e5da000, R15: 0xffffffffffffff9f
RFL: 0x0000000000010246, RIP: 0xffffff80046a3722, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x0000008000000038, Error code: 0x0000000000000000, Fault CPU: 0x6
Backtrace (CPU 6), Frame : Return Address
0xffffff839405b7e0 : 0xffffff800461d626
0xffffff839405b850 : 0xffffff80046b7e75
0xffffff839405ba20 : 0xffffff80046cd3bd
0xffffff839405ba40 : 0xffffff80046a3722
0xffffff839405bb90 : 0xffffff80046778b7
0xffffff839405be60 : 0xffffff8004670c2b
0xffffff839405bf20 : 0xffffff800495af43
0xffffff839405bf50 : 0xffffff80049e060a
0xffffff839405bfb0 : 0xffffff80046cdc03
BSD process name corresponding to current thread: Adobe Premiere P
Mac OS version:
12C3103
Kernel version:
Darwin Kernel Version 12.2.1: Thu Oct 18 12:13:47 PDT 2012; root:xnu-2050.20.9~1/RELEASE_X86_64
Kernel UUID: 3F93B852-872F-3DF0-BCF8-46D48024C422
Kernel slide:     0x0000000004400000
Kernel text base: 0xffffff8004600000
System model name: iMac13,2 (Mac-FC02E91DDD3FA6A4)
System uptime in nanoseconds: 1591787384351
last loaded kext at 7017365571: com.nvidia.CUDA     1.1.0 (addr 0xffffff7f85f16000, size 12288)
last unloaded kext at 164420432471: com.apple.driver.AppleFileSystemDriver     3.0.1 (addr 0xffffff7f868c6000, size 8192)
loaded kexts:
com.nvidia.CUDA     1.1.0
com.logmein.driver.LogMeInSoundDriver     1.0.0
com.attotech.driver.ATTOiSCSI     3.4.1b1
com.TrustedData.driver.VendorSpecificType00     1.7.0
com.apple.driver.AppleBluetoothMultitouch     75.19
com.apple.driver.AppleHWSensor     1.9.5d0
com.apple.iokit.IOBluetoothSerialManager     4.1.2f9
com.apple.filesystems.autofs     3.0
com.apple.driver.AppleMikeyHIDDriver     122
com.apple.driver.ApplePlatformEnabler     2.0.6d1
com.apple.driver.AGPM     100.12.81
com.apple.driver.X86PlatformShim     1.0.0
com.apple.driver.AudioAUUC     1.60
com.apple.driver.AppleHDA     2.3.5fc12
com.apple.driver.AppleUpstreamUserClient     3.5.10
com.apple.iokit.IOUserEthernet     1.0.0d1
com.apple.GeForce     8.0.6
com.apple.Dont_Steal_Mac_OS_X     7.0.0
com.apple.driver.AppleMikeyDriver     2.3.5fc12
com.apple.driver.AppleIntelHD4000Graphics     8.0.6
com.apple.driver.AppleSMCLMU     2.0.3d0
com.apple.iokit.BroadcomBluetoothHCIControllerUSBTransport     4.1.2f9
com.apple.driver.AppleLPC     1.6.0
com.apple.driver.ApplePolicyControl     3.2.13
com.apple.driver.AppleIntelFramebufferCapri     8.0.6
com.apple.driver.AppleBacklight     170.2.5
com.apple.driver.AppleMCCSControl     1.1.11
com.apple.driver.MaxTranserSizeOverrideDriver     3.1.7
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless     1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib     1.0.0d1
com.apple.BootCache     34
com.apple.driver.XsanFilter     404
com.apple.iokit.IOAHCIBlockStorage     2.3.1
com.apple.driver.AppleFWOHCI     4.9.6
com.apple.driver.AppleSDXC     1.4.0
com.apple.driver.AppleUSBHub     5.5.0
com.apple.driver.AirPort.Brcm4331     612.20.15
com.apple.iokit.AppleBCM5701Ethernet     3.5.0b9
com.apple.driver.AppleAHCIPort     2.5.1
com.apple.driver.AppleUSBEHCI     5.5.0
com.apple.driver.AppleUSBXHCI     1.5.1
com.apple.driver.AppleEFINVRAM     1.7
com.apple.driver.AppleACPIButtons     1.7
com.apple.driver.AppleRTC     1.5
com.apple.driver.AppleHPET     1.8
com.apple.driver.AppleSMBIOS     1.9
com.apple.driver.AppleACPIEC     1.7
com.apple.driver.AppleAPIC     1.6
com.apple.driver.AppleIntelCPUPowerManagementClient     196.0.0
com.apple.nke.applicationfirewall     4.0.39
com.apple.security.quarantine     2
com.apple.driver.AppleIntelCPUPowerManagement     196.0.0
com.apple.driver.IOBluetoothHIDDriver     4.1.2f9
com.apple.driver.AppleMultitouchDriver     235.29
com.apple.iokit.IOSerialFamily     10.0.6
com.apple.kext.triggers     1.0
com.apple.driver.DspFuncLib     2.3.5fc12
com.apple.iokit.IOAudioFamily     1.8.9fc11
com.apple.kext.OSvKernDSPLib     1.6
com.apple.iokit.IOSurface     86.0.3
com.apple.nvidia.nvGK100hal     8.0.6
com.apple.NVDAResman     8.0.6
com.apple.iokit.IOBluetoothFamily     4.1.2f9
com.apple.iokit.AppleBluetoothHCIControllerUSBTransport     4.1.2f9
com.apple.driver.AppleThunderboltEDMSink     1.1.8
com.apple.driver.AppleThunderboltEDMSource     1.1.8
com.apple.driver.AppleHDAController     2.3.5fc12
com.apple.iokit.IOHDAFamily     2.3.5fc12
com.apple.iokit.IOFireWireIP     2.2.5
com.apple.driver.AppleSMBusPCI     1.0.11d0
com.apple.driver.X86PlatformPlugin     1.0.0
com.apple.driver.AppleSMC     3.1.4d2
com.apple.driver.IOPlatformPluginFamily     5.3.0d47
com.apple.driver.AppleGraphicsControl     3.2.13
com.apple.driver.AppleBacklightExpert     1.0.4
com.apple.iokit.IONDRVSupport     2.3.6
com.apple.driver.AppleSMBusController     1.0.11d0
com.apple.iokit.IOGraphicsFamily     2.3.6
com.apple.iokit.IOUSBMassStorageClass     3.5.1
com.apple.driver.AppleUSBHIDKeyboard     170.2
com.apple.driver.AppleHIDKeyboard     170.2
com.apple.iokit.IOUSBHIDDriver     5.2.5
com.apple.iokit.IOSCSIBlockCommandsDevice     3.5.5
com.apple.iokit.IOFireWireSerialBusProtocolTransport     2.1.1
com.apple.iokit.IOSCSIArchitectureModelFamily     3.5.5
com.apple.iokit.IOFireWireSBP2     4.2.2
com.apple.driver.CoreStorage     296.10
com.apple.driver.AppleUSBMergeNub     5.5.0
com.apple.driver.AppleUSBComposite     5.2.5
com.apple.driver.AppleThunderboltDPOutAdapter     1.8.9
com.apple.driver.AppleThunderboltDPInAdapter     1.8.9
com.apple.driver.AppleThunderboltDPAdapterFamily     1.8.9
com.apple.driver.AppleThunderboltPCIUpAdapter     1.2.6
com.apple.driver.AppleThunderboltPCIDownAdapter     1.2.6
com.apple.iokit.IOFireWireFamily     4.5.5
com.apple.driver.AppleThunderboltNHI     1.6.3
com.apple.iokit.IOThunderboltFamily     2.1.8
com.apple.iokit.IO80211Family     510.4
com.apple.iokit.IOEthernetAVBController     1.0.2b1
com.apple.iokit.IONetworkingFamily     3.0
com.apple.iokit.IOUSBUserClient     5.5.0
com.apple.iokit.IOAHCIFamily     2.3.1
com.apple.iokit.IOUSBFamily     5.5.0
com.apple.driver.AppleEFIRuntime     1.7
com.apple.iokit.IOHIDFamily     1.8.1
com.apple.iokit.IOSMBusFamily     1.1
com.apple.security.sandbox     220
com.apple.kext.AppleMatch     1.0.0d1
com.apple.security.TMSafetyNet     7
com.apple.driver.DiskImages     344
com.apple.iokit.IOStorageFamily     1.8
com.apple.driver.AppleKeyStore     28.21
com.apple.driver.AppleACPIPlatform     1.7
com.apple.iokit.IOPCIFamily     2.7.3
com.apple.iokit.IOACPIFamily     1.4
com.apple.kec.corecrypto     1.0
Model: iMac13,2, BootROM IM131.010A.B05, 4 processors, Intel Core i7, 3.4 GHz, 32 GB, SMC 2.11f14
Graphics: NVIDIA GeForce GTX 680MX, NVIDIA GeForce GTX 680MX, PCIe, 2048 MB
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x02FE, 0x45424A3831554738424255352D474E2D4620
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x02FE, 0x45424A3831554738424255352D474E2D4620
Memory Module: BANK 0/DIMM1, 8 GB, DDR3, 1600 MHz, 0x029E, 0x434D534F384758334D314131363030433131
Memory Module: BANK 1/DIMM1, 8 GB, DDR3, 1600 MHz, 0x029E, 0x434D534F384758334D314131363030433131
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xF4), Broadcom BCM43xx 1.0 (5.106.98.100.15)
Bluetooth: Version 4.1.2f9 11046, 2 service, 18 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
PCI Card: pci11c1,5901, sppci_ieee1394openhci, Thunderbolt@11,0,0
Serial ATA Device: APPLE HDD ST3000DM001, 3 TB
Serial ATA Device: APPLE SSD SM128E, 121.33 GB
USB Device: hub_device, 0x8087 (Intel Corporation), 0x0024, 0x1d100000 / 2
USB Device: Ext HDD 1021, 0x1058 (Western Digital Technologies, Inc.), 0x1021, 0x1d130000 / 8
USB Device: hub_device, 0x0424 (SMSC), 0x2412, 0x1d180000 / 3
USB Device: BRCM20702 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x1d181000 / 4
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x828b, 0x1d181300 / 7
USB Device: hub_device, 0x8087 (Intel Corporation), 0x0024, 0x1a100000 / 2
USB Device: Keyboard Hub, apple_vendor_id, 0x1006, 0x1a130000 / 5
USB Device: Apple Keyboard, apple_vendor_id, 0x0250, 0x1a132000 / 6
USB Device: USB Storage, 0x05e3 (Genesys Logic, Inc.), 0x0716, 0x1a120000 / 4
USB Device: FaceTime HD Camera (Built-in), apple_vendor_id, 0x8511, 0x1a110000 / 3
FireWire Device: Drobo3, Drobo, 800mbit_speed
I hope anybody can help me, it's a wedding video with deadline....

I would venture to guess that adobe would tell you to disable the hack altogether and retest. It could be worth a shot. And I don't mean just shutting of the gpu in prefs, i mean actually disabling the pref.

Similar Messages

Help with Adobe Premiere Pro and AME CS6

Hi all,
First off, i would like to state that i'm pretty inexperienced in video editing, so please keep that in mind when answering or questioning something.I will try to explain my question to the best of my abilities, but please answer in a 'simple' manner, and don't shoot me when i miss something obvious.
I came across a 'performance?'-issue (slow exporting) for which i don't really know how to find the solution. I've been struggling with it for a while.
Your (any) help or insight is greatly appreciated!
My system:
Windows 7 Professional - 64 bit (Service Pack 1)
RAM 20 GB
Intel Core I73770 (dual quad core)
Direct x 11.0
Nvidia NVS 310
Adobe premiere pro CS6 (upgrading to adobe CC is unfortunately not an option)
Adobe media encoder CS6
They asked me to edit some video's on a regular basis, nothing complicated, just a 'training'-video. Length of video is about 2 hours edited.
File info:
Source file is 1920x1080 (1,0), 25fps, Upper, 2:11:10:24, 48000Hz, Stereo
There is one audio channel (left is standard mic, right is a shotgun mic) which is split to two audio channels, edited in aodbe audition (basic noise reduction)
I've been running into export times of over 12 hours (exported to mp4), which i'm guessing is a bit much.. . The slowness is also occuring with other export settings.
I came across a possible solution (in short: changing the Video Rendering and Playback in the project settings of APP) but that field is inactive for me...? what's up?
"Use Preview Files" works in CS5.5 but is "Useless" in CS6
I don't really know what to do from here, to figure out the solution. Any suggestions on fixing or troubleshooting the extremely long export times??
Thx in advance.

Dual video problems - Do you have dual graphics adapters?
IF YES, read below
-http://helpx.adobe.com/premiere-pro/kb/error---preludevideo-play-modules.html
-http://forums.adobe.com/thread/1001579
-Use BIOS http://forums.adobe.com/thread/1019004?tstart=0
-link to why http://forums.adobe.com/message/4685328
-http://www.anandtech.com/show/4839/mobile-gpu-faceoff-amd-dynamic-switchable-graphics-vs-n vidia-optimus-technology/2
-Mac Utility for dual adapters http://forums.adobe.com/thread/1017891?tstart=0

PPro and AME crashes...all the time. When you start them up, when you work, when you export, ever since I downloaded the updates last week.

I've been trying to edit and export timelapses I've shot in July. It's been an uphill battle since then.
First Lr gave me mountains of issues (seems to be doing ok now) and now Ppro and AMe is doing the same. Since I've downloaded the update last week they have both just stopped working. AME doesn't even want to start up anymore. Ppro starts ok but won't export anything anymore. The is one older project that I've finished before the update. That exports fine. But any new project I've created since refuses. I'm dropping the images into a 4k sequence, the dropping the 4k sequence into a 1080 sequence so I can ad some movement. Bet even if I take the images directly to the 1080 sequence it crashes the moment I hit export.
The timeline on this project is KILLING me! It's not supposed to take this long.
Please help!

Hi LFW,
Lowflyingweasel wrote:
I'm in South Africa. Don't know if the service here is somehow different. But I have tried during business hours! Your set Business hours. The online chat has been unavailable for days. I tried them twice before starting this thread.
Sorry to hear that. I'll raise the issue with my superiors a bit later this today. I have heard our chat software is disconnecting randomly in some cases. We are updating that system, but I can find out more later.
Lowflyingweasel wrote:
I am a little desperate and cannot believe that this tread had been active for 8 days without contact??!! If I posted wrong, or you need more info or whatever, please, why didn't anyone simply say that?
I am responsible for handling this forum and other products in the digital video realm. Because of the volume, it is not possible to answer every post. We do rely on the community to help out for posts like this, but some of them simply get by us. Yours was especially neglected and I apologize for that. Our forums are very good most of the time, but for a guaranteed response, you were doing the right thing by contacting support. The fact that both the forum and support failed you is very troubling and I'll see to it that you get the help you need. Since chat is not working for you, try the phone. Once connected, ask for the "video queue" so that you will be routed to the appropriate support team immediately.
Lowflyingweasel wrote:
I have restarted, reinstalled, tried to re-write the preference file, 8 new project file, re-exported all the images and could manage all but 3 time-lapses. They simply will not export. Not in ANY format from Pr CC 2014 nor via AME.
You may want to trash preferences for both Premiere Pro and AME. See the instructions below. I will also include troubleshooting steps I have been giving users. These steps may help you, as well.
Try the following:
Quit Premiere Pro, then reboot the computer. Launch Premiere Pro once more
Sign out from Creative Cloud, restart Premiere Pro, then sign in
Update any GPU drivers
Trash preferences
Ensure Adobe folder preferences are set to read/write in all 3 locations.
Delete media cache
Delete preview files: usually located here: Documents > Adobe > Premiere Pro > 8.0 > Adobe Premiere Pro Preview Files > [Your Project]Delete the preview files in this folder by dragging them to the Trash.
Remove plug-ins
If you have AMD GPUs, make sure CUDA is not installed
Repair permissions
In Sequence Settings > Video Previews, change the codec to one that matches your footage
Disconnect any third party hardware
If you have a CUDA GPU, ensure that the Mercury Playback Engine is set to CUDA, not OpenCL
Disable App Nap
Reboot once more
Thanks,
Kevin

Premiere Pro and Media Encoder crash while rendering H.264

Very recently, a problem's popped up where Premiere Pro and Media Encoder (CC) will crash while rendering H.264.
It's only while rendering H.264 - other formats seem to work fine.
And I don't mean that it returns an error, I mean it hard crashes with a Windows "Adobe Premiere Pro CC has stopped working" popup.
It doesn't crash at a consistent time during the render, even on the same project. Occasionally, it won't crash at all, but this is usually not the case.
I've tried disabling CUDA and my overclock to no avail. Please help!

On the topic of opening a project on the exact same version of Premiere Pro CC 2014 (yes it is definitely up to date, and the 2014 version), to overcome this export crash problem that ZachHinchy has brought up - you can't. Technically speaking, one should easily be able to open a Premiere Pro CC 2014 project from one system on another system running the exact same up to date, legitimate version of Premiere Pro CC 2014 without any kind of error. But for some reason, this has been disallowed(?) by Adobe. It has facepalm written all over it. Does anyone agree that this is at least a little bit silly?
I have tried exporting a Final Cut Pro XML from my project to try and open the sequence at uni on a Mac, so I can render my project when I finish my edit. It half works - the clips are there, but the sequence is gone - i.e. 12 hours of painstaking sequencing and micro-edits that had me at several points in time wanting to insert my hand through my monitor with enough force to make a large hole. I really cannot afford redo this sequence, as my assignment is due tomorrow, and I have to work at 6 oclock in the morning, so I also cannot afford to stay up till the early hours of tomorrow morning. Wish me luck that some miraculous event has taken place overnight that will somehow allow me to just open my project, on the same version of Premiere, on a Mac, without hassle. (Apple OS is not friendly to anything but its own selfish nature, so I am having doubts).
Adobe please, if you can do anything at all to help, you will save my assignment, and my faith will be restored. Otherwise, I'll just get my money back and buy Final Cut instead.
I cant even
If I find a way to fix either of these problems, I will post straight away.

Premiere Pro CC 2014 Crashing with rendering, freezing system, and more

Hello,
I'm having some serious issues with Premiere pro on my late 2013 iMac.
OSX 10.9.5
3.2GHz Intel Core i5
16GB 1600 MHz DDR3
NVIDIA FeForce GT 755M 1024MB
I'm working in 1920x1080 23.976fps. Media files are from sony FS700 .MTS and Cannon 5DmkIII .mov
Multiple times per day, PP crashes on me. It all started when I was getting really choppy playback which would be accompanied by this error message:
A Low Level Exception has occurred in ImporterMPEG (Importer)
This would soon after lead to the program freezing and me having to force quit the program. After contacting Adobe the first time about this persistent issue, the tech explained to me that it was a "Memory Leak" issue and that there was nothing that could be done. After the support team member ended our chat online before helping me solve my issue, I called support. I provided my case number and this person picked up where the helplessly left me and did the typical Adobe one fix all: He went into the hidden library and cleared all of my preferences, removed any third party plugins, and cleared the files in the root applications Adobe folder, renamed a folder "Adobe.Old" etc.
As I explained to the support team member on the phone, this is not a solution but rather a bandaid until it happens again.
Low and behold it has happened again. This time the support team member had me create a new System Administrator account on my computer thinking that there was a permissions problem with my other account which was conflicting with PPCC2014. While this was a major pain to switch between the new account and any other program that I had set up for day to day work, it allowed me to continue editing and at least (at a less efficient rate) get things done.
Now, while using my new System Administrator account, I am getting terrible crashes that not only stall the program, but force me to hard re-boot my computer. These crashes are accompanied by a terrifying looking screen that I was only able to capture once.
They've only become more intimidating as now I cant even see the program when this happens, but this is the only screen capture that did not turn out completely black.
I'm looking to see if anyone has had any extreme issues like this and if so how they were able to fix it. I've now spent 6+ hours with support and after the last one was told I would receive a personal email follow up by the end of the day (never happened) to take further actions based on the performance after the new account creation.
I need help. Now.
-John

Hi John,
First of all, try this: Re: A low level exception occured in: Importer MPEG (Importer)
Next, make sure that if you updated OS X to 10.9.x, or later, you must check the following each time you update: Premiere Pro CC, CC 2014, or 2014.1 freezing on startup or crashing while working (Mac OS X 10.9, and later)
Other things to try:
Sign out from Creative Cloud, restart Premiere Pro, then sign in
Update any GPU drivers
Trash preferences
Delete media cache
Remove plug-ins
Repair permissions
Disconnect any third party hardware
Remove QT components from Mac HD > Library > QuickTime
If you have a CUDA GPU, ensure that the Mercury Playback Engine is set to CUDA, not OpenCL
Disable App Nap
Reboot
Report back if anything here worked for you.
Thanks,
Kevin

Premiere Pro 2014 is crashing and freezing and I have to use force quit to get it to shut down.

Premiere Pro 2014 is crashing every day. i am running Premiere Pro 2014 on a 2013 imac with 3.4 GHz Intel Core i5 with 16 GB RAM. Playback on premiere continually freezes and the program crashes. Or the playback will start to freeze and then I save and close the project file/program, but the program will not close and I have to force quit. This is extremely frustrating. Premiere Pro CC was super stable and I rarely if ever had a problem. I have changed my permissions to give myself read/write. I have created a new project file in 2014 and then imported all my sequences from my updated project file but none of these strategies have worked. I am considering creating a new project file and going back to working solely in CC because I am on a deadline and troubleshooting this issue is taking up so much time.

I have had to force quit PP CC four times today. The fourth was when it crashed while trying to reopen it. I have had exactly the same problems as described above. I have no solutions to offer. I will go through a week of constant Premiere Pro bugs and poor performance then experience a period that seems too good to be true only to end up having a day like today. I can't believe that they call this a professional editing suite. It just wastes so much of my time pissing around trying to fix things and managing all the extra render and preview files it makes each time I have to save a new copy of a project which usually results in renaming it. It gets confusing after a while. Really not happy with this and have begun to learn Avid so as soon as this project is done, PP will be history.

Why Do Both Photoshop CS5 (64 Bit) and Premiere Pro (64 Bit) Crash on Start up.

Both Photoshop CS5 (64 Bit) and Premiere Pro (64 Bit) Crash on Start up. 32 bit version of Photoshop works fine.
Here is the problem signature when they crash.
Problem signature:
Problem Event Name:          APPCRASH
Application Name:          Photoshop.exe
Application Version:          12.0.0.0
Application Timestamp:          4bbc5b10
Fault Module Name:          CoolType.dll
Fault Module Version:          5.7.82.7602
Fault Module Timestamp:          4b980c97
Exception Code:          c0000005
Exception Offset:          0000000000073a92
OS Version:          6.1.7601.2.1.0.256.48
Locale ID:          1033
Additional Information 1:          7c82
Additional Information 2:          7c821a1fc13b00b508d1bb6ee7ecaf44
Additional Information 3:          019c
Additional Information 4:          019cb6db15489631b8a43faf27e30830
Problem signature:
Problem Event Name:          APPCRASH
Application Name:          Adobe Premiere Pro.exe
Application Version:          5.0.3.0
Application Timestamp:          4ce382d1
Fault Module Name:          CoolType.dll
Fault Module Version:          5.7.82.7449
Fault Module Timestamp:          4b7b1af3
Exception Code:          c0000005
Exception Offset:          00000000000739ea
OS Version:          6.1.7601.2.1.0.256.48
Locale ID:          1033
Additional Information 1:          889a
Additional Information 2:          889afed61eb6ddf1c1c3419adc6026b6
Additional Information 3:          8235
Additional Information 4:          823549a371dff618695395cc0a8514ee
Both are referencing cooltype.dll. I ran Font Doctor on all system and non-system fonts and found no errors. Booted without Extensis Suitcase loading. Nothing works. All 32 bit programs work fine. Any clues would be appreciated.

It does not necessarily mean a "corrupt" font, but can be a font that PrPro, and PS, cannot handle.
Though I have read that changes have been made, Open Office's DejaVu font would crash PrPro's Titler - every time. There are quite a few others. Font Dr, and similar utilities, will not see the font(s) as corrupt, but they are so poorly designed, that PrPro and PS cannot deal with them.
Though it can be a long, drawn out process, one can often zero in on the problem font(s), with a little work. This is accomplished by first defining the "System Fonts," and not touching them. Then, uninstall half of the remaining fonts, and testing PrPro and PS. If they launch fine, you know that somewhere in that list of fonts, the problem exists. If there is still a failure to launch, chances are good that the problem font(s) reside in that half, that are still installed. Note: because the problem still exists, does not guarantee that there are NOT problem fonts in that uninstalled group, so keep that in mind.
Repeat the proces, by uninstalling half of the remaining fonts and testing.
If necessary, repeat by removing half of the now remaining fonts and testing.
When you get to a point, where you are no longer getting problems, reinstall fonts, in small groups, testing in between. The smaller the groups, the easier it will be to pinpoint the problem font(s).
Keep notes on which fonts you are uninstalling and reinstalling, until you narrow it down to the problem font(s).
I would start by uninstalling any "free fonts," and then commercial, 3rd party fonts. A lot of free fonts are just poorly designed, and can cause issues, though they might work fine in some other programs.
I use a font manager, so that I only have ~ 350 fonts installed at one time, and then dynamically install fonts, as needed for Projects. That keeps my machine clean, and if, upon installation, I get a crash/hang, I know that at least one font in that Set is causing it. This helps, as my workstation has ~ 19,000 fonts on it, and some are free fonts, and many are from 3rd parties. Some are also very, very old.
Good luck,
Hunt
PS - one common cause for hangs on loading PrPro can be from VST's, used in Audio-editing. If you also have a lot of VST's, you could have two issues with two separate programs, i..e. PS hanging on fonts, and PrPro hanging on VST's. The results would be the same, but the causes could be different. That leads to even more work. For PrPro, also see this ARTICLE. If you get PS launching, but PrPro is still not functioning, drop by the PrPro Forum, and someone can help you there.

I just installed Adobe CC Premiere Pro and it continuously crashes!

I just installed Adobe CC Premiere Pro and it keeps crashing. I've tried creating a new project, opening an existing project -- nothing works. I can start a new project and get as far as to import clips into the project window but the moment I try to play a clip or create a sequence from it, it crashes. I'm running off a brand new laptop (Lenovo X1 carbon 3rd gen) 8Gb Ram, i5 processor, best of anything I could get on this specific machine. Any thoughts??
The files I'm opening with a new project are MP4 files from a gopro camera. The existing project was a CS5.5 file that it attempted to update to CC -- it actually located all of the files fine and as soon as it gets to the workspace with everything laid out, it crashes. Let me know if I can supply any more information.

I just posted Im having the same issue.
Premiere Pro 2014.2 is crashing
I love PPRO 2014 very much but, wrote an nasty gram to Adobe because each update seems to have issues.
I have set my autosave to 5 min saves and each time I see it say AUTO SAVING I use it as a reminder to do a real save.
I have a super system and it didn't use to crash like this every hour.
Why not try it out for a year and do a major update vs little updates that have issues the last 3 times.
I can't render either with the hardware setting, which did work for a year then, the latest update screwed that up.
The Adobe Tech blamed it on Apple but, hey - it worked for a year until Adobes update.

Nvidia CUDA driver update fixes crashes for Premiere Pro and other applications

We are seeing reports that the CUDA 5.5.47 driver update released today addresses the crashing problems introduced by the CUDA 5.5.43 driver update in Premiere Pro and other applications. So, if you have an Nvidia GPU, please update your drivers to use the most recent version of the CUDA driver.
Thanks!

It should be added that only Macs and Quadros need the CUDA driver. That is not required for use with GeForce cards on Windows.

Adobe Premiere Pro is constantly crashing and freezing

I'm a new user to adobe and I've used their free trials in the past for cs6, but this latest version of Premiere Pro keeps crashing while I'm in the middle of projects. I really don't know what the problem is. Is there something I need to update?

Macbook Pro 13" 2013
OS Mavericks
8gb RAM
Processor 2.5 GHz Intel Core i5
Graphics Intel HD Graphics 4000 1024 MB
I forget what it said specifically, but the error message said something along the lines of
"There was a serious problem with Premiere pro and it needs to shut down immediately. It will try to save your current session"

Premiere pro and media encoder CC problem

Hi guys,
I hope some of you can help me, I installed new version of premiere pro and media encoder CC and now none of them works, I can edit in premiere but as soon as I press export message apears ''sorry a serious error has occurred that requires adobe premiere to shut down'' when I try to open encoder it shut down on startup.
I'm using old IMac 2.4ghz intel core duo, 2gb 667 mhz ddr2 sdram, ATI Radeon HD 2600 Pro 256 MB, OS X 10.8.5.
This is the error report, please help:
Process:
Adobe Media Encoder CC [946]
Path:
/Applications/Adobe Media Encoder CC/Adobe Media Encoder CC.app/Contents/MacOS/Adobe Media Encoder CC
Identifier:
com.adobe.ame.application
Version:
7.2.0.43 (7.2.0)
Code Type:
X86-64 (Native)
Parent Process: launchd [136]
User ID:
501
Date/Time:
2014-02-10 08:44:28.001 +0100
OS Version:
Mac OS X 10.8.5 (12F45)
Report Version: 10
Interval Since Last Report:
1264 sec
Crashes Since Last Report:
1
Per-App Interval Since Last Report: 24 sec
Per-App Crashes Since Last Report:   1
Anonymous UUID:
7E711766-8C55-00D3-811F-852F73421407
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
terminate called throwing an exception
abort() called
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib
0x00007fff9483c212 __pthread_kill + 10
1   libsystem_c.dylib
0x00007fff8d74ab24 pthread_kill + 90
2   libsystem_c.dylib
0x00007fff8d78ef61 abort + 143
3   libc++abi.dylib
0x00007fff96ff79eb abort_message + 257
4   libc++abi.dylib
0x00007fff96ff539a default_terminate() + 28
5   libobjc.A.dylib
0x00007fff8f49d887 _objc_terminate() + 111
6   libc++abi.dylib
0x00007fff96ff53c9 safe_handler_caller(void (*)()) + 8
7   libc++abi.dylib
0x00007fff96ff5424 std::terminate() + 16
8   libc++abi.dylib
0x00007fff96ff658b __cxa_throw + 111
9   com.adobe.dvacore.framework
0x000000010022814d dvacore::filesupport::DirHelper::Create() + 813
10 com.adobe.AMEAppFoundation.framework
0x0000000104f285e9 AME::foundation::AppUtils::GetUserPresetDir(bool) + 425
11 com.adobe.Batch.framework
0x0000000105c0a842 AMEBatch::Initialize() + 2194
12 com.adobe.ame.application
0x00000001000273cb AME::app::AMEAppInitializer::AMEAppInitializer(exo::app::AppInitArgs&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >&) + 811
13 com.adobe.ame.application
0x000000010000ad6a AME::app::AMEApp::InitApplication(exo::app::AppInitArgs&) + 2426
14 com.adobe.exo.framework
0x000000010513e77a exo::app::AppBase::Initialize(exo::app::AppInitArgs&) + 1066
15 com.adobe.ame.application
0x00000001000141a8 AME::RunTheApp(exo::app::AppInitArgs&, std::vector<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >, std::allocator<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > > >&) + 1576
16 com.adobe.ame.application
0x0000000100056a38 main + 424
17 com.adobe.ame.application
0x0000000100003f74 start + 52
==========================
Edited by moderator to trim the crash report down to the essentials. Since these forums do not support attaching file (due to legal and security issues), we recommend uploading files using Acrobat.com’s Sendnow (https://sendnow.acrobat.com) or similar services (YouSendit.com, etc.)

Hi mawe81,
Thanks for posting on Adobe forums,
Please follow this document http://adobe.ly/1f2EHCg
and let us know if this fix your issue or not.
Regards,
Sandeep

Premiere Pro / Media Encoder crash during encoding

Afternoon guys, wonder if anyone has any tips on how to solve my issue. It's a new pc that I'm working on, my first project on it, everything working great in terms of the edit, but crashing whilst encoding both through Premiere Pro and Media Encoder with an error message (below). I'm not great with this stuff so please let me know if I need to provide more info and I'll provide much information as I can.
I'm a creative cloud user.
-Premiere Pro cs 6 (6.0.3) - I have tried to re-install the software, and ran all the updates yesterday after the install. Problem still persists.
-Encoder cs6 (6.0.3.1)
-Windows 7 Professional service pack 1, 64bit. Whilst I was online re-installing Premiere Pro windows did some updates (I generally keep my editing pc's offline).
-DSLR footage (.mov) for video, up to 3 sources of video (nested for multicam shoot) and running one source of audio (mp3 file). Two of the timelines I'm trying to encode are about 45 minutes long.. I have succesfully encoded other clips (a 5 minute, and a 35 minute previously. Miraculously this morning I encoded a 1h12m clip using the mpeg2-dvd preset with only adjustment of quality bumped from 4 to 5). So this was encoded after all the updates, however since then everything else is not working.
-Initially encoder was either freezing, or giving me an error message. Since re-installing all the software yesterday it now does not freeze, but I get the error message: "Adobe Media Encoder CS6.0 has stopped working... A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available." I get the same message when encoding with both AME and Premiere Pro. I click "close" from here and nothing else happens.
-Trying to export to mpeg2-dvd, I have tried the PAL widescreen preset, as well as trying to adjust the settings, doesn't seem to make a difference, the error message pops up different points during encoding.
-The only plugin I have used is magic bullet looks for some grading. It also fails to encode with no plugins used.
-PC     - Intel i7-3770 @ 3.40ghz,
          - 32GB ram
          - Operating system and Adobe Suite on c: (SSD 240gb)
          - Project source footage (video, audio, etc) f: (2tb)
          - Encoding files to e: (SSD 240gb)
          - my case is an Antec 902, with no additional fans. It does sound like it's working harder during encoding, not sure if a heat issue could be causing the software to error?
-I am using the mercury playback engine with a Gefore gtx 680 (2gb).
I have not been able to find any definitive answeres with regard to the crashes. I did also have encoder hanging whilst reading the xmp file. I have tried encoding video only (audio disabled) and whilst it doesn't hang during reading of xmp file, it still stops working with the above error message.
I also run an older PC with i920, 24gig, gtx570 and it never crashes but performs much slower. It is also running windows 7, same setup but different hardware. Not sure if the hardware on my new pc could be causing the issues, if you you guys have any troubleshooting tips it would be much appreciated. At this point i have tried starting a new project, new timelines, nothing seems to work, so I have transferred the data to my old pc for encoding (as I need to deliver the discs to a client), but I need to get this new setup working properly.
Cheers,
Stevan

Hi Axel,
Thanks for your suggestions, I just tried cleaning out the media cache and also rendered out a wav file of the audio and placed it in the timeline and deleted the mp3 version.. Tried once again to encode an mpeg2-dvd file.
1st attempt encoding through Media Encoder, pal widescreen with variable bit rate set to 6, 7 and 8 = everything froze, had to restart via button.
2nd attempt encoding through Media Encoder = this time tried video only same settings just no audio = same error (Adobe Media Encoder cs6.0 has stopped working...)
3rd attempt encoding through Premiere Pro, same settings with audio = same error message.
4th attempt encoding through Media Encoder, pal wide preset as standard with no change = same error message.
5th attempt encoding through Media Encoder, h264 preset for vimeo, 720p = same error message.
6th attempt encoding through Media Encoder, AVI (Uncompressed) 720 x 480 preset. 1m40s in the dreaded blue screen appeared. "A problem has been detected and windows has been shut down to prevent damage to your computer. A clock interrupt was not received on a secondary processor within the allocated time interval. " Bla bla bla.
In all instances the encoding is absolutely flying, but always ends up crashing.

Premiere Pro CC 2014 crashing constantly

Premiere Pro CC was great. Premiere Pro CC 2014 is not so great!
Constantly crashing every time I go to render after a while.
It happens so inconsistently I cannot explain.
I wish Adobe would see this post and contact me to resolve.
We pay for 5 seats every month and should not have to deal with software crashing constantly.
Thanks,
J

Hi, I have the same problem too.
Premiere pro cc 2014 crash constantly. I found problem in the overflow of RAM when I quickly scan (review) my clips on the timeline or resize the clips.
My configuration:
Premiere pro cc 8.1; 16Gb RAM; SSD 120(where i store and work with my video); CPU Intel i72700K; Windows 7 Pro x64

Premiere Pro and Adobe Media Encoder running slow

Hello everyone,
I'm having trouble with CS4, which is running significantly slower than CS3 did on a older machine. The CS4 suite is installed on a Dell Precision M6400:
Windows Vista 64-Bit
Intel Core 2 Duo CPU T9400 @ 2.53 GHz
8 GB RAM
NVIDIA Quadro FX 2700M Graphics with 512MB dedicated memory
The OS is running on a 57.5 GB HD (C:) and the Adobe suite is installed on a 298 GB Solid State HD (D:), except for Adobe Media Encoder, which is installed on the C: drive.
My project has 4 15-16 minute sequences. The sequences are in DV NTSC, 29.97 fps, My scratch disks are set to a folder on the C: drive. Media Cache Files and the Media Cache Database points to a folder on the D: drive.
These are some of the problems I'm having:
- Premiere Pro CS4 generates peak files every time I open a project
- It then takes 3-5 minutes to render before I can preview a 16-minute sequence
- Adobe Media Encoder takes 5 hours to render a 16-minute sequence (as flv) that has been previously rendered
- AME takes 1 hour to render every 15 minute sequence that has never been rendered before
Are my settings affecting their performance? Is there any way to improve it? Thanks.
(Premiere Pro is the only app that is slow)

The data rate for replay is one thing, the data rate from disk to memory then from memory to CPU and back the other way are different matters and ought not to be confused. It is well-established that for a computer to edit AVCHD you need top end components, and note that I said there were three tasks to distinquish with increasing hardware requirements, namely merely replaying the video, specifying edits in the editor and then the rendering. It is commonly accepted by all the industry vendors that to do remotely commercial AVCHD rendering you need a minimum Quadcore CPU then that eats data fast, in order to not let it go to waste you need a fast motherboard bus fast memory and in order for none of those to go to waste you need the fastest disk set-up you can manage. I in fact have a 4-disk RAID0 volume using SATA (I think the disk model is SATAII but I have to await return from the repair center before I can confirm). For this RAID0 volume I have run speed test software from BlackMagic because I have one of their HDTV capture cards. It recorded that this volume which remember is doing parallelised IO is just fast enough to receive a encoded HDTV stream from the BlackMagic card but too slow to receive an uncompressed HDTV stream, indeed when I tried both I found the volume did keep up with compressed but fell behind with uncompressed. Remember that with a RAID0 volume of 4 SATAII disks a given file gets spread over the four disks and hence IO is spread over those 4 3G/s data lanes. Also remember with these disks 3G/s is just a burst speed, for AVCHD we are interested in sustained serial IO which is much less.
Before my machine broke down, I found that it took 5 hours to render 33 minutes of HDTV albeit as it went along it transcoded from AVCHD to a Microsoft HD format for Vista-only. Another interesting thing is that I found that the longer this render ran the slower it became, the estimated time started at 3 hours but the actual was five and the last one third took maybe 3 hours. Because the machine broke after that run I couldn't figure the bottleneck. For my machine bear in mind that at the repair shop we found that the Quadcore had only half the necessary electrical power plugged in, the monitor software showed however that it constantly ran around 90% of whatever capacity that reduced power supply permitted. Now then we can puzzle over why it got slower and slower and yet CPU consumption remained consistent and near to full capacity, memory was not the bottleneck because that was constant at 6.4G. But you can say that this was maybe performing like a Dualcore and was hitting some sort of wall, if you had a 1 hour render with that rate of degeneration of performance factored in what would happen to the render time, and for 3 hours you could be running indefinitely. I hope when the machine comes back the correct power supply will make it behave like a Quadcore should for this type of application. Anyway I have two theories for the degradation. First is just that PrProCS4 was getting its knickers in a twist and thereby just doing more computation per minute of video to be rendered as time went by, maybe internal resource management related to OO-type programming maybe, or related to disk IO falling behind, both these theories have problems, for the latter the CPU usage should then have dropped also.
Anyways, you need really a Quadcore system and blazing fast disk to work fully with AVCHD commercially, we found an external SATAII disk so if I were you I would just go get one and move on with your life.
Message du 03/06/09 16:08
De : "Jim Simon"
A : "JONES Peter"
Copie à :
Objet : Premiere Pro and Adobe Media Encoder running slow
For AVCHD you MUST have FAST disks.
AVCHD actually has a lower data date than DV. You need lots of CPU muscle, but disk speed is really not a factor specific to AVCHD. Anything that works for DV will work just as well for AVCHD (and HDV as well).
>

The project was saved in a newer version of Premiere Pro and cannot be opened in this version

I edited a project on CC on one computer and saved it on my external. My friend took the same project to edit it on her computer under her own name and licence. Both of us recently upgraded to CC. But the same project that worked a few hours back on Premiere Pro CC, does not work now also on Premiere Pro CC and I received a message saying: The project was saved in a newer version of premiere pro and cannot be opened in this version." Can you please help us.?
Message was edited by: Kevin Monahan
Reason: Your title was too long.

Hi alexxxkid,
You should be able to import the xml into an earlier version.
Backward compatibility has never been there with Premiere and it is always recommended not to update in the middle of a project.
As far as the crash is concerned, please tell me more about it so that i can help you to the best of my knowledge.
Thanks,
Rameez

Premiere Pro and AME crashes hole iMac

Similar Messages

Maybe you are looking for