Thanks so much for emailing us email the output of the DisplayLink debug tool (which gathers the DisplayLink related log files).
Looking at what was gathered from \Program Files\DisplayLink Core Software\Debug
It appears DisplayLinkManager.exe (the main user mode component of the DisplayLink drivers) has crashed and left behind some .dmp files in this directory.
Looking at DisplayLinkManager.log, it appears to be an assert that’s happening during power transitions. The failed assert is (itr->target) is unexpectedly null at line 189 in file .\DDCManager.cpp for build 5.5.27797.0.
This doesn’t mean anything to us, but could help pinpoint things for the driver developers at DisplayLink.
As you said before, the system is running Vista 64 SP2. AMD Athlon dual-core 5050e. nVidia GeForce 7025/ nForce 630a GPU.
So unfortunately this appears to be a driver bug that would happen with any DisplayLink-based device. And since you’ve tested 5.3, 5.4, and 5.5, with similar problems - it’s probably a situation or series of events at power time related to this AMD/nVidia machine configuration that the DisplayLink drivers never expect to happen. So we need a fix in the drivers.
What we’re going to do is report this problem to DisplayLink, send them your complete set of logs, and follow up on it until we think we have a driver version which is expected to have the problem resolved.
But this requires waiting for new driver versions - and this can take some time, unfortunately.
So we have two choices in the meantime:
* We don’t want you stuck with hardware/driver that isn’t working properly, so returns should be as easy as possible. Visit http://www.amazon.com/gp/css/returns/… and if you’re beyond the period Amazon will handle returns, just email your Amazon order # to email@example.com and we’ll refund directly
* The other choice is to turn off standby/hibernate on this machine so the problem isn’t triggered, until we have the driver fix.
Again, my apologies for this problem and thank you for sticking with us to where we have good evidence of what the underlying problem is.
Either path you take, we totally understand. Just let us know.