Premiere 2019 v 13.0 crashes after 1 min

[adamå53489650]

Hi.

Just updated to the latest version (v 13.0), and the "crash report" window appears after 1 min of running the program.

The previous version 2018 v 12.1.2 and 2017 v 11.1.4 works perfect. Any solution?

My specs:
Hp Omen

cpu: i7-7700 2,80ghz

Ram: 16gb

Video: Geforce gtx 1050 Ti (4Gb)

[Carlos Ziade]

make sure that other pc is not running pp on 'software only'

yes Nvidia is releasing new drivers for Premiere Pro 2019

refer to Premiere Pro system requirements please:

Adobe Premiere Pro CC System Requirements

[Niam_N]

Hi, I am having the same problem and made a post on it but received no help, I am hoping for some help here. I want to add my pc specs and that my program is responsive when the crash report is up but I can't use it but it is usable for a few seconds after the crash report window closes. It was working fine with the old version, I have also reinstalled 3 times and cleared cache and everything.

PC Specs: GTX 1060, i7-6700, 16GB DDR4 ram, 500GB Samsung 960 EVO, 1TB HDD

Thanks in advance

[adamå53489650]

The problem is not solved in the latest update 13.0.1.

[velements]

I was having the same problem, and this 1 minute crash happened on both Premiere and After Effects 2019.

The weird thing is it only happened on my laptop but not my desktop, and here is my laptop sepc:

Asus VivoBook Pro N580VD

Intel i7-7700HQ

GeForce GTX1050

Intel HD Graphics 630

I tried many different GeForce driver version as suggested in the posts above, but no luck.

Yesterday, I saw there is an update on the Intel HD graphics driver(24.20.100.6025) for my laptop, and I updated.

Problem solved... no more crash.

[Wes Howell]

Thanks for the update and information.

Intel Driver

https://downloadcenter.intel.com/download/28289/Intel-Graphics-Driver-for-Windows-10?product=88345

[adamå53489650]

I tried the latest nvidia driver 416.81 as well without any success 😕

[Wes Howell]

Hi Adam,

I believe your laptop has dual GPU's, correct?  I have been working with many customers with multiple GPUs that have needed to update both.

Can you go directly to the Intel site and update your Intel GPU?

This has resolved problems for many.

Intel Driver

https://downloadcenter.intel.com/download/28289/Intel-Graphics-Driver-for-Windows-10?product=88345

Please let me know if that helps.  If not, I'm happy to make sure you get the assistance you need.

Wes

[lmarby]

Sorry, that doesn't help at all. v13.1 crashes 0 seconds after loading, on

a Windows system with dual GPU, new drivers for both.

I have 4 independent Windows systems with different current hardware (all

with Geforce). Only on one system, v13.1 works smoothly. 2 systems crash,

and 1 obviously works without Cuda, with tedious rendering.

I have been working with Adobe Premiere since 1995. All through the years

when you had to sav your projects every ten minutes.

But Premiere 2019 is the worst piece of crap software they have released in

the last 20 years.

Am Di., 13. Nov. 2018 um 16:09 Uhr schrieb Wes Howell <

forums_noreply@adobe.com>:

Premiere 2019 v 13.0 crashes after 1 min created by Wes Howell

<https://forums.adobe.com/people/Wes+Howell> in Premiere Pro CC - View

the full discussion <https://forums.adobe.com/message/10746287#10746287>

[Peru Bob]

lmarby  wrote

I have 4 independent Windows systems with different current hardware (all

with Geforce). Only on one system, v13.1 works smoothly. 2 systems crash,

and 1 obviously works without Cuda, with tedious rendering.

What is different about that system?

[adamå53489650]

According to the "auto intel driver detection software" i've got the latest driver for my intel graphics (intel hd graphics 630)

The one you linked is for 530, can i use that driver for my 630?

[Wes Howell]

HI Adam,

We have been recommending that users update to the latest Intel drivers directly via their site.

This has resolved related issues for the majority of users with the Intel hardware.

Drivers can be tricky and vary depending on device, as referred to with the slightly older hardware referenced in the post above (Glad rolling back resolved the issue in that case).

The Intel utility has caused some confusion for users, but updating directly the site has worked in most cases.

Here is a direct link for the 630.   I'd try the latest version of that driver.  Please let me know how that goes.  I'm here to help.

Downloads for Intel® HD Graphics 630

[lmarby]

Hi Wes,

that Intel tool in my case "only" installs the driver version that the Windows System config will install, too. Fun thing is, that newer drivers exist.

I have 2 very similar systems sitting side by side (2 mid-range gaming notebooks - 1 Acer, 1 MSI). Both equipped with Intel HD Graphics 630. The Acer will only update unto driver 21.20.16.4627 (Intel), the MSI unto 22.20.16.4708. The MSI is the older rig, but it runs Premiere 2019 without problems, the Acer is 1 year newer, but it crashes.

[Wes Howell]

Can you try downloading and updating the Intel GPU drivers directly from the Intel site?

Definitely sounds like you need the latest driver.  I wouldn't use the Intel tool

Wes

[lmarby]

I followed the link that you shared. It led my to that Intel tool... Will try again (yes, I want the lates driver!)

[Steve_Cre8tv Media]

My system is still crashing when PP is initially loading and comes to the importerQuickTime.prm  file...

Hey Adobe, I’d like to get my $53 monthly CC payment back as your products are not working...

Come on, please get this resolved - I need to edit!

Thank you,

Steve

Steven Gibbs

Producer/Editor

[Personal information removed by moderator.]

[R Neil Haugen]

