STOP Chrome Freezing on Windows 11: 9 Fixes (2026)

Key takeaways

• Chrome freezing on Windows 11 is almost never a Chrome bug. GPU driver conflicts and Efficiency Mode throttling are the two most common causes.
• Press Shift+Esc to open Chrome Task Manager before the window locks. Sort by CPU to find the hung process.
• GPU drivers are the top fix after any Windows 11 update. Update first before trying anything else.

Your Chrome window goes gray. The title bar reads “Not Responding.” The cursor turns into a spinning circle. You cannot click anything, cannot close tabs, and force-quitting means losing everything. This is a freeze, not a crash. Chrome is alive but stuck waiting on something it cannot get.

As of March 2026, the most common trigger is a GPU driver conflict between Chrome 146 and the Windows 11 update released that month. DWM.exe (Desktop Window Manager) competes with Chrome for GPU resources, and when they deadlock, Chrome hangs. Separately, Windows 11’s Efficiency Mode throttles background Chrome processes. If a tab tries to respond while throttled, the internal timeout fires and the whole window locks.

Quick Diagnosis

Match your symptom to the most likely fix before working through all nine:

Fix 1: Check Chrome Task Manager for the Hung Process

Chrome has its own Task Manager that shows individual tab and extension processes. This is the fastest way to identify what is causing the freeze. Open it before Chrome fully locks, while you still can.

1. Press Shift+Esc while Chrome is in focus to open the Chrome Task Manager.
2. Click the CPU column header to sort by CPU usage descending.
3. Look for any process showing unusually high CPU (above 50%). That is your freeze source.
4. Click that process and select End Process to kill only that tab without losing everything else.
5. Also check chrome://crashes in the address bar. If Chrome has been logging hangs silently, you will see them here.

If Chrome is already unresponsive when you try this, open Windows Task Manager (Ctrl+Shift+Esc), find all chrome.exe processes, and identify which has the highest CPU or disk usage. End that specific process. Chrome will show a “Restore” prompt for the killed tab.

Fix 2: Disable Hardware Acceleration

Hardware acceleration lets Chrome use your GPU for rendering. When there is a driver conflict, which is common after Windows 11 updates, this causes freezes during scroll, video playback, or tab switching.

1. Open Chrome and navigate to chrome://settings/system
2. Toggle off Use graphics acceleration when available
3. Click Relaunch to restart Chrome
4. Test Chrome for 30 minutes under normal usage

If freezes stop, your GPU driver has a conflict with Chrome’s rendering pipeline. Proceed to Fix 5 (GPU driver update) and then re-enable hardware acceleration. You want it on for performance once the driver is correct.

Note: with hardware acceleration off, video rendering falls back to CPU. YouTube and Google Meet will use more CPU than normal. This is a diagnostic and temporary fix, not a permanent setting.

Fix 3: Clear GPU Cache and Shader Cache

Chrome compiles GPU shaders and stores them locally to speed up rendering. A corrupt shader cache entry can cause Chrome to hang every time it renders the same element. That is why some freezes happen consistently on specific sites.

1. Close Chrome completely (make sure no chrome.exe processes remain in Task Manager)
2. Press Win+R, type %localappdata%\Google\Chrome\User Data, and press Enter
3. Delete the GPUCache folder
4. Navigate one level up to User Data\Default\ and delete the ShaderCache folder
5. Reopen Chrome. It will rebuild both caches from scratch.

Expect a slightly slower first page load as shaders rebuild. Normal behavior, clears up after one or two navigations.

Alternatively: navigate to chrome://settings/clearBrowserData, switch to the Advanced tab, check Cached images and files, and click Clear data. This is less thorough than manual deletion but requires no file system access.

Fix 4: Disable Windows Efficiency Mode for Chrome

Windows 11 introduced Efficiency Mode to reduce background app power consumption. It works by lowering the CPU thread priority for processes it considers background tasks. The problem: when Chrome needs CPU time to complete a tab render or extension operation while throttled, the operation times out internally. The freeze typically lasts 5–30 seconds and then resolves on its own.

To disable Efficiency Mode specifically for Chrome:

1. Open Windows Task Manager (Ctrl+Shift+Esc)
2. Click the Details tab
3. Right-click any chrome.exe process
4. If you see Efficiency mode: On, click it to toggle off

The toggle applies per-session, not permanently. For a permanent fix, use the Power & sleep settings panel:

1. Open Settings > System > Power & sleep > Additional power settings
2. Select High performance or Balanced (avoid Power saver)
3. If on a laptop, also check Settings > System > Power > Battery saver and ensure it does not activate below 50%.

Fix 5: Update GPU Drivers

Outdated or newly regressed GPU drivers are the single most common cause of Chrome freezing on Windows 11 in 2026. Chrome 146 changed how it communicates with the GPU for hardware-accelerated compositing, and drivers from 2024 or early 2025 often do not handle this correctly.

For NVIDIA GPUs:

1. Open NVIDIA GeForce Experience or visit nvidia.com/drivers
2. Download the latest Game Ready or Studio driver
3. Run the installer and select Custom installation > Clean install
4. Restart Windows after installation completes

For AMD GPUs:

1. Open AMD Software: Adrenalin Edition or visit amd.com/support
2. Check for driver updates and install the latest
3. Restart after installation

For Intel integrated graphics:

1. Open Device Manager (Win+X > Device Manager)
2. Expand Display adapters, right-click your Intel GPU
3. Select Update driver > Search automatically for drivers
4. Or visit intel.com/content/www/us/en/download-center for manual download

After updating, re-enable hardware acceleration (Fix 2 step 2) and test.

