Windows 1803 BSOD PNP_Detected_Fatal_Error

nordiccamel · 05-08-2018, 03:39 PM

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.

Scandinavica · 05-15-2018, 01:00 PM

Quote:

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 · 05-16-2018, 08:01 AM

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 · 05-17-2018, 05:20 PM

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 · 05-17-2018, 06:22 PM

Quote:

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 · 05-17-2018, 07:17 PM

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.

Scandinavica · 05-25-2018, 07:01 AM

Just tried the new drivers get the same pnp error bsod

AlbanRampon · 05-25-2018, 07:19 AM

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

PavelN · 05-17-2018, 08:53 AM

Hello,
I have 4 notebooks and after the latest Windows 10 update, they are not able to work when connected to the Toshiba Dynadock. When I disconnect the dynadock the notebooks work without problems. I tried to install latest "8.5 M0 17 Apr 2018" software and drivers but it still does not work. I tried completely uninstall the display link software then connect the Dynadock. When there is no display link software (drivers) installed notebooks work. But when I install display link software and windows starts to detect and install drivers it falls down to the blue screen with the error "PNP detected fatal error." Is there any solution? Thank you for your help

Pavel N.

ITNewb · 05-17-2018, 12:17 PM

Hi
I'm having the same BSOD, PNP error started this morning, Preparing a full memory .dmp file now after I had made sure I was running the latest 8.5 MO update, and the issue was still there.

I did, it is.

05-08-2018, 03:39 PM	#1
nordiccamel Junior Member Join Date: May 2018 Posts: 5	Windows 1803 BSOD PNP_Detected_Fatal_Error 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.

05-16-2018, 08:01 AM	#3
AlbanRampon Senior Member Join Date: Sep 2015 Location: Cambridge, UK Posts: 1,678	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) __________________ Alban Rampon Senior product manager, universal docking stations and accessories "DisplayLink is proud to be a Synaptics brand." Where to download the latest DisplayLink drivers How to clean up a corrupted installation How to report issues to DisplayLink for a speedy resolution

05-25-2018, 07:01 AM	#7
Scandinavica Junior Member Join Date: May 2018 Posts: 2	New 8.5 M1 Driver same error Just tried the new drivers get the same pnp error bsod

05-25-2018, 07:19 AM	#8
AlbanRampon Senior Member Join Date: Sep 2015 Location: Cambridge, UK Posts: 1,678	Yep, as explained in this thread, the BSoD does not come from DisplayLink driver. __________________ Alban Rampon Senior product manager, universal docking stations and accessories "DisplayLink is proud to be a Synaptics brand." Where to download the latest DisplayLink drivers How to clean up a corrupted installation How to report issues to DisplayLink for a speedy resolution

05-17-2018, 08:53 AM	#9
PavelN Junior Member Join Date: May 2018 Posts: 1	Blue screen Hello, I have 4 notebooks and after the latest Windows 10 update, they are not able to work when connected to the Toshiba Dynadock. When I disconnect the dynadock the notebooks work without problems. I tried to install latest "8.5 M0 17 Apr 2018" software and drivers but it still does not work. I tried completely uninstall the display link software then connect the Dynadock. When there is no display link software (drivers) installed notebooks work. But when I install display link software and windows starts to detect and install drivers it falls down to the blue screen with the error "PNP detected fatal error." Is there any solution? Thank you for your help Pavel N.

05-17-2018, 05:20 PM	#4
nordiccamel Junior Member Join Date: May 2018 Posts: 5	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.

05-17-2018, 07:17 PM	#6
nordiccamel Junior Member Join Date: May 2018 Posts: 5	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.

05-17-2018, 12:17 PM	#10
ITNewb Junior Member Join Date: May 2018 Location: Cambridgeshire, UK Posts: 2	Same Here - confirmed on two different docks. Hi I'm having the same BSOD, PNP error started this morning, Preparing a full memory .dmp file now after I had made sure I was running the latest 8.5 MO update, and the issue was still there. I did, it is.