Skip to main content
Inspiring
December 21, 2017
Answered

Premiere 2017 crashes/freezes in Bluescreens

  • December 21, 2017
  • 6 replies
  • 1186 views

Hello,

I'm afraid my first posting is a "Help-me!"-Posting... I'm mainly using Photoshop, Illustrator and InDesign, so I'm new to Premiere. I'm a hobbyist and wanted to create a film from a holiday. I worked with Premiere before, but it is the first Time on my new Setup (sadly, with Windows 10). I'm sorry for issues with the language, I'm not a native english speaker.

Specifications are the following:

Motherboard Model: MSI X299 RAIDER (MS-7A94)

Motherboard Chipset: Intel X299 (Kaby Lake)

Total Memory Size: 64 GBytes (Quad-Channel)

Video Card #1: MSI GTX 1080 Ti AERO OC

Video Bus #1: PCIe v3.0 x16 (8.0 GT/s) @ x16 (2.5 GT/s)

Driver Version: 23.21.13.8871 (GeForce 388.71) / 15.Dez.17

Video Card #2: MSI N710GT (MS-V8C9)

Video Bus #2: PCIe v2.0 x8 (5.0 GT/s) @ x4 (2.5 GT/s)

The systems main use is 3D Rendering, which it does pretty well, but also for my job which requieres a lot of Paperwork, Calculations etc. Because of this, the system has 6 Monitors in total, 4 at the 1080ti, 2 at the N710GT

Problem is the following: Whenever I start Premiere Pro CC, it either crashes directly to Bluescreen, taking the PC with him, or it comes to the application, where it crashes between 10 and 60 seconds after, also to Bluescreen.

I've tried some fixes... First, actualisation of drivers, second redirecting Premiere only to the 1080ti via the nvidia control panel, opening the ports in the firewall like recommended by Adobe here (After Effects oder Premiere Pro stürzt nach dem Start ab - Sorry for German). I have not advanced...

Can anyone help?

Thank you in Advance!

This topic has been closed for replies.
Correct answer Praios

Ok... I think (hope) I solved it. While the ntdll braught nothing new, it inspired me to strictly kick out every software expect from tools totally nessersary. Without success... So I switched to bios...

To make it short: Disabeling the Intel Turbo Boost Technology "in the hardware" solved the issue. Just changing it by software, or deinstalling the software, didn't do anything, it had to be disabled in bios. Premiere ran stable longer than ever, I hope it continues...

6 replies

PraiosAuthorCorrect answer
Inspiring
December 23, 2017

Ok... I think (hope) I solved it. While the ntdll braught nothing new, it inspired me to strictly kick out every software expect from tools totally nessersary. Without success... So I switched to bios...

To make it short: Disabeling the Intel Turbo Boost Technology "in the hardware" solved the issue. Just changing it by software, or deinstalling the software, didn't do anything, it had to be disabled in bios. Premiere ran stable longer than ever, I hope it continues...

Legend
December 28, 2017

Nice find.

PraiosAuthor
Inspiring
December 23, 2017

I'm sorry, that wasnt formulated really precise...

Reducing to one monitor and only one gpu doesnt work to solve the problem, but also getting a "new" thing from the eventviewer...

First, there is the obvious (Translated, because original in german):

294/5000

The computer was restarted after a fatal error. The error code was: 0x00000124 (0x0000000000000000, 0xffffbf82fb3b8028, 0x00000000b2000000, 0x0000000000070005). A full image was saved in: C: \ WINDOWS \ MEMORY.DMP. Report ID: 47b620de-997a-4c9d-b513-ed09faf8f01b.

Then there is these notification

Audit events were deleted from the transport.

Then I have - of course - these things:

The system was unexpectedly shut down on December 22, 2017 at 09:13:48.

The only thing close to more detail is these

Name of the failed application: Adobe Premiere Pro.exe, version: 11.1.2.22, timestamp: 0x592e1ca1

Name of the failed module: ntdll.dll, version: 10.0.16299.64, timestamp: 0x493793ea

Exception code: 0xc0000005

Error offset: 0x0000000000029a55

ID of the failed process: 0x2f04

Start time of the failed application: 0x01d37a6f1cb4bfff

Path of the failed application: C: \ Program Files \ Adobe \ Adobe Premiere Pro CC 2017 \ Adobe Premiere Pro.exe

Path of the failed module: C: \ WINDOWS \ SYSTEM32 \ ntdll.dll

Report ID: ca319fe4-e5c0-4a09-81b4-527c92ac9ab

Full name of the failed package:

Application ID that is relative to the failed package:

I also found these in "Sicherheit und Wartung" (Security and Maintainance?)

problem signature

Problem Event Name: BlueScreen

Code: 1a

Parameter 1: 41793

Parameter 2: ffffa33fff7b8fe0

Parameter 3: 5a

Parameter 4: 59

OS Version: 10_0_16299

Service Pack: 0_0

Product: 256_1

OS Version: 10.0.16299.2.0.0.256.48

Locale ID: 1031

I'm afraid, thats all I can deliver...

PraiosAuthor
Inspiring
December 23, 2017

Hello again,

I'm afraid, does not work either.

After a bit of testing myself, I can conclude that the error (Bluescreen, Freeze, Over-and-Out) appears with every Adobe-Software, exepct for the first CC-Versions (e.g. Premiere 7, Photoshop 14) which run quiete fine.

So there seems to be a combining element of the "new" Versions which just happens to "hate" my Setup (I repeat: All other Software runs fine).

I rearranged my Workflow to the old versions, which I can do because it is hobby only, but the solution cant be going back to 4+ year old software or rebuilding part of a workstation-plus-monitor-setup for which I collected money a long time to make it powerful like it is...

Legend
December 23, 2017

I'm afraid, does not work either.

What does not work either?

PraiosAuthor
Inspiring
December 22, 2017

Thanks for your suggestion; I tried but without success.

I even got a step further and diasabled the second 3D-Card (the GT710), but also without success. The crashes are the same.

Even worse, I recognized that many other applications are unstable as well. Photoshop and Lightroom, also AfterEffects. The only difference is, that I can work about 5 Minutes with them. But to make it clear: It affects ONLY Adobe CC Programs, every other program, even the hardware hungry 3D Apps run completely stable.

For the Premiere-Issue, I tried to downgrade, first to 2017 (no difference), than another version down to CC - and this one seems stable over a long time, so, I can eventually build my holiday video. On my Notebook the applications run smoothly, but I'm not looking forward rendering videos on a 12" with only the basic Intel-Onboard-Grafics...

My next try would be disabeling GPU-Support completely, needless to say this cant be the final solution...

Legend
December 22, 2017

OK.

Leaving the second GPU out and only one monitor connected for now, report back what Windows Event Viewer has to say about the crashes.

Legend
December 21, 2017

As a test, have only one monitor connected until you get PP working.

John T Smith
Community Expert
Community Expert
December 21, 2017

I've never had a crashing problem, but PPro (and Encore) use a LOT of power when I am working... you never get to the point where PPro is working your CPU hard, but what size is your power supply?

BSOD shutdowns http://forums.adobe.com/thread/1427408?tstart=0 (may be due to hardware problems???)

-http://blogs.adobe.com/kevinmonahan/2014/01/13/computer-shuts-down-with-premiere-pro-or-after-effects/

-http://www.howtogeek.com/222730/how-to-find-out-why-your-windows-pc-crashed-or-froze/

-http://www.howtogeek.com/school/using-windows-admin-tools-like-a-pro/lesson3/

PraiosAuthor
Inspiring
December 21, 2017

Thanks for your quick response!

The power-supply is 1000W. There are other power-intensive applications like DAZ Studio and Blender, which work fine, even when rendering over hours (stresstest), without a cooling issue.

The Power is there, but I dont come into the application to use it...