Weird Screen Flickering on my new build

haza12d

Honorable
Apr 17, 2017
119
1
10,715
I recently put together a new build about a month ago and just last weekend I started having issues with my display where it would turn off and on quickly when I try to pull up any system Settings such as right click on the desktop and select Display Settings or right click on the taskbar anf select Taskbar Settings and or when I run Speccy. This flicker would also present itself when I try to install any new programs.

Sometimes it would do it every time I did any of the things mentioned above. Other times it won't.

This only happens when I enable HDR/WCG and turn on UHD (Samsung UN55NU7100) and set it to 4K @60hz.

I thought maybe my card wasn't sufficient enough to run 4K settings or there was a problem with my graphics card (1080ti Gaming X TRIO) but swapping that out with a 1070ti or a 1080, the same thing happens.

Using the any of the cards mentioned above in another system running the same resolution/settings in Windows and my TV, I'm unable to replicate the problem.

I've used three different sets of HDMI cables and the same results.

Google says that screen flickering could either be caused by an incompatible app or an outdated graphics driver but even using the last 5 builds of Nvidia drivers and doing a clean install of Windows doesn't solve it.

I'm really not sure what to do at this point.

Here are my system specs:
i7 8700K
Corsair H115i Pro RGB (Push/Pull)
MSI Z370 Gaming M5
16GB Corsair Vengeance RGB DDR4 3000 (2x8GB)
MSI GTX GeForce 1080 Ti Gaming X TRIO
EVGA 750GQ 750W 80+ Gold
850 EVO 120GB mSATA SSD (mSATA to 2.5" Enclosure)
MP500 120GB NVMe SSD
850 EVO 250GB SSD
3TB Seagate Barracuda 7200RPM
Corsair 780T Full Tower
5x Bitfenix Spectre 140mm Fans (4 Intake, 1 Exhaust)
Windows 10 Pro 64-Bit
Corsair K95 RGB Platinum
Corsair Glaive
Corsair Void PRO RGB (USB)
MM800 Polaris Mouse Pad

Also maybe worth mentioning is that my boot drive is the mSATA SSD in a 2.5" Sabrent Enclosure

There is also a clean install of Windows on the Corsair MP500 that I used to see if it the problem would present itself... And it does.

Could the two separate Windows installations be cause of the problem?

Any thoughts or suggestions would be greatly appreciated.
 

CaptainCretin

Respectable
Jul 18, 2016
625
0
2,160
First thing is to unplug the power from anything that isnt needed to boot and see what happens; you have an awful lot of stuff listed, and any one of them might be in conflict with any other one; or the total might be too much for the psu to keep a stable supply to, especially if the high current stuff isnt spread evenly between the 12v rails.
 

haza12d

Honorable
Apr 17, 2017
119
1
10,715
I'll give it a try with the just the mSATA SSD and 1 stick of RAM and see if that helps any.

I also forgot to mention that I'm using a set of Phanteks Extension Cables from my PSU, I'm gonna remove those and run the cables direct to the GPU.

If it is the PSU not giving enough juice at 4K @60Hz... what should I get? 850W?
 

CaptainCretin

Respectable
Jul 18, 2016
625
0
2,160


The psu should give you more than enough power, I was just trying to eliminate any other hardware issues first. Whenever you have a suspected hardware problem, strip the system down to the minimum number of components and start from there.

In the past I have had everything from a gfx card coming loose in the PCI socket after a minor earthquake, to the motor on an ancient floppy drive going short circuit.

It might be a bug in the monitor firmware itself, so also check for other users reporting issues, and the Samsung website in case they issue a firmware update.
 

haza12d

Honorable
Apr 17, 2017
119
1
10,715
Thanks, I'll try that.

With that process in mind, would the onboard graphics on my Motherboard automatically kick in when I boot without my Graphics Card? Or do I need enable some setting in BIOS?
 

CaptainCretin

Respectable
Jul 18, 2016
625
0
2,160


Unless you have manually disabled it in BIOS, it should kick in automatically.

That is a point though, you want to make sure the system wasnt trying to use both gfx card and on-board gfx together; some boards do this, and I can see it being an issue when you are running hi-rez; the on board wouldnt be able to keep up.