Chrome Not Responding? 5 TESTED Fixes That Work (2026)

Chrome’s “Not Responding” is a Windows OS-level signal: the browser’s main process stopped pumping its message loop for roughly 5 seconds. That grays the entire window. It is not an “Aw, Snap!” crash (one tab’s renderer died, other tabs are fine) and not a tab freeze (one tab locked, the Chrome window still works). Each state has a different cause and a different fix.

Fix 1: End the Hung Process Without Killing the Whole Browser

The fastest recovery (and the one that saves the most tabs) is targeting only the process causing the hang.

While Chrome still accepts Shift+Esc:

1. Press Shift+Esc to open Chrome’s Task Manager.
2. Click the CPU column to sort descending.
3. Look for any process showing sustained high CPU: typically an Extension, GPU Process, or a specific tab.
4. Click that row and select End Process. Chrome kills just that process; everything else stays open.
5. Check chrome://crashes afterward. Chrome logs hang reports here automatically, and the crash IDs can help identify a repeating culprit.

When Chrome is already fully locked:

1. Open Windows Task Manager with Ctrl+Shift+Esc. This bypasses the locked Chrome window entirely.
2. Click More details if in compact view, then the Processes tab.
3. Find the Google Chrome group. Expand it.
4. Look for a chrome.exe entry with spiking CPU or disk I/O (not flat). End that specific process.
5. Do not end all Chrome processes at once. Chrome restores your session on the next launch if some processes survive cleanly.

What you’ll lose: Only the content in the process you ended. Session data (other tabs, form fields you typed in other tabs) survives if Chrome can close gracefully.

Fix 2: Disable Hardware Acceleration If Chrome Locks During GPU Work

If “Not Responding” happens consistently when scrolling, loading heavy pages, or playing video, a GPU driver hang is freezing Chrome’s rendering pipeline. The browser process waits for the GPU response indefinitely until Windows declares it unresponsive.

1. Navigate to chrome://settings/system
2. Toggle off Use graphics acceleration when available
3. Click Relaunch
4. Test Chrome under normal usage: scroll through a video-heavy page, open YouTube, switch tabs rapidly

If the hang stops, the GPU driver is the actual problem. Disabling hardware acceleration is a workaround, not a fix. Proceed to Fix 4 (GPU driver update) and then re-enable acceleration. Running Chrome in software rendering mode permanently increases CPU load on video-heavy sites.

You can also check chrome://gpu for any fields reading “Software only, hardware acceleration unavailable.” That confirms driver-level failures Chrome already detected.

Fix 3: Identify and Remove the Runaway Extension

Extension service workers run in Chrome’s browser process context. A service worker that enters an infinite loop, makes repeated failing network calls, or tries to read a corrupt database blocks the shared event loop. That is what causes the “Not Responding” state more often than any other single factor.

30-second diagnosis: Open a new Incognito window (Ctrl+Shift+N). Extensions are disabled in Incognito by default. Use Chrome normally for a few minutes. If it does not hang in Incognito, an extension is causing the problem.

To find the specific extension:

1. Go to chrome://extensions/
2. Toggle off all extensions
3. Re-enable them one at a time, using Chrome normally for 2–3 minutes between each
4. When the hang returns, the last-enabled extension is the culprit
5. Check chrome://process-internals for service worker status. Entries marked as RUNNING that should be idle may indicate a stuck worker

Extensions most likely to cause main-process hangs: VPNs that intercept all network requests, clipboard managers, screen recorders, and extensions last updated before Chrome 125 (pre-MV3 service worker changes).

Suspended tabs and runaway extensions: If you use tab suspension, suspended tabs cannot run scripts. That means their extension interactions go quiet. But the extension’s own service worker can still misbehave independently of any tab. SuperchargePerformance’s chrome.tabs.discard() suspension eliminates tab-level script pressure on the browser process — but it does so selectively: tabs playing audio (tab.audible), pinned tabs, tabs with unsaved form input (detected via injected script checking for changed form fields), and 25+ auto-protected domains (Gmail, Google Docs/Sheets/Slides/Drive/Calendar, Figma, Notion, Slack, Discord, Teams, Linear, Miro, Canva, Airtable, Asana, Monday, and others) are never suspended, even when background tabs are. That intelligence matters here: a naive suspender that freezes a Figma tab mid-edit is worse than no suspender at all. Perf’s suspension cannot stop an extension service worker that is stuck in its own loop — the right fix for a runaway service worker is removing the extension.

Fix 4: Update GPU Drivers

