DisplayLink overloads Windows Kernel

jdelatorre · 07-01-2016, 11:27 AM

Dear Alban,

I attach you our Platform people message, please tell me if it helps anyway, best regards:

“In our scenario, it is not possible to remove any layer from the system, as all of them are required to enforce security in our systems. The protector.sys file is part of Checker solution (from GMV), and it is in charge of monitoring security settings in the computer. It’s the interaction with this file what is causing issues when operating at the same time than your driver, as observed by our technicians. The issue appears when Checker is already installed in the Operating System and the DisplayLink Driver for the USB Lilliput UM-1010 is installed. At that moment, and during the installation, the system goes to BSoD.

If installed in a different order, this is, DisplayLink driver first and Checker software secondly, the BSoD occurs when the system is rebooted with the same Error Code than in the other scenario. We have already tested a lot of other drivers and software, in collaboration with GMV, and it seems it’s the DL driver what is causing the BSoD, and we contacted you so this could be clarified.

07-01-2016, 11:27 AM	#14
jdelatorre Junior Member Join Date: Jun 2016 Posts: 4	Dear Alban, I attach you our Platform people message, please tell me if it helps anyway, best regards: “In our scenario, it is not possible to remove any layer from the system, as all of them are required to enforce security in our systems. The protector.sys file is part of Checker solution (from GMV), and it is in charge of monitoring security settings in the computer. It’s the interaction with this file what is causing issues when operating at the same time than your driver, as observed by our technicians. The issue appears when Checker is already installed in the Operating System and the DisplayLink Driver for the USB Lilliput UM-1010 is installed. At that moment, and during the installation, the system goes to BSoD. If installed in a different order, this is, DisplayLink driver first and Checker software secondly, the BSoD occurs when the system is rebooted with the same Error Code than in the other scenario. We have already tested a lot of other drivers and software, in collaboration with GMV, and it seems it’s the DL driver what is causing the BSoD, and we contacted you so this could be clarified.