The problem with an Unknown Error is that the cause is...unknown. Without that, there's no surefire fix. You'll have to experiment with different things. Try to render small sections to see if you can find where it fails. Try removing effects to see if one of them is a problem. Try exporting to a different hard drive, to a different codec, to a different resolution.
Hi Jim, I contacted the Adobe help guys directly and they took over my computer in order to try and figure it out. We went through tons of troubleshooting ( I had already) and it turns out that the Premiere project has to be on the local drive and the associated media can still be on external HDs, it can also export to External HDs providing the proj file is on the local drive. But if the Project file is located in the same folder as the media files on the external HD it cant render or export - so my suggested workflow is keep the project file on the local drive. So every new machine I want to take the project to I have to import the project into a new clean project saved on the local drive. I am used to FCP 7 and CS3 but this seems absured to me. I am dissapointed with CC so far.
I'm experiencing the same problem. I tried moving my project file over (don't ask why I didn't copy it, I was frustrated!) and now Premiere tells me it's damaged!! Is there anyway to reverse this??
The Adobe KB Article (http://helpx.adobe.com/premiere-pro/kb/error-compiling-movie-rendering -or.html ) does not answer the question asked, because the end of the error message is "Unknown error" which is not listed in this article.
I often encouter this error which is a RANDOM error which occurs only with pictures (4256x2832 .jpg or more when I use panoramic pictures with more than 50 MPx) but never with video (1920x1080 HD .m2ts) from my camcorder. The only way I found to do a complete render is :
- save and close the project without editing it,
- close Adobe Premiere Pro (CS6 or CC, same error),
- reopen Premiere Pro and reload the project,
- resume the render.
If I render WITHOUT Mercury Playback Engine : all is perfect, no error but the render needs very much more time.
My own conclusion : this render crash might be due to VRAM oveflooded during render with Mercury Playback Engine (this might be checked and monitored with the freeware GPU-Z).
My GPU is GTX 570 with 1280 MB VRAM and the render are only full HD (H.264 1920x1080i).
If you have a solution except remove the GPU and purchase a GTX 770 OC 4 GB VRAM, I am waiting for it.
My actual system :
- CPU Intel core i7 970 (6 cores, overeclocked to 3,9 GHz),
- MoBo : Intel DX58SO2,
- RAM : 24 GB,
- GPU GTX570 with VRAM 1280MB (Nvidia driver allways up-to-date),
- HDD : RAID 10 with four WD 1002FAEX (7200 tpm, 64 MB cache),
- OS W7 64 SP1, 64 bits (allways updated)
I just updated to the newest update premiere pro cc 2015 and I'm having the same issue with exporting my media. I've tried to move the project file to the local drive but it still doesn't work when I'm exporting to h264. I seem to be able to export with a quicktime wrapper in the CINEFORM codec. But so far, the newest update has been completely screwing me up with most of my renders. Sometimes its a problem that I can fix by exporting out sections of my timeline and finding the faulty media and replacing it (but having to do that is stupid because I've never had to do that before until this update). However, since updating, I have had an enormous amount of problems with most every single project I wish to export. We never had this problem with the older versions of premiere. And now, when a deadline is coming up, I have to troubleshoot EVERY SINGLE TIME to export my project. This is not a good thing. Please help!
Windows 10 Pro
Intel(R) Xeon(R) CUP E5-2597 v3 @ 2.60GHz
64-bit Operating System, x64-based processor
x2 NVIDIA GeForce GTX 980 Graphics Cards