I dont think I'm alone in not having a clue why renders fail. Its hard to be scientific about it when the exact same clip will fail at random points. This is the error: its always the same code. - Encoding Time: 00:01:10 03/02/2017 03:40:21 PM : Encoding Failed ------------------------------------------------------------ Export Error Error compiling movie. GPU Render Error Unable to process frame. Writing with exporter: H.264 Writing to file: \\?\D:\was on q\video\southbankrd524_red-sky GJ Kennedy.mp4 Writing file type: H264 Around timecode: 00:00:19:02 - 00:00:19:11 Rendering effect: AE.ADBE Lumetri Rendering at offset: 19.080 seconds Component: EffectFilter of type GPUVideoFilter Selector: 9 Error code: -1609629695 Sometimes closing premiere and clearing the media cache helps, sometimes I have to reset the prefs too. Usually I end up rebooting. Premiere now also occasionally crashes when I got to export. Once it's crashed in this manner it will continue to. I have to select a small piece of footage to export, to get the export diologue to open, then it will open on the full clip. Just for a giggle I reset the status in AME, and kept trying to render. It failed at 35, 19, 51, 21, 14.03, 14.18, 14.120, 17.9 then I lost the will to live. It also failed on export from premiere at random times. This is a typical sequence: 2 of the adjustment layers have a lumetri effect with different Blend modes. Each clip has 1-4 lumetri effects - some masked. is there anything unusual here? Am I asking premiere to do something it wasn't designed for? If I knew for a fact that it was a hardware issue I would replace my video card (gtx970). But its always been like this. If I knew if it was the blend modes on the adjustment layers or something - anything - that I could work on to eliminate I would, but why is it random?! Why?!!? Edit: windows 10, creative suite (up to date). i7 5920K, 64gb RAM. Mem tested ram, stress tested system including graphics card. All fine. My system drive is an 850 evo, files are on a raid 5. So I just rebooted, and the exact same Ame job rendered. I just reset the status and it completed no problem. So its NOT an issue with premiere cache files or prefs - those times it rendered after doing that was just coincidence. Mod note: Title of the post has changed to reflect the issue. Thanks, KM
... View more