If you open Task Manager and see dwm.exe chewing through 30, 50, or even 80 percent of your GPU while you’re doing nothing, something is clearly off. dwm.exe is the Desktop Window Manager — the Windows component that draws every window, animation, and transparency effect on your screen. A little GPU usage is normal, but sustained high usage means it’s being forced to work far harder than it should, and you’ll feel it as stuttering animations, laggy window dragging, and a laptop that runs hot and loud for no apparent reason.

This problem comes up constantly in tech forums because the symptom is so visible and the cause is rarely obvious. The Desktop Window Manager doesn’t misbehave on its own; something in the graphics pipeline is pushing it. That could be a buggy driver, an app with broken hardware acceleration, mismatched multi-monitor settings, or even a Windows update that changed how the GPU scheduler works. The fixes below go from the quick checks that solve most cases to the deeper repairs for stubborn ones.

Before you start, note your GPU model and driver version (Task Manager’s Performance tab shows both). You’ll want that information if the driver turns out to be the culprit, and it’s useful context for everything that follows.

Why this happens

  • Buggy or outdated graphics drivers: A bad driver release can make the Desktop Window Manager render inefficiently, causing GPU spikes that persist even on an idle desktop.
  • Conflicting hardware-accelerated GPU scheduling: The HAGS feature changes how the GPU scheduler works, and on some driver and hardware combinations it causes dwm.exe to use far more GPU than normal.
  • Mismatched multi-monitor refresh rates: Running one monitor at 60Hz and another at 144Hz forces the compositor to juggle different frame timings, which can inflate dwm.exe GPU usage significantly.
  • Apps with broken hardware acceleration: A browser tab, Discord overlay, or video player with malfunctioning GPU acceleration can force constant full-screen redraws through the window manager.
  • Corrupted visual effects settings: Damaged transparency or animation settings can put the compositor into a state where it re-renders far more than necessary.
  • Windows update changed GPU behavior: Feature updates sometimes reset graphics settings or introduce driver conflicts that manifest as dwm.exe GPU spikes.
  • Wallpaper slideshow or animated backgrounds: Rapidly changing backgrounds, animated wallpapers, and widgets that refresh constantly all add sustained compositor workload.
  • Second GPU or hybrid graphics conflict: On laptops with both integrated and discrete graphics, the wrong GPU handling the desktop composition can cause abnormal usage patterns.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Identify what’s driving the GPU usage

Start by confirming the numbers and finding patterns. Open Task Manager, go to the Performance tab, select your GPU, and watch the usage graph. Then check the Processes tab sorted by GPU to confirm dwm.exe is actually the top consumer.

  1. Open Task Manager (Ctrl + Shift + Esc) and go to Performance > GPU.
  2. Watch the graph for 30 seconds while doing nothing — note the baseline.
  3. Switch to the Processes tab, sort by the GPU column, and confirm dwm.exe is the main consumer.
  4. Close all applications and check again. If dwm.exe drops to near zero, reopen apps one by one to find the trigger.

If a specific app causes the spike, that app’s hardware acceleration is the real problem — jump to Fix 5. If dwm.exe stays high with everything closed, keep going.

Fix 2: Update or roll back your graphics driver

Drivers are the number one cause of dwm.exe GPU issues. A fresh install of the latest stable driver fixes most cases, but if the problem started right after a driver update, rolling back is the faster fix.

  1. Check your current driver version in Task Manager’s Performance > GPU view.
  2. If the problem is new, open Device Manager, expand Display adapters, right-click your GPU, and choose Properties > Driver > Roll Back Driver.
  3. Otherwise, download the latest driver from your GPU maker: use the Intel driver detection tool for Intel graphics, NVIDIA’s driver page , or AMD’s driver download page .
  4. During installation, choose the clean install option if offered, which removes old driver files that might be conflicting.
  5. Restart and check dwm.exe GPU usage again.

Fix 3: Toggle hardware-accelerated GPU scheduling

Hardware-accelerated GPU scheduling (HAGS) offloads scheduling work to the GPU. On some systems it helps; on others it’s the direct cause of dwm.exe spikes. Since it cuts both ways, the test is simple: flip it and observe.

  1. Open Settings > System > Display > Graphics.
  2. Click Change default graphics settings.
  3. Toggle Hardware-accelerated GPU scheduling to the opposite of its current state.
  4. Restart your laptop — this setting requires a reboot.
  5. Monitor dwm.exe GPU usage for a few minutes. Keep whichever setting gives lower usage.

