DisplayLink 7.9 M4 Crashes Windows 7 Pro

GlSRacer · 01-19-2016, 05:02 PM

DisplayLink 7.9 M4 has crashed my Windows 7 Pro SP1 installation twice. The first time was after I tried to update from an older driver version to 7.9 M4. After restart Windows 7 was unrecoverable. I tried all the tools that I normally use professionally and some I found by searching. None were able to recover Windows so I started over with a fresh installation and after installing the 7.9 M4 drivers and restarting Windows failed to start. This time it was able to recover on its own. I had performed a full back up on the new installation prior to install just in case. During recover it seems that windows has removed the driver and associated software but I ran the cleaner tool just in case. I also received a message that 2 of the drivers were unsigned. I am usually able to accept and continue but this wasn't possible for some reason. I checked around and I'm not seeing that others are having this specific issue.

As far as my system goes, I'm running a Lenovo Y700 with AMD FX-8800P and the newest Radeon Crimson driver package. The display device is a Coredy DHD3000 dual head display adapter. I was previously able to use the adapter with the included rev 1 cd (7.9 M2) but experienced screen glitches when using Mozilla software, specifically with Thunderbird Mail client. As mentioned after updating to M4 I experienced a hard crash.

AlbanRampon · 01-20-2016, 04:19 PM

This was handled through a support ticket.
Windows not up to date means the Microsoft certificates to check the signature are not up to date.
The driver even if wrongly recognised unsigned doesn't crash a full Windows install.

See FAQ Error message: Windows requires a digitally signed driver

mhamen · 02-03-2016, 03:20 PM

Sorry I will have to agree with GISRacer. I installed the M4 version which you still have posted to the website yesterday. The computer in question is now in a startup repair loop because it believes dlkmdldr.sys is corrupted. It would probably be helpful to take down the M4 version until you can get this fixed.

ITDan · 02-03-2016, 09:46 PM

I have a laptop now suffering the same fate. Can't even boot into Safe Mode. DLKMDLDR.SYS is the file implicated.

This is a Dell E6540, drivers up to date, Win 7 Enterprise.

AlbanRampon · 02-04-2016, 02:50 PM

To validate Microsoft signature, you must have Microsoft certificate verification up to date. That works for everyone like that. The only reason you go in repair mode with DL is because our graphics drivers are loaded during startup and your other drivers are most likely lower down in the food chain. And your machine is outdated.

DisplayLink did not write the digital signature verification system for Windows.
You are most welcome to flag it to Microsoft, but I can foresee them saying you should keep installing their cumulated security patches for "your comfort and safety". They advised us to do what we did for 7.9 M4.

Having a signature not validating would not completely crash a hard drive. It's a just a file deletion or roll back matter. Microsoft designed that to avoid system corruption and if you don't pass the list of WHQL tests (Win10 is different tests), they don't sign your drivers.

As already commented, for 7.9 M5, we will go against Microsoft recommendation and include our signature again on top of the one of Microsoft. Now Windows 10 TH2 is much more prevalent than the Windows 10 TH1 RTM, I am a bit less concerned about issues on it.

Windows 10 users have asked for 7.9 M4. So if I remove it, they will be unhappy.

The only way to please everyone was that everyone had an up to date machine with all Microsoft patches. Or have a digital signature verification which worked properly out of the box in Windows 10.

ITDan · 02-04-2016, 03:06 PM

I understand your points about Microsoft and ultimately a system that is not fully patched being to blame.

The fact is that when you install a piece of software, with no warnings about compatibility issues or out of date certificates, and without knowing that your Windows install must be fully patched it is the software's fault. How would end users know that they should make sure they are fully patched before proceeding?

We'll agree to disagree.

