MUX switch randomly failing

BartoszCichecki / LenovoLegionToolkit

Lightweight Lenovo Vantage and Hotkeys replacement for Lenovo Legion laptops.

GNU General Public License v3.0

4.53k stars 219 forks source link

MUX switch randomly failing #68

Closed ARYN-27 closed 2 years ago

ARYN-27 commented 2 years ago

The MUX switch randomly fails and sometimes refused to switch the display over to dGPU. Before coming to the conclusion, I tried

DDU the graphics driver
Performed a clean graphic driver installation
Installed Nvidia Driver 496.13 [Known to not mess up MUX]
Install Nvidia Driver provided by Lenovo [Nvidia Driver 472.56]

But when I turned off LenovoLegionToolkit and switched to Vantage, the MUX worked properly. So I tried again with LenovoLegionToolkit and the MUX activates and fails to switch to iGPU. Had to reset the graphics card with [Alt+Crtl+Shift+b].

Problem started after updating to LenovoLegionToolkit version 1.6.2.

log_2022_01_03_14_51_21.txt

BartoszCichecki commented 2 years ago

When you say it is randomly failing you mean that dGPU does not activate when you start a game for example? Or the screen goes black or what exactly? Is the Toolkit in the foreground or in tray? And when you says it fails to switch to iGPU only, what processes are listed by nVidia driver? (You can enable optimus indicator in tray from nVidia Control Panel).

I understand we are talking about Optimus not MUX switch.

ARYN-27 commented 2 years ago

I am asking regarding the MUX switch.

When you say it is randomly failing you mean that dGPU does not activate when you start a game for example?
- Yeah, the game usually triggers the MUX to use dGPU as a display driver. If it doesn't it sends the signal through the iGPU for display.

BartoszCichecki commented 2 years ago

Ok, so your laptop has Advanced Optimus right?

ARYN-27 commented 2 years ago

Ok, so your laptop has Advanced Optimus right?

I think so. As per my understanding, MUX and Advanced Optimus are different things; but I figured out what was causing the whole issue. It was "ColorPicker.exe" from Microsoft PowerToys that was causing the issue. Once I turned of the ColorPicker module, the issue went away.