Second display disappears

chashock · 10-18-2009, 11:36 PM

This time I got things to work for a couple of hours, but it ended up in the same result.

Attached is everything from the dump folder. All but one file shows the last activity as 2:42, but one shows 6:28, which is about the time it crashed on me.

I've also attached a couple of screen shots of the Task Manager. As you can see, total CPU usage is reflecting what is in the System Idle Process in the After screen shots, but clearly not the Before.

Let me know what other info I can get you.

chashock · 10-19-2009, 06:47 PM

Martin:

Another update. I plugged in just one of the displays this afternoon to try and get something done, and less than 5 minutes after plugging it in, the display went dark on me and my CPU usage skyrocketed.

I've attached the debug folder (the files updated almost immediately this time) as well as a screenshot.

Thanks!

Martin · 10-19-2009, 11:30 PM

Thanks for the logs. I can see that the usb device is reporting errors, but the logging level is perhaps not high enough to get anything informative. I'm going to get back to you tomorrow with some information on how we can gather more descriptive logs. Unfortunately, this is also an area I'm not too familiar with, so I'll have to raise a bug and keep an eye on it for you.

Martin.

chashock · 10-23-2009, 04:52 PM

Thanks for the update, Martin; I've been away on business so I just saw this. I'd noticed a lot of errors in the logs as well, but none of them really made any sense to me, either, as this isn't something I spend a lot of my time doing.

Let me know if there's anything else I can do on my end to get you more information. I'm really wanting to get back to my four displays.

Thanks!

Martin · 10-27-2009, 05:49 PM

Hi,

Have you had a chance to try the product release available from WU? It seems that I cannot get people to look at it when it's from the RC.

If you are still seeing the problem, merge the attached registry file, which will increase the verbosity of the logging. Once you've done that, reboot and wait until the problem occurs. Then, zip up all the logs from c:\program files\displaylink core software\debug and upload them here.

Thanks,
Martin.

chashock · 10-30-2009, 12:07 AM

I'm hazarding a guess here, but it may not be that people don't want to try it, but that it isn't there.

I've been anxiously awaiting the released driver ever since I saw posts about it being released to WU, and nothing has shown up in WU for me related to DisplayLink (although when I first installed Win7 it immediately found the RC driver).

Also, the reg entry doesn't seem to be attached to the post. Can I download the new driver directly?

chashock · 11-04-2009, 09:52 PM

I don't know if this thread or forum is even being monitored anymore, since the driver is supposedly "production", but the problems are persistent on my machine.

The new driver never showed up in WindowsUpdate OR via the Check for updates option of the DisplayLink Manager, so I downloaded the driver manually and installed.

The CPU problem is not nearly as pronounced in this version of the driver, but it is still there. Instead of reporting ALL of the System Idle Process as active CPU cycles and slowing my machine to a crawl, it only shows about 1/2 of the CPU being utilized, when in reality only about 10% is and the other 90% is SIP. Still extremely strange behavior, and it indicates to me that when the driver fails it is not releasing resources back properly and it hangs in some "shutdown" process or other.

Both displays still disappear after about 10 minutes or so of use. On top of that, it now causes my primary displays running off my nVidia 9300 card to get very fuzzy after the DisplayLinks fail. Very strange behavior.

I'm afraid if this doesn't get resolved soon I may have to dump these in favor of a second video card to get all my displays running. Very disappointing. This device had a lot of promise for many users I support, but this kind of instability just doesn't leave me with a lot of confidence.

Martin, if you're still watching, and want me to try something, let me know. I'm happy to try and continue troubleshooting this with you guys.

10-19-2009, 11:30 PM	#3
Martin Member Join Date: Sep 2009 Posts: 75	Thanks for the logs. I can see that the usb device is reporting errors, but the logging level is perhaps not high enough to get anything informative. I'm going to get back to you tomorrow with some information on how we can gather more descriptive logs. Unfortunately, this is also an area I'm not too familiar with, so I'll have to raise a bug and keep an eye on it for you. Martin.

10-23-2009, 04:52 PM	#4
chashock Junior Member Join Date: Oct 2009 Posts: 11	Thanks for the update, Martin; I've been away on business so I just saw this. I'd noticed a lot of errors in the logs as well, but none of them really made any sense to me, either, as this isn't something I spend a lot of my time doing. Let me know if there's anything else I can do on my end to get you more information. I'm really wanting to get back to my four displays. Thanks!

10-27-2009, 05:49 PM	#5
Martin Member Join Date: Sep 2009 Posts: 75	Hi, Have you had a chance to try the product release available from WU? It seems that I cannot get people to look at it when it's from the RC. If you are still seeing the problem, merge the attached registry file, which will increase the verbosity of the logging. Once you've done that, reboot and wait until the problem occurs. Then, zip up all the logs from c:\program files\displaylink core software\debug and upload them here. Thanks, Martin.

10-30-2009, 12:07 AM	#6
chashock Junior Member Join Date: Oct 2009 Posts: 11	I'm hazarding a guess here, but it may not be that people don't want to try it, but that it isn't there. I've been anxiously awaiting the released driver ever since I saw posts about it being released to WU, and nothing has shown up in WU for me related to DisplayLink (although when I first installed Win7 it immediately found the RC driver). Also, the reg entry doesn't seem to be attached to the post. Can I download the new driver directly?

11-04-2009, 09:52 PM	#7
chashock Junior Member Join Date: Oct 2009 Posts: 11	I don't know if this thread or forum is even being monitored anymore, since the driver is supposedly "production", but the problems are persistent on my machine. The new driver never showed up in WindowsUpdate OR via the Check for updates option of the DisplayLink Manager, so I downloaded the driver manually and installed. The CPU problem is not nearly as pronounced in this version of the driver, but it is still there. Instead of reporting ALL of the System Idle Process as active CPU cycles and slowing my machine to a crawl, it only shows about 1/2 of the CPU being utilized, when in reality only about 10% is and the other 90% is SIP. Still extremely strange behavior, and it indicates to me that when the driver fails it is not releasing resources back properly and it hangs in some "shutdown" process or other. Both displays still disappear after about 10 minutes or so of use. On top of that, it now causes my primary displays running off my nVidia 9300 card to get very fuzzy after the DisplayLinks fail. Very strange behavior. I'm afraid if this doesn't get resolved soon I may have to dump these in favor of a second video card to get all my displays running. Very disappointing. This device had a lot of promise for many users I support, but this kind of instability just doesn't leave me with a lot of confidence. Martin, if you're still watching, and want me to try something, let me know. I'm happy to try and continue troubleshooting this with you guys.