Skip to main content
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

November 8, 2015

Macbook Pro mid 2012 (El Capitan 10.11.1), Core i7 2,6, 16 GB RAM.

NVIDIA GeForce GT 650M 1024 MB

Same problem

Never had an issue with lack of resources with CUDA and Premiere before even working with 4K footage.

Now I just could not edit anything with this black screen.

I doubt it's an issue of my resources, I couldn't go back to previous system (Yosemite), I just want Adobe or Apple to fix the issue or at least to tell us that you know about the issue, that you're trying to fix it and that's it's not someone personal problem of hardware, but a common problem happening with many-many people (most of them also have never used feedback option to tell you about the problem).

THans
Participating Frequently
November 7, 2015

I'm having a similar problem.  Everything seems to be fine for the most part but my big difference, which I, too believe is a bug in the system.  Every time I click on the Color on the top, next to the editing, my whole program goes black.  I can reopen the project file and get back to where I was but that tab goes black every time.  I'm currently in a class at a college so having a problem like this when a grade depends on it, isn't cool.  Please look into this.  It was working just fine a week ago and now, it's not working fine at all.  Please advise.

Kevin-Monahan
Community Manager
Community Manager
October 29, 2015

Hi Jonathan,

We haven't seen a response from you since you created this thread. Please do let us know if you fully solved the issue. For others on this thread, a few things have been helpful in solving the "black screen" issue.

 

  • Reboot the computer: try to do this a few times a day.
    • This helps reset, refresh hardware items, especially the RAM cache, which you need for intense timelines.
  • Perform regular system and program maintenance:
    • update drivers
    • make sure you meet system requirments
    • run any disk clean or disk utility to clean permissions
    • trash preferences
    • do a clean removal of media cache (make sure all projects are closed first: File > Close all Project, then choose Edit > Preferences > Media Cache and then delete ALL cache files by clicking the bottom button and then click OK).
    • Make sure all folders having to do with Adobe and Premiere Pro have permissions set to Read and Write.
    • If you are doing more 4K now, maybe you need a better GPU, for example.
  • If your computer is a laptop, is underpowered and/or outdated (especially your CPU and GPU), and does not meet system requirements, it will exhibit the "black screen" issue. Consider updating your components or switching to a newer computer.
  • If your computer is newer and has components that are well in spec (core i7, 2+ GB VRAM for your GPU, etc.) and you get the "black screen" issue it is likely to do with:
    • Too many video effects and you have overloaded your GPU VRAM. Use the "Render and Replace function here to get better performance in this section of the timeline. You can also remove video effects at the location where the screen goes black, but most people prefer to render and replace or "mixdown" effects. 
    • You are using 4K footage and your system is not powerful enough for that workflow.
    • You are using 4K footage and are editing in a HD sequence, so scaling is occurring, which is a GPU process. This reduces available GPU cycles from other processes.
      • If HD is the intended output, you might consider transcoding footage from 4K to HD before you begin editing in the project organization stage of your production or create HD proxies.  See documentation about transcoding on ingest.
      • Your GPU drivers are not updated. 
        • This is mostly a Windows tip. Download the current drivers from the manufacturer's site.
        • Mac does not have video driver issues as they are automatically installed with a supported version of macOS.
      • Your GPU control panel on Windows is incorrectly set.
        • Check the requisite control panel. There may be two GPUs and the control panel has the wrong GPU enabled for high quality graphics capability. The control panel for your GPU might be pointing to the more underpowered GPU of the two.
        • Even though you may have a significantly powered GPU, it may be an older one that doesn't support the drivers for a new version of the OS.
        • The GPU is problematic, in general. You can rule out GPU interaction. Choose File > Project Settings > General and set the Renderer to Mercury Playback Engine Software Only. It's very slow, but reliable.


Other workarounds include:

  1. Toggle Track Output (the eyeball) off then on again. (note: this may take a few tries)
  2. Check for OS updates or roll back the OS.
  3. Rolling back video drivers to previous versions of video drivers
  4. Rolling back to an earlier OS
  5. Rolling back to an earlier version of Premiere Pro
  6. Not video effects intensive sections (those with a lot of video graphics, titles, color correction, etc.) and then use render and replace.
  7. Avoid Long GOP codecs, like H.264. Transcode to editing codec or create proxies.
  8. Turn off Hardware Decoding in General Preferences.
  9. Use a smart rendering workflow where you render the timeline to ProRes as you work - and then export to ProRes using previews.

 

I will mark this post as the correct answer and will add any other solutions users may have to this thread. Send me a PM if you think your solution should be mentioned.

 

Thanks,
Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
DrTc
Inspiring
November 3, 2015

