Premiere Pro CC Crashes While Rendering With Mercury OpenCL

Hi guys!
Every time I try to render a ~2 min video in H.264 using the OpenCL renderer which is fully supported on my 7970 (2x Crossfire) the program crashes while rendering. (Usually around 28%)
If I switch to Mercury Software renderer, it renders perfectly.
I am currently using AMD 13.6beta2 drivers, and PPCC is fully updated, any suggestions?
Additionally, for the half minute that it tries to render with OpenCL before crashing, by checking the GPU utilization % in AMD catalyst overdrive, it seems to not be utilizing the gpu at all... And then promtly crashes of course...
I hope I can fix this problem soon... Really dissapointed with this adobe product.
Thanks a lot!

Rendering without any effects ----------> Still Crashes
Disabling Crossfire ----------------------- > Still Crashes
Reinstalling Premiere ---------------------> Still Crashes
Physically Removing the 2nd GPU -----> Works
So, is there any way I can get this to work while having both GPUs physically installed in the computer?
It would be quite a hastle to remove the 2nd one each time I need to use PP!
One odd thing also is that from watching the gpu utilization while rendering H.264 1080p, the GPU is only being used to about 30%, and very intermittently.... I would imagine things would accelerate quite a lot if it actually utilized the whole GPU!
Thank you very much guys!

Similar Messages

Premiere Pro Freezes mac while rendering Fast Color Corrector & Rgb curves

I am having a problem that is impacting our business. We are doing commercials that we are doing color correction of the subject using Fast Color Corrector and RGB curves. When these effects are added to the sequenced video, the performance of the Mac Pro slows down considerably.
Then when we go to render the project so that we can see the effects in real time, the computer freezes completely. The program usually informs us that it must close due to a serious error. I have attempted to restart the computer, clean up permissions etc to solve this problem but to no avail. Why would this happen? Any ideas on how to solve it?
Here are the specs:
Using Premiere Pro CC 7.2.1 (4)
Mac Pro: 3.2 Ghz Quad-Core Intel Xeon
Memory: 24 GB
ATI Radeon HD 5770 (1024 MB)
OS: 10.8.5

