Windows 10 Pro Insider 14251 release issue

willybob · 02-02-2016, 03:35 PM

Hello,

Since Build 14251, screen constantly flickers when Displaylink driver is installed and DL device is connected.

Tried the trick with the registry keys to delete, did not work at all.

Looks like a driver issue under this specific build. Previous build was not affected by this issue.

On the other side, Microsoft annouced that there could be some memory issues with this build : "...Due to a recent memory management change, you may see periodic app crashes or other memory related app errors. ..."

Reverted back to Build 11102 and everything is fine again.

Looks like explorer is crashing in a loop because of Displaylink driver under Build 14251 which causes this flickering.

Uninstalling Displaylink driver under 14251 makes everything work again, hence why the driver is involved in this situation : Instalaltion works fine, but as soon as you connect the device, it starts flickering and everything gets really slow. You can still control everything tho.

Disconnecting the DL device stops the flickering after a while.

AlbanRampon · 02-03-2016, 08:22 AM

Hello Willybob,

Would you please have the logs taken when the issue occurs?
We've got thousands of docks used by people who get pre-versions of Windows and this is a single report so it might be an isolated incident linked to your configuration we need to look at.

How can I report Windows installation issues to DisplayLink?

Regards,
Alban

willybob · 02-04-2016, 10:43 AM

Hi,

The report is attached.

Same behavior under 14257 Insider Build : DL Software is installing without any issue, just after conenctig DL device, it flickers constantly.

Latest Fresco USB 3.0 driver is installed

willybob · 02-04-2016, 10:50 AM

HI again,

Second report : This one is taken under the flickering state, just in case it shows something happenning.

AlbanRampon · 02-04-2016, 11:47 AM

Thank you WillyBob, interesting the version you have! I didn't think it was ready to be in the wild... This build is the start of a fundamental change, not just a minor update. That's why you got the warning that crashes would be expected.

You might have two phenomenons here:

1. Flickering:
Could you please describe the flickering?
Is it on all screens or only the monitor through DisplayLink?
Is it linked with you moving stuff to that monitor or even when displaying the desktop it flickers?
Do you get an image from Windows?
Do you hear the Windows USB connect/disconnect sound? The port USB joue au yoyo. That could explain the

2. When it's slow, would you be able to check the CPU load for DisplayLink Manager / DisplayLink User Agent? We have a known bug on 7.9 M4 (build 7.9.1336.0) we're fixing for 7.9 M5.

willybob · 02-04-2016, 12:00 PM

Hi alban,

Thanks for trying to help.

So, my sytem is setup like this :

Asus Notebook U36SD with only one display (Samsung) with dual input.
One output is connected to HDMI
Second one to UGA-4KDP

I get two screens on the same monitor then.

Behavior :
Everything is installed, including the DL adapter driver.

If I disconnect (physically or logically) the DL Adapter, everything works fine, but of course I get nothing on this screen.

If I try to extend desktop throught the adapter, flickering starts and keep going even when doing nothing.

No sound like the connect/disconnect one) Screen is just blinking for ever (Laptop display and HDMI screen).
If I disconnect the HDMI, same thing happens on the laptop screen.

Windows still works of course.

When it flickers, DisplayLink Manager and User Agent are both using around 5% CPU.

When I disconnect output through DL Adapter, it goes back to 0% CPU.

Fun enough, everything works fine under the 11102 Insider Build. No trouble. Started since moving to 12451, then 12457. between every move, DL stuff was uninstalled, cleaned properly, update was done then DL stuff was reinstalled.

Update : another funny thing :

Assuming that
1 is the laptop screen
2 is the HDMI display
3 is the DL display

When I try to expand the desktop to monitor 3 through the DL adapter, it flickers. 2 is active but flickers, 1 is active but flickers.

When I try to duplicate the desktop from display 2 to display 3 through DL it does not flickr, but 3 stays off.

When I try to duplicate the desktop from display 1 to display 3 through DL it does not flickr, but 3 stays off.

AlbanRampon · 02-05-2016, 10:42 AM

Ok WillyBob. Thank you for all these helpful details!

I created a support ticket, once at least some minimal testing is done, I would like to see if our latest software is addressing it. You should receive an email on Monday with a download link, unless we discover a show-stopper over the weekend.

My ref: 21659

willybob · 02-05-2016, 10:50 AM

Hi Alban,

OK this way. In the meaning time, I reverted to Insider Build 11102 so I can use my DL device properly.

If any need, tell me, I can reprocess the last build in minutes for further testing.

willybob · 02-12-2016, 04:59 PM

Hi all,
Replying to myself : Problem solved.

Having an Optimus graphic card system (Intel HD 3000 / nVidia GT520M) on my Asus U36SD notebook, figured out that desactivating the nVidia controller solved my issues under Windows Insider Build 14257 (works also for Build 14251).
Build 11102 does not have any issue with Optimus.

If you have this kind of issues with this kind of setup, it's worth a try.

