Skip to main content
Inspiring
July 15, 2019
Answered

Crashing with Premiere Pro CC 2019 (13.1.3) on Windows

  • July 15, 2019
  • 7 replies
  • 6590 views

WARNING!  RUN AWAY!  RUN AWAY!

My public service announcement for the day... DO NOT UPGRADE TO 13.1.13!!!  I usually never upgrade in the middle of the project, but 13.1.12 was already crashing a lot, and it looked like this update might help.  It is now crashing 5 to 6 times more.  I am on over 40 crashes today and counting.  I literally have not been able to go more than a 15-minute stretch without a crash or the program freezing up.  I'm also getting strange "Out of System Memory" errors... I have 32 gigs of RAM and it's not showing that I'm anywhere near my limit in Task Manager.  I also have two really important projects due today, and have spent hours on reboots and re-installs.  All my drivers were up-to-date before I installed.

ANOTHER WARNING! Here's what got me...  You might think you could try 13.1.13 (like I did) and if it didn't improve things you could just go back to 13.1.12 (like I did).  You can't.  It's not in the past versions selection in Creative Cloud.  I saw there were a few other posts looking for this link, if anyone finds it please let me know.

I can't for the life of me figure out why Adobe would release this... I know they must do testing on real-world machines?  So far every version of 13 has been a mess as far as stability is concerned.  I know this is complex software and I'm trying to be patient but seriously... this is pushing limits.  I haven't felt confident in any version of 13.  There must be some way to improve this.

Premiere Pro 13.1.13 (Run away!  Run away!!!)

Dell Alienware Laptop 15 r4, 15.6-inch display

Windows 10 Home 64-bit

8th Generation Intel i7-8750H

NVIDIA GeForce GTX 1070 OC with 8GB GDDR5

32GB DDR4-2666MHz RAM

Moderator note: changed title to reflect actual issue.

This topic has been closed for replies.
Correct answer AlaskanNomadProductions

Hey Kevin, thanks for the reply.  I sincerely appreciate you on these forums, you put a lot of time and energy into helping us. Plus I like the way you zing people. It’s classy and done in such a way that makes the zingee wonder if they’ve just been zung.

As for the rant I’m sure you saw coming from a mile away: I’m not overly concerned about Adobe's explanation of what happened with 13.1.3. But if I can drop a bit of honesty, I wrote that because I’m tired of problems with Premiere being someone else’s fault.  It’s not Adobe’s fault that Premiere is buggy as hell upon release.  It’s a third-party’s fault.  Or it’s the user’s fault for not updating their drivers (or apparently in the case of 13.1.3 it’s both).  And if it’s not that, it’s the community’s fault because we haven’t filed enough Feature Requests to get something fixed.  Or (as an earlier post in this thread inanely pointed out) it was actually MY fault this happened, because you guys give us two activation licenses – and I’m supposed to shell out another $5,500 on an identical editing system so that I can test the updates before installing them on my main system.  You know, kinda like it’s your fault if your car breaks down because you didn’t buy another car.  I noticed that both you and another Adobe employee gave this concept a “thumbs up”.

I just feel like it would be refreshing as hell at some point to have Adobe say “You know what, we messed up.  This release was bad, and we’re wondering just like you how this could have gone so wrong.  But we’re human and we make mistakes and we’re working very hard to make sure that it’s not going to happen again.”  That would be awesome.  And I think it would make a lot of us feel better about the situation.  Especially because I wasn’t just making things up when I said I had two important projects due that day, and the client was breathing down my neck and I was getting ready to leave town for two weeks and this was throwing a major wrench into my life. In this business you’re only as good as your last job, and frankly on that day Premiere was making me look bad. People lose clients and money and their livelihood when things like that happen.

So if Adobe employees could think twice before telling us it’s our fault because we need to do something like file more Feature Requests, that would be nice.  Many of us don’t feel that our opinions sway much anyway…  the Top 10 requests on Uservoice (Linux, Blackmagic RAW, ProRes RAW, Warp Stabilizer, etc) have all been marked as “Under Review”, many with no further comment from Adobe for over a half-year and counting.  The Top 10 requests on After Effects haven’t even garnered a response.

Anyway, thanks for listening and considering and I hope that some of this might resonate.

Oh, and about the zing part, I was talking about this.  I said: “If you look around the forums, there are plenty of Mac users that were having the same problems. Hopefully this fixes their issues as well.”  You replied (which I flippin’ love): “A good thing—the Windows Registry issue did not affect Mac users. Thanks for the concern, though!”

