Build 10074 and update drivers

ragsdalej · 05-05-2015, 09:38 PM

I've been having an odd problem and was waiting for the latest build to see if that resolved it which it hasn't. I'm not sure if its just the driver vs build issue or if its a combo of my existing drivers. I'm running three monitors on a lenovo W530 with a Nvidia Quadro K1000M. The DisplayLink drivers install fine, the screen even becomes active but it is not recognized in the display settings. It also randomly acts like it has been disconnected and reconnected causing the screens to flicker etc. Any workarounds known or is it a waiting game till the next driver release.

PaulJ · 05-06-2015, 08:18 AM

Hi ragsdalej,

It does sound like an issue we've seen before but not one I would expect to be present now. If you could generate logs with our support tool and attach them here we will have a look.

Thanks,
Paul

bagserker · 05-11-2015, 07:13 PM

I was actually having a similar issue as described by ragsdalej. I ran the support tool and have attached it here. Please advise.

jasonwomack · 05-11-2015, 10:22 PM

Quote:

Originally Posted by bagserker

I was actually having a similar issue as described by ragsdalej. I ran the support tool and have attached it here. Please advise.

Having problems since 10074 as well. In my case the DisplayLinkManager service keeps crashing repeatedly. I've attached a support file.

jasonwomack · 05-12-2015, 05:21 PM

Quote:

Originally Posted by jasonwomack

Having problems since 10074 as well. In my case the DisplayLinkManager service keeps crashing repeatedly. I've attached a support file.

Just tried the Beta 2 update and have the same issue (DisplayLinkManager service crashes repeatedly.) I've uploaded the diagnostic information.

EDIT: I should mention that the net effect of this is my external displays flash and then lose signal, then flash again, then lose signal.

PaulJ · 05-13-2015, 11:55 AM

Hi jasonwomack,

Your issue can be resolved by deleting the following two registry keys:

• HKLM\SYSTEM\CurrentControlSet\Control\GraphicsDriv ers\Configuration
• HKLM\SYSTEM\CurrentControlSet\Control\GraphicsDriv ers\Connectivity

If you could try that and let us know what happens that would be great.

Thanks,
Paul

bagserker · 05-13-2015, 12:17 PM

PaulJ, did you have anything I should try? I tried what you recommended to jasonwomack, but I wasn't sure what to do after deleting those reg keys. Didn't seem to make a difference.

bagserker · 05-13-2015, 12:29 PM

And here's my latest support file...

jasonwomack · 05-13-2015, 03:40 PM

Quote:

Originally Posted by PaulJ

Hi jasonwomack,

Your issue can be resolved by deleting the following two registry keys:

• HKLM\SYSTEM\CurrentControlSet\Control\GraphicsDriv ers\Configuration
• HKLM\SYSTEM\CurrentControlSet\Control\GraphicsDriv ers\Connectivity

If you could try that and let us know what happens that would be great.

Thanks,
Paul

Thanks, that did the trick. Is this something that we should try if, after future builds of Windows 10 are released, we encounter similar problems?

PaulJ · 05-14-2015, 08:16 AM

Hi jasonwomack,

We believed that this was only an issue if you had upgraded from one of our earlier Windows 10 preview builds so you should never have to do this more than once. If you see similar issues and deleting these keys fixes the issue we would like to know as it's possible there is a different issue here. Out of interest can you tell us which versions of DisplayLink software you have been using on this system and after which upgrade this issue occured?

Thanks,
Paul

05-05-2015, 09:38 PM	#1
ragsdalej Junior Member Join Date: May 2015 Posts: 1	Build 10074 and update drivers I've been having an odd problem and was waiting for the latest build to see if that resolved it which it hasn't. I'm not sure if its just the driver vs build issue or if its a combo of my existing drivers. I'm running three monitors on a lenovo W530 with a Nvidia Quadro K1000M. The DisplayLink drivers install fine, the screen even becomes active but it is not recognized in the display settings. It also randomly acts like it has been disconnected and reconnected causing the screens to flicker etc. Any workarounds known or is it a waiting game till the next driver release.

05-06-2015, 08:18 AM	#2
PaulJ Member Join Date: Jul 2010 Posts: 83	Hi ragsdalej, It does sound like an issue we've seen before but not one I would expect to be present now. If you could generate logs with our support tool and attach them here we will have a look. Thanks, Paul

05-13-2015, 11:55 AM	#6
PaulJ Member Join Date: Jul 2010 Posts: 83	Hi jasonwomack, Your issue can be resolved by deleting the following two registry keys: • HKLM\SYSTEM\CurrentControlSet\Control\GraphicsDriv ers\Configuration • HKLM\SYSTEM\CurrentControlSet\Control\GraphicsDriv ers\Connectivity If you could try that and let us know what happens that would be great. Thanks, Paul

05-13-2015, 12:17 PM	#7
bagserker Junior Member Join Date: May 2015 Posts: 12	PaulJ, did you have anything I should try? I tried what you recommended to jasonwomack, but I wasn't sure what to do after deleting those reg keys. Didn't seem to make a difference.

05-14-2015, 08:16 AM	#10
PaulJ Member Join Date: Jul 2010 Posts: 83	Hi jasonwomack, We believed that this was only an issue if you had upgraded from one of our earlier Windows 10 preview builds so you should never have to do this more than once. If you see similar issues and deleting these keys fixes the issue we would like to know as it's possible there is a different issue here. Out of interest can you tell us which versions of DisplayLink software you have been using on this system and after which upgrade this issue occured? Thanks, Paul