there is a problem with laptops which have Intel CPU + GTX 1050/1050Ti/1060/1070. The problem is, whenever you try to do some action on the OS, discrete GPU is triggered and it causes a 0.5s freeze.
Some actions, which cause the dGPU to wake up and lock up the whole system for about 0,5 seconds are:
- Right click on desktop
- Left click on battery-icon in task-bar
- Opening Chrome-browser
- Opening Windows Image Viewer (app + classic Foto viewer)
- Opening system control panel
- Provocation any animation on task bar (e.g. thumbnail-preview, ...)
- Loading a new tab in Firefox
Here is a video demonstrating Display Setting Freeze:
Another video showing dGPU switch on a lot of simple tasks:
We have tried updating every software possible, but no luck.
- Intel driver
- NVIDIA driver
- Chipset driver
The problem can be found on all laptop brands: ASUS, Acer, Clevo, Dell, Gigabyte, HP, Lenovo, MSI, Razer.
The problem can be solved by either disabling Intel GPU, which forces the system to always work with NVIDIA, or disabling NVIDIA GPU. Both of them is not an option though, as if you disable Intel, not only you will drain the battery faster, but also some games will stop working. If you disable NVIDIA, then what is the point of buying a laptop with a discrete GPU?
There is a also a workaround: configuring TrayPwrD3 to always work with NVIDIA in the backgound. This keeps the NVIDIA GPU alive but also drains battery faster. And there is no poaint in that as it renders Optimus useless!
So, manufacturers have to come up with a fix.
Workaround for Right Click Freeze
Go to regedit and remove those two entries:
Restart and voila! You don't have a freeze on right click anymore.
I believe we have root caused the issue and are testing various potential fixes, one looking promising so far. This happens often though in fixing bugs, we'll attempt to check in and hopefully it won't cause other issues or break when combined with other code fixes. It is a step in the right direction though and I thought I'd share progress. If all goes well, we could be looking at a fix in our March/April driver depending on any complications and perhaps a Beta if I can get one out sooner. I'll keep the updates coming as they're available.
Message was edited by: Recep Baltaş