My friend has a mac pro 5,1 with w3680 cpu. He said he gets crashes in premiere. I've been trying to help him out but when I'm at his house I can't reproduce the crash. I've run geekbench to see if I can't crash the machine too and it doesn't crash. He keeps saying he thinks it's related to temp so I installed istat. This is the values he gets in istat. Can someone help let me know how this looks?
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Crashing in Adobe Premiere, temp related?
- Thread starter joebclash
- Start date
- Sort by reaction score
Premiere crashes all the time, every day, for many different reasons.
Those stats don't look too bad, but is that at idle or during load? We'll definitely need more info to troubleshoot, like what he's specifically doing in Premiere (editing, transcoding/exporting, etc), the OS, version of Premiere, etc.
Those stats don't look too bad, but is that at idle or during load? We'll definitely need more info to troubleshoot, like what he's specifically doing in Premiere (editing, transcoding/exporting, etc), the OS, version of Premiere, etc.
That was taken about 5 minutes after running geekbench cpu testing. For some reason he's gotten in his head the premiere crash is related to cpu temps. I was running geekbench to see if I can get some sort crash. He said he was getting crash during exporting alot of the times. I did notice after running geekbench gpu testing there some graphics glitch in Chrome. Perhaps a gpu issue?
Crash during export is USUALLY related to an un-rendered effect or plugin issue with the GPU acceleration renderer (CUDA/Metal/OpenCL).
Try to force render the entire timeline and then export with "match sequence settings". Then make compressions in Media Encoder. This is the workaround Adobe will first recommend after 8 hours of haggling with them.
If your timeline is very long or has multiple clips with effects (color is an effect!), render sections at 0:30-0:60 intervals with render in to out. This helps to pick out an offending clip or effect.
Some older/legacy Red Giant plugins need to be updated for CC 2018. There is a Red Giant updater that automatically checks this, but some MAY need to be upgraded to the latest versions.
Some of the built-in Adobe effects have known to be problematic on stacked layer renders in the past, such as morph cut and warp stabilizer. If using those, place into their own timeline, render the effect, export matching sequence settings, then bring the render back into your main timeline. Again, a workaround but works.
Try to force render the entire timeline and then export with "match sequence settings". Then make compressions in Media Encoder. This is the workaround Adobe will first recommend after 8 hours of haggling with them.
If your timeline is very long or has multiple clips with effects (color is an effect!), render sections at 0:30-0:60 intervals with render in to out. This helps to pick out an offending clip or effect.
Some older/legacy Red Giant plugins need to be updated for CC 2018. There is a Red Giant updater that automatically checks this, but some MAY need to be upgraded to the latest versions.
Some of the built-in Adobe effects have known to be problematic on stacked layer renders in the past, such as morph cut and warp stabilizer. If using those, place into their own timeline, render the effect, export matching sequence settings, then bring the render back into your main timeline. Again, a workaround but works.
Just to be clear the screen shot was 5 minutes after the geekbench cpu test completed. Since I helped him upgrade this cpu he wants me to help him reapply thermal paste. I just don't think that will help. I think this is more with an issue with the used gtx 1050 ti he bought used on ebay...
I just bought a 1060 on eBay. I installed the suggested Nvidia and Cuda driver for High Sierra 10.13.5, but PP crashed on export. CUDA wouldn't show up as a Render Engine option either, just Open CL, Metal, and Software, so (I posted on this forum today about this) I updated to the latest 10.13.6 High Sierra, then updated to the newest NVidia driver (after deleting all old NVidia files). Now CUDA shows up as an option in PP and it exports fine (and fast).
Remove CUDA (simple remove the system preference), change Premiere to OpenCL, and then testing for a while.
it's worth trying to change the GPU render mode from CUDA to openCL, iv been having crashes in resolve 15 beta with openCL & CUDA but no crash's with metal.
and things like turning of one plugin at a time to see if crash stops is also worth a go.
if you do think it's temps get a screen shot during work.
@bsbeamer is on the dot with info needed for troubleshooting
and things like turning of one plugin at a time to see if crash stops is also worth a go.
if you do think it's temps get a screen shot during work.
@bsbeamer is on the dot with info needed for troubleshooting