Yes. I experimented on my own and got confirms from a couple of sources. Where the problem was is bad suggestions about what settings to use in Premiere Pro.
The first setting you want to check (although Premiere Pro will probably see the card right away is:
File > Project Settings > General - Make sure that Mercury Playback Engine GPU Acceleration is selected. Everyone agrees on this.
Now is where the fun begins. There is a school of thought that says to go here:
Sequence > Sequence Setttings - Under Video Previews, they want you to check off Maximum Render Quality. Once you do this, you must also go to:
Preferences > Memory - and change Optimize Rendering for Performance
DO NOT DO THIS! What I found is that this significantly slows down your system and makes rendering and exporting take over your computer (and I have a lot of ram). Leave your change with the setting Mercury Playback Engine GPU Acceleration and you should be great.
I have found a significant change in running color correction effects, exporting and rendering. You will too.
Let me know how you make out after your setup.
Have a great day!

Adobe Premiere Pro CS4 crashes on load with project

When I try to load my CS4 projects the application crashes with the error:
"Sorry, a serious error has occurred that requires Adobe Premiere Pro to shut down. We will attempt to save your current project."
I have my hard drive partitioned: C drive for my OS; D drive for my data; and I also have an external hard drive which is H. I installed Adobe Premiere on my D drive and saved all the my project files and data on my external drive H. A couple weeks ago I got a virus and I wiped out my C drive. So, I reinstalled Windows XP. After reinstalling XP and getting my machine back up and running I removed Premiere Pro CS4 from my D drive and installed it on my C:drive. I connected my external drive to my computer and Windows assigned the drive letter F to my external. I launched my project file and it said it could not find my data and it crashed with the above message. I opened my project file in a text editor and I saw that file path was H:\... for all my data so I reassigned the drive back to H hoping that was the reason for the crash. Much to my chagrin it was not as I try opening the project file now and it finds all the files but it still crashes. I'm all out of ideas at this point. Is there a log file that I can look at to try to troubleshoot this any further? Has anyone seen this happen before? Should I reinstall Adobe Premiere Pro? I am under a time crunch here as I need to open this project and make some edits.
Any help is greatly appreciated!
Thanks.
-Jeff

Jeff,
The Page File is MS Windows' "virtual memory." It gets activity, when physical RAM is not available. Especially with video editing, this happens a lot. It can be set via Control>Panel>System. Windows can either dynamically create and size the file, as is necessary, or it can be set to provide the necessary size statically - always the same, and is *usually* set to ~ 2.5x the physical RAM.
With one physical HDD, that is partitioned, you have about 4-5 operations going on at the same time, and your I/O system is basically telling the heads of your HDD to be in different places/platters at this same time. Unfortunately, this is impossible, and one gets system hangs, sluggish performance, crashes or worse.
There are several good threads on suggested HDD setups for NLE work on this forum. I'd step back a level, so you get all Premiere forums, and search for some of these articles. There are a lot of worthwhile suggestions for number, type, connection and configuration of HDD's.
Good luck,
Hunt

Premiere Pro CS5 crashes while editing 4.5K-RED-Material

Hi there,
I'm editing 4.5K-material with Premiere Pro CS5. After a couple of minutes (mostly after watching sequences longer then 10 seconds) the program crashes. Windows 7 tells me that "ImporterREDServer.exe" doesn't work anymore and then Premiere freezes. I doubt that it is a performance problem, because with CS4 and regular 4K-RED-material I haven't had any problems on the same PC. I deinstalled CS5 several times (with Cleanupscript and everything) and re-installed it, but the problem remained the same.
I would really appreciate some help or any idea what the problem could be. Thanks in advance!
Daniel
My system:
i7 860 @ 2.8 GHz
8 GB RAM
Windows 7

Well, well. After many tests with other platforms we came to the conclusion that it was not Premiere Pro that caused problems but the material itself. This is some kind of a worst case scenerio. In the process of copying the data onto hdds some frames within the data got damaged and causes Premiere to crash. Since the data on both discs is corrupt differently we now try to rebuild as many files as possible. Yet there will be clips that can't be saved. Anyhow. There will be a film and that's the most important thing.
Thanks again for your help everybody
Daniel

Premiere Pro will crash when rendering part of timeline and cancelling - common issue?

There have been times where my timeline was red- so I chose part of the timeline, hit enter to render, and then realized it was going to take too long so I cancelled out. However, every single time (when I hit cancel, not "x"), it will tell me that Premiere Pro crashed and close the program. Can anyone replicate this? Is this a known issue? I didnt see it reported anywhere. It is not random. I can anticipate it happening every time I do that.

None at all. It's the strangest thing. There are times where I will start a render, not realizing how long it will take, change my mind, and try to cancel and it happens. I may just need to resort to reinstall the application if I can if no one else is experiencing the same issue.

Premiere Pro CS6 crashing while playing video encoded with Picvideo M-JPEG

Here is a video of what happens: http://www.youtube.com/watch?v=gmP0UBGvEUA
Whole video is alright except for those 10-90 frames that causes adobe to crash.
At first i thought that there was a problem in 64bit decoder, but every other software (64bit videoplayer or 64bit video-editor) can read those frames alright.
Please, help me with this.

This MJPEG http://forums.adobe.com/thread/730396 discussion may help

Premiere Pro CC Crashing When Rendering Nested Sequences

When I try to render out my project which has a nested sequence (see below),
As you can see I have 2 sequences. My original cut is "IN CAR". I then have another sequence titles "TEST" in which I have laid out the entire sequence of "IN CAR". When going to render this project, I simply get an error saying "Error Compiling Movie".
I can render a single sequence without any trouble.. but as soon as there is a nested sequence, it crashes.
Is there something I'm doing wrong?
My specs:
iMac 27inch Late 2013
Quad Core
32GB RAM
GTX 780
3.5GHz Processor
Any help is greatly appreciated.

The Unknown Error is the bane of the PP editor, simply because the cause is unknown, and without that, there's no way to suggest a definitive fix.
You'll have to experiment with different things, see what works and what doesn't.

Adobe Premiere Pro CS4 crashes

My Premiere Pro CS4 crashes while It loads the workspace and then automatically close.
I had this problem before and there was a solution but i saved it as my favourites and it no longer exist because of the new forums.
Damn Adobe

I do not know the older article, but THIS ONE might give you tips on gathering "clues," as to what is going on, when PrPro shuts down.
You say that all of your drivers are updated - double-check, as this is a very common cause.
Good luck,
Hunt

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 random crashing since update to 2014.2

Been working on the SAME big project over 18 months, in Pr Pro CC, 2014, working on the SAME PC:
Win 7 SP1 pro 64bit, i7-3770K, 32GB fast memory (25.7 available for Pr), Intel HD 4000 graphics on Asus motherboard with 30" NEC Multisync screen at 2560 x 1600 (same as for years)
42GB free on my SSD drive C: and 54GB free on my SSD drive S: for preview files, 24GB free on my SSD drive T: for caching files. Project files etc stored on a normal hard drive F: (for Files!) 1.25TB free.
NOW last update to 2014.2 and I get constant RANDOM crashes (Windows encountered a fault and had to close this program) despite updating graphics driver and trying different settings in preferences, use mercury etc. No particular action causes it - sometimes I am just watching it play a sequence and it just stops. Though of course it may be rendering the last edit at the time.
Sometimes it runs for all of 15 mins and I think the problem has sorted then it goes again and I have to restart the project, find where I was and re-do my last edits. If I remember to press Ctrl-S very frequently (every few seconds) it seems to run for a while then I forget for 5 mins and it crashes.
Grrrr what did you do to the latest version, Adobe?? I need to get this project finally finished in a hurry.... I wish I had not updated the program! Of course I cannot go back as it says the saved copy is now incompatible with earlier Pr Pro versions.
I then tried running a previous version at the same time, as simonray suggested in his post - it worked! So I am able to continue as normal provided I do this stupid bodge fix.
So it really is down to Adobe as it is the same project, same PC, just different version update. You did something to a great, stable, program that made it unstable, Adobe...
To ANSWER RAMEEZ from previous thread:
A variety of issues can cause PPRO to crash:
a problem with the Preferences, or some other pref-related file in the Profile-<USERNAME> bin. >> DIDN'T CHANGE ANYTHING since 1½ years running previous PrPro versions on SAME PROJECT on SAME PC
the graphics driver Checked for latest version - didn't stop the crashing
third-party plug-ins - don't have any
a problem with the cache files. I am using the same 2 x SSD I have been using for years for autosave and caching. 54GB free space / 24GB free space (current cache in place)
a problem with the project file (if you're loading a project...) Doesn't apply
the Preferences files be set to read-only How would that happen? Never happened before on any other update and I can change it.
the user not having administrator rights Only one user on PC since installation, full rights
a conflict/incompatibility with some OS setting Haven't changed anything
a problem on the licensing/authentication side. I'm signed up to full Adobe CC. Everything else works, Ps, Lr, Id ...
A log file might help identify the cause of the crash. Please right-click 'My Computer', select "Manage," look under 'Event Viewer->Windows Logs->Application' to see if there's an event there from Premiere Pro. If so, copy the contents of that log and paste them here.
>>>>>>>>>>>>>>
Faulting application name: Adobe Premiere Pro.exe, version: 8.2.0.65, time stamp: 0x5486db4a
Faulting module name: VideoFilterHost.dll, version: 8.2.0.65, time stamp: 0x5486bf85
Exception code: 0xc0000005
Fault offset: 0x000000000006d692
Faulting process id: 0x19d0
Faulting application start time: 0x01d022d29c3e2d43
Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Adobe Premiere Pro.exe
Faulting module path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\VideoFilterHost.dll
Report Id: 1097ced4-8ec8-11e4-aaaf-08606e6e6383
<<<<<<<<<<<<<<<
Thanks,
Rameez

Problem Solved! (with a small catch)
While searching crashing issues I came across this thread,"Premiere Pro random crashing since update to 2014.2"
Marc_Lec Answered (and I paraphrase here)"...I had the same problem and this is what I did. In 'Preferences Memory' I increased the memory reserved for other application to at least half the installed and changed the optimize render from 'performance' to 'memory."
Thank You Marc_Lec for what has been a game changer for me since my last computer and the beginning of PremiereCC problems.
I changed my Memory reserved for Other Applications from the default 7gigs to 1/2 of my approx.31 available Gigs = 16Gigs. Viola!
No more crashing what-so-ever!
I still have to purchase an older GTX 980 graphics card to take advantage of Adobe's approved code to utilize X=Cuda Cores and GPU, but I think I'll hang onto my new TitanX, in hopes that Adobe will write code and approve it someday in the near future.
Now why doesn't Adobe say this officially about Memory Settings? (I don't know maybe they do and I missed I somewhere)
Mine and probably many peoples computers problems here on this board may be attributed to a simple Memory adjustment, because the computer needs more than 7Gigs to run itself, not to mention Premiere.

CS6 crash while rendering

Hi,
recently CS 6 crashes while rendering, this happens at the beginning (ca. 800 frames), i change from GPU to CPU, deletet the cache files, try a different sequence
with other videos, all the same
in task manager i can't kill the premiere prozess
after crashing only the power/reset button helps
the strange is, at the same time my complete network crashes to ??
Windows 7 pro
16GB RAM
Genforce GTX570 Driver 340.52
Intel i7-2600K
With Media Encore there are no problems.
can someone help me ?

The problem with PP CS6 crashing during render has increased from once in a while to where it cannot complete any renders.
---->>> Encoding to H.264 MP4. Seems to do fine on AVI renders. H.264 MP4 is the key to the problem. <<<---
The error that it is reporting says that the "output directory could not be found", but the problem is the same when rendering to a different (not RAID) drive. Does not crash with AVI render. Replaced H.264 Codec -->> No change. Crashed at 90% of a 50 second file render to lowest level MP4 file.
It is not the motherboard - Replaced Gigabyte with ASUS Sabertooth 990FX
It is not the CPU - Replaced AMD 6 core with AMD 8 core FX
It is not heat. Cabinet is cool, all fans are running, no dust, no blockage.
It is not power supply - Replaced 750 W power supply with 850 W power supply.
It is not memory - Increased memory from 16GB to 32 GB, Computer repair shop rotated and tested memory.
It is not virus (no email on this machine, current virus protection and security software).
It is not drive space - Increased RAID from 2TB to 8 TB - Problem actually got worse - (crashes sooner)
It is not the video card - drivers verified correct by Nvidia - (Quadro 4000) - tested by installing a different video card - No change.
It is not software install - Uninstalled total CS6 package and reinstalled.
It is not a specific render file - It will not complete any renders now.
It is not a recent software install - The only software that has been updated is Adobe but that was ruled out by the total uninstall/reinstall. Backup install on a laptop is able to complete renders on the files that crash on the "big" machine. Nothing new has been installed. Virus and SpyBot show "clear".
It is not the CUDA or Mercury setting - Tested with CUDA on and off.
It's not the Playback settings - Tested for GPU Acceleration and Mercury Playback Engine Software only.
It is not the C: drive - Replaced with SSD.
Ran while watching Performance Monitor - No hint of problem before crash point. (video available).
So, what are we missing?
Windows 7 Pro
64 Bit
32 GB Ram
8 TB RAID
ASUS Sabertooth 990FX
AMD FX8350 (8 core)
Performance Score: 7.1
Power Supply 850 W.

CS4 Premiere (and Encore) crash on opening with blue screen

I have been having a terrible time with CS4 Premiere Pro crashes over the last month or so. Initially PP would just disappear from the screen as it was opening up, and if it didn't crash it was quite often after the Matrox RT.X2 logo came up after selecting the project to open. I had less problems starting a new project than opening a previous one. Sometimes it would open and crash during the work process without warning...forcing me to save after every change. Then it got worse.
I looked to the Adobe CS4 bulletin on crashes and it was suggested to update drivers. The first driver I looked at needed an update (Nvidia Quadro FX1500 256 MB) so I had their download service do the work and installing. During the process it stopped with 'Nvidia display pannel extension cannot install due to a version mismatch. Resetting the display drives may solve this problem' without any suggestions on how to do that. I have 2 Dell 24" monitors slightly different from each other but worked great before all this.
From this point everything got even worse. System Restore to the previous day did nothing. Everytime I tried to open Premiere (or Encore) the whole computer crashed (blue screen) and restarted automatically. I can no longer play any video without crashing -- not an AVI, MOV, WMV, etc. Not even a finished DVD will play on the computer now.
I have the latest versions updates of Premiere Pro 4.2.1 as well as the Matrox RT.X2 tools.
While the Nvidia driver update situation made the situation worse, I was having problems with Premiere Pro CS4 way before this with 'instant' crashes and no warnings. Strange that Photoshop CS4 works just fine as this has evolved into a video problem...and I need your help to get PP running again.
I'm not a techie so please reply in novice language. When CS4 came out it took Matrox quite a while to get off 'beta' tools upgrade so I waited until it was off beta (April 2010) and had my computer hardware expert upgrade my computer with CS4 and the new Matrox install -- way too technical for me to do. It worked great...until about a month ago when all this started.
I don't think the equipment I have now on my 2006 computer would work with CS5 - maybe you can look below and tell me.
For reference, here is my equipment: XP Professional SP 3; AMD Athlon 64 x 2 dual core processor; 4800+ 2.41 GHz, 3.25 GB RAM; Nvidia Quadro FX1500 256MB; 2 Dell monitors - 2407WFP and ST2410; Matrox RT.X2; 2TB WE Raid Edition SATA 16MB; Blu-Ray burner BDR-2058BK; Pioneer 111 Dual Layer DVD Rewrite Burner; Sound Blaster Audigy4 24 Bit; Built in FD controller 2 IDE on the main board.
Brian

Thanks harm for your suggestions but I'm lost. I am not a techie. Went to your thread on building a new computer and it was way way over my head...so I'm back here asking for your suggestions as I couldn't even figure out how to copy/paste my equipment listed above and post this message there instead.
Took my box back to the vendor who put it together for me in 2006 for $6000 and he's going to try and get it up and running again for me. I told him about your recommendation to lose the Matrox and he doesn't think it's the problem if I want fast rendering, etc. He says he's used RT.X2 in a ton of systems he's put together and work just fine. He's going to try getting my present computer running, first of all without any new additions and then make suggestions. It ran beautifully under CS2, so much so I skipped CS3 and was very late adding on CS4 ... and that's when the problems started. Perhaps CS4 was just too demanding for my 2006 equipment...which probably means CS5 is even more demanding.
So....two questions:
1. If I upgrade what I've got, where do I start? Or is it worth upgrading or better to start brand new (budget problems no doubt)
2. If I start brand new, what do I put in the new box? I looked at your 3 different cost areas and the budget config is probably not what I need but warrior level too high. Even the middle road you recommened looks a little low for what I want to do making BR disks, but you would know.
I assume some of the current equipment I've got could still be used, perhaps even the Matrox if that keeps costs down by not having to replace it with something else. There is a new C drive for my programs and a new 2TB internal hard drive for files (which I mirror backup to an external 2TB drive).
Could you make some build recommendations that I could give to my vendor? Many thanks.
Brian
ps...how do you copy/paste on this forum?

PREMIERE PRO CS4 CRASHES every time I try to export to media....

Import a file in whatever format (MPEG 2, MPEG 4, AVI, etc.), I add effects (or leave the file untouched) and then try to export it to MEDIA...Then Premiere Pro CS4 crashes giving me this error:
Premiere Pro has encountered an error.
[..\..\Scr\Component\ComponentFactory.cpp-119]
After pressing "continue" it brings another message:
Sorry, a serious error has ocurred that requires Adobe Premiere Pro to shut down. We wil attempt to save your current project.
I press OK and the Crash Report dialog box appears....
I installed Premiere Suite 3 weeks ago and I have never used this software before....Premiere has never allowed me to export any file...
My Lap Top has Windows 7 Ultimate - 64 with NVidia GT 130 1 GB video card, 8 GB of RAM, 1 TB of HD and 1920 x 1080 P display...
Any advice? or somebody who has had the same problem?
Thanking you for your time and courtesies in assisting me, please receive my best regards.
AZUARO

Have you just installed the software or applied
updates also?
Updates are needed for premiere as well as Media and other.......
Ciao
Giorgio

Mac Pro keeps crashing while sleeping.

MacPro3,1 Quad-Core Intel Xeon, 2.8 GHz, 6 GB running OSX 10.10.1
Mac Pro keeps crashing while sleeping. Just did a clean install of Yosemite so not a lot of extras loaded on this machine.
Crash log is below, can anyone help?
Crash log
Anonymous UUID: F22DEA9F-F3D7-E141-BC81-27F54620A33A
Sat Dec 27 09:48:40 2014
*** Panic Report ***
panic(cpu 4 caller 0xffffff80105ff683): "TLB invalidation IPI timeout: " "CPU(s) failed to respond to interrupts, unresponsive CPU bitmap: 0x84, NMIPI acks: orig: 0x0, now: 0x0"@/SourceCache/xnu/xnu-2782.1.97/osfmk/x86_64/pmap.c:2471
Backtrace (CPU 4), Frame : Return Address
0xffffff80e1953970 : 0xffffff801053a811
0xffffff80e19539f0 : 0xffffff80105ff683
0xffffff80e1953a80 : 0xffffff8010605913
0xffffff80e1953b70 : 0xffffff80106065e5
0xffffff80e1953bd0 : 0xffffff80105b6b4a
0xffffff80e1953ce0 : 0xffffff80105acd2c
0xffffff80e1953d10 : 0xffffff80105a9013
0xffffff80e1953d40 : 0xffffff8010a79eb0
0xffffff80e1953d60 : 0xffffff8010afe8e3
0xffffff80e1953dc0 : 0xffffff80105e8e54
0xffffff80e1953e10 : 0xffffff801053e91c
0xffffff80e1953e40 : 0xffffff80105235a3
0xffffff80e1953e90 : 0xffffff8010533e8d
0xffffff80e1953f10 : 0xffffff801060a142
0xffffff80e1953fb0 : 0xffffff801063ac66
BSD process name corresponding to current thread: UserEventAgent
Mac OS version:
14B25
Kernel version:
Darwin Kernel Version 14.0.0: Fri Sep 19 00:26:44 PDT 2014; root:xnu-2782.1.97~2/RELEASE_X86_64
Kernel UUID: 89E10306-BC78-3A3B-955C-7C4922577E61
Kernel slide: 0x0000000010200000
Kernel text base: 0xffffff8010400000
__HIB text base: 0xffffff8010300000
System model name: MacPro3,1 (Mac-F42C88C8)
System uptime in nanoseconds: 9286723571276
last loaded kext at 911450085459: com.apple.iokit.IOSCSIBlockCommandsDevice 3.7.0 (addr 0xffffff7f92ef0000, size 81920)
last unloaded kext at 1089150090027: com.apple.driver.AppleUSBCDC 4.2.2b5 (addr 0xffffff7f92edb000, size 16384)
loaded kexts:
com.apple.driver.AppleRAID 4.0.6
com.apple.driver.AppleBluetoothMultitouch 85.3
com.apple.driver.AudioAUUC 1.70
com.apple.iokit.IOBluetoothSerialManager 4.3.1f2
com.apple.filesystems.autofs 3.0
com.apple.driver.AppleOSXWatchdog 1
com.apple.driver.AppleUpstreamUserClient 3.6.1
com.apple.driver.AppleMCCSControl 1.2.10
com.apple.kext.AMDFramebuffer 1.2.8
com.apple.driver.AppleHDA 267.0
com.apple.iokit.IOUserEthernet 1.0.1
com.apple.AMDRadeonX3000 1.2.8
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.iokit.CSRBluetoothHostControllerUSBTransport 4.3.1f2
com.apple.driver.AppleHWAccess 1
com.apple.driver.AppleLPC 1.7.3
com.apple.kext.AMD5000Controller 1.2.8
com.apple.driver.AppleMCEDriver 1.1.9
com.apple.driver.AppleHV 1
com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0
com.apple.iokit.SCSITaskUserClient 3.7.0
com.apple.driver.XsanFilter 404
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.BootCache 35
com.apple.iokit.IOAHCIBlockStorage 2.6.5
com.apple.driver.AppleIntel8254XEthernet 3.1.4b1
com.apple.driver.AppleUSBHub 705.4.1
com.apple.driver.AppleFWOHCI 5.5.2
com.apple.driver.AppleAHCIPort 3.0.7
com.apple.driver.AirPortBrcm43224 700.36.24
com.apple.driver.AppleIntelPIIXATA 2.5.1
com.apple.driver.AppleUSBEHCI 705.4.14
com.apple.driver.AppleUSBUHCI 656.4.1
com.apple.driver.AppleACPIButtons 3.1
com.apple.driver.AppleRTC 2.0
com.apple.driver.AppleHPET 1.8
com.apple.driver.AppleSMBIOS 2.1
com.apple.driver.AppleACPIEC 3.1
com.apple.driver.AppleAPIC 1.7
com.apple.driver.AppleIntelCPUPowerManagementClient 218.0.0
com.apple.nke.applicationfirewall 161
com.apple.security.quarantine 3
com.apple.security.TMSafetyNet 8
com.apple.driver.AppleIntelCPUPowerManagement 218.0.0
com.apple.iokit.IOSCSIBlockCommandsDevice 3.7.0
com.apple.iokit.IOUSBMassStorageClass 3.7.0
com.apple.driver.IOBluetoothHIDDriver 4.3.1f2
com.apple.driver.AppleMultitouchDriver 260.30
com.apple.iokit.IOSerialFamily 11
com.apple.kext.triggers 1.0
com.apple.driver.AppleSMBusController 1.0.13d1
com.apple.driver.DspFuncLib 267.0
com.apple.kext.OSvKernDSPLib 1.15
com.apple.iokit.IOAudioFamily 200.6
com.apple.vecLib.kext 1.2.0
com.apple.iokit.IONDRVSupport 2.4.1
com.apple.iokit.IOAcceleratorFamily2 156.4
com.apple.iokit.IOSurface 97
com.apple.iokit.IOBluetoothHostControllerUSBTransport 4.3.1f2
com.apple.iokit.IOBluetoothFamily 4.3.1f2
com.apple.iokit.IOFireWireIP 2.2.6
com.apple.kext.AMDSupport 1.2.8
com.apple.AppleGraphicsDeviceControl 3.7.21
com.apple.driver.AppleHDAController 267.0
com.apple.iokit.IOGraphicsFamily 2.4.1
com.apple.iokit.IOHDAFamily 267.0
com.apple.iokit.IOUSBUserClient 705.4.0
com.apple.driver.AppleSMC 3.1.9
com.apple.driver.IOPlatformPluginLegacy 1.0.0
com.apple.driver.IOPlatformPluginFamily 5.8.0d49
com.apple.driver.AppleUSBHIDKeyboard 175.5
com.apple.driver.AppleHIDKeyboard 175.5
com.apple.iokit.IOUSBHIDDriver 705.4.0
com.apple.driver.AppleUSBMergeNub 705.4.0
com.apple.driver.AppleUSBComposite 705.4.9
com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.7.0
com.apple.iokit.IOBDStorageFamily 1.7
com.apple.iokit.IODVDStorageFamily 1.7.1
com.apple.iokit.IOCDStorageFamily 1.7.1
com.apple.iokit.IOATAPIProtocolTransport 3.5.0
com.apple.iokit.IOSCSIArchitectureModelFamily 3.7.0
com.apple.iokit.IOFireWireFamily 4.5.6
com.apple.iokit.IOAHCIFamily 2.7.0
com.apple.iokit.IO80211Family 700.52
com.apple.iokit.IONetworkingFamily 3.2
com.apple.iokit.IOATAFamily 2.5.3
com.apple.iokit.IOUSBFamily 705.4.14
com.apple.driver.AppleEFINVRAM 2.0
com.apple.iokit.IOHIDFamily 2.0.0
com.apple.driver.AppleEFIRuntime 2.0
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.sandbox 300.0
com.apple.kext.AppleMatch 1.0.0d1
com.apple.driver.AppleKeyStore 2
com.apple.driver.AppleMobileFileIntegrity 1.0.5
com.apple.driver.AppleCredentialManager 1.0
com.apple.driver.DiskImages 389.1
com.apple.iokit.IOStorageFamily 2.0
com.apple.iokit.IOReportFamily 31
com.apple.driver.AppleFDEKeyStore 28.30
com.apple.driver.AppleACPIPlatform 3.1
com.apple.iokit.IOPCIFamily 2.9
com.apple.iokit.IOACPIFamily 1.4
com.apple.kec.corecrypto 1.0
com.apple.kec.Libm 1
com.apple.kec.pthread 1
Model: MacPro3,1, BootROM MP31.006C.B05, 8 processors, Quad-Core Intel Xeon, 2.8 GHz, 6 GB, SMC 1.25f4
Graphics: ATI Radeon HD 5770, ATI Radeon HD 5770, PCIe, 1024 MB
Memory Module: DIMM Riser B/DIMM 1, 2 GB, DDR2 FB-DIMM, 800 MHz, 0x802C, 0x31384832353637324A445A38304547314436
Memory Module: DIMM Riser B/DIMM 2, 2 GB, DDR2 FB-DIMM, 800 MHz, 0x802C, 0x31384832353637324A445A38304547314436
Memory Module: DIMM Riser A/DIMM 1, 1 GB, DDR2 FB-DIMM, 800 MHz, 0x830B, 0x4E543147543732553839443642442D414320
Memory Module: DIMM Riser A/DIMM 2, 1 GB, DDR2 FB-DIMM, 800 MHz, 0x830B, 0x4E543147543732553839443642442D414320
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x88), Broadcom BCM43xx 1.0 (5.10.131.36.16)
Bluetooth: Version 4.3.1f2 15015, 3 services, 26 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en2
PCI Card: ATI Radeon HD 5770, Display Controller, Slot-2
PCI Card: ATI Radeon HD 5770, ATY,HoolockParent, Slot-2
PCI Card: pcif6ff,194, Slot-4
Serial ATA Device: ST2000DM001-9YN164, 2 TB
Serial ATA Device: WDC WD1001FALS-41K1B0, 1 TB
Serial ATA Device: Hitachi HDS721010KLA330, 1 TB
Parallel ATA Device: PIONEER DVD-RW DVR-112D
USB Device: My Passport 0730
USB Device: Bluetooth USB Host Controller
USB Device: USB Hub
USB Device: Keyboard Hub
USB Device: Apple Keyboard
FireWire Device: built-in_hub, Up to 800 Mb/sec
Thunderbolt Bus:

The panic was caused by the MAXPower device or its software, maybe with help from one or more of the other third-party system modifications you've installed.
First check the manufacturer's website for an update. If there is none, or if it doesn't help, I suggest you remove the device, back up all data, and then remove the software according to the manufacturer's instructions. Reboot and see whether there's an improvement. If there isn't, post another panic report.

Premiere Pro keeps crashing when using overwrite (.) shortcut in Source Monitor

When editing a clip in the source monitor and then using the (.) key to overwrite the clip onto my timeline Premiere Pro keeps crashing. If I select the Timeline window and then press the (.) key it works fine, but if the Source Monitor is highlighted and I press (.) it crashes every time and shows these windows:
Premiere Pro has encountered an error.
[/Volumes/BuildDisk/builds/mightykilt/shared/
adobe/Mediacore/Backened/Make/Mac/../../Src/
Sequence/LinkContainer.cpp-184]
and then opens this one:
Adobe Premiere Pro
Sorry, a serious error has occured that requires
Adobe Premiere Pro to shut down. We will attempt to
save your current project.
It saves my current project as a copy, which is good, but I've now ended up with lots of copies of the same project as it keeps on crashing. In order to work I have to make sure that the Timeline is highlighted before I use the shortcut. It makes for very precarious and tense editing!
I've tried to update my system (I have the Production Premium Suite), but it came up with this:
Adobe Bridge CS6 5.0.2 Update
There was an error installing this update. Please quit and try again later. Error Code: U44M1I200
Extension Manager 6.0.5 Update
There was an error installing this update. Please quit and try again later. Error Code: U44M1I200
Prelude CS6 1.0.2 Update
There was an error installing this update. Please quit and try again later. Error Code: U44M1I200
Adobe Photoshop 13.0.5
There was an error installing this update. Please quit and try again later. Error Code: U44M1I200
Photoshop Camera Raw 8.1(CS6)
There was an error installing this update. Please quit and try again later. Error Code: U44M1I200
DPS Desktop Tools CS6 26.0.0 Update
There was an error installing this update. Please quit and try again later. Error Code: U44M1I200
Adobe Illustrator CS6 Update (version 16.0.4)
There was an error installing this update. Please quit and try again later. Error Code: U44M1I200
Dynamic Link Media Server CS6 1.0.1 Update
There was an error installing this update. Please quit and try again later. Error Code: U44M1I200
Adobe SpeedGrade CS6 6.0.4 Update
There was an error installing this update. Please quit and try again later. Error Code: U44M1I200
Adobe InDesign CS6 8.0.1 update
There was an error installing this update. Please quit and try again later. Error Code: U44M1I200
Adobe After Effects CS6 11.0.2 Update
There was an error installing this update. Please quit and try again later. Error Code: U44M1I200
Fireworks CS6 update to improve Mac 10.8 platform compatibility and resolve usability bugs.
There was an error installing this update. Please quit and try again later. Error Code: U44M1I200
Adobe Media Encoder CS6 6.0.2 Update
There was an error installing this update. Please quit and try again later. Error Code: U44M1I200
Adobe Audition CS6
There was an error installing this update. Please quit and try again later. Error Code: U44M1I200
Adobe Premiere Pro CS6 6.0.2 Update
There was an error installing this update. Please quit and try again later. Error Code: U44M1I200
Flash Pro CS6 update 2
There was an error installing this update. Please quit and try again later. Error Code: U44M1I200
I'm using a MacBookPro 15", OS X 10.8.4 and editing footage filmed at 24fps 1920x1080 on my Canon 550D/T2i. All .MOV files.
I purchased my software from iSoftware.co.uk. I'm worried that could be the problem.
Any help would be hugely appreciated. Thank you.
Sam

A crash with a very similar error message was fixed in the new CC release. The bug report in that case involved creating a multi-cam sequence, so it might not be directly related.
If you have a chance to download the CC trial, we'd be interested to know whether the crash remains in the new version.

Premiere Pro CC Crashes While Rendering With Mercury OpenCL

Similar Messages

Maybe you are looking for