If Fix 2 stopped the “Not Responding” hangs (or if chrome://gpu shows driver errors), the underlying cause is an outdated or regressed GPU driver conflicting with Chrome 149’s hardware-accelerated compositing pipeline.

NVIDIA:

1. Open NVIDIA GeForce Experience or go to nvidia.com/drivers
2. Download the latest Game Ready Driver
3. Run the installer, choose Custom installation, check Perform a clean installation
4. Restart Windows

AMD:

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

Intel integrated graphics:

1. Open Device Manager (Win+X)
2. Expand Display adapters, right-click your Intel GPU, select Update driver
3. Or download directly from intel.com/download-center

After the driver update, go back to chrome://settings/system and re-enable hardware acceleration. Then restart Chrome and test.

Fix 5: Reset the Chrome Profile If Nothing Else Works

A corrupt profile database — specifically the Preferences file or IndexedDB entries — can cause Chrome to hang on startup or within seconds of opening. This is rare but produces hangs that bypass all other fixes.

Soft reset (preserves most data):

1. Go to chrome://settings/ → Reset settings in the left panel
2. Select Restore settings to their original defaults
3. Click Reset settings to confirm
4. Extensions, shortcuts, and some preferences are removed; bookmarks and history stay

Fresh profile (most thorough):

1. Close Chrome completely (check Windows Task Manager that no chrome.exe processes remain)
2. Press Win+R, type %localappdata%\Google\Chrome\User Data, press Enter
3. Rename the Default folder to Default.old
4. Reopen Chrome. It creates a new Default folder and prompts for Google account sign-in
5. Sign in to restore bookmarks and passwords from Google Sync

If Chrome stops hanging with the new profile, something in your previous profile data was corrupt. The Default.old folder stays intact so you can copy specific files back (like your bookmarks, at Default.old\Bookmarks) if needed.

Why Chrome Stops Responding (Not the Same as Aw Snap)

Chrome runs four distinct process types. Understanding which one is stuck tells you where to look:

“Not Responding” always means the browser process stopped. The three most common triggers:

1. Runaway extension service worker — a service worker loops or blocks, starving the browser’s event queue
2. GPU driver hang — the GPU process stops responding; the browser process waits and Windows notices first
3. Synchronous I/O block — the browser tries to read/write a profile file (Preferences, IndexedDB) and the disk blocks the main thread

The third case is why adding Chrome’s data directory to Windows Defender exclusions sometimes resolves it. Real-time scanning can hold file locks that Chrome’s main thread blocks waiting on. Full details in fixing Chrome freezing on Windows 11.

“Aw, Snap!” follows a completely different path: a renderer process (one tab) crashes or gets killed by the OS due to memory pressure, and Chrome shows the error page. Other tabs are unaffected. If you’re seeing “Aw, Snap!” rather than a gray dimmed window, see fixing Aw, Snap crashes instead. For high overall memory consumption that leads to both types of hangs, see fixing Chrome high memory usage.

When Chrome Won’t Respond Despite Fixes

If all five fixes fail to prevent the hang, these escalation paths cover the edge cases:

Check for Windows system file corruption: Run sfc /scannow in an elevated Command Prompt. Corrupted Windows system DLLs can produce GPU pipeline failures that surface as Chrome hangs. SFC repairs them without reinstalling Windows.

Test a new Windows user account: Create a temporary Windows user (Settings → Accounts → Family & other users → Add someone else). Sign in there and open Chrome. If it does not hang, the issue is in your Windows user profile, not Chrome itself. A Windows profile repair or migration is the fix.

Try Chrome Canary: Download from google.com/chrome/canary. Canary runs as a separate browser and does not affect your stable Chrome installation. If Canary does not hang, a bug in the current stable build will be fixed in an upcoming update.

Copy your profile before a full reinstall: Before uninstalling Chrome, copy %localappdata%\Google\Chrome\User Data\Default\Bookmarks and Login Data somewhere safe. A clean Chrome reinstall deletes the entire User Data folder and these files will be gone otherwise.

If X → do Y:

• Hangs always happen at the same site → Fix 3 (disable extensions first, then test site in isolation)
• Hangs started right after a Windows Update → Fix 4 (driver regression is the #1 cause)
• Hang lasts 5–30 seconds then resolves on its own → not a true Not Responding; likely Windows Efficiency Mode throttling, see Chrome freezing on Windows 11
• Chrome hangs within 10 seconds of opening, before any tabs load → Fix 5 (corrupt profile)
• Chrome hangs only during video or scroll-heavy pages → Fix 2, then Fix 4