Since switching to software mode seems to be the only solution that works effectively, I have a question. In a project where within PR, the Mercury Engine was disabled, and then the render was sent to queue for AME, would AME use Mercury Engine to render it faster, better even if the Premiere project was set  in software only mode?

Participant
October 29, 2015

Guys, GameRaveTV's solution works. U just click the visibility icon a couple of times, and it fixes

Participant
October 24, 2015

OK. Here's a workaround I stumbled upon.

Open the Reference Monitor [Window>Reference Monitor]. That's it.

Something about having the Reference Monitor open sends the video out to my HDMI connected "2nd" monitor. I just keep it open and buried underneath other tabs. Hopefully the Adobe folks can deduce something from the fact that having the Reference Monitor open sends video out and closing it immediately makes it go away.

Good luck!

Thanks,

Jay

Software Version

Adobe Premiere Pro CC

2014.2 Release

8.2.0 (65) Build


System Specs

MacBook Pro (Retina, 15-inch, Mid 2015)

2.8 GHz Intel Core i7

16 GB 1600 MHz DDR3

AMD Radeon R9 M370X 2048 MB

OSX El Capitan 10.11

Participant
October 28, 2015

That workaround works for me Jay, but only when my Thunderbolt Display is connected! When working with just my MacBook Pro on it's own it doesn't!

This is clearly software related as the monitor in After Effects CC 2015 works perfectly.

I find it hard to believe that this problem was first highlighted 2 years and 3 months ago! Adobe are no longer offering advice or appear to be making any attempt to fix it!

Software Version

Adobe Premiere Pro CC

2015.02 Release

9.0.2 (6) Build


System Specs

MacBook Pro (Retina, 15-inch, Early 2013)

2.7 GHz Intel Core i7

16 GB 1600 MHz DDR3

NVIDIA GeForce GT650M 1024 MB

OSX El Capitan 10.11.1

Kevin-Monahan
Community Manager
Community Manager
October 29, 2015

Hi JB,

I find it hard to believe that this problem was first highlighted 2 years and 3 months ago! Adobe are no longer offering advice or appear to be making any attempt to fix it!

Creating a forum post usually results in no action except help from the community. For the team to take action, you must file a bug report. File bugs here.

Thanks,
Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
Inspiring
October 22, 2015

Has there really been no solution yet to this problem? I have to restart my projects every 5-10 minutes!

Participant
October 12, 2015

Hello All,

I get the same problem after fresh installation of my system, I opened the project on which I was working before the installation, It wont show me screen,

Then I updated all my video plugins like Apple Quicktime, Thanks LORD after this update my problem resolved.

Thanks & Blessings.

Inspiring
October 9, 2015

Same problem here, ever since updating to OS X El Capitan. Wasn't having this issue prior to that. Now it's the same thing being reported by everyone else - black screen in any timeline, only DSLR footage and text layers on the timeline. I have to quite every 10 minutes or so because of this...usually Force Quit because once this kicks in, Premiere won't quit with the normal command. I'm also in CUDA mode, not OpenCL because of the widely reported pixelation issue happening in PP when running OpenCL. I will test with Software Only rendering and see if that produces better results.

Premiere Pro 2015.0.2

MacBook Pro (Retina, 15-inch, Late 2013)

OSX 10.11

2.6 GHz Intel Core i7

16 GB 1600 MHz DDR3

NVIDIA GeForce GT 750M 2048 MB

MrBarkan
Participant
October 9, 2015

I'm on a Macbook Pro Retina 15-inch 2.3ghz i7 16gb of RAM NVIDIA GT 750M running on OSX 10.11 and have the same issue... I'm sure it's something with CUDA... i've had issues with the Adobe+CUDA combination since forever really. Not sure why. I thought about taking the MBP to the Genius Bar at Apple and get the motherboard replaced, but apparently it happens on PCs as well.

Now in 10.11 and Premiere 2015.0.2 a new issue has surfaced: when I switch from CUDA to OpenCL whichever frame I'm paused it goes haywire, going normal only on Play.. but if I export that crazy colored frame exports it like that. Something with CUDA+OpenCL+Lumetri?

MJames261
Participant
October 7, 2015

I have the same issue. It has been increasingly more frequent since the last update. The program monitor goes black, but I can still track & listen to audio just fine. No errors are reported in the log file and it doesn't matter if I'm running multiple Adobe products or not.

System Specs:

Intel® Xeon® Processor E5-1620 (8 cores @ 3.7GHz)

Windows 7 Professional 64-Bit (SP-1)

Quadro K600 (Driver Version 353.62)

500GB OS Drive

256GB Cache SSD

32GB RAM

Thanks,