Shotcut Black Screen Flickering

Help/How To
1

Hi Shotcut forum,

I’m wondering if you can help me please. Shotcut is flickering to a black screen when I click around the UI, drag video into the timeline, move my mouse, etc. This started around a week ago, coinciding with an NVIDIA GPU driver update, a windows update and moving to the latest version of Shotcut.

I’ve recorded a video here: https://vimeo.com/1057175213

So far, I have tried the below:

  • Deleting my Shotcut Register
  • Reinstalling Shotcut
  • Installing the previous version of Shotcut
  • Installing the previous NVidia graphic driver
  • Updating my CPU, BIOS & integrated graphic drivers
  • Turning off NVIDIA Geforce overlay - Geforce seems to treat Shotcut like I’m running a game

This issue only happens with Shotcut as far as I know - no other program or game is doing this.

Hardware:

MB: Gigabyte B760M X AX DDR4 1.2
Operating System: Windows 11
GPU: NVIDIA Geforce RTX 4070
CPU: Intel Core i5-13500 13th Gen
Monitor: LG Ultragear
Shotcut Version: shotcut-win64-250125

I would really appreciate your help - thank you all in advance.

2

I have never experienced this, and it is very rarely reported if ever. I too use RTX 4070 on Windows 11. It’s weird; it is not only the Shotcut window rather the entire screen. I have seen systems with external monitor flicker to black like this occasionally due to HDMI resets. Sometimes that is attributed to a bad cable. Sometimes it is when using too high quality video settings in the OS (or TV box such as my UHD blu-ray player). But Shotcut does not affect Windows’ display settings.

Restart (power cycle) the computer if you haven’t. I cannot think of anything else to try or troubleshoot except perhaps some entries in Windows Event Viewer might say something, but often these are difficult to read.

3

Thanks for the help, much appreciated.

  • I tried looking at WEV, all I can see for shotcut is hang error + force closing the program when it eventually froze
  • I tried reconnecting the display port into all three of my graphics card outputs - same issue
  • I’ve restarted my PC, still the same problem

It’s bizarre - I didn’t have this problem until about a week ago! I’m trying to remember what happened right before it. There was definitely all three of a GPU driver update, shotcut update and windows update.

Perhaps it’s a monitor issue? My refresh rate is 165hz, don’t know if that changes anything.

4

Look for any messages related to the graphics subsystem, like anything from NVIDIA.

Is that what you have configured in Windows Display Settings? If so, I would try to reduce that, first try 60. If it works, try increasing from there.

5

Thank you again for the help.

I’ll be honest with WEV - I’m not sure where/what to look at sorry. I went Windows Log > Application and searched both nvidia and shotcut. Last nvidia log was hours before I opened shotcut:

Faulting application name: nvcontainer.exe, version: 1.42.3485.3667, time stamp: 0x66e983b0
Faulting module name: nvapi64.dll_unloaded, version: 32.0.15.6636, time stamp: 0x674f5d87
Exception code: 0xc0000005
Fault offset: 0x000000000041bdab
Faulting process id: 0x4C84
Faulting application start time: 0x1DB7D96795E4608
Faulting application path: C:\Program Files\NVIDIA Corporation\NvContainer\nvcontainer.exe
Faulting module path: nvapi64.dll
Report Id: 9bdb91ad-f7bd-4b81-b120-838f33021474
Faulting package full name: 
Faulting package-relative application ID:

Correct on display settings. I tried 60hz & 144hz, both had the same problem!

6

This is just a wild shot in the dark. But, if your system has integrated graphics, you could try to disconnect the RTX 4070 and connect to the integrated graphics. Not a final solution, of course, but maybe informative as a test.

7

Thank you - I connected to the integrated graphic via HDMI and was fine.

How bizarre! OK, this must be a graphics card issue. Might be I need to wait for new drivers.

8

I’ve managed to resolve the issue by rolling back two driver editions. I’m now back on v566.36 (Dec 5th 24) Geforce Game Ready Driver, and no longer experience the issue. I will wait until the next driver edition and test again.

1 Like