It has to be software. Nothing has worked for me other than lowering the resolution of the external display below 4k. I'm hoping the update today fixes it.
Surface Pro 4 - External screen keeps turning on/off (black flickering)
Hi there,
I just made a video of my recent problem: https://www.youtube.com/watch?v=Phi\_Yru77aM
You can see that when I'm using the built-in screen of my SP4 (i7, 16GB, 512GB) and only one 4K external screen (both at 60hz), this monitor keeps turning black on a random basis. All my drivers and firmware are up to date (Surface Dock and Surface). I even tried the last Intel Iris 540, same results. I tried another MDP to DP cable, same results. I tried another screen, same results. I tried different refresh rates, same results.
I bought this screen a month ago and I was working fine at the beginning. I strongly suspect an update or the fact that I tried to connect two 4K monitors at 60hz (and I would have damaged something in the process?).
If I deactivate the built-in screen, the problem goes away (something that I just found tonight).
Should I send the device in warranty or just wait for a software fix? The 4K experience is not there yet, I'm a bit disappointed I have to say.
Cheers,
D.
Surface | Surface Pro | Display and screen
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
171 answers
Sort by: Most helpful
-
Anonymous
2017-10-17T12:08:23+00:00 -
Anonymous
2017-10-17T06:24:16+00:00 Not sure actually but it would look software to me because it was working fine on my setup before Spring update...
Has anyone gotten some news on this problem?
I noticed something last week, the automatic brightness adjustment was not working properly and somehow, I could watch videos on the SP4 display and use Lightroom on my 4K display without having any flickering. I had to reboot the SP4 at some point, the automatic dimming worked again but the black flickering came back.
A clue or not a clue, that's the question ;-)
Cheers,
G.
-
Anonymous
2017-09-26T11:52:03+00:00 I'm having the same issue on new Surface Pro (2017) i7/16GB. I'm using the Samsung U28E590D which is on the list.
What I have tried (1) Software repair tool, (2) various display port to mini display port cables, (3) HDMI 2.0 adapter, (4) Microsoft warranty replaced my Surface Dock over the issue, (5) I've warranty replaced the U28E590D screen and it still happens on my replacement screen, (6) I've tried turning off Hyper-V, (7) Tried 59 Hz / 60 Hz
Microsoft wants me to call them so they can keep troubleshooting it, but it seems like a pretty widespread issue. I suspect they will warranty replace my Surface over this issue, but I doubt the replacement will contain a fix as it is pretty apparent that the device is defective by design since the SP4, and MS didn't fix any of the underlying usability problems before releasing the new SP.
Surface Pro 4 with same monitor and same issue.
Ran the Software Repair tool = no fix.
Ran the Dock repair file = no fix.
I believe the flickering began for me after the Creators Update.
I have noticed that turning off Freesync holds off the flickering, but it is painfully laggy, and need to do more testing to see if that permanently solves the flickering on/off issue.
I just updated last night:
2017-09 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4040724)
...and the issue still remains. Immediately after rebooting after update it was worse, turning on and off every other second.
-
Anonymous
2017-09-16T20:51:48+00:00 Yes tried an AOC 4k monitor same problem
No issues if I disable the surface screen and use external display only
-
Anonymous
2017-09-16T16:34:28+00:00 Hi there,
Yes, the problem is unchanged at the moment. I still cannot use both external and Surface displays at the same time wihtout experiencing the black flickering.
I haveaalready submitted a feedback report. Do you more of them? The worrying part is that it seems that the last Surface model (2017) is also affected by the same issue.
What should we all do next ?
G.