Premiere Pro Crashing Issue

[commsd86558115]

Dear Adobe Support Team,

I am experiencing a recurring issue with Adobe Premiere Pro that is severely impacting my workflow. Whenever I work on my project, the software suddenly closes, especially when I add effects or modify anything. This issue has been happening since yesterday, and I have tried various troubleshooting methods, including uninstalling and reinstalling the program, but the problem persists.

I am unable to make progress on my project due to this issue and would appreciate your urgent assistance in resolving it.

Thank you for your help.

Best regards,

[okwhatsthematter]

looks like there is a new update for beta

[Aitor.de.iturria]

Yeahhh! The new 25.1 works with my project. They fixed

[Matthijs_]

Great that we have a fix now, thank you for posting that Fergus.

Going forward however, I am really hoping the quality process will be thouroughly reviewed. As mentioned by other, so many projects were in total limbo for days. 

It cannot be that such an obvious bug that even comes to expression in NEW projects (first test case I assume for the quality department), get shipped to every beta program user. 

Really hoping this is taken seriously and improvements are made in this process.

[okwhatsthematter]

looks well optimised also quicker moves in the timeline

[Nick Garcia]

Thanks for the fix, and a quick one too. But I have to agree with Matthijs. It's a bit of a surprise that such a  HUUUUUGE bug that affected almost everyone even went through to be in the update, despite it being a beta issue. Something should be taken more seriously in the update and testing process.

It seems like the issue was even showing the effects control panel regardless of clips or file type. Upon clicking anything, if your workflow had the effects panel enabled it'd be instant crash. How that got through to a patch is beyond me, and with no option to roll back or temporarily continue working with another version.

I just hope some notes were taken so it doesn't happen again, I'll disable auto update from now and always be skeptical to any beta updates. 😕

[Jerel3533864570pz]

This. I'm always forgiving of the issues because I know the risk I take working with beta and am always able to export an XML to get a project back a version... but as I've been very happy with the direction you guys are taking the latest version, I'm wanting to keep working on it. As such, I am also turning off auto-updates and delay updates by a week, keeping an eye on the forums. 

[ramonc72694568]

There should be a rollback option no matter what. I understand its a beta but it does work and these are projects that take time, during that time we can find bugs,  but we cant test anything if we cant trust to do any work on them.  Now I am super cautious trying these betas unless we can roll back to a previous build immediately. This should be no issue.

[R Neil Haugen]

There is always notable potential risks when using anything labeled 'beta' ... so as always, I would never recommend doing anything that has absolute deadlines without a fallback.

The 'standard' part of the year, where the beta and release versions are the same, is actually different. As then ... if the beta chokes, you simply open the release version and go. But now, with the beta being the next major version, we can't.

I was suprised to realize you cannot go back a build with the betas. Really surprised.

[Stuart-M-Rankin]

Same issue for my Adobe CC subscription. I use Adobe PP 2024 builds 24.5 and up. Crashes every few seconds then crashes on startup. MEANWHILE PP Beta works flawlessly.  What gives?  Whole crashing thing is pretty consistent with PP anyway but usually I can get work done. Not this time. The mental crashing started a week and a half ago after an update to 24.6 then 24.6.1. Going back to 24.5 didnt help - just keeps crashing. I have an Nvidia GeForce RTX 4090 GPU, Intel i9-1400k and 192 gb ram on win 11 - definitely within spec 😉 

[Stuart-M-Rankin]

In both Beta and PP standard I get error message when trying to share with Frame.IO. Any thoughts on how to troubleshoot this?

[MyerPj]

Nice rig @Stuart-M-Rankin 

I must ask, are you running any overclocking or head-up display, to show temps or frames ps, etc...

Someone said in a thread, they enabled xmp in the bios, and that was enough to get things working.