Inspiring

Answered

Premiere Pro 2018 constantly crashing

Forum|Forum|8 years ago
November 5, 2017
40 replies
50789 views

Recently updated to 2018 and it keeps crashing. Completely random but enough for it to drive me up the wall.

Windows 10

Dell XPS 15 4K - intel i7 7th gen - 32 gb ram

Editing GH5 10bit FHD long GOP clips, Mavic drone and GoPro .mov and .mp4

No other apps open

Tried both CUDA and software only

Cache files deleted

Only once has it come back with a crash report (I was using legacy titles) and it sent me to a completely random forum thread. The rest of the time it just hangs in the middle of an action, which could be anything from slicing a clip to changing the tool. In a ten hour day it crashes at least ten times. Sometimes after opening the package after crashing it crashes again immediately, but sometimes not.

Whilst I've been having problems with Premiere Pro running properly on my XPS, it didn't crash like this in version 2017. This is new to 2018.

Anything else I can add to assist with bug-testing?

Crash

This topic has been closed for replies.

Correct answer unknownsailor

Been offline since my last post until recently but many of my problems have been resolved by the latest version that came out a week or two ago. Pr is not crashing anymore, in particular when trimming clips, which would almost guarantee a crash.

The other thing I did was buy an external SSD (Samsung T5) and this has helped significantly.

Pr is still slowing down when I start layering multiple 10 bit or 4K files. One strategy I'm using is to do adjustment layers and text last because they really slow things down, as does warpalising. My timeframe still stalls by the end of one of my projects (normally 15mins in length, made up of 10bit and 4K footage) so it's easier to render a sequence rather than trying to play it, which is still a pain, but at least it's not crashing any more.

Show previous replies

N

NVHHung

Participant

It seems that everything was working fine with cuda 396.64. I disabled all active core, turned to auto. PC does not crash anymore. People can try

GLOBAL STOCK FOOTAGE

Known Participant

What is the point of paying out for a good graphics card if we must disable it for Premiere to work without crashing. It is absolutely counter productive and not economical.

A fix is what is needed. Having to cripple our machines just so they do not crash is absolutely backwards. Its like rolling a car with no engine down a hill and saying 'Look, It still works'.

R Neil Haugen

Legend

"Adobe" can't outguess all hardware/OS/firmware changes and build the NLE so that it covers all possible things anyone else might do. So with OS changes, firmware/driver changes, hardware changes, the users at times do need to modify the settings or modify hardware. I do understand that you're on a Mac, which is of course rather more limited for choices/options & modifications than a PC, which sucks. A user choice, of course.

You commented that CUDA was working ok with one driver ... then of course, one could choose to stay with that driver. Or, alternatively, use OpenCL or Metal, which are available on the Mac side, each with it's own ups/downs depending on the particular GPU involved and a million other data points.

Some of the AMD GPU's are working very nicely with Metal, as I've seen. That of course could also be a user choice. Once upon a time, PrPro just didn't work with AMD components, and I had to pass a relatively new computer to my wife for her stills editing and get a new machine based on Intel/Nvidia. Now, if chosen wisely, one can get a fast machine with AMD/Radeon parts.

I saw a thread on the Hardware forum a while back, a guy has spent a bit of change building a custom editing machine and was incredibly angry that PrPro didn't run fast on it. So ... he was asked to post the parts included. Amazing list, many spendy things from CPUs to you name it. None of the crucial components ... CPU, mobo, GPU, and data-movement (due to mobo choice combined with parts) was actually something that worked within the way that PrPro works.

He was asked if he'd actually checked for what things work well with PrPro before building, and was incensed at the question. But ... that was his choice. He could have spent a few minutes perusing the Hardware forum, the Puget Sound System's advice listing, checked with SafeHarbor Computing or ADK, and made vastly different choices that would have made a really hot system.

Building & modding the systems to work best with Reality just seems to me part of the job of doing the work. But of course, everyone's mileage always varies. Humans being more varied than hardware, software, firmware multiplied against each other.

Neil

Everyone's mileage always varies ...

ellenas2491298

Participant

For me, every other time i go save my work it crashes. It's actually driving me up the wall. I've lost so much work and time due to this. Makes me want to stop using premier.

GLOBAL STOCK FOOTAGE

Known Participant

Switch up your editing software, the only way to get Adobe's attention is to hit them in the pocket. It's also great to have the skills for multiple editing softwares.

N

NVHHung

Participant

I discovered that cuda for mac caused crash for Adobe apps. I deleted the cuda and my machine was working normally. Remove cuda if you install

GLOBAL STOCK FOOTAGE

Known Participant

Working normally , as in having cuda acceleration speeds or working normally as in no cuda and slow performance ?

N

NVHHung

Participant

not crash pr. Performance is slightly reduced but must be accepted if I want to use Pr in my case. Everyone can try the same thing ^^

S

Swirly Whirly Media

Participant

Same thing here. Import crashing, Selection tool intermittently working. More crashing. Totally sucks. Its costing me big time.

Not a happy camper with Adobe sucks premiere pro.

Peferling

Inspiring

If you have a workstation with multiple cards. It's time to play card swap o'rama. You have a conflict with your GPU on one of the interrupts. Every time I build a machine, I have to play this out. Which slot is on the fastest buss for the raid card, but does not share interrupts with the GPU and the system drive? Sometimes I have to disable a needless things, like the front USB panel, (and stick with the back). Other times it's a how things are plugged in.

There is an application that sniffs the internal bandwidth and presents a real time graph to show conflicts. Google DPC Latency to know more.

