Chrome is the world’s most-used browser, but even a well-maintained install can crash without warning — tabs disappear mid-session, you see the “Aw, Snap!” error page, or the whole browser closes with no explanation. When Chrome keeps crashing, the cause is almost always one of a small set of known problems: a rogue extension, a corrupted cache, a GPU driver conflict, or simply an outdated version.
The six fixes below are ranked easiest-first and each takes one to five minutes. Most users get Chrome stable again after the first two steps.
Quick Answer
Disable all Chrome extensions at chrome://extensions, then re-enable them one at a time to find the one causing crashes. If that doesn’t help, clear the cache via Settings → Privacy and security → Clear browsing data (set to All time) and update Chrome at Menu → Help → About Google Chrome. These two steps resolve most crashes.
Fix 1: Disable Extensions One at a Time
Extensions are the most common Chrome crash trigger. A single outdated or poorly coded add-on can bring down the entire browser, including tabs it isn’t running on.
- Type
chrome://extensionsin the address bar and press Enter. - Toggle all extensions off using the blue switches.
- Restart Chrome. If it’s stable, re-enable extensions one at a time — restarting after each — until the crash returns.
- Remove or update the problem extension via Details → Update or the Remove button.
Pro tip: Extensions update silently in the background. If crashes started recently, check which add-on updated last — it’s usually the culprit.
Fix 2: Clear Chrome’s Cache and Cookies
A corrupted cache file can cause Chrome to crash on specific sites or after a few minutes of browsing. This fix takes under a minute.
- Press Ctrl + Shift + Delete (Windows) or Cmd + Shift + Delete (Mac).
- Set Time range to All time.
- Check Cached images and files and Cookies and other site data.
- Click Clear data, then restart Chrome.
Fix 3: Update Chrome to the Latest Version
Chrome updates itself in the background, but the update only applies after a full restart — so many users run outdated builds without realising it. An unpatched security or stability bug can cause repeated crashes.
- Click the three-dot menu (⋮) in the top-right corner.
- Go to Help → About Google Chrome.
- Chrome checks for updates automatically on this screen. Install any available update.
- Click Relaunch when prompted.
Troubleshooting tip: If the update button is greyed out, download the latest installer from Google’s official Chrome support page and run it over your existing installation — this forces a clean update without wiping your profile.
Fix 4: Disable Hardware Acceleration
Hardware acceleration offloads page rendering to your GPU, which is faster on most systems — but it can conflict with certain GPU drivers, especially after a driver update. Crashes during video playback or while scrolling image-heavy pages are a strong signal this is the cause.
- Open Chrome’s menu (⋮) and click Settings.
- Search for “hardware acceleration” in the settings search bar.
- Toggle Use graphics acceleration when available to Off.
- Click Relaunch.
The trade-off is slightly slower rendering. If this fixes the crashes, update your GPU drivers and then consider re-enabling the setting.
Fix 5: Reset Chrome Flags to Default
Chrome’s experimental features page lets you enable beta features, but these can break after a Chrome version bump. If you (or an extension) ever touched chrome://flags, a reset is worth trying.
- Type
chrome://flagsin the address bar. - Click Reset all at the top of the page.
- Click Relaunch.
Your bookmarks, passwords, and extensions are not affected by this reset — only experimental feature toggles are cleared.
Fix 6: Reset Chrome Settings or Reinstall
If none of the above works, Chrome’s internal settings or profile data may be corrupted. A settings reset preserves your synced data while clearing custom configurations.
- Go to Settings → Reset settings → Restore settings to their original defaults.
- Click Reset settings to confirm.
- If crashes continue, uninstall Chrome via Control Panel → Programs (Windows) or drag it to Trash (Mac), then download and reinstall a fresh copy.
If you’re signed in to your Google account, bookmarks and passwords sync back automatically after reinstalling. On Windows, corrupted profile data can survive a standard reinstall — if crashes persist after reinstalling, also delete C:\Users\YourName\AppData\Local\Google\Chrome\User Data before running the installer again. For browser memory issues alongside crashes, see Stop Google Chrome From Eating Your RAM: 7 Fixes That Actually Help.
Which Fix Fits Your Situation?
| Crash Pattern | Most Likely Cause | Best First Fix |
|---|---|---|
| Crashes on one specific site | Corrupted cache | Fix 2: Clear cache |
| Crashes immediately on launch | Extension conflict | Fix 1: Disable extensions |
| Crashes after a GPU driver update | Hardware acceleration conflict | Fix 4: Disable GPU acceleration |
| “Aw, Snap!” on all pages | Outdated Chrome version | Fix 3: Update Chrome |
| Crashes after a Chrome update | Experimental flag conflict | Fix 5: Reset flags |
Common Mistakes to Avoid
- Clearing only browsing history, not cache — History and cached files are separate. Always tick Cached images and files when troubleshooting crashes; clearing history alone does nothing for this problem.
- Skipping the Relaunch prompt — Updates and settings changes don’t apply until Chrome fully restarts. Clicking away from the prompt means the fix hasn’t taken effect yet.
- Re-enabling all extensions at once — Adding them back in bulk defeats the purpose. Re-enable one at a time so you can identify the exact problem add-on.
- Reinstalling without removing profile data — On Windows, a standard uninstall leaves the profile folder intact. Corrupted data at
C:\Users\YourName\AppData\Local\Google\Chrome\User Datawill reload with the new install. - Assuming Chrome is always the culprit — If other applications also freeze or crash, check that your system drive has at least 5 GB free and run a Windows SFC scan before blaming the browser.
Frequently Asked Questions
What does the “Aw, Snap!” error mean?
Chrome ran out of memory or the page’s renderer process crashed. Closing unused tabs, enabling Memory Saver (Settings → Performance), or disabling extensions usually clears it. If it appears on every page, an outdated Chrome version is the most likely cause.
Does reinstalling Chrome delete my bookmarks and passwords?
No — if you’re signed in to your Google account, bookmarks, passwords, and history sync back automatically after you reinstall and sign in. If you’re not signed in, export bookmarks first via Ctrl + Shift + O → menu → Export bookmarks before uninstalling.
Can malware cause Chrome to crash?
Yes. Malicious browser extensions or code injected into Chrome processes can cause crashes that look like ordinary bugs. If standard fixes don’t help, run a scan with Windows Defender or Malwarebytes Free before attempting a reinstall.
Will trying Firefox tell me if the problem is Chrome-specific?
Yes — if the same page loads fine in Firefox but crashes Chrome, the issue is in Chrome’s configuration rather than the website. See Why Is Firefox Slow? 8 Settings and Fixes to Speed It Up for a comparison of how browser troubleshooting differs between the two.
Conclusion
Chrome crashes are nearly always fixable without losing your bookmarks or data. Start with extensions and cache clearing — those two steps resolve the vast majority of issues in under five minutes. If you’ve worked through all six fixes and Chrome is still unstable, the problem has moved to the OS level; a Windows SFC scan or macOS disk check is the logical next step.
Also see: How to Fix the “Your Connection Is Not Private” Error in Chrome if SSL warnings are appearing alongside your crashes — the two issues can share a root cause.
Last updated: June 21, 2026