Blue Screen - dlkmd.sys - after updating Nvidia Driver

[SkyBeam]

Originally Posted by AlbanRampon

Hello,
Would you please roll back your Nvidia driver to use a version from 2016 instead of this version from 2017?
I believe there is an altitude problem here. If your BDoDs stop with the 2016 edition of the NVidia drivers, that's an issue we are developing a solution for currently.

I confirm the same issue here on a Lenovo W530 laptop running nVidia GeForce drivers version 378.49. Bluescreen in dlkmd.sys.

This is not the first time DisplayLink does not play well with nVidia drivers. Recently the same issue happened on drivers > version 362 (see here).

Somehow this makes me believe that either nVidia does not care about DisplayLink compatibility or DisplayLink is not based on some official Interfaces and uses unofficial hooking which are subject to change. Perhaps DisplayLink should get in contact with nVidia to provide some stable API which ensures new drivers not to break our installations on every upgrade. At least a bluescreen should be avoided. Even if DisplayLink functionality cannot be assured the system should not crash at startup. I guess the average user would simply not know how to recover their system using safe mode and removing drivers manually from the registry (that's how I recovered now).

And yes, there are good reasons to use the latest graphics driver. On machines where games are run it's a must and on office machines latest drivers ensure best stability and performance.

[AlbanRampon]

Originally Posted by SkyBeam

I confirm the same issue here on a Lenovo W530 laptop running nVidia GeForce drivers version 378.49. Bluescreen in dlkmd.sys.

This is not the first time DisplayLink does not play well with nVidia drivers. Recently the same issue happened on drivers > version 362 (see here).

Yes, it did happen 11 months ago and we addressed it when nVidia was activelu unloading/blocking our driver.
We have a new driver architecture from Windows 10 Anniversary Update onwards where graphics vendors must comply with their new drivers. Perhaps we had tried multiple times to talk to nVidia... Perhaps you will have noticed we did not have the issue with Intel graphics cards.
In the new driver architecture, the kernel mode graphics driver is not from DisplayLink but Microsoft directly and Microsoft can prevent the digital signing of drivers which are not compliant.

Regards,
Alban

[mjd]

I can confirm on my laptop with Nvidia 850M, DisplayLink version 8.1 M0 on 64-bit Windows 7:

• 378.49 - January 24, 2017 - Blue Screen
• 376.33 - December 14, 2016 - okay

[AlbanRampon]

Originally Posted by mjd

I can confirm on my laptop with Nvidia 850M, DisplayLink version 8.1 M0 on 64-bit Windows 7:

• 378.49 - January 24, 2017 - Blue Screen
• 376.33 - December 14, 2016 - okay

Thank you. We believe we have found the root cause.
Changes in this area of the code require full GPU compatibility tests though, as we certainly don't want to fix something to break it for someone else!

If readers are interested, we can look into sharing an 8.2 Development Build to validate on your platform, but after we've done some tests and our confidence level is satisfactory.

Kind regards,
Alban

[crashsuit]

Originally Posted by AlbanRampon

Thank you. We believe we have found the root cause.
Changes in this area of the code require full GPU compatibility tests though, as we certainly don't want to fix something to break it for someone else!

If readers are interested, we can look into sharing an 8.2 Development Build to validate on your platform, but after we've done some tests and our confidence level is satisfactory.

Kind regards,
Alban

I'd be interested in these, if/when they're available. I also got the blue screen after updating my nVidia drivers from the previous version to the latest current version.

Lenovo W541, i7-4910mq, nVidia Quadro K2100M.

[EricBa]

Originally Posted by AlbanRampon

Thank you. We believe we have found the root cause.
Changes in this area of the code require full GPU compatibility tests though, as we certainly don't want to fix something to break it for someone else!

If readers are interested, we can look into sharing an 8.2 Development Build to validate on your platform, but after we've done some tests and our confidence level is satisfactory.

Kind regards,
Alban

Hello Alban,

Thank you for looking into our problem, but even if I understand all your words, I don't really understand the meaning of it (not IT and not English ).

So, what do I have to do to be able to update normally all Nvidia drivers and restart my laptop without the Blue Screen, and without rebooting my Windows 7 Ultimate?

Regards,
Eric

[AlbanRampon]

Hello,

I'll try and be clearer then
Would you please both (and others who want it) send an email to technical_enquiries@displaylink.com with the following?
- Subject line = 8.2 Development Build for 24705
- Link to this forum thread.
- Asking your ticket to be assigned to Alban (that's me).

When engineering has something ready, I can then look for your tickets and send you the new test driver. It should be next week if tests are fine.

Have a nice weekend!
Kind regards,
Alban

[AlbanRampon]

Hello,

I have notified everyone who has created a ticket.
Here are now links to the 8.2 Beta forum I created for the feedback on that version.

8.2 Beta 1 - 8.2.1336 17th February 2017 to get the file with its limitations.
Create a new thread in 8.2 Beta for Windows with your feedback.

Have a nice weekend,
Alban

[Mthatcher]

Hello!

I have a P50 Laptop with a M2000M GPU installed in it and I am affected by the dlkmd.sys BSOD . I am thinking of installing this dev driver. How is the confidence level in this driver looking since you posted this for people to test?

Thanks!
Mitch

[tfkong]

Originally Posted by AlbanRampon

Hello,

I'll try and be clearer then
Would you please both (and others who want it) send an email to technical_enquiries@displaylink.com with the following?
- Subject line = 8.2 Development Build for 24705
- Link to this forum thread.
- Asking your ticket to be assigned to Alban (that's me).

When engineering has something ready, I can then look for your tickets and send you the new test driver. It should be next week if tests are fine.

Have a nice weekend!
Kind regards,
Alban

Hello,

Recently, I had recovered my laptop "Thinkpad W540", and I got the same dlkmd.sys blue screen problem when I connected my LT1421w USB monitor, as I had tried the displaylink drivers downloaded from Lenovo and Windows update.

Has the latest driver from the Displaylink website fixed the problem?

My configurations:
- Win 7 Pro 64-bit SP1
- Nvidia Quadro K1100M (driver version: 391.25)
- Monitor Lenovo LT1421w

Thanks for your support. Happy New Year!