Crash on Launch

[Jordan Clay]

Premire crashes on pretty much ALL of my projects. I launch premiere click on recent, the splash screen will come up start loading into the project and as the media starts to populate it crashes.

• Updated cloud
• Updated premire
• Updated Drivers (CPU,GPU you name it I updated it)
• cleared all cache
• cleared profiles
• Installed older versions (went back 5 versions)
• Started New Sequence Imported old sequence
• Took off GPU accel
• Changed Cache folder location
• Uninstalled ALL 3rd party plugins
• Used beta compatibility check (Everything is good)
• Renamed Project
• launched project from premiere, launched project from windows explorer

I have spent hours upon hours Ive been up since 6am thats 4 more hours of doing nothing but trying to get a project to launch. Will a dev for the love of god check my .DUMP file to see what is going on. This is a $11,000 project that has had constant delays because premiere will not launch my projects. I have 16 classes with over 3 hours of footage each all of them have closed captions and If I have to start over this is 100s of hours of work LOST because of a program.

Ryzen 5950x

AMD 5700

I NEED A DEV TO LOOK AT MY DUMP FILES PLEASE BECAUSE THIS HAS BEEN GOING ON FOR MONTHS AND NO ONE CAN GIVE ME A SOLUTION

Mod note: Title was changed to reflect your issue.

[Blate Papes]

Hey bro!

Not sure if this will help, but I had been having a constant problem with pausing/freezing/playback during editing for months, getting progressively worse. I was working on a big 4K project that was taking me FOREVER because of this. I asked for help on here but no one gave me answers. Finally I found out about deleting all preference files at app startup. I did this, and bam my computer and project are beasts again.

I'm not sure if you already did it, and I'm sorry if so. But just figuring that it helped me, I thought I'd mention it here.

I'm on a mac, so when starting the app, you hold shift+option+command. Then a little screen pops up with 4 options to choose from that lets you delete all preference files.

Again, sorry if you've already done this, just thought I'd mention it since I asked for help 3 times and no one even mentioned this was a thing. This is the link I used to do it: https://helpx.adobe.com/in/premiere-pro/using/reset-preferences.html

[Jordan Clay]

I sincerily appreciate your help. I have done this and it does help "load into the project" faster however when the project starts loading the clips it still crashes. This helps for one launch. I'll put it like this. If I launch the project 50 times ONE time it will open and I can start working. However if I close the project I will have to start relaunching the project 50-100 times again before It will start without crashing. Being able to open the project and work if I keep launching it over and over and over tells me that this is completely random. If there was something my computer was doing then 100% my hardware couldnt physically open it. There is a bug that is probably an error that can be bypassed if you keep relaunching the project. Sometimes i can launch it 3 times and start working, Sometimes I have to launch it 10 times before it works. Today I have launched it well over 100 times just to start working. Its absoloutley abysmal that it takes me 4 hours to START WORKING.

[Peru Bob]

I wonder if you might be experiencing a failing hard drive?

[Jordan Clay]

I thought so too. Every drive that I use has the very same issue. Internal/External doesnt matter.

No other program has issues. After Effects works just fine. Davinci works just fine. Any other program I use on my computer that isn't Premiere or Media Encoder works absolutely flawless. I never get blue screens or hangs. These two programs are the only two things that refuse to work properly.

[Richard M Knight]

Is there anything unusual with your audio hardware and settings?

[Jordan Clay]

I use professional DAW's (reaper) for audio engineering. I have done audio for years. My Audio Interface Never gives me problems. I unplugged it and went straight into onboard audio, the problem still persists. I have uninstalled a huge number of  VST's to see if that was a cause, the problem still persists. Thanks for the recommendation but I'm pretty sure I have went over everything besides a complete fresh install of Windows and I have come to the conclusion that either a dev needs to look at my DUMP files to see what is going on, or for the next few months ill just have to keep bugging the forums. I have tried all of the "Do this if your premiere is crashing" tutorials on here, I have spoken to customer service as they guided me through everything. I'm at the point where I just want to use the program without wasting hours just trying to have a stable program. As of right now I have spent close to $1,000 just to use premiere, I am paying for a monthly "service" I would like some assistance from someone who can look into my problem.

[Kevin-Monahan]

Hi @Jordan Clay,

I got your note. If you create a new project, does the same thing happen? Can you share any of these files so I can forward them to the devs? See if this thread may hold a solution for you: https://community.adobe.com/t5/premiere-pro-bugs/premeire-pro-crashes-immediately-after-launch/idc-p...

I hope the community and devs can assist you. I'll move this post into the Bugs forum, as well. Sorry for the frustration.

Thanks,
Kevin

[jstrawn]

"I NEED A DEV TO LOOK AT MY DUMP FILES PLEASE..."
Have you attached a dmp file somewhere? I did not see one. If you can repro the problem on demand then please collect the dump file and send it to me via direct message.

[Jordan Clay]

I PM'D @jstrawn thank you @Kevin-Monahan 

[Kevin-Monahan]

Fantastic. James is the man. He should be able to assist you. Please post back any solutions, if you don't mind and have time.

Thanks,
Kevin

[Jordan Clay]

If James can solve my problem I will definetly post it and I'll buy him a round.

[Kevin-Monahan]

Nice!

[jstrawn]

I can't promise to solve it but the dmp file and other details I see in that direct message are a good start. Thanks for working with us on this. I'll be in touch directly.

[Jordan Clay]

Guys @jstrawn took a look at my DUMP and found a VST (MagicDeathEye_64) that I use for my Audio was the culprit. I uninstalled it and everything works now no crashes. @Kevin-Monahan Thanks for everything BIG THANK YOU to @jstrawn he took the time out of his day to help me and I am very thankful. If you're also an audio Engineer using Pro tools, Reaper, and you have piles of VST's one of them may be the reason your premiere is crashing. Hopefully this helps someone out there pulling their hair out like me.

[jstrawn]

OK that's great news @Jordan Clay and I'm so glad things are working well for you again. Hopefully this will help others as as well but there are just so many things that can interfere. Thanks much for extracting usable crash and dmp files that helped us figure it out.

SO... I'd like to remind others coming across this thread that there are so many things that can cause Pr to fail in a major way. Often it is the result of some conflict with something completely outside our control... like VST plugins. We like to be pro-active and suppress any problems that we know about, but there are just so many things that can get in the way. So, please, if you are experiencing a massive problem like this crash on launch, try to get us actionable things like crash logs and process dump files so that we can get Pr working for you again... Even when it's not actually our fault.

[Kevin-Monahan]

So thankful to hear your reply and success in solving your issue @Jordan Clay! And thanks to @jstrawn for tracking down your problem. Great story highlighting how the community in partnership with Premiere Pro developers can succeed in solving issues.

Cheers,
Kevin

[mstegner]

I downloaded the latest demo of MagicDeathEye effects and was not seeing a crash with any of the 3 effect types (AU, VST3, VST).  I was trying version 1.2.2 directly from their website.
I did notice that the effect is not retaining settings, which I will create a bug for right now.