05-08-2018, 03:39 PM | #1 |
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-15-2018, 01:00 PM | #2 | |
Junior Member
Join Date: May 2018
Posts: 2
|
Problems with win10 1803 update
Quote:
I have the exact same problem on a DELL Lat e7250 |
|
05-16-2018, 08:01 AM | #3 |
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-17-2018, 08:53 AM | #4 |
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, 12:17 PM | #5 |
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. |
05-17-2018, 12:25 PM | #6 |
Senior Member
Join Date: Sep 2015
Location: Cambridge, UK
Posts: 1,678
|
Thanks a lot ITWebn,
I recommend you don't waste your time changing the driver for now. 8.5 M1 won't create or prevent the BSoD either. We are lucky there are multiple reports. This will help us get higher priority! Kind regards, Alban
__________________
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, 01:57 PM | #7 |
Junior Member
Join Date: May 2018
Location: Cambridgeshire, UK
Posts: 2
|
https://drive.google.com/open?id=
Minidump file in link, full memory dump came in over 6GB, I hope this helps. Last edited by AlbanRampon; 05-17-2018 at 02:12 PM. Reason: Alban removed the link |
05-17-2018, 02:17 PM | #8 | |
Senior Member
Join Date: Sep 2015
Location: Cambridge, UK
Posts: 1,678
|
Quote:
The crash is from the kernel graphics driver. (IMAGE_NAME: IndirectKmd.sys) But there's someone interfering with it. Cylance Protector filter driver is intercepting the calls (CyProtectDrv64). Would you have the leisure to try and repro without that utility filtering the Windows graphics driver? That should be the first question Microsoft would ask me! Kind regards, Alban 2: kd> kc # Call Site 00 nt!KeBugCheckEx 01 nt!IoSetDevicePropertyData 02 dxgkrnl!DXGMONITOR::_UpdatePnPDeviceProperties 03 dxgkrnl!DXGMONITOR::_OnMonitorDeviceNodeReady 04 dxgkrnl!MonitorNotifyDeviceNodeReady 05 dxgkrnl!DpiPdoHandleQueryId 06 dxgkrnl!DpiPdoDispatchPnp 07 dxgkrnl!DpiDispatchPnp 08 nt!IofCallDriver 09 CyProtectDrv64 0a 0x0
__________________
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, 02:29 PM | #9 |
Senior Member
Join Date: Sep 2015
Location: Cambridge, UK
Posts: 1,678
|
Receive a full memory dump through ticket.
Same driver filtering the OS graphics. 1: kd> kc # Call Site 00 nt!KeBugCheckEx 01 nt!IoSetDevicePropertyData 02 dxgkrnl!DXGMONITOR::_UpdatePnPDeviceProperties 03 dxgkrnl!DXGMONITOR::_OnMonitorDeviceNodeReady 04 dxgkrnl!MonitorNotifyDeviceNodeReady 05 dxgkrnl!DpiPdoHandleQueryId 06 dxgkrnl!DpiPdoDispatchPnp 07 dxgkrnl!DpiDispatchPnp 08 nt!IofCallDriver 09 CyProtectDrv64 0a CyProtectDrv64 0b CyProtectDrv64 0c CyDevFlt64 0d CyDevFlt64 0e nt!IofCallDriver 0f WUDFRd!RdPnpTracker::RdPnpProcessor 10 WUDFRd!RdPnpTracker::RdPnpProcessor 11 WUDFRd!RdPnpTracker::RdPnpProcessor 12 WUDFRd!RdPnpTracker::RdPnpProcessor 13 WUDFRd!RdPnpTracker::RdPnp 14 WUDFRd!RdFdoDevice::RdPnp 15 WUDFRd!RdDevice::ProcessIrp 16 WUDFRd!RdDriver::RdDispatch 17 nt!IofCallDriver 18 dxgkrnl!DpiFdoHandleQueryDeviceRelations 19 dxgkrnl!DpiFdoDispatchPnp 1a dxgkrnl!DpiDispatchPnp 1b nt!IofCallDriver 1c nt!PnpAsynchronousCall 1d nt!PnpSendIrp 1e nt!PnpQueryDeviceRelations 1f nt!PipEnumerateDevice 20 nt!PipProcessDevNodeTree 21 nt!PiProcessReenumeration 22 nt!PnpDeviceActionWorker 23 nt!ExpWorkerThread 24 nt!PspSystemThreadStartup 25 nt!KiStartSystemThread
__________________
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, 05:20 PM | #10 |
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.
|
|
|