F5F Stay Refreshed Software Operating Systems Processing heavy GPU load with dwm.exe

Processing heavy GPU load with dwm.exe

Processing heavy GPU load with dwm.exe

R
Rami_Silber
Junior Member
Find
42
07-04-2016, 10:50 PM
#1
Laptop: Legion 5i (GTX 1650) The dextop window manager consumes a lot of GPU power (50%-90%). This issue began today and has caused my laptop to slow down. I’m even experiencing frame drops in games. In titles that previously ran at about 80fps, they now drop to around 30fps. Optimus is active but turning it off doesn’t cause problems. As a student, battery life matters to me. Anyone have any solutions for this? Adjusting the priority of dwm.exe didn’t help.
Reply
Reply
R
Rami_Silber
07-04-2016, 10:50 PM #1

Laptop: Legion 5i (GTX 1650) The dextop window manager consumes a lot of GPU power (50%-90%). This issue began today and has caused my laptop to slow down. I’m even experiencing frame drops in games. In titles that previously ran at about 80fps, they now drop to around 30fps. Optimus is active but turning it off doesn’t cause problems. As a student, battery life matters to me. Anyone have any solutions for this? Adjusting the priority of dwm.exe didn’t help.

Reply
Reply
I
IamPiggy
Member
Find
242
07-05-2016, 03:05 AM
#2
The desktop window manager is a program that handles the graphical interface of your computer's operating system, specifically Windows. Review this discussion on the Microsoft Forum thread about high GPU usage with the desktop window manager.
Reply
Reply
I
IamPiggy
07-05-2016, 03:05 AM #2

The desktop window manager is a program that handles the graphical interface of your computer's operating system, specifically Windows. Review this discussion on the Microsoft Forum thread about high GPU usage with the desktop window manager.

Reply
Reply
B
black_energy_
Member
Find
137
07-06-2016, 12:29 AM
#3
It's been nearly three years but no one has found a fix in that discussion.
Reply
Reply
B
black_energy_
07-06-2016, 12:29 AM #3

It's been nearly three years but no one has found a fix in that discussion.

Reply
Reply