Windows 10 v1903, dGPU on graphics intensive app
 

Hello List,

I have been using DisplayLink for a while now.

I just updated Windows 10 to 1903 and now when ever I try and launch any game it crashes. Everything else works.

I have updated the latest DisplayLink Driver to 9.1.1651.0 but this does not fix the issue.

All games DO work when I plug my monitor Directly into my Laptop.

This means that there is a DisplayLink driver problem when playing games under Windows 10 v1903 using HDMI. But could effect all display connections with DisplayLink and Windows 10 v1903.

Any ideas when this will be fixed?

Thanks,
L

Hello Landosa,

Actually, from your test you proved it's a regression in Windows 10 v1903 behaviour.

Microsoft is currently working on that bug.
In the meantime, I'd like to suggest you select the laptop display as "main display" in Windows display settings before launching the game.

Kind regards,
Alban

Is there any news on this? I haven't been able to run OpenGL apps since the 1903 update.

Hello,

The OS fix has been rolled out to Windows 10 Insiders build 18932.
Would you or anyone else be able to feed back on the status for your application(s)?

Kind regards,
Alban

After an upgrade to Windows 10 preview 18936 build, I was able to start Adobe Photoshop CC 2019, which I couldn't before this upgrade due to the bug with the GPU setup.

I think this will resolve your issue also.

Excellent stvlada, thank you for confirming.
What about the performance? I believe you should see it improved compared to previous OS.

Haven't been able to troubleshoot more, but I do experience WUDFHost in combination with Chrome, triggers my CPU fan spinning even just with one page opened in Chrome, while browsing.
I can see that WUDFHost is also using GPU #0 and CPU resources and together with Chrome they ignite my CPU fan.

If I'm not connected with my D3100 docking station, using only Chrome on my laptop, CPU fan is silent and not spinning at all.
So, still some issues with WUDFHost.

Hello Stvlada,
Would it be possible for me to start a private email thread with you?
We have been trying to reproduce what you describe for a while now, unsuccesfully.
We even purchased the same machine as the one you have...
Kind regards,
Alban

Alban, of course! You are more than welcome :)

I'm having an issue with my D3100 and wonder if this is what I am experiencing

Hello,
It is not.
You have created a different thread with a totally different behaviour and it will be handled there rather than mudding this thread.
Regards,
Alban

Good evening,

I am pleased to tell the fix for multi-GPU machines has been approved for deployment to Windows 10 v1903 (19H1).
It is currently tracking to be an optional update starting rolling out on Tuesday 27th August (overall OS patch, not just that) and then pushed to all machines as part of the Tuesday 10th September cumulative patch and newer.

Optional updates are manually installed by going to Settings > Updates & Security > Windows Update, and clicking on "Check for updates".
There is no change to the DisplayLink driver you are currently using.

Kind regards,
Alban

Does that mean that this bug only affects machines with multi-GPU setups like the Nvidia/Intel Optimus system? i.e. is a workaround for the bug to turn off Optimus and run solely on the Nvidia GPU?

The workaround for the bug from this thread is to mark the laptop display as "main display" before starting the application.
Most can't really disable the iGPU.

Hello,

I have heard that the cumulative patch usually distributed on Tuesdays will be distributed from Friday.
We will post when we've seen it.

Kind regards,
Alban

Any word on the 1903 patch?

I clicked check for update and got offered 2019-08 cumulative update KB4512941.

As I posted, the Tuesday update was postponed to Friday. We're Friday and the update is available.
I however don't have more than one GPU on my machine and it's the weekend in Europe where test teams are located so I can't cross-check the update does include the fix as planned, but you can when the update is offered to your country/machine.

I just installed KB4512941, and my PC is still locking up using certain programs in extended screens on multi-monitor mode. I didn't see any mention of a DisplayLink fix in the patch notes for KB4512941.

So I had few rounds of installing Windows Insider Previews on my computer and it worked fine until last update. After that I've lost WiFi option and no network settings at all. However, my internet worked if I'm connected through the TCP cable but that was not an option. Therefore, I had to reinstall Windows 10 yesterday and I've used most recent ISO
Windows 10 1903 b 18362.329

Now I'm experiencing problems not being able to start different apps if my laptop screen is not set as a main display. Usually my laptop screen is "disconnected" and I'm running two external monitors.

We need urgent fix on this as I'm not willing to spend hours reinstalling my Windows again due to bad Insider Preview patches.

EDIT:
Particular issue is with Viber app (viber.com).
My laptop has two GPUs, Intel 530 and nVidia GTX 960. By default most of the apps are handled by Intel 530.
To workaround this I had to do Right click on the app > Run with graphic processor > High-performance nVidia processor.
This way I managed to start Viber app.

Microsoft hasn't resolved this issue fully, so please address it further and one more time. This is really critical.

Any news on a fix for this issue?

It appears to be fixed for me after the latest Windows updates. I had two available for my PC, and now after updating Photoshop is no longer crashing, not giving me a video driver error.

It appears that the fix was not included in the September 10 update.

There was an update available this morning that included the DisplayLink fix. I'm now able to run OpenGL apps again.

Note: I'm on the Windows Insider Slow Ring for updates. I don't know if the update is available outside the Windows Insider program.

Hello,
Each app reported, including Viber, was tested to start properly on both iGPU and dGPU selected.
This suggests more a local problem than a general OS issue.
It would be extremely difficult for me to put a business case justifying that starting Viber on Intel GPU is critical and would need your assistance.
Regards,
Alban