Surface Book 2: External Monitor Flickering

Thanks PriceCook,

I've just ordered a 3' cable and will test it once it arrives and report back.

Still, seems crazy that the Surface Go has no issue whereas the mighty SurfaceBook 2 struggles to send a USB C connection - I read somewhere else that it may be an issue with the two separate graphics processors conlicting with eachother and in this instance the unit needs replacing. Hope this isn't the case as I can't find anywhere else here in Belgium that has the same spec machine in stock with a Qwerty base.

Cheers for now.

D

Good luck!

This was happening constantly to me - I have two Samsung Monitors plugged into my SurfaceBook2 via a USB-C hub.

I checked the devices attached to the SurfaceBook2 here: Control Panel\All Control Panel Items\Devices and Printers

Under the Unspecified items, there is one Device listed normally, plus the USB 2.0 Hub devices. However Windows sometimes also has as a second and apparently unhelpful Device (same icon as the one normally there) also listed. When I click on this and Remove Device, all flickering stops.

The appearance of the second Device is apparently random, but it is always there when the screens are flickering and removing it always stops that.

I hope this helps!

THANK YOU! Been trying to figure this out for hours and stumbled on your post... The same exact issue here and when I changed the cord to my 3 foot one, and now my tv isn't flickering when I use it as another monitor. 

Update... May have spoken too soon... Slight flickering now... this is **** :[

I have been struggling with this exact same problem ever since I took my Surface Book 2 out of the box, approximately six months ago. Today, the problem has been solved.

I had tried two different HDMI cables (one with an HDMI to USB C adapter, and another that didn't need the adapter), and had the same problem. I tried hooking my laptop up to two different monitors and two different HDMI TVs and had the same problem. I spent HOURS on the phone with Microsoft support, all for naught. Then, I took a four-hour round trip to the Microsoft store in San Diego; there, we were unable to replicate the problem. I was frustrated beyond belief.

Once back home, I started wondering what was different at the Microsoft store as opposed to home (other than being a different monitor, and I knew that wasn't it), so it had to be the cable since I had not taken either of my cables with me. I went to Staples.com and ordered this cable: https://www.staples.com/StarTech-com-USB-C-to-HDMI-Male-Male-Adapter-Cable-1-m-Black-CDP2HDMM1MB/product_IM17M4376. It worked! No more flickering! 

It seems that the two cables I was using before were both 6' long, and the new cable is 3' long. Apparently, past 3', the signal gets lost on the way to the monitor. Of course, the Surface Book 2 *should* be able to drive a 6' cable, but I'm not going to complain, now that everything seems to be working as it should. The 3' cable is barely long enough to go between the monitor and my laptop, so this may not be an option for everyone, but if you can bring the monitor and laptop closer together, this may be the fix you've been looking for. Good luck!!

I have had this problem more than one time.  The first time I thought I solved the problem by installing an upgraded monitor.  But the second time, I was not permitted to install the Intel drivers.

After major messing around with fully reinstalling windows, cleaning USB-C ports etc,  I found the issue. 

I noticed that attempts to charge my mobile phone via the USB-C port would initiate then stop within 30 seconds.  (same behaviour of the monitor).  So I started looking into the USB-C setup.

If you go to Settings >> Devices >> Bluetooth and other devices.    you will see Mouse, keyboard & Pen.  Under this it lists the Surface Keyboard.  In my case It reported that there was a fault with the keyboard  (noting that the keyboard was working perfectly).  

I disconnected the Surface Book 2 Screen.  Checked the cleanliness of the terminals and replaced the monitor:  Problem solved.

Not sure if this will help everyone, but it is a very simple solution, so definately worth checking early in the process.