Skip to main content
Participant
May 10, 2025

Premiere Pro Project Crash for specific saved project.

  • May 10, 2025
  • 8 replies
  • 672 views

I have a project file I work with weekly for a client, every week I create new reels and shorts. 3 Days ago I saved the project, now every time I open it the thing crashes. 

 

Even auto-saved files past a certain hour crash. 

When I open a new project and import sequences, the new project also crashes after saving and opening again.


I have uninstalled and reinstalled clean versions.
I have installed older versions. 
I have uninstalled all 3rd party plugins.
I have updated all drivers, Bios, CPU, GPU,  C++

I have followed every step on this
website. https://helpx.adobe.com/premiere-pro/kb/fix-premiere-pro-crash-issues.html

I have sent hundreds of crash reports and have a few saved .dmp files I could send. 

 

1) Version 25.2.3 
2) Windows 11 







 

8 replies

Bruce Bullis
Community Manager
Community Manager
May 12, 2025

Even VST audio plugins, which are not managed by PPro's Plugin Manager...?

V-AAuthor
Participant
May 12, 2025

Not in the office yet, will check when I have a chance. But I did uninstall all 3rd party plugins and it did not resolve. 

Community Manager
May 12, 2025

Hello @V-A
Did looking into Bruce's solution work for you?

Bruce Bullis
Community Manager
Community Manager
May 12, 2025

The crash reports from your email address all point to crashes within the ERA6_NoiseRemoverPro.vst3 plugin.

MyerPj
Community Expert
Community Expert
May 10, 2025

Obviously, make sure you have copies of all the things you will be testing with.

You can rename the folders the media is in, and try loading the project w/out media, sort of like the others are saying, but it's easy to do.

Peru Bob
Community Expert
Community Expert
May 10, 2025

Try removing media or sequences one at a time to see if something is corrupting the project.

V-AAuthor
Participant
May 10, 2025

Everything is local on C

Participating Frequently
May 10, 2025

You can try disconnecting all external hard drives and mapped network shares and see if somehow your project will open. If it does, then go back and reconnect one by one and find whcih one(s) are causing the conflict upon opening that project. Has happened to me before but I was on Mac.