"Error completing render" [Elements 2025]

[Mr. Rail]

Hi,

since I have Elements 2025, I have troubles when rendering. The message "error completing render" (screenshot attached).

The timestamp is given. So far, it was always at a cut/between two adjacend videos.

Most common source: there is invalid transition, e.g. a movie transition at the very end of a clip. So I cut a but and then it works (transition is shown striped in the invalid section)

But there are also cases in which two adjacend videos without any transition or with a vialid transition and I just do not know what to do.

Even worse: it is unreasonanle. I just have a film, in which it processed up to minute ten (a cut), then the error. When trying again, new errors occur at earlier cuts, first around Minute 2, next try at the first cut in Second 14.

With the previous Elements 2022 it worked, also invalid cuts were just ignored.

I do not know what to do. It is very frustrating. Even if there are clear invalid cuts, there should be a way to check it before. Otherwise 45 Minutes of processing is lost until an error in Minute 45 or so.

I cannot see any impact of the error. In the rendered preview everything looks and works fine. No error there when rendering.

Has anyone an idea? Any help is highly appreciated!

[Ann Bens]

Delete section as given in the error message from timeline and do the edit again.

If a transition shows diagonal stripes it means the clip has not been trimmed back sufficiently. It uses duplicate frames instead.

On a side note: OneDrive is grand for backup, but not suited for editing. Best is to use a local drive.

[Mr. Rail]

Hi Ann,

thank you very much.

That's the way I tried it. But there are new errors appearing when I process again.

It is a one hour video, I never got after 10 minutes, as new errors appear (with unstripped transitions or even just two adjacend videos).

OneDrive: this is a local SSD drive, it is just syncronized automatically.

[Ann Bens]

As said before use a local drive.

Post computer specs incl gpu driver nr.

[Mr. Rail]

Please find attached the specs. and GPU driver nr. If you need more, let me know.

The onedrive is a local drive in my computer (works also offline). However I changed to export to another location outside the onedrive folder and without syncronisation. No change 😞

It seems random, the problem appears at one cut withing the first five minutes, different in each try.

Best regards,

Simon

[Mr. Rail]

I copied this from system info as well:

Gerätename GIOVA-CENTRAL
Prozessor Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz 3.70 GHz
Installierter RAM 64,0 GB
Geräte-ID 42F98619-FD29-46BC-82B5-6EE7B87CADCD
Produkt-ID 00330-80000-00000-AA196
Systemtyp 64-Bit-Betriebssystem, x64-basierter Prozessor
Stift- und Toucheingabe Unterstützung der Toucheingabe mit 10 Touchpunkten

Edition Windows 11 Pro
Version 23H2
Installiert am ‎10.‎12.‎2023
Betriebssystembuild 22631.4541
Leistung Windows Feature Experience Pack 1000.22700.1055.0

[Ann Bens]

Update windows and your gpu driver (manually to the most current studio driver).

[Mr. Rail]

Hi,

I found a youtube video and maybe it is the same problem - this would explain why it happens only in a few videos and normally everything works fine:

In the video there are clips in which the timing has changed (made quicker or in my case slower). According to the Youtuber this kills elements. His recommendation: slize the video.

I did. I rendered the one hour project in 9 slizes, means I have nine processed videos. As each of it only took a few minutes I could just retry if the error came, latest after the third time it worked.

Then I created a new project, added the nine prepocessed videos. And rendered it as a whole. It worked quickly without any issues and I have the 1 hour video now ready. (but slizing is really a punishing job).

So I assume, the speed changed clip could be the course. I never had that issue in my news programme, in which I never change speed of clips. The Youtuber says, there is a bug in Premiere Elements.

I checked Windows, MSI and NVDIA for new driver, but newer nothing is offered currently.

This is the video: https://youtu.be/EA2G7sD_ySM?si=7cuTwlJ4nw50NqoI

[Ann Bens]

Elements 2025 is different from the older versions.

Might  want to check again.

Big update for windows 24H2

Your nvidia driver is from sept 2024. Been several driver updates since. (update manually)

https://www.nvidia.com/en-us/drivers/

Most likely your mobo needs updating too.

[Mr. Rail]

Hi,

I found the driver updated and installed it (NVDIA).

I know it is an older video with the old Elements. But the workaround works and the problem seems the same.

No change. Video with clips with changed speed: problem!

Project without clips with changed speed: no problem!

I will test further to see whether this remains the problem.

[Ann Bens]

What kind of video are you using for speed ramps.

Variable framerate mode is known to give issues.

Post screenshot of media in MediaInfo in TREEVIEW.

[Mr. Rail]

Please find attached the info of one of the files I changed the speed in the project.

The project is out of about 80 clips, of which 10-15 the speed has been changed.

[Ann Bens]

Your issue is most likely the Frame Rate mode which is variable. Needs to be constant.

Convert the clips you use for speed ramp to constant framerate mode with Handbrake before bringing them into Premiere.

You can use the Replace footage option .

Converting videos with Handbrake - YouTube

HEVC can also cause issue as its a heavily compressed codec.

[Mr. Rail]

OK, thank you very much.

I just found that I can suppries variable frame rates at my recording device (Samsung S24). So hopefully we finally found the issue and everything works as expected in future 🙂

I can select HECV and H.264 to record, Samsung recommends HEVC for high quality and H.264 for high compatibility.

[Ann Bens]

What the Phone manufacturer recommends and what an edit program can do are two different things.

Find a camera app for your phone that records in constant framerate mode: will save a lot of headaches.

Variable framerate is a well-known issue in the editing world.

[Mr. Rail]

OK, thank you for the explanation. I found the option to switch of the variable frame rate. Will do and test 🙂