Hello,

In the logs you included, the computer was fetching the proper driver from Windows Update , the last time before today was on 31st July.
Then yesterday, instead of the normal installation, the wrong driver is selected for import
"Setup Import Driver Package" from the hard drive.

>>> [Setup Import Driver Package - C:\Program Files\DisplayLink Core Software\8.2.2152.0\USBDriver\DisplayLinkUsb.inf]
>>> Section start 2017/08/07 08:59:03.048

Do you get any error when running the cleaner? For instance, may you confirm you specifically run it "Run as Administrator..." even if your user has admin privileges?
Would you have new logs after you ran the cleaner and before you plug the device in?
Then, make sure the folder C:\Program Files\DisplayLink Core Software\ is deleted.
Then, do NOT run any installer. Simply plug in the device. You should NOT see any installation wizard, only the Windows "I found a USB device, let me fetch the driver from WU" message. If you see the DisplayLink installer. Cancel the installation straight away, collect new logs and send them to me.

The driver build installed cannot technically be on Windows Update for Windows 10 Creators Update so it can't fetch it from there.
This means there's something wrong locally. We can do the fixing manually, but that's tedious, hence me trying to let Windows do its job.

Kind regards,
Alban

so here is the file from right after running the cleaner (as an administrator) and then the other from right after plugging in the dock. Still same situation.....works if it plugged in before turning on, but if I unlpug the dock (as if I went to one of our remote sites) and then plug it back in, it give the same blue screen.

Great, thanks for the logs.
We are getting somewhere!
The last logs show you've got the proper driver installed without any DisplayLink kernel driver...
Now we've put aside DisplayLink, let's look at the graphics part!

I don't see any MEMORY.DMP file here.
Either it was too big to be collected or it was not created.
If you've got it on your hard drive, can you put it on a One Drive, Dropbox or any other cloud storage of your choice so I can download it?
If it's not created, you will need to change your options to create a FULL MEMORY dump: https://www.sevenforums.com/tutorial...eate-bsod.html

Kind regards,
Alban

Great, thanks for the logs.
We are getting somewhere!
The last logs show you've got the proper driver installed without any DisplayLink kernel driver...
Now we've put aside DisplayLink, let's look at the graphics part!

I don't see any MEMORY.DMP file here.
Either it was too big to be collected or it was not created.
If you've got it on your hard drive, can you put it on a One Drive, Dropbox or any other cloud storage of your choice so I can download it?
If it's not created, you will need to change your options to create a FULL MEMORY dump: https://www.sevenforums.com/tutorial...eate-bsod.html

Kind regards,
Alban

So the memdump file is 15.9 GB, I have no way to upload that to you unfortunately.....

Maybe you can switch to minidump then?

Otherwise, I would advise using a more recent Intel graphics driver Intel® Graphics Driver for Windows* [15.40] Version: 15.40.36.4703 Date: 6/23/2017.
You would need to use the manual process with the ZIP as described in "How to Manually Install a Graphics Driver in Windows".

Kind regards,
Alban

I'm not at the office today, but will be back tomorrow and will try the mini dump.

I was unable to produce the mini dump, and the drivers you linked also did nothing.....I've re-formatted my laptop and we'll see what happens when I plug into the dock on Monday morning.....I'll let you know

I am surprised. There must be another setting on your computer then.
That's the only purpose of the blue screen: generate the memory dump to be analyzed and find the trace/calling function which tripped. For this, debug symbols are needed and they're not displayed on the blue screen itself...