Surface Pro [1796 model] multiple monitors surface dock // d6000 dock issues

[AlbanRampon]

Hello,

They use QT with OpenGL libraries.
It could be the Intel graphics driver OpenGL pass-through issue we've discussed numerous times on this forum or another. Or it could be from these libraries. It might be more the latter as the pass-through issue can usually be worked around by changing the primary display.

Do you see the white area in a Print Screen screenshot of the issue or is the content visible on it?

Kind regards,
Alban

[surfacePro123]

Thanks for the reply.

Not fully sure what you mean but i took a screen shot and its all white I do not see content.

thanks.

[AlbanRampon]

Thank you for the information.
The Print Screen screenshot does not really capture what is being on the screen, but what Windows thinks is there.
What is shown on the Print Screen is taken before the content is handed over to our encoder.
As the content is corrupted on the Print Screen, it is corrupted before DisplayLink driver gets it, so no amount of code change in the DisplayLink driver will be able to recreate the data which is not available.
This leaves 3 possibilities based on what computes the pixels:
1. The application,
2. The GPU driver,
3. The Windows OS.

I don't believe it can be an issue in Windows. I've never heard about that white screen before.
It might be a GPU driver issue, but this would be something new. What Intel graphics driver version are you using? (check in Device Manager in Display Adapters, version is like aa.bb.cc.dd).
It's the first time I hear about white screens, so it might be from the application, or a way the application reacts on another issue.
To proceed further, we would need to test with other machines. For this, the application would be required.
The only thing we now know is that it's not the DisplayLink driver, but that doesn't solve much...

Kind regards,
Alban

[surfacePro123]

thanks again for trying to help

https://imgur.com/qxHmCg5

[AlbanRampon]

Alright, can you try the following driver?
https://downloadcenter.intel.com/dow...Windows-15-60-

You MUST use the ZIP file and go through Device Manager to manually select the driver.
Here is the process:
https://www.intel.com/content/www/us...s-drivers.html

The second number is the branch. The first is the level of graphics supported and the last is the driver version.
The 20 branch you use is newer than the 60 where the OpenGL bug was fixed, but they might have regressed the change by mistake.
If everything works fine on 60, then the issue comes from the graphics driver.
If it still doesn't work on 60, then the most likely candidate would be the application as we have verified the fix on the 60 branch in our labs and with multiple users.

Kind regards,
Alban

[surfacePro123]

Thanks for the help. so its an older driver? is that ok to use? will it cause me other problems?

[AlbanRampon]

The driver branch you are using today did not exist when your computer was manufactured.
It had to be shipped with a previous generation driver.