02-02-2016, 03:35 PM	#1
willybob Junior Member Join Date: Sep 2011 Posts: 24	Windows 10 Pro Insider 14251 release issue Hello, Since Build 14251, screen constantly flickers when Displaylink driver is installed and DL device is connected. Tried the trick with the registry keys to delete, did not work at all. Looks like a driver issue under this specific build. Previous build was not affected by this issue. On the other side, Microsoft annouced that there could be some memory issues with this build : "...Due to a recent memory management change, you may see periodic app crashes or other memory related app errors. ..." Reverted back to Build 11102 and everything is fine again. Looks like explorer is crashing in a loop because of Displaylink driver under Build 14251 which causes this flickering. Uninstalling Displaylink driver under 14251 makes everything work again, hence why the driver is involved in this situation : Instalaltion works fine, but as soon as you connect the device, it starts flickering and everything gets really slow. You can still control everything tho. Disconnecting the DL device stops the flickering after a while. Last edited by willybob; 02-02-2016 at 04:14 PM.

02-03-2016, 08:22 AM	#2
AlbanRampon Senior Member Join Date: Sep 2015 Location: Cambridge, UK Posts: 1,678	Hello Willybob, Would you please have the logs taken when the issue occurs? We've got thousands of docks used by people who get pre-versions of Windows and this is a single report so it might be an isolated incident linked to your configuration we need to look at. How can I report Windows installation issues to DisplayLink? Regards, Alban __________________ Alban Rampon Senior product manager, universal docking stations and accessories "DisplayLink is proud to be a Synaptics brand." Where to download the latest DisplayLink drivers How to clean up a corrupted installation How to report issues to DisplayLink for a speedy resolution

02-04-2016, 11:47 AM	#5
AlbanRampon Senior Member Join Date: Sep 2015 Location: Cambridge, UK Posts: 1,678	Thank you WillyBob, interesting the version you have! I didn't think it was ready to be in the wild... This build is the start of a fundamental change, not just a minor update. That's why you got the warning that crashes would be expected. You might have two phenomenons here: 1. Flickering: Could you please describe the flickering? Is it on all screens or only the monitor through DisplayLink? Is it linked with you moving stuff to that monitor or even when displaying the desktop it flickers? Do you get an image from Windows? Do you hear the Windows USB connect/disconnect sound? The port USB joue au yoyo. That could explain the 2. When it's slow, would you be able to check the CPU load for DisplayLink Manager / DisplayLink User Agent? We have a known bug on 7.9 M4 (build 7.9.1336.0) we're fixing for 7.9 M5. __________________ Alban Rampon Senior product manager, universal docking stations and accessories "DisplayLink is proud to be a Synaptics brand." Where to download the latest DisplayLink drivers How to clean up a corrupted installation How to report issues to DisplayLink for a speedy resolution

02-04-2016, 12:00 PM	#6
willybob Junior Member Join Date: Sep 2011 Posts: 24	Hi alban, Thanks for trying to help. So, my sytem is setup like this : Asus Notebook U36SD with only one display (Samsung) with dual input. One output is connected to HDMI Second one to UGA-4KDP I get two screens on the same monitor then. Behavior : Everything is installed, including the DL adapter driver. If I disconnect (physically or logically) the DL Adapter, everything works fine, but of course I get nothing on this screen. If I try to extend desktop throught the adapter, flickering starts and keep going even when doing nothing. No sound like the connect/disconnect one) Screen is just blinking for ever (Laptop display and HDMI screen). If I disconnect the HDMI, same thing happens on the laptop screen. Windows still works of course. When it flickers, DisplayLink Manager and User Agent are both using around 5% CPU. When I disconnect output through DL Adapter, it goes back to 0% CPU. Fun enough, everything works fine under the 11102 Insider Build. No trouble. Started since moving to 12451, then 12457. between every move, DL stuff was uninstalled, cleaned properly, update was done then DL stuff was reinstalled. Update : another funny thing : Assuming that 1 is the laptop screen 2 is the HDMI display 3 is the DL display When I try to expand the desktop to monitor 3 through the DL adapter, it flickers. 2 is active but flickers, 1 is active but flickers. When I try to duplicate the desktop from display 2 to display 3 through DL it does not flickr, but 3 stays off. When I try to duplicate the desktop from display 1 to display 3 through DL it does not flickr, but 3 stays off. Last edited by willybob; 02-04-2016 at 01:34 PM.

02-05-2016, 10:42 AM	#7
AlbanRampon Senior Member Join Date: Sep 2015 Location: Cambridge, UK Posts: 1,678	Ok WillyBob. Thank you for all these helpful details! I created a support ticket, once at least some minimal testing is done, I would like to see if our latest software is addressing it. You should receive an email on Monday with a download link, unless we discover a show-stopper over the weekend. My ref: 21659 __________________ Alban Rampon Senior product manager, universal docking stations and accessories "DisplayLink is proud to be a Synaptics brand." Where to download the latest DisplayLink drivers How to clean up a corrupted installation How to report issues to DisplayLink for a speedy resolution

02-05-2016, 10:50 AM	#8
willybob Junior Member Join Date: Sep 2011 Posts: 24	Hi Alban, OK this way. In the meaning time, I reverted to Insider Build 11102 so I can use my DL device properly. If any need, tell me, I can reprocess the last build in minutes for further testing.

02-12-2016, 04:59 PM	#9
willybob Junior Member Join Date: Sep 2011 Posts: 24	Hi all, Replying to myself : Problem solved. Having an Optimus graphic card system (Intel HD 3000 / nVidia GT520M) on my Asus U36SD notebook, figured out that desactivating the nVidia controller solved my issues under Windows Insider Build 14257 (works also for Build 14251). Build 11102 does not have any issue with Optimus. If you have this kind of issues with this kind of setup, it's worth a try.