Log reporting killed my Dynadock

alphadog00 · 11-13-2015, 01:09 PM

I just uploaded logs.... very disturbing morning.

I arrived at my machine to find it off. On booting I had a crash report implicating USB. I opened the display link reporting tool, change logs to verbose and collected logs (Display link HDMI monitor on and extended desktop).

After moving log to another directory, I changed logging level back to info in the tool, and after typing my password, my machine hung. BoD. Unplugging Dynadock had no effect, so reboot.

Now my Displaylink is gone (no display) but Dynadock eithernet works. Changing from HDMI to DVI on monitor and Dyndock, has no effect. Rebooting both, no effect. No display at all from Dynadock now. I guess it could be a corrupt driver... but unsure.

I sent both logs - gmail link to google drive.

Thanks

11-13-2015, 01:09 PM	#1
alphadog00 Junior Member Join Date: Oct 2015 Posts: 18	Log reporting killed my Dynadock I just uploaded logs.... very disturbing morning. I arrived at my machine to find it off. On booting I had a crash report implicating USB. I opened the display link reporting tool, change logs to verbose and collected logs (Display link HDMI monitor on and extended desktop). After moving log to another directory, I changed logging level back to info in the tool, and after typing my password, my machine hung. BoD. Unplugging Dynadock had no effect, so reboot. Now my Displaylink is gone (no display) but Dynadock eithernet works. Changing from HDMI to DVI on monitor and Dyndock, has no effect. Rebooting both, no effect. No display at all from Dynadock now. I guess it could be a corrupt driver... but unsure. I sent both logs - gmail link to google drive. Thanks