04-06-2010, 11:20 AM | #1 |
Junior Member
Join Date: Apr 2010
Location: Portugal, Europe
Posts: 4
|
External monitor freezes
Hi,
First, sorry for my bad english I purchase the toshiba dynadock v10 to link all my external devices to my laptop DELL inspiron, via a single USB cable. All devices (ethernet, mouse, keyboard, external hard-disk) work well, except the TFT samsung (conected via DVI-I to VGA adapter), that after a while of work well, freeze and i have to use the laptop monitor instead. This TFT is working OK, when disconected from the dynadock. I´ve instaled the new 5.2 version and even the beta 5.3 version, but the problem is still existing. Do you have similar problems reported ? what is the solution ? thank´s |
04-07-2010, 11:52 AM | #2 |
Senior Member
Join Date: Feb 2009
Posts: 1,561
|
Hi
This could be caused by errors on the USB bus. Corrupted packets are causing the video on the dock to lock up. Could you try a different USB port or a different USB cable? Thanks Wim |
04-08-2010, 09:15 PM | #3 |
Junior Member
Join Date: Apr 2010
Location: Portugal, Europe
Posts: 4
|
hi,
i try in another USB port, but after a while the monitor freezes again. i run the debug aplication, the zip is in the atach. thanks |
04-09-2010, 07:59 AM | #4 |
Senior Member
Join Date: Feb 2009
Posts: 1,561
|
Hi
Thanks for the logs. They show: 01:04:22.440 DeviceWindow:USB_0117_002780 DeviceRaw USB_0117_002780 WARN DeviceRaw.cpp:133 Connect USB_0117-002780 failed: USB transmit failed This means that there is a communication problem on USB and the software is losing connection with the dock. My guess is there is a hardware fault somewhere in the connection from the USB dock to the PC. I'm pretty sure its not a software issue. Wim |
04-09-2010, 10:52 PM | #5 |
Junior Member
Join Date: Apr 2010
Location: Portugal, Europe
Posts: 4
|
hi,
but only the TFT freezes, all the other devices that are conected via dock are OK. opsss... freezes again... ataching debug again... but i´m typing this on my external keyboard and with my external mouse and ethernet link via dock. thanks |
04-16-2010, 02:34 PM | #6 |
Junior Member
Join Date: Apr 2010
Posts: 4
|
I'm also seeing this issue the 5.3 beta drivers.
My setup is a HP 2710P tablet running Windows 7 x64. When this issue happens (usually on or two times per day) pressing winkey + p and switching from display mode from "Extended" to something else and then switching back brings the displaylink monitor back to life again. I never had this issue with the 5.2 driver. |
04-19-2010, 04:37 PM | #7 |
Junior Member
Join Date: Apr 2010
Location: Portugal, Europe
Posts: 4
|
Hi,
I´m with Windows Vista 64bits.... maybe the problem is on 64 OS ? I´ll try that workaround. Thank´s |
06-14-2010, 06:29 PM | #8 |
Junior Member
Join Date: Feb 2009
Posts: 1
|
Same issue here
I also have this issue. It is a new issue in 5.3, as I have not experienced it before this version. Refreshing the external monitor (either by using the win+p method described above, or by right clicking on my laptop monitor, selecting "screen resolution", then making some change to force a refresh of the external monitor) fixes the problem each time. I experience this issue one to two times per day.
|
08-10-2010, 09:40 PM | #9 |
Junior Member
Join Date: Jul 2010
Posts: 2
|
I have the same issue as well, I am a fan of display link so I purchased another dock thinking my chipset was bad and had the same issue, all other devices work just the video freezes.
|
08-11-2010, 01:52 PM | #10 |
Junior Member
Join Date: Jul 2010
Posts: 4
|
i also have this problem
I'm running a MacBookPro with Win7x64 in BootCamp. My displaylink monitor freezes up at least once a day. I thought i may have had a bad dock, so I purchased a different brand - one that my coworkers are all using - and I still have this problem.
I'm using the 5.4b1 driver with an eVGA UV19+, currently. i see the reports above on the usb drivers... but like everyone else is saying, none of my other USB devices have any problems. it's only the displaylink drivers with the usb video adapter that has a problem. is there any update on this issue? is there a known cause? |
|
|