Repeated disconnects

[saare1]

I'm experiencing repeated disconects

I have followed the steps here http://www.displaylink.com/support/ticket.php?id=269 and i'm still experiencing issues.

How often does the issue occur? At least once per hour
How do you invoke the issue? There does not appear to be any particular trigger for the disconnect
How do you recover from the issue? Disconnect and re-connect or "scan for hardware changes" on the device in "device manager"
Was the issue present in older versions of DisplayLink software? Yes
How are you connected to the DisplayLink device? Directly or through a USB hub? Hub - Surface Book with Surface dock

All drivers are up to date. Logs attached

[AlbanRampon]

Hello,

First thank you for providing details and the logs, this is very helpful.

I can see USB communication is failing, then the driver waits and Windows crashes the driver after 10s. I imagine that before you have the disconnect, you probably have the screen frozen for about 10s max.

Would you mind trying to connect the USB32DVIPRO directly to the Surface Book and report if the behaviour changes? This would help understand contributing factors.

Kind regards,
Alban
My refs:
Dump 2880+13680+3864 = ReportBugcheckForSwapChainTimeoutDriverDidNotRelea seFrame
Dump 1480= HandleNewSwapChain critical section lock-up

[saare1]

Thanks for getting back to me. Your summary is spot on.

I'll try connecting directly and let you know how this affects things.

Thanks,
Alex

[saare1]

After testing it would appear that connecting directly is stable.

[saare1]

can anything be done to address the connectivity issues via the surface Dock?

[AlbanRampon]

Hello,

I have logged a request for analysis. We will first need to reproduce it and see what is cutting the USB traffic.

But, as this is the only report of such issue we have had, the analysis is queued and not scheduled.
In the meantime, you may wish to look to see if there is a firmware update for the Surface Dock which might update its internal USB hub firmware as this issue might have been observed with other devices downstream.

Kind regards,
Alban