07-29-2015, 10:34 PM | #1 |
Junior Member
Join Date: Jul 2015
Posts: 4
|
Windows 10 RTM + V7.9 = BSOD
My configuration:
Dell DisplayLink D3100 SW: 7.9 OS: Windows 10 RTM PC: Dell Latitude E7450 notebook (with Intel HD 5500 graphics) My issue: System either crashes with BSOD or the NTB display keeps turning off and on every 2 seconds (when it's on there is only a black screen with mouse pointer)...Usually it ends up with BSOD and the Intel graphic adapter is disabled after I restart the machine. It happens even if there is nothing plugged in to the D3100. PS: I've uninstalled all previous tools with the DL cleaner utility. And all drivers are up to date. Any thoughts? Last edited by rocky.intel; 07-29-2015 at 10:43 PM. Reason: config |
07-30-2015, 08:23 AM | #2 |
Senior Member
Join Date: Jan 2012
Posts: 1,523
|
Hi,
Could you attach the output of this tool so we can investigate? http://support.displaylink.com/knowl...rticles/533818 Can you advise if you upgraded from a previously version of Windows and if you upgraded from a previous version of DisplayLink software? Thanks, James |
07-30-2015, 08:44 AM | #3 |
Junior Member
Join Date: Jul 2015
Posts: 4
|
I've upgraded from Windows 8.1, uninstalled the previous software using the cleaner utility (the standard add/remove features didn't work for DL software).
Then I connected the DL. The howto for the support utility say "Ensure the DisplayLink adapter is connected to your PC." Unfortunately, I can't do that because once I connect it it starts restarting my graphic card and it won't recover even if I disconnect the DL. I have to restart the notebook. Anyway, when I clicked "System Compatibility Check" it says everything's fine. I'm attaching the support info. Let me know if I can fetch some more details for you. |
07-30-2015, 12:42 PM | #4 |
Senior Member
Join Date: Jan 2012
Posts: 1,523
|
Hi,
Please try these steps: 1. Disconnect your docking station 2. Uninstall DisplayLink software 3. Run the Cleaner tool from here: http://support.displaylink.com/knowl...rticles/533821 4. Reboot 5. Install 7.9 M0 from here: http://www.displaylink.com/downloads/downloads.php 6. Reconnect your docking station Thanks, James |
07-30-2015, 04:34 PM | #5 |
Junior Member
Join Date: Jul 2015
Posts: 4
|
just tried that. (it doesn't really differ from what I did earlier)
the moment i plug in the DL the display starts turning off and on again and never recovers from that state. after a restart my graphic card is disabled. so i need to enable it in the device mgr again. these error/warning messages from the eventlog could be relevant (from the oldest to the newest): ------------------ A service was installed in the system. Service Name: dlkmdldr Service File Name: \SystemRoot\system32\drivers\dlkmdldr.sys Service Type: kernel mode driver Service Start Type: boot start Service Account: ------------------- A service was installed in the system. Service Name: dlkmd Service File Name: \SystemRoot\system32\drivers\dlkmd.sys Service Type: kernel mode driver Service Start Type: demand start Service Account: ------------------- <-----this is where the blinking starts i suspect Display driver igfx stopped responding and has successfully recovered. ------------------- Display driver igfx stopped responding and has successfully recovered. ------------------- Display driver igfx stopped responding and has successfully recovered. ------------------- The previous system shutdown at 5:52:36 PM on 7/30/2015 was unexpected. ------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------- The driver \Driver\WUDFRd failed to load for the device ACPI\INT3400\2&daba3ff&3. The driver \Driver\WudfRd failed to load for the device ROOT\WPD\0000. The driver \Driver\WUDFRd failed to load for the device USB\VID_0A5C&PID_5804&MI_01\6&c51bbdb&0&0001. The driver \Driver\WUDFRd failed to load for the device USB\VID_0A5C&PID_5804&MI_02\6&c51bbdb&0&0002. ------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xffffe0015e5d4ff8, 0x0000000000000000, 0xfffff8014b0112f8, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 073015-7484-01. thanks for looking into this issue! |
08-02-2015, 10:13 AM | #6 |
Junior Member
Join Date: Jul 2015
Posts: 4
|
It seems to work fine with new Intel HD driver version 10.18.15.4256.
More info here: http://drivers.softpedia.com/blog/in...t-488094.shtml |
|
|