Skip to main content
Participating Frequently
January 25, 2018
Question

Premiere Pro CC Crash

  • January 25, 2018
  • 2 replies
  • 343 views

I Just built a new Windows 10 PC and I am having so many issues with Premire Pro CC crashing when I try and render out a video.  Here are my specs.

Windows 10

32 GB of Ram

NVIDIA 1080Ti Graphics Card

Samsung SSD for the boot drive

M2 SSD for my Cache Drive

Samsung Pro SSD for my Media drive


I am working with .mov footage coming from a tricaster. I am able to import it and edit it just fine but anytime I export the footage it just crashes the computer. I am trying to export out an MPEG 2 file as well as a h.264 file. The video is over 2 hours long and the Raw file I am working with is over 90 GB.  I have edited this same file format on a MacPro on my work machine and it works fine. I also tried to render out the .mov file into a different codec to see if that would help and it just cashed my computer again.  Why is it crashing on my new PC that should be way faster than the Mac Pro. If anyone has had an issue like this and has any suggestions I would love to hear it.  Thanks.

    This topic has been closed for replies.

    2 replies

    Participating Frequently
    February 16, 2018

    I am now getting the Blue screen of Death when I just try and import in some footage and work on a project.  Has anyone else had this issue. Thanks.

    Kevin J. Monahan Jr.
    Legend
    January 31, 2018

    Hi DavidT,

    Does it behave the same way when exporting a small section? How about exporting another source for media as a test? Does that work?

    Thanks,
    Kevin

    Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
    Participating Frequently
    January 31, 2018

    I have tried with a small section and it still crashed. I have rendered out other files and it works just fine.  The file also works on my 7 year old iMac and rendered out fine. Just an issue with my New PC that should be 10x better than my iMac.  I think it might be a QuickTime issue But I have not lfigured it out yet.