D
DakotaBuell
I started having this issue about 2 weeks ago after I installed a video game. While watching videos, playing games, or having any sort of movement on screen would cause the Desktop Windows Manager GPU usage to jump to about ~35-40% usage on the 3D engine, in my case, on BOTH 1080TIs. with that kind of usage, I am seeing a massive FPS loss in games and even worse, lag on windows desktop when doing day to day tasks. Prior to two weeks ago, the Desktop Windows Manager would have a 1-3% usage across the board.
Through some testing, I discovered that the one of the new games I installed required the Microsoft 2013 Redistributable x64 and x86; I think it was .Net. This seem to cause the issue. I tested the installation on my laptop (my laptop did not have this issue prior) which has a 4k screen and Nvidia GPU and it started to experience the same problem. I believe that there is an incompatibility with the older .Net engine and high dps screens; the Desktop Windows Manger is a sort of fallback probably as a way to maintain compatibility. When the screen are set to 1080p, the Desktop Windows Manger's GPU usage is far less noticeable.
Unfortunately, uninstalling it and the game did not revert the issue though it did cause some weird behavior in the windows desktop. I still have not solved the issue. Somehow I literally at the point where only do one task at a time on my pc. Given that it seem to be caused by one set of redistributables and they are Microsoft's, can something can be done about this for the future? Is there something else I missed? This problem only started in the last two weeks and the only change in that time was the installation of Star Wars Fallen Order and its dependency on 2013 Redistributable.
I am probably going to re-install the OS soon if I cannot find a fix.
Some stuff I have tried:
1. Virus and Malware scans, they came up no hits
2. Re-installed the graphics driver
3. Ensured that the GPUs are NOT in a power saving mode.
4. Lowering the priority of the Windows Desktop Manager in the task manager
5. Lowering screen resolution to 1080p which masted the issue however is not an acceptable solution
Extra info:
OS: Windows 10 Pro, build 1909
CPU: i7 hex-core @ 3.8GHz,
GPU(s): x2 EVGA 1080Ti OC
Screens: x2 Acer Predator x27 (4k @ 144hz)
Continue reading...
Through some testing, I discovered that the one of the new games I installed required the Microsoft 2013 Redistributable x64 and x86; I think it was .Net. This seem to cause the issue. I tested the installation on my laptop (my laptop did not have this issue prior) which has a 4k screen and Nvidia GPU and it started to experience the same problem. I believe that there is an incompatibility with the older .Net engine and high dps screens; the Desktop Windows Manger is a sort of fallback probably as a way to maintain compatibility. When the screen are set to 1080p, the Desktop Windows Manger's GPU usage is far less noticeable.
Unfortunately, uninstalling it and the game did not revert the issue though it did cause some weird behavior in the windows desktop. I still have not solved the issue. Somehow I literally at the point where only do one task at a time on my pc. Given that it seem to be caused by one set of redistributables and they are Microsoft's, can something can be done about this for the future? Is there something else I missed? This problem only started in the last two weeks and the only change in that time was the installation of Star Wars Fallen Order and its dependency on 2013 Redistributable.
I am probably going to re-install the OS soon if I cannot find a fix.
Some stuff I have tried:
1. Virus and Malware scans, they came up no hits
2. Re-installed the graphics driver
3. Ensured that the GPUs are NOT in a power saving mode.
4. Lowering the priority of the Windows Desktop Manager in the task manager
5. Lowering screen resolution to 1080p which masted the issue however is not an acceptable solution
Extra info:
OS: Windows 10 Pro, build 1909
CPU: i7 hex-core @ 3.8GHz,
GPU(s): x2 EVGA 1080Ti OC
Screens: x2 Acer Predator x27 (4k @ 144hz)
Continue reading...