Windows 1803 BSOD PNP_Detected_Fatal_Error

[Scandinavica]

Originally Posted by nordiccamel

I have 4 different models of computers that have be updated to Windows 1803. All of them are experiencing the same issues with our DisplayLink USB display adapters.

Surface 4 Pro
Surface 3 Pro
HP EliteBook x360 1030 G2
HP Probook 650 G1

As soon as they finished the 1803 upgrade and rebooted they BSOD'd. The message is PNP_Detected_Fatal_Error. If you unplug the Display Link adapter, the computer boots fine.

The issue can be replicated on all 4 machines.
If you plug in the USB display adapter directly or via a powered USB hub, the computer BSODs again. The Computer will get in a loop of BSOD and reboot until you unplug the Display Adapter. Once unplugged the computer boots and works just fine. If you plug it in again it will BSOD in a few seconds before any of the external screens light up.

No other external items are plugged in to the computers. all available updates have been applied to all machines.

I have tried upgrading the DisplayLink software, currently using v8.5.3365.0. I have ran the DisplayLink install cleaner and then reinstalled the DisplayLink software. Running DisplayLink Windows Support Tool 1.0.0.28 shows no errors.

I have the exact same problem on a DELL Lat e7250

[AlbanRampon]

Hello,

This will need to be addressed by Microsoft as out driver doesn't have the capability to generate BSoDs.
They will need the memory dump to investigate this.

If you go in system advanced settings and do generate full memory dump, then create the issue, you will get a MEMORY.DMP file.
Please compress this file and share it with us via the cloud storage provider of your choice so we can create a bug report to Microsoft.

We have had one report via ticket with the file so I've already got the bug creation listed, but having more files would help.

Kind regards,
Alban

Ref 27809 - PNP_DETECTED_FATAL_ERROR BSOD on RS4 (connection or loop at boot)

[nordiccamel]

I sent in two dumps via email. I also have CylanceProtect installed. I sent in one dump with Cylance running. and one dump after stopping the Cylance services.

[AlbanRampon]

Originally Posted by nordiccamel

I sent in two dumps via email. I also have CylanceProtect installed. I sent in one dump with Cylance running. and one dump after stopping the Cylance services.

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

[nordiccamel]

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.

[AlbanRampon]

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.

[nordiccamel]

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

[Scandinavica]

Just tried the new drivers get the same pnp error bsod

[AlbanRampon]

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