Skip to main content
Participant
September 6, 2024
Answered

Fix for the GPU render Error -1609629695

  • September 6, 2024
  • 3 replies
  • 1133 views

Hello,

 

Just wanted to help for those who wants to find a solution for the the Error -1609629695.

 

No CPU overheating, export without Cuda, Media cache delete, PC restart, Sequence in an out, changing Windows swap file size, freeing up 100 gb extra space, exporting to another disc, exporting  only 1 hour of footage - nothing worked.

 

This was the solution worked for me: https://helpx.adobe.com/premiere-pro/kb/fix-premiere-pro-crash-issues.html

 

New project / Worksplace, Windows / Worksplace, Import from Worksplace, then File / Import the project file.

 

Please close this thread, but don't delete it, let others to be able to find it with Google Search.

Correct answer Kevin-Monahan

Hi @habala_0288,

I see, so importing your project into a brand new project fixed your issue. Thanks for reporting back.

 

Cheers,
Kevin

3 replies

Inspiring
May 3, 2025

Did not work:
Importing into new project 
Resetting prefs
Rendering in to out (worked, but subsequent export failed, even using same format as previews)
exporting in media encoder worked with quicktime, but with render artifacts, failed exporting to h.264

Rolling back to 25.1 worked for me.  Colour managment issue? 

Its a long time since I've had this type of error with premiere.  I am now kicking myself for updating to the current version.  

I'm assuming people are experiencing this in the latest version?

 

Project settings> general> renderer
Software only is no longer an option in here.  Where has that gone?


 

Participating Frequently
February 17, 2025

Hi, I'm still getting the error, your fix does not work for me with the same error code.

File > New > New Project > Import Project. Go to render, still getting problem. I check the timeline where the error occurs, absolutely nothing wrong with the files, or anything when pre-rendered in AE, the second I go to AME, it still crashes.

Participant
May 3, 2025

same for me :// what did you end up doing?

 

Kevin-Monahan
Community Manager
Kevin-MonahanCommunity ManagerCorrect answer
Community Manager
October 9, 2024

Hi @habala_0288,

I see, so importing your project into a brand new project fixed your issue. Thanks for reporting back.

 

Cheers,
Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio