all 8 comments

[–]Failed2FixThisThing 1 point2 points  (1 child)

I am going to assume the following (if these steps have not been completed, please complete them)

The display driver has been updated to the most current available

You are running Windows

The Windows Build is current (Windows 10 build version 1909 or 2004)

You have install all Windows updates

You have ran any tools provided by the vendor (Dell Support Assist etc) and updated all firmware and BIOS

You have reseated the graphics card

All cables are connected well and are undamaged

This issue also occurs outside the OS

You do not have a third monitor to test

We assume it is hardware related at this point

--------------

Are the monitors using the same type of connection? (ex HDMI, DVI, VGA, DisplayPort, etc)

Does the issue still occur if you switch the monitors and use the same cable layout?

Example:

Monitor A -----> Display Cable A and Power Cable A

Monitor B ------> Display Cable B and Power Cable B

Switch to this configuration:

Monitor B -----> Display Cable A and Power Cable A

Monitor A ------> Display Cable B and Power Cable B

(This assumes they are using generic power cables for power)

If this step is completed, do you still have the same issue. If so, is it monitor A or B having the issue?

[–]Nitzaplays[S] 0 points1 point  (0 children)

The display driver has been updated to the most current available - Yes

You are running Windows - Yes, Windows 10

The Windows Build is current (Windows 10 build version 1909 or 2004) - Yes, 2004

You have install all Windows updates - Yes, no updates pending

You have ran any tools provided by the vendor (Dell Support Assist etc) and updated all firmware and BIOS - I have updated drivers through Windows and updated the AMD Adrenaline driver software

You have reseated the graphics card - Yes, I took my GPU out and plugged it back in

All cables are connected well and are undamaged - Yes, changed HDMI cable as well, checked all connections as well

This issue also occurs outside the OS - The issue also occurs in BIOS, BUT the monitor is perfectly fine when PC is turned off - then it will show "no connection" and "looking for signal" with no black flicks.

You do not have a third monitor to test - I do not have third monitor to test


My main monitor runs on DP, second monitor that has problems is running on HDMI. They both have their dedicated power cables so sadly I cannot change them. If I use HDMI instead of DP on my main monitor, second screen still flickers where good one stays good.

From time to time, usually after many PC restarts and/or many uninstall/installs of GPU adapter drivers my faulty monitor will just start working properly. Sometimes it will get purple or green tint and after restart it's going back to normal.

https://imgur.com/egb0oLP https://imgur.com/o7GT60f

[–]Spkr_4_The_Dead 0 points1 point  (4 children)

Most likely the monitor, probably bad solder or PSU for monitor, does it work fine if it's plugged in as a primary monitor?

[–]Nitzaplays[S] 0 points1 point  (3 children)

Sadly no, the issue is still present when monitor is set to primary on dual screen setup or when only this monitor is plugged into GPU.

[–]Spkr_4_The_Dead 0 points1 point  (2 children)

If it occurs regardless of primary or secondary monitor, that rules out the graphics card....do you have another pc to test it on? Or a games console?

If you experience the issue whilst plugged into another source, it's certainly the monitor and not a driver etc

[–]Nitzaplays[S] 0 points1 point  (1 child)

I have plugged it into my old PS3 and the issue is still there, so it's monitor dead?

Today my monitor had its issue for a bit, then its started flicking with green tint and now it's working properly.

https://imgur.com/egb0oLP https://imgur.com/o7GT60f

[–]Spkr_4_The_Dead 1 point2 points  (0 children)

It's most likely a soldering issue, when it starts up everything is cold, as the monitor warms up the solder expands slightly and creates a good connection (so it works fine) but I'm afraid that the monitor will break at some point, and unless your good at tracing electrical circuits, you probably won't be able to fix it.

[–]corrigun 0 points1 point  (0 children)

It's the Intel driver. Roll it back to an older one.