For more on this feature, see our guide on how to enable hardware-accelerated GPU scheduling in Windows 11 .

Fix 4: Fix multi-monitor refresh rate mismatches

If you use an external monitor, mismatched refresh rates are a classic dwm.exe GPU trigger. The compositor has to synchronize frames across displays running at different rates, and that overhead shows up directly in dwm.exe.

  1. Open Settings > System > Display > Advanced display.
  2. Check the refresh rate of each display.
  3. If they differ (for example, 60Hz laptop panel and 144Hz external monitor), try setting both to the same rate — or at least to rates that divide evenly.
  4. Disconnect the external monitor temporarily to confirm it’s the cause.

Fix 5: Disable hardware acceleration in the offending app

When one application drives the compositor crazy, its GPU acceleration is usually broken. Browsers, chat apps, and video players are the usual suspects.

  1. In your browser, go to Settings and turn off Use hardware acceleration when available (Chrome: Settings > System; Edge: Settings > System and performance).
  2. In Discord, go to User Settings > Advanced and disable Hardware Acceleration.
  3. Restart the app and check whether dwm.exe GPU usage drops.
  4. If it does, leave acceleration off for that app or update the app to a version with fixed acceleration.

This trade-off costs the app a little rendering speed but can eliminate massive compositor overhead. Related reading: what to do if Chrome uses high CPU on Windows 11 .

Fix 6: Reset visual effects and personalization

Damaged transparency settings or an animated background can keep the compositor working overtime. Resetting these to simple values removes that load.

  1. Go to Settings > Personalization > Background and set a static picture instead of a slideshow.
  2. Go to Settings > Accessibility > Visual effects and turn off Transparency effects and Animation effects temporarily.
  3. If dwm.exe calms down, re-enable effects one at a time to find the culprit.
  4. Our guide on how to disable transparency effects in Windows 11 walks through the full set of options.

Fix 7: Run system file checks and reset the graphics stack

If nothing else worked, corrupted system files or a damaged graphics stack may be at fault. These built-in tools repair Windows components without touching your files.

  1. Open Command Prompt as administrator (search “cmd”, right-click, Run as administrator).
  2. Run sfc /scannow and wait for it to complete, then restart.
  3. If problems persist, run DISM /Online /Cleanup-Image /RestoreHealth and restart again.
  4. As a last resort, use Settings > System > Recovery > Reset this PC with the “Keep my files” option.

Microsoft’s Windows support documentation has additional display troubleshooting steps if you need them.

Closing

High dwm.exe GPU usage looks alarming but is almost always a software problem with a software fix — usually a driver update, a HAGS toggle, or one misbehaving app. Work through the fixes in order, testing after each change, and you’ll find the culprit without reinstalling Windows or replacing hardware.

Frequently asked questions

Is dwm.exe a virus?
No. dwm.exe is the Desktop Window Manager, a core Windows process responsible for drawing windows, transparency, and visual effects on your screen. It is supposed to be running. Malware sometimes disguises itself with similar names, so check that the process is located in C:\Windows\System32 — if it is, it’s the legitimate Windows component.
Why does dwm.exe suddenly use so much GPU?
The most common triggers are a buggy graphics driver update, a misbehaving application forcing constant screen redraws, a second monitor running at a mismatched refresh rate, or hardware-accelerated GPU scheduling conflicts. High GPU usage from dwm.exe is almost always a driver or configuration problem, not a hardware failure.
Can I just end the dwm.exe process?
You can try, but Windows will restart it immediately because it’s essential. Ending it won’t fix the underlying cause anyway. The right approach is to identify what’s driving the GPU usage — usually the graphics driver or a specific app — and fix that instead of fighting the process itself.
How much GPU should dwm.exe normally use?
On an idle desktop, dwm.exe should sit between 0 and 5 percent GPU usage, occasionally spiking when you move windows or trigger animations. If it constantly sits above 20-30 percent while you’re doing nothing, something is wrong and worth investigating with the steps below.