FIX dwm.exe High GPU Usage from Chrome on Windows (2026)

Key takeaways

• Close Chrome and dwm.exe drops instantly. That’s your confirmation Chrome is the source of GPU contention.
• Background tabs submit GPU frames to dwm.exe continuously, even when minimized. Animations run whether you see them or not.
• Suspend background tabs to stop frame submissions at the source. Disable hardware acceleration only if driver updates don’t help.

You open Task Manager to check why your game is dropping frames, and there it is: dwm.exe sitting at 30–60% GPU usage while Chrome is open. Close Chrome and it disappears. dwm.exe is Windows’ display compositor — it handles all window transparency, animations, and the final frame sent to your display. When Chrome background tabs run animations or video with hardware acceleration, they continuously submit GPU frames to dwm.exe for compositing, even when Chrome is minimized behind your game.

Quick Diagnosis

Fix 1: Suspend or Close Background Tabs

Each suspended tab stops submitting GPU frames to dwm.exe entirely.

1. Press Shift + Esc to open Chrome Task Manager.
2. Sort by CPU or Memory to identify active background renderers.
3. Select tabs you are not using and click End Process — they will show a reload prompt when you return.
4. Go to Settings > Performance (chrome://settings/performance) and enable Memory Saver to have Chrome auto-discard inactive tabs.

Fix 2: Disable Chrome Hardware Acceleration

This moves Chrome’s rendering from GPU to CPU, which takes Chrome out of dwm.exe’s compositor queue entirely. Video and WebGL will be less smooth, but it tells you definitively whether the GPU is the bottleneck.

1. Go to Settings > System (chrome://settings/system).
2. Toggle off Use graphics acceleration when available.
3. Click Relaunch.
4. Open Task Manager (Ctrl+Shift+Esc), go to the Performance tab, and select GPU — dwm.exe’s GPU usage should drop immediately.
5. Note: video playback and WebGL will be less smooth. Re-enable once GPU drivers are updated.

Fix 3: Clear Site Cache

If dwm.exe spikes only when a specific site is open, cached media content may be triggering high-frequency redraws.

1. Navigate to the site that causes the spike.
2. Click the lock icon in the address bar.
3. Select Site settings > Clear data.
4. Reload the page and check Task Manager.

Fix 4: Update GPU Drivers

Outdated GPU drivers can have inefficient compositing code that forces dwm.exe to do more work than necessary.

• NVIDIA: Download and install the latest driver from nvidia.com/drivers.
• AMD: Download from amd.com/support.
• Intel: Download from intel.com/downloadcenter.

After installing new drivers, relaunch Chrome with hardware acceleration enabled and recheck dwm.exe GPU usage.

Fix 5: Adjust Windows Visual Effects

Reducing Windows’ own visual effects lowers dwm.exe’s baseline GPU load, leaving more headroom for Chrome.

1. Press Win + R, type sysdm.cpl, and press Enter.
2. Go to the Advanced tab and click Settings under Performance.
3. Select Adjust for best performance to disable all animations, or manually uncheck transparency effects and window animations.

Cutting GPU Load from Background Tabs

Suspending background tabs is the most direct fix for this problem — it stops the GPU frame submissions at the source. SuperchargePerformance automates that:

• Tab suspension via chrome.tabs.discard() terminates renderer processes for inactive tabs. A suspended tab submits zero GPU frames — dwm.exe has nothing to composite for those tabs.
• Ad and tracker blocking at the network level prevents animated ad content from loading. Animated ads are one of the highest-frequency sources of GPU redraws in background tabs.
• Script blocking (free levels 1–2) stops third-party scripts that trigger CSS animations and layout recalculations in background tabs.

If you are just trying to fix the game frame drops, manually closing or suspending video tabs costs nothing and often solves it without any extension.

Technical Background

Chrome’s multi-process architecture uses a dedicated GPU process to manage hardware-accelerated rendering. When a Chrome tab uses hardware acceleration, its renderer process sends draw commands to the Chrome GPU process, which generates GPU textures. These textures are then submitted to dwm.exe (Desktop Window Manager) via DirectX for final compositing onto your display.

The problem is that this pipeline runs for every active tab — including background tabs you cannot see. A tab with a rotating carousel or a video player continuously submits new textures to dwm.exe, even if that tab is behind 10 others. dwm.exe must process all incoming surfaces regardless of whether they are visible.

With 20 background tabs generating continuous texture updates, dwm.exe’s GPU workload scales linearly. Suspending those background tabs via chrome.tabs.discard() terminates their renderer processes, cutting the texture stream to zero for those tabs.

For the macOS equivalent, see fixing WindowServer high CPU on Mac.