Is 2018 having any issue for you? One of the useful options of the CC series is the ability to run multiple major versions simultaneously on a machine. I've got ... 2015.2 ... 2017.4 ... the last 2018 ... and the current 2019 version installed. You can check the build numbers to see what's an update (within a version) and what's an upgrade (new version). 2014.2 is the 9.x builds, 2017 the 11.x builds, 2018 is 12.x, and 2019 is 13.x.

If running in 2018 works, you can keep running until they get the fix out for this. I tend to keep projects in their original version myself.

Neil

[Steve_Cre8tv Media]

Hey Neil,

Yes, I'm using 2018 12.1.2 without any problems but I want to use the new 13.0.1 version - its the newest and has more features that I'd like to use and I'm paying for it...

Thanks,

Steve

[R Neil Haugen]

Been there ... had to wait something like four months once until the bug what was eating my machine got properly fixed.

But you're also paying for the whole host of previous apps available. Which means you can keep working while bugging them about the new version's bug. As I did ... with gleeful abandon, of course!

Neil

[Steve_Cre8tv Media]

Haha... “gleeful”?... well....

yea, my 2018 is used everyday, but they shouldn’t release stuff without de-bugging more thoroughly - I know it’s tough but it’s what they signed up for to provide. We really shouldn’t be Beta Testers for what we are paying for, imo...

Thank you,

Steve

Steven Gibbs

Producer/Editor

[R Neil Haugen]

Know the feeling. But I'm also a flippin' realist.

They made some choices ... to work with a wider range of media than anyone, and a wider range of gear than anyone ... and between those, given the range of media & gear that makes them build for, they can't possibly test for every combo of OS, gear, and installed programs. I mean ... for some people with a build a while back, Microsoft's onedrive.dll file caused all kinds of pain within PrPro. Delete the file, it worked fine. Reinstall that library file, bang.

But it only was a problem for a small subset of Pc's ... maybe a few percent, I'd guess ... they could have had a couple hundred PC beta people, and still not had one with that issue. I wasn't affected, but clearly there were users that were. It was just one user, btw, who posted here with similar symptoms to others, finally got to the point he stripped his machine of apps, then removed one dll at a time while checking out PrPro. Found that when he removed that dll, PrPro worked perfectly. Reinstall, same problems.

And posted that here. Which of course also got sent to the engineers, who'd been totally unable to figure that particular set of symptoms out because they couldn't repro them to determine what the Hades was causing it.

At NAB last year, a number of aisle-talk discussions I was in of editors were of course discussing stability problems. Several posited that maybe Adobe's PrPro team should rethink trying to work on everything, and perhaps give a list of codecs and gear it's designed for ... anything past that, well, that's fine. But only guaranteed on X set of stuff.

Apple sure runs a lot stiffer set of environment limits on users for say FCPx for example. One OS only, a very limited set of gear, limited codecs. No one thought that tight a set of rules was needed, but many said they'd trade a bit of leeway in codecs/gear at least for more stability.

Neil

[Wes Howell]

I sent you an email, Steven.  Did it get trapped in a spam filter?

[Steve_Cre8tv Media]

Hey Wes,  Thanks, got it... I've been unable to get back to you with work etc... I will try the solutions described below here to see if this works... if not, I'll get back to you and see what we can do...

Thanks, Steve

[Mo Moolla]

Hey there Steve

As a pro producer/editor I can relate to your frustration. Thought I would add my 2c in from a neutral standpoint.

When a new app is being released there is a lot of hype and marketing surrounding it to get the end users interested. With the launch of CC2019 being touted more of a revolution than evolution many users expected miracles. Faster rendering. Enhanced effects running on GPUs on AE. Photoshop being able to almost "sense" what needs removing in content aware etc etc. I assure you have seen the vids.

Unfortunately Adobe gets the proverbial rap of the knuckles when things go wrong which, if you come to think of it, is justified as they are selling paid for apps. The problem comes in when software is dependant on different OS versions, GPU drivers, new or discontinued codecs etc.

This is why the user community exists. To keep track as much as possible, of the bugs that are bound to plague these releases. It is great that the community gets involved by asking questions and that the forum members who assist give up so much of their time without asking anything back.

So now that the violins have stopped playing lets get real. I personally feel that Adobe will learn a lot by this launch and the issues surrounding it. I am absolutely sure they are working on strategies to enable this from not happening in the future. If you look at Apple, the reason FCP is stable is because it lives in a controlled ecosystem.And Apple is making this environment even more controlled with METAL so they aren't dependant on 3rd party graphics manufacturers. Clever guys. Adobe is just one of many 3rd party vendors who are dependant on the OS companies as well as the hardware manufacturers. Its a monumental effort liaising between all companies concerned and I can only imagine the blood shot yes of the engineers in the background.

I am hoping this sort of issue doesn't rear its head in the future but for now, even though I understand you are a paying client and want to use the new features, if you are on a mission critical project I would say stay on CC2018. The fixes are coming soon.

Please note that these are my personal points of view and I in no way represent Adobe or their policies.

Thanks Steve and best of luck

Mo

[lmarby]

Hi Wes,

It is like you forecasted - for dual gpu systems the Intel driver makes the difference in these days. I downloaded (manually) the newest Intel driver that was available yesterday. Installed - and the crashes with 13.1 are gone.

I am not sure if I have maximum perfomance. The rig seems to need to render where Premiere 2018 (and 2016 etc.) did not, although the Nvidia monitor cleary shows that GeForce 1060 is doing the work. But I am using very old Nividia drivers right now which I downgraded to in search for a remedy.

Thanks a lot, and I will keep you updated.

Ludwig

[Kevin-Monahan]

Adam,

Did you follow Wes' advice? How are you doing now. Are you up and running?

Thanks,
Kevin