01-19-2016, 05:02 PM	#1
GlSRacer Junior Member Join Date: Jan 2016 Posts: 1	DisplayLink 7.9 M4 Crashes Windows 7 Pro DisplayLink 7.9 M4 has crashed my Windows 7 Pro SP1 installation twice. The first time was after I tried to update from an older driver version to 7.9 M4. After restart Windows 7 was unrecoverable. I tried all the tools that I normally use professionally and some I found by searching. None were able to recover Windows so I started over with a fresh installation and after installing the 7.9 M4 drivers and restarting Windows failed to start. This time it was able to recover on its own. I had performed a full back up on the new installation prior to install just in case. During recover it seems that windows has removed the driver and associated software but I ran the cleaner tool just in case. I also received a message that 2 of the drivers were unsigned. I am usually able to accept and continue but this wasn't possible for some reason. I checked around and I'm not seeing that others are having this specific issue. As far as my system goes, I'm running a Lenovo Y700 with AMD FX-8800P and the newest Radeon Crimson driver package. The display device is a Coredy DHD3000 dual head display adapter. I was previously able to use the adapter with the included rev 1 cd (7.9 M2) but experienced screen glitches when using Mozilla software, specifically with Thunderbird Mail client. As mentioned after updating to M4 I experienced a hard crash.

01-20-2016, 04:19 PM	#2
AlbanRampon Senior Member Join Date: Sep 2015 Posts: 1,685	This was handled through a support ticket. Windows not up to date means the Microsoft certificates to check the signature are not up to date. The driver even if wrongly recognised unsigned doesn't crash a full Windows install. See FAQ Error message: Windows requires a digitally signed driver __________________ Alban Rampon Senior product manager, universal docking stations and accessories Where to download the latest DisplayLink drivers How to clean up a corrupted installation How to report issues to DisplayLink for a speedy resolution

02-04-2016, 02:50 PM	#5
AlbanRampon Senior Member Join Date: Sep 2015 Posts: 1,685	To validate Microsoft signature, you must have Microsoft certificate verification up to date. That works for everyone like that. The only reason you go in repair mode with DL is because our graphics drivers are loaded during startup and your other drivers are most likely lower down in the food chain. And your machine is outdated. DisplayLink did not write the digital signature verification system for Windows. You are most welcome to flag it to Microsoft, but I can foresee them saying you should keep installing their cumulated security patches for "your comfort and safety". They advised us to do what we did for 7.9 M4. Having a signature not validating would not completely crash a hard drive. It's a just a file deletion or roll back matter. Microsoft designed that to avoid system corruption and if you don't pass the list of WHQL tests (Win10 is different tests), they don't sign your drivers. As already commented, for 7.9 M5, we will go against Microsoft recommendation and include our signature again on top of the one of Microsoft. Now Windows 10 TH2 is much more prevalent than the Windows 10 TH1 RTM, I am a bit less concerned about issues on it. Windows 10 users have asked for 7.9 M4. So if I remove it, they will be unhappy. The only way to please everyone was that everyone had an up to date machine with all Microsoft patches. Or have a digital signature verification which worked properly out of the box in Windows 10. __________________ Alban Rampon Senior product manager, universal docking stations and accessories Where to download the latest DisplayLink drivers How to clean up a corrupted installation How to report issues to DisplayLink for a speedy resolution

02-03-2016, 03:20 PM	#3
mhamen Junior Member Join Date: Feb 2016 Posts: 1	Sorry I will have to agree with GISRacer. I installed the M4 version which you still have posted to the website yesterday. The computer in question is now in a startup repair loop because it believes dlkmdldr.sys is corrupted. It would probably be helpful to take down the M4 version until you can get this fixed.

02-03-2016, 09:46 PM	#4
ITDan Junior Member Join Date: Jun 2013 Posts: 10	I have a laptop now suffering the same fate. Can't even boot into Safe Mode. DLKMDLDR.SYS is the file implicated. This is a Dell E6540, drivers up to date, Win 7 Enterprise.

02-04-2016, 03:06 PM	#6
ITDan Junior Member Join Date: Jun 2013 Posts: 10	I understand your points about Microsoft and ultimately a system that is not fully patched being to blame. The fact is that when you install a piece of software, with no warnings about compatibility issues or out of date certificates, and without knowing that your Windows install must be fully patched it is the software's fault. How would end users know that they should make sure they are fully patched before proceeding? We'll agree to disagree.