As not to leave a good zing un-returned, I would like to say: Good to hear it’s not affecting Mac users.  I’ll let the guy who posted “Today we updated to 13.1.3 and it's crashes all the time. We are on a 2013 iMac and have one of the last Nvidia GeForce GTZX 780M” know that he is mistaken, and his computer must not be crashing, as the issue he’s discussing does not affect Macs.

I am hoping for a return zing.  In fact I would be disappointed by anything less. Ball’s in your court Kevin!

Cheers….

7 replies

Inspiring
July 29, 2019

I was gone for 10 days shooting, so wanted to update this post.

After I got back to the office and download the 13.1.4 patch, things seem to be working.  Today I had 2 crashes in a 4-hour period, which isn't ideal, but still a vast improvement over the crash every 10 - 15 minutes I was experiencing before. 

So big thanks to Adobe for getting this fix out pretty quickly.

I would like to note, however, that on the Adobe website it says that "Premiere Pro 13.1.4 includes all of the improvements from 13.1.3 with an additional bug fix that addresses a launch issue for some Windows systems with outdated drivers."

As stated in my original post, all my drivers were current at the time of the 13.1.3 update.  The only thing that  has changed on my system was downloading the 13.1.4 patch.  So pushing this issue off on a third-party feels a bit disingenuous to me.

Also for the record, the original title of this post was "DO NOT UPGRADE TO 13.1.13!!  Anyone have a link to 13.1.12?"  This was changed, I'm assuming by a moderator.  The title now seems to indicate that this was an Windows only issue, but if you look around the forums, there are plenty of Mac users that were having the same problems. Hopefully this fixes their issues as well.

Kevin J. Monahan Jr.
Legend
July 30, 2019

Hi,

still a vast improvement over the crash every 10 - 15 minutes I was experiencing before.

So big thanks to Adobe for getting this fix out pretty quickly.

Cheers! Glad things are better. Hope that new projects will produce fewer crashes. We are working very hard on that issue now.

As stated in my original post, all my drivers were current at the time of the 13.1.3 update.  The only thing that  has changed on my system was downloading the 13.1.4 patch.  So pushing this issue off on a third-party feels a bit disingenuous to me.

I would not be overly concerned with the way these things are worded. Perhaps it was a fix that Microsoft never notified us about? If the specifics are important to you, I can try and find out for you.

the original title of this post was "DO NOT UPGRADE TO 13.1.13!!  Anyone have a link to 13.1.12?"

I changed the title for a couple of reasons, both of which should not be taken personally:

  1. A good title will include the actual issue for search purposes. Others may want to find your post to solve their own issue.
  2. Individuals do not have legal access or "links" to previous versions of Premiere Pro that are not included in the Creative Cloud application.

The title now seems to indicate that this was an Windows only issue

It seems to be a Windows only issue since the patch did solve your issue (and for other WIN users too). Hope it's OK to leave it as is so that others may find it.

if you look around the forums, there are plenty of Mac users that were having the same problems. Hopefully this fixes their issues as well.

A good thing—the Windows Registry issue did not affect Mac users. Thanks for the concern, though!
Let us know if you run into any additional issues we can assist with.

Regards,

Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
AlaskanNomadProductionsAuthorCorrect answer
Inspiring
July 30, 2019

Hey Kevin, thanks for the reply.  I sincerely appreciate you on these forums, you put a lot of time and energy into helping us. Plus I like the way you zing people. It’s classy and done in such a way that makes the zingee wonder if they’ve just been zung.

As for the rant I’m sure you saw coming from a mile away: I’m not overly concerned about Adobe's explanation of what happened with 13.1.3. But if I can drop a bit of honesty, I wrote that because I’m tired of problems with Premiere being someone else’s fault.  It’s not Adobe’s fault that Premiere is buggy as hell upon release.  It’s a third-party’s fault.  Or it’s the user’s fault for not updating their drivers (or apparently in the case of 13.1.3 it’s both).  And if it’s not that, it’s the community’s fault because we haven’t filed enough Feature Requests to get something fixed.  Or (as an earlier post in this thread inanely pointed out) it was actually MY fault this happened, because you guys give us two activation licenses – and I’m supposed to shell out another $5,500 on an identical editing system so that I can test the updates before installing them on my main system.  You know, kinda like it’s your fault if your car breaks down because you didn’t buy another car.  I noticed that both you and another Adobe employee gave this concept a “thumbs up”.