C

carlosg26489137

Inspiring

Hi same problem. What to do help me pls

peterk58475497

Participant

So...total disaster for me. Crash, Freeze...ridiculously unstable...who cares what my specifics are??? Latest computer, latest software...can anyone recommend a different brand of editing software? I'm on a PC so can't do final cut...can't believe I may have to just go buy a mac and final cut to finish all my projects !!!! WADDAJOKE

GermanTV

Inspiring

I have random crashes as well with Premire Pro 2018 (12.0.0 and 12.0.1) and some of them I find descibed in comments above. In Team Projects as well as in normal projects. And I have the same experience that Premiere 2017.2 was running near rock solid. I can just say it again: new collegues are coming with costfree Davinci Resolve and make me a hard to explain why we should keep Premiere as our paied house editing software when it is constantly crashing.

PREMIERE VERSION: Premiere CC 2018.0.1

DRIVER: Latest Drivers

SYSTEM:

Windows 10

Ryzan 7 x1800

32Gb Ram

NVIDIA GeForce GTX 1070 (EVGA)

120 GB m.2

8TB RAID 10

Audiointerface Focusrite 6i6

R

ricardoa3601073

Participant

Unfortunately, I updated Premiere 2017 before reading this forum. For the last two weeks I can not work, even after doing all the actions suggested by Adobe support, reinstall Windows 10 and go back to the 2017 version. Besides losing my patience, I lose credibility with my clients. I read that these crash problems start after hours ... in my case I could not get in 10 minutes of editing without crash! What to do? Any suggestion?

B

bradleyc6122788

Known Participant

11 crashes within 3hrs.

12.01 update random crashes

12.00 gave me random graphical glitches that had been reported by others

Working with the usual Sony A7s codecs as usual, on macOS 10.13.3, iMac 2013 - haven't had any problems before.

The thing that's driving me nuts is that it's totally random.

- double clicked on a nested item - CRASH

- adjusted the length of some audio - CRASH

- trimmed a clip - CRASH

iMac Pro arriving next week, so i'll be eagerly testing the latest version on this newer system - but there shouldn't be any problems running on my 2013 iMac.

Stepping way back to version CC 2017

Please Adobe, justify the ever-rising subscription fee and stop these interruptions in so many peoples workflows...

nathanieljimenez

Participant

Same thing has been happening to me. Even after I drag something into the timeline from import. Or if I try to click space bar to stop a preview, PrPro will crash. WOW WOW WOW Please adobe help!!

peterk58475497

Participant

Program is so unstable...

What they don’t tell you is you HAVE to have a high power video card... otherwise forget it.

NVidi 970 or above

Sent from my iPhone

Ricardo Denchuski

Participant

WHAT? @adobe does not say nothing about?

R Neil Haugen

Legend

From everything I've seen on this and a couple other forums, there are clearly some random crashing issues past 'normal'. Trying to apply basic troubleshooting 101 on the users who've posted, I don't see a common thread ... and realistically, it seems for many having this it's not constant but random. They do X with 15 clips, fine. Come back the next day, rework them ... one clip, BOOM. Buh-bye!

Reopen, all is normal. Then something else ... BOOM. Buh-bye!

Would drive anyone nuts.

The one place I'm actually wondering ... the last couple OS releases, Apple has really rebuilt their underlying video code stuff ... and MS did that with Win10 Creator. I'd heard from a couple editors in large shops who'd been on the phone with upper tech from MS when every machine in their shop went phoeey in PrPro, and were told that they should take their entire shop back to like 'enterprise version 1607' or something like that as there are problems that MS is currently working on resolving that only affect heavy-duty computations with video subsystems & code involved.

So I'd been avoiding the update, but ... while working on Wednesday afternoon in PrPro, I got a 2-second dialog "Windows has suffered an error and needs to restart" ... BOOM, instant shut down. Instant restarting also ... BIOS screen, then blue screen "Windows is applying updates, this will take longer than normal and involve several restarts, do not turn off your machine" ... and yea, it was updating me to Creator.

Forty five minutes later, it finally opened to actually use. But all the video apps were screwy. Even VLC. In PrPro, and I've several versions installed ... none of them showed the workspaces bar. Reset to saved layout ... BOOM! ... immediate complete crash of machine, just stopped shut down. After rebooting and just doing this for a while in frustration, I got a PrPro hang but NOT a crash of Windows OS.

A couple days of just trying to redo things, poking the box, and ... I'm back to fairly stable operations in the Video apps.

But that mess wasn't Adobe ... it was MS in nature.

And seeing the threads on the forum here ... the last 2-3 Mac updated OS's also caused a ton of issues.

None of which makes me too confident. I just hope that the OS producers get together with the app producers a bit better on these things, I think that would solve some of the issues.

Neil

Everyone's mileage always varies ...

S

sangarone

Participant

It has recently started happening to me in Davinci Resolve as well, which is a bit worrying... Ive done every diagnostic test and cant find anything wrong, im at a complete loss here.

Q

Quinn Lubbe

Known Participant

Spent the last hour with an Adobe support technician who remotely tried to fix my system. Waste of time, I‘m afraid.

CUDA playback on full screen via Mercury stutters then freezes.
Random crashes (even happened to the technician during remote session)
When I ALT TAB to another application and back into Premiere, timeline frozen. Have to wait a few minutes before it comes back to life.
Generally slower and less responsive on the timeline

Seriously Adobe just be honest and tell us that something went haywire in the last update.

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded