Surface Pro 3 external monitor / display port issues

Anonymous

I know many people have been having issues with external monitors and the displayport connections on the Surface Pro 3 and Surface dock. I've been having some issues too, and thought I'd share my config / workarounds in case it helps. I believe the issue is fundamentally with the Surface video drivers getting confused, not the docking station.

My explicit questions are: Is there an easy way to force it to detect new displays? Anybody have any other suggestions on how to resolve this? Is there some way to open a formal technical ticket with MS?

My hardware: Surface Pro 3 i7, 256 GB; Surface docking station, 2 HP Z24i displays (1920x1200 resolution each), StarTech Mini DisplayPort 1.2 to Triple Head DisplayPort MST Hub (StarTech PN# MSTMDP123DP)

It's setup as follows: Mini DisplayPort MST Hub plugged into back of docking station, HP monitors plugged into ports 1 and 2 of the hub.

I've had this setup running for about 2 weeks. At first I couldn't get it working, but with the last firmware update in mid August it started working fine.

HOWEVER, just this week I've had issues where I can't get the Surface to detect the displays / output to them when I first plug in to the dock in the morning OR sometimes when it's waking up from going to sleep (like at lunchtime). No amount of fiddling / plugging / unplugging things seems to consistently fix it. The 'Detect' button in the Screen Resolution window doesn't help. Doing a shutdown / restart of the Surface also doesn't consistently work. Note that when the Surface gets like this, even plugging the Hub directly into the mini display port on the Surface itself (with it not docked) won't work.

The reason I believe this is a Surface / Windows issues is that when it gets into this state, within the screen resolution settings in windows it often thinks that there is another active display plugged in and will act as such (e.g. lets me extend or duplicate the desktop) - even if I have the surface completely undocked, not plugged into anything. Specifically it says it is a "Display device on: Mobile PC Display" with a resolution lower than 1024 x 768. See pic below. This state often survives through a reboot of the Surface.

The general process I usually get to work after a couple tries:

-Use Windows-P keys to set the surface to use only the internal display

-Shutdown the surface and undock

-Unplug the dock and hub

-Plug hub back in

-Power Surface back up while undocked and login

-Dock surface

-Plug dock back in

-I'll know it works at this point because the displays will automatically come on (no need to use windows-P key to toggle them)

NOTE TO FORUM MODS:

Before you reply with your standard questions, know that I've already done all the normal things, including shutdown, check all cables, all updates installed, run the hardware and devices troubleshooter. I've also checked related threads, such as: http://answers.microsoft.com/en-us/surface/forum/surfpro3-surfdevice/external-display-flicker/1e2b9154-0533-4137-880f-55a90d2d6659?page=1&tm=1409850909719 (Note I've never had an issue with flicker) and http://www.surfaceforums.net/threads/mini-displayport-on-new-docking-station-doesnt-work.10577/ (This isn't an active vs. passive adapter thing.) Once I get it working it works just fine until the surface undocks or reboots. It's clearly an issue with Windows / Surface not properly detecting displays.

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.

0 comments

129 answers

Anonymous

2014-11-26T15:16:42+00:00

I am also getting this issue and it has become more evident since the last firmware update 18/11/2014.

I use the surface 3 for working and I can't spend a random amount of time (never less than 15 minutes and up to 1 hour) every morning plugging and unplugging cables while I restart everything.

I also contacted the surface support (UK) and they told me it was the first time they heard of the issue. They couldn't do anything to help me in the end. I thought I found the solution when I shut down the device instead of resetting and it worked but today I have been proved wrong.

I have a reference number for the issue but... if they don't know anything about it... what's the point in me losing 1h with them?
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2014-11-26T17:06:42+00:00

I am also getting this issue and it has become more evident since the last firmware update 18/11/2014.

I use the surface 3 for working and I can't spend a random amount of time (never less than 15 minutes and up to 1 hour) every morning plugging and unplugging cables while I restart everything.

I also contacted the surface support (UK) and they told me it was the first time they heard of the issue. They couldn't do anything to help me in the end. I thought I found the solution when I shut down the device instead of resetting and it worked but today I have been proved wrong.

I have a reference number for the issue but... if they don't know anything about it... what's the point in me losing 1h with them?

so far, I have been able to recover with just a "shutdown" (hold the button until it dies). Reboot does not work. my workaround is to always do a "shutdown" when I know I am heading back from a meeting to the docking station. then everything fires up just fine for me, other than the time it takes to spin it up.

hope the next firmware fixes this issue.

I also looked for the "disable wireless on LAN" in the Bios, and it does not exist.

:-(((
Was this answer helpful?

0 comments No comments
Anonymous

2014-12-03T22:16:59+00:00

I have the same issues. I am using the surface dock and two Dell U2414 monitors. One monitor will nearly always work but I never know when the second will quit. I haven't figured out a fix that will always get the second monitor to come back on. It is 5-30 minutes of fiddling every time. I've even tried the recommended steps here with some success but not with consistency.

Frustrating!!
Was this answer helpful?

0 comments No comments
Anonymous

2014-12-03T22:32:28+00:00

I have the same issues. I am using the surface dock and two Dell U2414 monitors. One monitor will nearly always work but I never know when the second will quit. I haven't figured out a fix that will always get the second monitor to come back on. It is 5-30 minutes of fiddling every time. I've even tried the recommended steps here with some success but not with consistency.

Frustrating!!---

my 3 has now started to be even more flaky when plugged back into the docking station. mouse, keyboard and docking station attached monitor not being found. the Mini-DV on the tablet has always worked to date..... yes 5 to 30 minutes of turning off, turning on, cycling the docking station, rebooting, etc... I am rapidly thinking about moving back to a true laptop. we'll see.

the weirdest thing is the mouse moving on the screen, but none of the W8 app buttons are active. like a screen print with no hyperlinks. Don't know if the mouse is not clicking or the apps are not active... takes several off/ons to make work again.

come on Microsoft, it's a fancy laptop, what behind the scenes is not "getting it"?????
Was this answer helpful?

0 comments No comments
Anonymous

2014-12-10T10:05:20+00:00

Just chiming in to add my 2 cents.

We (so far) have 7 Surface Pro 3 in the company. 3 are connected to dual Dell U2414H using the dock and Daisychain. The others are connected to single monitors (different Dell monitors) using the dock.

I can confirm what others are saying here. Somtimes the monitors are just not recognised (or the second monitor in the chain) when we redock.

On several occasions the second monitor in the chain completely disappeared. The only way I could solve it was to swap out the second monitor (which works fine elsewhere).

Inconsistent and very frustrating!

This is stopping us from rolling out on a larger scale - such a shame - otherwise love the devices :-/
Was this answer helpful?

0 comments No comments