View Single Post
Old 05-17-2016, 01:34 PM   #2
AlbanRampon
Senior Member
 
Join Date: Sep 2015
Posts: 1,685
Default

Hello,

Thank you for including the logs, that's helpful.

I am not sure what you did remove when you mention removing the "device and driver".
The NIC name you see is our name before it is rebranded. Because the branding is done by the driver and it seems removed partially, you keep the non branded name.

Are you sure the error comes from the NCM driver and not Windows stack?
I seem to see the error 31 can happen on some network adapters. It's not something I've read before and I handle most of the tickets.
http://www.tomshardware.co.uk/answer...k-adapter.html

I'd recommend starting from a something clean on the network side, and then installing the driver.
On the logs, I see a couple of USB errors, but they seem to recover.

Kind regards,
Alban
__________________
Alban Rampon
Senior product manager, universal docking stations and accessories

Where to download the latest DisplayLink drivers
How to clean up a corrupted installation
How to report issues to DisplayLink for a speedy resolution
AlbanRampon is offline   Reply With Quote