Fix 6: Disable Conflicting Extensions

Extensions run in Chrome’s main browser process. A poorly written extension that enters an infinite loop or makes repeated network calls can block Chrome’s event loop, causing the entire window to become unresponsive.

The 30-second test: open a new Incognito window (Ctrl+Shift+N). Extensions are disabled by default in Incognito. Use Chrome normally for a few minutes. If Chrome does not freeze in Incognito, an extension is the cause.

To find the specific extension:

1. Navigate to chrome://extensions/
2. Toggle off all extensions
3. Re-enable them one at a time, testing for a few minutes each
4. When the freeze returns, you have found the culprit
5. Check if an update is available for that extension, or remove it

Extensions that are most likely to cause freezes: VPNs that intercept network requests, screen recorders, and any extension that has not been updated since Chrome 144 or earlier.

Fix 7: Reset Chrome Profile

A corrupt Chrome profile can cause persistent, unexplainable freezes, particularly freezes that happen within seconds of Chrome opening, before any tabs fully load. The profile stores your preferences, cached login sessions, and extension settings locally.

A profile reset preserves your bookmarks and history but removes extensions, saved passwords (export them first), and custom settings.

1. Navigate to chrome://settings/ and click Reset settings in the left sidebar
2. Select Restore settings to their original defaults
3. Click Reset settings to confirm

If you want to start fresh without losing your Google account sync data:

1. Close Chrome
2. Navigate to %localappdata%\Google\Chrome\User Data\
3. Rename the Default folder to Default.old
4. Reopen Chrome. It creates a new Default folder and prompts you to sign in.
5. Sign into your Google account to restore bookmarks and passwords from sync

If Chrome stops freezing with the new profile, the issue was in your profile data, most likely a corrupt extension state file or preferences database.

Fix 8: Add Chrome to Windows Defender Exclusions

Windows Defender’s real-time protection scans file writes as they happen. Chrome writes constantly: cache files, IndexedDB updates, session state, cookies. On systems with mechanical HDDs or slow SSDs, this scanning creates I/O contention: Chrome writes a file, Defender scans it before Chrome can confirm the write, and Chrome’s next operation blocks waiting for the disk to free up. The result looks identical to a Chrome freeze.

Adding Chrome’s data directory to Defender’s exclusion list eliminates this scanning overhead:

1. Open Windows Security from the Start menu
2. Go to Virus & threat protection > Virus & threat protection settings
3. Scroll to Exclusions and click Add or remove exclusions
4. Click Add an exclusion > Folder
5. Add: %localappdata%\Google\Chrome\User Data
6. Click Select Folder

This exclusion removes real-time scanning for Chrome’s own data directory only. It does not affect scanning of downloads or other directories. If you are uncomfortable with this, the alternative is upgrading to a faster SSD. The core issue is scan latency, not a Defender bug.

Fix 9: Reduce Active Tab Count

Each active Chrome tab is a renderer process that consumes 70–180 MB of RAM. On a machine with 8 GB of RAM running Windows 11, 20+ active tabs can exhaust physical memory. Once Chrome starts paging to disk, every tab switch triggers a disk read and the browser freezes for several seconds waiting for the page to load from the page file.

The threshold varies by machine, but if you regularly freeze at high tab counts, this is the cause:

1. Press Shift+Esc inside Chrome to open the Chrome Task Manager
2. Sort by Memory column. Any tab above 500 MB is a candidate for closing.
3. Close tabs you are not actively working with
4. For reference tabs you want to keep accessible, bookmark them or use a read-later service

Chrome’s built-in Memory Saver (at chrome://settings/performance) will auto-discard background tabs to reduce pressure, but it uses heuristics that are sometimes too aggressive and can discard tabs you were about to use.

Preventing Freezes with Automatic Tab Suspension

Most freeze patterns come back to the same root: too many active tabs keeping Chrome’s processes saturated. Every active tab runs JavaScript timers, renders animations, and writes to disk, even the ones behind other tabs. When that load spikes, Chrome can hang.

SuperchargePerformance uses chrome.tabs.discard() to suspend inactive tabs automatically, dropping their RAM footprint to near zero without closing them. Suspended tabs produce no CPU load and no disk writes. Switching back to a suspended tab reloads it, the same as Chrome’s built-in Memory Saver, but with more precise control over which tabs are protected.

14 apps are auto-protected from suspension: Figma, Notion, Slack, and similar tools where losing state would be disruptive. Everything else goes idle automatically after a configurable period. The result is lower steady-state RAM, less disk I/O, and fewer of the memory-pressure hangs described in Fix 9.

If your freezes match Fixes 1, 3, 4, or 5, the problem is environmental (drivers, Windows settings, cache) rather than tab count. Fix those directly first.

If Nothing Works

If Chrome still freezes after all nine fixes:

• Try the Chrome Canary channel (google.com/chrome/canary/). If Canary does not freeze, the issue is in your stable Chrome version and will likely be patched in the next update.
• Check chrome://gpu for any fields showing “Software only, hardware acceleration unavailable.” This confirms a driver-level incompatibility.
• Run sfc /scannow in an elevated Command Prompt. Corrupted Windows system files can cause GPU pipeline failures that Chrome surfaces as freezes.
• Test a new Windows user account. If Chrome runs fine there, the issue is in your user profile at the OS level, not Chrome itself.

If X → use Y: GPU driver just updated and Chrome started freezing → roll back the driver. Freezes only on video sites → disable hardware acceleration permanently and block video preload. Freezes after Chrome auto-updates → check chrome://settings/help to see if a newer stable version is available or downgrade temporarily.