I just feel like it would be refreshing as hell at some point to have Adobe say “You know what, we messed up.  This release was bad, and we’re wondering just like you how this could have gone so wrong.  But we’re human and we make mistakes and we’re working very hard to make sure that it’s not going to happen again.”  That would be awesome.  And I think it would make a lot of us feel better about the situation.  Especially because I wasn’t just making things up when I said I had two important projects due that day, and the client was breathing down my neck and I was getting ready to leave town for two weeks and this was throwing a major wrench into my life. In this business you’re only as good as your last job, and frankly on that day Premiere was making me look bad. People lose clients and money and their livelihood when things like that happen.

So if Adobe employees could think twice before telling us it’s our fault because we need to do something like file more Feature Requests, that would be nice.  Many of us don’t feel that our opinions sway much anyway…  the Top 10 requests on Uservoice (Linux, Blackmagic RAW, ProRes RAW, Warp Stabilizer, etc) have all been marked as “Under Review”, many with no further comment from Adobe for over a half-year and counting.  The Top 10 requests on After Effects haven’t even garnered a response.

Anyway, thanks for listening and considering and I hope that some of this might resonate.

Oh, and about the zing part, I was talking about this.  I said: “If you look around the forums, there are plenty of Mac users that were having the same problems. Hopefully this fixes their issues as well.”  You replied (which I flippin’ love): “A good thing—the Windows Registry issue did not affect Mac users. Thanks for the concern, though!”

As not to leave a good zing un-returned, I would like to say: Good to hear it’s not affecting Mac users.  I’ll let the guy who posted “Today we updated to 13.1.3 and it's crashes all the time. We are on a 2013 iMac and have one of the last Nvidia GeForce GTZX 780M” know that he is mistaken, and his computer must not be crashing, as the issue he’s discussing does not affect Macs.

I am hoping for a return zing.  In fact I would be disappointed by anything less. Ball’s in your court Kevin!

Cheers….

Kevin J. Monahan Jr.
Legend
July 18, 2019

See if this might assist your crashing issue: FixPr13.1.3CrashOnLaunch.zip Windows Registry Fix

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
Legend
July 15, 2019

Adobe allows two activations for their software.  One should always test updates and upgrades on a second system before upgrading a production machine.

Inspiring
July 15, 2019

OK.

If anyone has info on a download of 13.1.12, would love to get a link!  Any updates from Adobe would be appreciated.

On the flip side, if I hear of anything I will post it here.

Kevin J. Monahan Jr.
Legend
July 16, 2019

ANP,

If anyone has info on a download of 13.1.12, would love to get a link! 

The only way to receive Creative Cloud applications is via the Creative Cloud application. Certain versions do get removed for various reasons, and we do apologize that we have to do that from time to time.

Any updates from Adobe would be appreciated.

It's likely a GPU drivers issue as, by and large, we aren't experiencing the same issues you are. Therefore, please contact us to open up a case as soon as you can. We are open 7AM to 7PM PST. Contact us during these times to reach our video specialists: Adobe Help Center

Thanks,

Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
Community Expert
July 15, 2019

in addition to my first comments, if nothing works refer back to this ongoing thread where Adobe Premiere

staff are handling the issue and following up thoroughly with it:

Premiere crashes after 13.1.3 update

Community Expert
July 15, 2019

try the first must to steps when crashes happen:

01. trash preferences

02. clean media cache

03. delete render files

if you open a fresh new project, what happens?

did you try to start a new project and import your current one into it?

did you try to update your graphics card from the vendor's site?

your Windows version must be this: Microsoft Windows 10 (64-bit) version 1703 or later

Participant
July 15, 2019

+1

Premiere Team: Where is 13.1.2 rollback option?

Community Expert
July 15, 2019

Hi,

Sorry to hear you're experiencing crashing. Does this happen when you open Premiere, working with a file, or when rendering?


Here's a site that provides links to various versions of Adobe software:
https://prodesigntools.com/adobe-cc-2019-direct-download-links.html

Inspiring
July 15, 2019

Hi Dean, thanks for the response.  It has crashed on me opening the program and at random times working with files.  It seems to crash a lot when I'm working with proxy footage or toggling the Proxy view.  Outside of that, there is a lot of random crashing with no apparent reason.  I haven't seen it crash yet while rendering. 

That link you sent me... I'm trying to figure out how to download version 13.1.12 and there is only one Premiere Pro link that I can find.  Do you know what version this is?  Is there a link directly to 13.1.12 somewhere?  Thanks for any help.

Community Expert
July 15, 2019

If you can reproduce steps that result in a crash, it would be helpful to find a fix. Here is a page that may be of use in terms of troubleshooting.
https://blog.frame.io/2017/11/13/common-premiere-pro-crashes/

I'm not sure what 2019 version the Prodesigntools site links to.