Oh... I didn't check both yet. But as it's kernel driver I doubt changing the service status actually removes the calls. I'll check when I'm back on a machine with debug tools.

Kind regards,
Alban

With the info i received here, talking to my Cylance rep and doing some testing, it appears to be Device Control in the Cylance policy.

Device Control doesn't have to be set to bock anything, just enabled. If I disable the Device Control option, apply the updated policy and reboot then the BSoDs stop and the USB adapters work.

I have tested this on 2 out of our 4 machines so far and have been successful.

I've seen a post from them on Spiceworks and offered help.
I will see what Microsoft thinks too as they started looking into it a couple of hours ago.

I have verified that all four models of computer work correctly for me if i remove the Device Control in the CylanceProtect policy.

Thank you.

I'm trying to get a technical contact at Cylance for Microsoft as they have suggestions.
Would you mind asking your account manager? I'm not a Cylance customer and I don't want to weird them out.

Kind regards,
Alban

I passed your info along. He said he would reach out to get you in touch with someone at Cylance.

Hello,

He has, thank you.
Now they have all the data and a bug report from MS with suggestions, I would consider it closed from my end. I don't have visibility of bugs between other parties.

Thank you for taking the time to report this!

Kind regards,
Alban

New 8.5 M1 Driver same error
 

Just tried the new drivers get the same pnp error bsod

Yep, as explained in this thread, the BSoD does not come from DisplayLink driver.