Skip to main content
J
Jon Bradford
Participant
July 7, 2013
Answered

Program monitor keeps going black in Premiere Pro CC

  • July 7, 2013
  • 57 replies
  • 182082 views

PC - Premiere Pro CC - AMD Fire Pro (13.101-130604a-158071E-ATI)

I'm working on a project and the program monitor keeps going black in Premiere Pro CC while I am working on the timeline. I've got like 28 GB of memory alocated to the program and just updated the latest driver for my video card. No clue why this keeps happening, but the only way I can get around it is to restart. When I go to close down the program freezes and I have to shut it down in the system preferences.

Under a crazy deadline if you can help? Thanks

    This topic has been closed for replies.
    Correct answer KimagesImages

    Don't rely on Windows Update to keep your graphics drivers updated. It is woefully suited for that job.

    Instead, go to the Nvidia website and update your graphics drivers from there. 

    I recommend doing a clean install of the Studio (not Game Ready) drivers.


    Jeff,

     

    Thank you so much for your tip! PROBLEM SOLVED. I updated my Nvidia drives and everything is running smoothly. Windows "said' they were fine but when I went to the Nvidia site I was SO far behind! Thank you so much for such a great suggestion. 

    57 replies

    Show previous replies
    jusdog083
    jusdog083
    Participant
    April 2, 2017

    I had this problem since updating from Premiere CC to CC 2014. I thought it might be fixed in 2015 and 2015.3, and 2017 but it never was. In projects with a lot of Lumetri color filters, other filters, image file layers, title layers, or after effects layers on the timeline, I had to keep restarting Premiere in order to keep working without the dreaded black screen in the program monitor. The more layers like those mentioned above I had on the timeline, the more often the problem seemed to occur. The more complex projects became the most frustrating to work with.

    I have Nvidia GTX 760, 32GB DDR3 RAM, Intel Core i7-3770K and I'm on Windows 7.

    I rolled allllll the way back to Nvidia driver 332.21 (found here) from the latest driver, which is now 378.92.

    So far so good! I can scrub through all the different layers quickly and the black screen of death has yet to appear. Seems like an Nvidia problem to me.

    I should also mention that I adjusted my System Properties to take strain of my video card. I went to System Properties/Advanced/Performance/Settings/Visual Effects and unchecked just about everything except "Smooth edges of screen fonts". Not sure if this helped or not.

      Kevin-Monahan
      Community Manager
      Kevin-MonahanCommunity Manager
      Community Manager
      April 4, 2017

      Thank you for the update jusdog! Could be the ticket for other users w/ the same issue.

      Regards,
      Kevin

      Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
      K
      kevinmarchese
      Participant
      July 9, 2016

      Changing to mercury playback engine software only worked for me. At least for the moment. Thank you. Will report back

      Mac (27-inch, Late 2012)

      3.2 GHz Intel Core i5,

      24 GB 1600 MHz DDR3

      NVIDIA GeForce GTX 675MX 1024 MB

      10.11.5 OSX

      D
      Dave Lalande
      Known Participant
      June 20, 2016

      I'm having this same issue.

      Windows 7

      Certified Adobe workstation from Dell (factory, no mods) a few months old

      AMD FirePro W5100

      XEON 10 Core

      64 GB RAM

      This just started happening.  No videos will play in Premiere Pro.  MP4, MOV or anything, all I get is audio.  Adobe Media Encode and After Effects are having no problems with my clips.  I've been using the software for years and have made hundreds if not a thousand videos and now the software is not usable.  I've uninstalled Pr and reinstalled, still has the same issue.

      Not good...

      D
      Dave Lalande
      Known Participant
      June 20, 2016

      I reinstalled my video driver and now Pr can play video.  I can't explain why the other Adobe apps were working but Pr was not?

      I'm back in action.

      Thanks,
      Dave

      D
      Dave Lalande
      Known Participant
      June 22, 2016

      Looks like I'm still having this problem.  I was able to better track down where I think it's coming from.  When I open Ae and then open Pr the video is black.  I reload my drivers and the video comes back in Pr.

      Adobe please advise.

      Thanks,

      Dave

      brendan carolin
      brendan carolin
      Participant
      May 16, 2016

      welshonemillion​ has addressed the issue. Adobe, please fix it.

      Had to disable the expensive Quadro card so that this program will run correctly.

      raveng
      raveng
      Participant
      February 15, 2016

      Same problem here, working on W7 x64 i3 3,10 Ghz w/ 4GB with Premiere CC 2015, but solved as Kevin said, Renderer changed to Mercury Playback Engine Software Only. Now Program screen shows correctly the media of the timeline

      Revit
      Revit
      Participant
      February 15, 2016

      Yes that may alleviate the black monitor issue but now you just created a different problem for yourself.

      Revit
      Revit
      Participant
      January 27, 2016

      I now have the same issue. I did not have this issue in the past. I am experiencing this with both my windows PC: (Windows 10, Fast i7 quad core comp with a GTX960 graphics card), and my Macbook Pro Retina 15" (with a 660 graphics card). After editing for a while, my Program monitor will go black. Nothing I do fixes it except closing Premiere and re-opening it. I've tried toggling video layer visibility, changing it from alpha to multi-camera (that occasionally lets me see it in a smaller window), etc. This is absolutely a bug in Premiere.

      MrBarkan
      MrBarkan
      Participant
      December 19, 2015

      I've been simply avoiding using CUDA as an accelerator lately, OpenCL has been working quite well since the last update. But when on CUDA what makes it work for me is avoiding to have any other apps open, such as a browser or even a video player like VLC.

      GregTR
      GregTR
      Participant
      December 24, 2015

      OK. I did bite the bullet and bought a new video card. I replaced my ATI Radeon 5450 with a Gefore GTX 960 as I started doing some linear modifications on some of my clips which could be offloaded to the GPU so it sped up my render times by twofold. A one hour video now only takes 3.5 hours instead of 7, however for all practical intent and purposes 3.5 vs. 7 does not make a difference for me, it's still an overnight render.

      The blackouts have improved meaning that I could actually enable CUDA in premiere and have playback work for the most part. However it still breaks down at times in some scenarios which is quite frustrating as I still have to have it disabled for playback due to these scenarios.

      I record hockey games with 5 cameras. I create a multi camera stream of 4 of these cameras and I have another nested stream with the same camera stream on top of each other three times with different crops to display the clock and the home and visitor penalties. Then my final work stream has the multi camera stream on the bottom and the nested clock stream on top. When there is a goal or a penalty I crop out a small part of the multi-camera stream and repeat it above the other streams and remap its time to 50% for a slow motion replay. If my project has more than 3 of these replays then the replay does no longer work, it just shows a black field as soon as I do the time remap. Now the weird part is that if I flatten this multi-camera stream for the replay (I usually use the same camera angle for the replay period anyway) then everything works and it previews fine with CUDA. However Since I make color/level adjustments to the raw streams but keep them turned off during the camera angle cutting phase it's a pain to flatten the multi camera stream for the replays as I damn better have these adjustments right by then otherwise I have to redo them for each replay.

      So as of right now I turned off CUDA once again. It's rather unfortunate that this bug cannot be eliminated with 3+ years of feedback on the issue.

      RagnarUlricson
      RagnarUlricson
      Participant
      January 22, 2016

      I've had this exact problem and it caused a lot of ruckus. Came of course when I least needed it and it took me several days to pinpoint it.

      I'm on Windows 10 64 Bit, using a Geforce GTX 970 as graphics card.

      What caused it, in the end, was that the program "Sonic Suite 2", which is installed by Asus's mainboard software (and I'm not even completely sure what it does) was running in the background.

      As soon as I closed this program (and restarted premiere) everything went normal.

      So, I'm pretty sure that this is not really Adobe's fault - it might not be the same program, but it's very likely that some application running in the background is causing this problem for you. So really try and close everything that isn't absolutely needed for Premiere and if it works, you can narrow it down, one by one.

      It worked for me, hope it helps you as well.

        GregTR
        GregTR
        Participant
        November 19, 2015

        Actually for me it seems like if my playback is set to 100% I don't get a blackout but if it's set to 50% or Fit I get a blackout. I have tried everything else that was listed by others to no avail. I'm about to purchase a stronger video card and see if the acceleration support is better with it without blackouts.

        K
        Keith Moreau
        Known Participant
        November 19, 2015

        Hi Greg

        You can get a better graphics card but I don't think that is the solution to the problem, though it could speed up Premiere Pro. There are people experiencing this problem with the highest end systems. Though Kevin Monahan's list of possible workarounds is helpful, and I applaud Adobe for having a Adobe staff presence in this forum, I feel that Adobe's comment that this problem is due to an inadequate system is a red herring for most people out there. The problem lies, I feel, in Premiere Pro having a bug, and I also feel this should be one of the highest priorities for Adobe engineers to solve this. It has been 6 months since cc2015 was released. As I've mentioned in my podcast, "TechMove" -www.techmovepodcast.com - Adobe needs to stabilize their software first before adding features. A system that needs to be restarted or time consuming workarounds, starts losing it's usefulness, particularly for professionals with deadlines.

        -Keith

        blueyedea
        blueyedea
        Participant
        November 19, 2015

        ‌

        Richard Crook
        Richard Crook
        Known Participant
        November 16, 2015

        I was having the same problem.  I tried everything, but noticed the culprit was images that exceed 1920x1080 (the sequence size).  I resized them externally on a photo editor and boom...no more black screens.

        K
        Keith Moreau
        Known Participant
        November 16, 2015

        I actually noticed that placing large pngs did this as well. Or adding effects to those PNGs, for example adding a crop to a PNG caused this problem. Removing it didn't resolve it, I had to restart to resolve the problem. Replacing the PNG with a JPG solved the black screen problem (this time). I cannot scale my images to 1080P, what if I need to add some motion to the image? It has to be larger than 1080P. These are basic problems that should be tested and confirmed by Adobe and fixed, it's very simple stuff. There are so many instances from people in this thread alone to be able to reproduce and fix this problem. I'm imploring Adobe to resolve this asap. In the last couple of days I've had to restart Ppro 2015 about 15 times to reset the problem which can occur in a number of scenarios, many involving still image files but others now.

        Show more replies
        Terms & ConditionsAccessibility statement
        Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices