Crash On Opening Project - Unable To Select New Project Location

[Zwea]

Hello everyone,

Hopefully someone can help me out, because I'm losing a lot of time (and money) and I'm starting to get pretty frustrated. Pc specs are listed at the bottom of my post.

The problem:

I was running Premiere 22.6 and kept losing edits because of crashes during (auto)save. Supposedly this is (FINALLY) fixed in the upcoming release. Because losing edits multiple times a day is totally unworkable, I decided to install Beta version 23.1. I'm hesitant to upgrade full versions because I have some ongoing projects in CC22 I need to revisit often. I ALWAYS keep the previous version in case something goes wrong. It seemed to be working fine for a couple days. No more save crashes, some new additions to gpu-acceleration, etc. The only annoying this was the preview going black (permanently, audio still playing) whenever I opened any footage/music in the source window. Not that big of a deal, I could just select footage, drop it into the timeline, restart the program and then I'd be good to go. Anyway, last night it was all working fine, but since this morning I can't open the project anymore.

Whenever I open the project located on my D: drive, the following happens:

- Premiere loads up

- I select the project (it's the only one I have in CC23 Beta)

- The loading bar in the pop-up fills up

- When the bar is filled I get the spinning wheel for a few seconds

- Premiere completely closes without any warning or notification.

My workaround was to create a new project and import the old one to see if that worked. But it will only let me select my C: drive, where Windows and my programs are located. All my media and projects are on the D: drive. I cannot figure out a way how to create a project on the D: drive. It literally only shows the C: drive. Note: I have given the Adobe folder full access via folder properties.

Then I updated to Beta 23.2 to see if that might fix it. I started the program with Alt + click to reset preferences on startup. Then I tried removing the Beta version and once again completely re-installing it. Did not work.

Does anyone have a clue on how to fix this?

PC Specs:

Ryzen 9 3950X

Gigabyte X570 Aorus Elite

MSI RTX 2080 Super Gaming X Trio

GSkill Trident Z Neo 3600 CL16 64GB (4x16GB)

Samsung 970 Evo Plus 500GB (C: drive - Windows and programs)

Samsung 970 Evo Plus 2TB (D: drive - Projects and footage)

WD Ultrastar 16TB (Archive drive)

[Zwea]

Extra info:

- Already updated graphics driver

- Removed graphics driver with DDU and reinstalled from Nvidia website

- Already tried 100% fresh install

- Already had my RAM replaced earlier this year, didn't fix the problem

- Yes, my RAM is on the motherboard QVL

- Forgot to add my PSU: Corsair RM750X 2018

- Computer is running at stock settings, no overclocks whatsoever.

- Thought it might be a faulty GPU (VRAM) but doesn't seem to be the case since it only happens in Premiere.

- What I haven't tried is a complete Windows refresh, but I'm currently not in a position where I can take the time to go through a full rebuild of my system.

- BIOS is not on the latest version, but I doubt that would solve the issue. Other programs are fine.

[Zwea]

Accidentally marked the previous post as correct answer. Is there a mod available to revert that? Thanks.

[Kevin-Monahan]

Zwea,

Sorry about this situation. I can't help but think that your project has an issue; it might be corrupt. If importing an old project into a new one works for a while but eventually fails, that's a sign.

Can you test the theory by creating a new project in v.23 and see if you can replicate the problem? If you can, we can get a bug filed for you.

When I get a corrupt project file, it sometimes has to be rebuilt. You can rebuild any complicated project into a Production which can help prevent such corruption. Apologies, it is never a fun task, though.

As a troubleshooting step for your system, you might try checking folder permissions with any interaction with your application, project, or media.

You can use the template here to fill in more info that the devs can use to replicate the bug. How do I write a bug report?

Thanks,
Kevin

[Zwea]

Hey Kevin,

Thanks for your reply. I'm still having issues

Somehow I finally got 23.1 working again, but it still freezes on all kinds of actions. Playback doesn't work after importing and anything regarding captions. Since I finally got it to load up, I created a new project and it won't allow me to import the old project via media browser. The loading bar fills up and gets stuck, to the point where I have to force-quit. When I try to import via Ctrl + I it takes several minutes to import; practically gets stuck around 75%. And in the end it finally gives me an error: saying the project may be damaged, etc. There's only about 200gb of footage in the project, but a whole lot of sequences.

In 23.2 I couldn't even open up a project. It kept crashing on the splash screen. And if I were able to load, the project location would be stuck on the root folder of my C: drive. It won't even let me access my media drive.

So now we're back to the horrors of 23.1:

In the old project I just spent 30 mins just trying to import footage and it still won't let me import more than 1 folder at once. I'm dealing with constant force-quits here.

Honestly considering giving up on Premiere and redoing my entire project, since there's always something crucial that gets completely broken in the next version.

[Zwea]

@Kevin-MonahanDo you have a guide on how to rebuild your project via Productions? I'm gonna give it one last try before giving up completely. I need something I can rely on...

[Zwea]

So I just tried to start over completely with a 100% new project in 23.1. I import some footage and it freezes. Force-quit. Again. And again. And again.

I have to apologize for my rants; please know that I greatly appreciate the fact you're taking the time to help me out with this issue.

[Kevin-Monahan]

For Productions, you must have all projects open to keep the code intact when you do any migration. I believe this is covered in the documentation. https://www.cined.com/adobe-premiere-pro-best-practices-workflow-guide-released/

Kevin

[Kevin-Monahan]

Zwea,

I think I have it. Roll back drivers to 517. xx using the clean reinstallation option. I heard that the latest GPU drivers are faulty. This NVIDIA issue is pretty new info, so I hope it helps. I would be super happy for you if it did.

No problem with the rants. I'm an editor, beginning in the CMX and Sony RM-440 days, so I empathize with you guys behind the controls. We, editors, prefer straight talk. 

Cheers,
Kevin

[Zwea]

@Kevin-Monahan You're a legend! Going to try it right away and I'll get back to you asap. Fingers crossed! 

[Zwea]

Well it looks like that didn't do the trick. Importing the project into a new clean project still crashes Premiere. However, I am now able to import footage into the old one, which is a big step forward. It didn't quite fix the playback issue. I can play footage in the source window and project window. I can make cuts... But as soon as I trim the footage playback freezes again. Going to try to start Premiere with cleared preferences once more.

For the time being I'm just going to batch-cut up clips and hope I can remember which part is which. As long as I can get at least one short video out, the struggle has been well worth it. Have to keep feeding them something, right?

FYI: I rolled back to 517.40 studio driver with a clean install (did not use DDU for this).

[Zwea]

@Kevin-MonahanHas anyone been able to confirm the new studio driver fixed the issues? The playback bug is still driving me crazy. I still have to restart the program after every single shot I put on the timeline.