Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

a novel crash on export

Advocate ,
Feb 01, 2017 Feb 01, 2017

a project with lots of effects and lumetri layers:

first time I tried to export (via AME) it crashed.  No huge surprise for me.  Cleared cache. reset AME status, still crashed. Cleared cache rebooted.

At this point when I went file>export. Premiere would think about it, then crash:

Faulting application name: Adobe Premiere Pro.exe, version: 11.0.2.47, time stamp: 0x5876029b

Faulting module name: ntdll.dll, version: 10.0.14393.479, time stamp: 0x5825887f

Exception code: 0xc0000005

Fault offset: 0x000000000004de4f

Faulting process ID: 0x4050

Faulting application start time: 0x01d27c5d2f5b4a26

Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2017\Adobe Premiere Pro.exe

Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll

Report ID: 4ee14f75-d029-4718-a69b-b722e2661cf6

Faulting package full name:

Faulting package-relative application ID:

(Which google helpfully tells me could be just about anything - driver, windows update, software clashing, corrupt ntdll.dll,  less likely - hard drive failing, other hardware failing)

I created a new project and imported the old, still crashed

I tried to export a different sequence in the same project with little in it > still crashed.

A new project, new sequence just with a colour matte would allow me to get the export dialogue up without crashing.

Stop Press! New exciting behaviour - original project now spontaneously crashes without even trying to export.

And another! I cleared prefs, loaded project now a bunch of media is showing as offline. despite the fact its patently right there!

w10(up to date)

nvidia 378.49 (gtx970)

raid, ssd boot drive, ccloud up to date

493
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Feb 01, 2017 Feb 01, 2017
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Advocate ,
Feb 01, 2017 Feb 01, 2017

thanks jim, i didn't search on the exception code, but its similar to the faulting app -- it could be a list of things a mile long.

I did finally get it to start to render, but now its failing reliably after 4 seconds in.

I think I need to do a reinstall of windows wah

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Feb 01, 2017 Feb 01, 2017

It does sometimes come down to that.

But it's also not such a bad thing to do that every now and then.  I do it every 12 to 18 months or so.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Advocate ,
Feb 08, 2017 Feb 08, 2017
LATEST

just in case anyone else has a similar issue, Before reinstalling windows I tried this:

https://www.reddit.com/r/nvidia/comments/2ha3q9/howto_fresh_driver_install_for_new_gpu_or_any/

It involved downloading a driver cleaner and doing a whole entirely clean install.  I installed the previous version drivers, too as 378.49 seem to be buggy (admittedly with 10xx cards).  Rending now completes without incident (but I have to say that playback in premiere with effects on a track seems a lot slower than previously.  Not having used these drivers before, I cant say if its that. )

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines