Chrome Crashing on Windows or Mac: How to Stop Aw, Snap and Random Closes

Chrome crashing on Windows or Mac almost always traces back to a small set of culprits: a rogue extension, a corrupted cache, a GPU driver conflict, or simply an outdated build. The first time my own copy started throwing “Aw, Snap!” on every tab, I assumed the install was beyond saving — but the real cause was a single extension that had silently updated overnight.

I have rebuilt this troubleshooting routine across dozens of Windows and Mac machines, and the order below is ranked easiest-first. Each step takes one to five minutes, and most people get a stable browser back after the first two.

Quick Answer

Disable every Chrome extension at chrome://extensions, then re-enable them one at a time to find the one causing crashes. If that does not 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 fix most crashes.

Why does Chrome keep crashing in the first place?

Chrome runs each tab and extension in its own process, so a single faulty component can take down the whole window — including tabs it was never touching. In my experience the trigger is almost always an extension that updated itself, a cache file that went corrupt, a GPU driver that fell out of step with Chrome, or a version that never finished installing because the browser was never relaunched.

Knowing which pattern you are seeing tells you which fix to try first, so it pays to notice when the crashes happen — on launch, on one site, during video, or everywhere.

Crashes are a process problem, and matching the crash pattern to the right fix saves you from working through all six.

How do I find the extension that is crashing Chrome?

Extensions are the single most common crash trigger I see. One outdated or poorly coded add-on can bring down the entire browser, so this is always where I start.

1. Type chrome://extensions in the address bar and press Enter.
2. Toggle all extensions off using the blue switches.
3. Restart Chrome. If it is stable, re-enable extensions one at a time — restarting after each — until the crash returns.
4. Remove or update the problem extension via Details → Update or the Remove button.

Extensions update silently in the background, so if crashes started recently, check which add-on updated last — that is usually the one. The first time I did this I found the culprit on the third toggle, which beats reinstalling the whole browser.

Disable everything, then re-enable one at a time so you can pin the crash on a single add-on.

Will clearing the cache and cookies stop the crashes?

Often, yes. A corrupted cache file can make Chrome crash on specific sites or after a few minutes of browsing, and this fix takes under a minute.

1. Press Ctrl + Shift + Delete (Windows) or Cmd + Shift + Delete (Mac).
2. Set Time range to All time.
3. Check Cached images and files and Cookies and other site data.
4. Click Clear data, then restart Chrome.

If you want the same routine across every browser you use, my walkthrough on how to clear browser cache and cookies in Chrome, Firefox, Safari, and Edge covers each one step by step.

A stale cache is a classic cause of site-specific crashes, and clearing it for All time takes under a minute.

Could an outdated Chrome version be the problem?

Frequently. Chrome updates itself in the background, but the update only applies after a full restart — so plenty of machines run outdated builds without anyone realising. An unpatched stability bug can cause repeated crashes.

1. Click the three-dot menu (⋮) in the top-right corner.
2. Go to Help → About Google Chrome.
3. Chrome checks for updates automatically on this screen. Install any available update.
4. Click Relaunch when prompted.

If the update button is greyed out, download the latest installer from Google’s official Chrome support page and run it over your existing install — this forces a clean update without wiping your profile.

An outdated build only patches itself on relaunch, so the About page is where you confirm you are current.

Should I turn off hardware acceleration?

If your crashes happen during video playback or while scrolling image-heavy pages, yes. Hardware acceleration offloads rendering to your GPU, which is faster on most systems but can conflict with certain GPU drivers — especially right after a driver update.

1. Open Chrome’s menu (⋮) and click Settings.
2. Search for “hardware acceleration” in the settings search bar.
3. Toggle Use graphics acceleration when available to Off.
4. Click Relaunch.

The trade-off is slightly slower rendering. When this fixed the crashes on a machine I was helping with, I updated the GPU drivers afterward and re-enabled the setting with no further trouble.

GPU conflicts show up as crashes during video or scrolling, and toggling acceleration off is the quickest test.

What if I changed Chrome flags by accident?

Chrome’s experimental features page lets you enable beta features, but these can break after a version bump. If you or an extension ever touched chrome://flags, a reset is worth trying.

1. Type chrome://flags in the address bar.
2. Click Reset all at the top of the page.
3. Click Relaunch.

Your bookmarks, passwords, and extensions are untouched by this reset — only experimental feature toggles are cleared.

A single stale flag can break after an update, and Reset all clears them without affecting your data.

How do I reset or reinstall Chrome without losing my data?

If nothing above works, Chrome’s internal settings or profile data may be corrupted. A settings reset preserves your synced data while clearing custom configurations.

1. Go to Settings → Reset settings → Restore settings to their original defaults.
2. Click Reset settings to confirm.
3. 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 are signed in to your Google account, bookmarks and passwords sync back automatically after reinstalling. On Windows, corrupted profile data can survive a standard reinstall — so if crashes persist, also delete C:\Users\YourName\AppData\Local\Google\Chrome\User Data before running the installer again. If memory pressure is part of the picture, my guide on cutting Chrome’s RAM with built-in settings pairs well with this reset.

A settings reset keeps your synced data; only a profile-folder deletion on Windows clears truly corrupt data.

Which fix matches your crash pattern?

When I triage a crashing install, I match the symptom to the most likely cause before touching anything. This table is the shortcut I use.

Crash Pattern	Most Likely Cause	Best First Fix
Crashes on one specific site	Corrupted cache	Clear cache and cookies
Crashes immediately on launch	Extension conflict	Disable extensions
Crashes after a GPU driver update	Hardware acceleration conflict	Turn off hardware acceleration
“Aw, Snap!” on all pages	Outdated Chrome version	Update Chrome
Crashes after a Chrome update	Experimental flag conflict	Reset flags

Match the pattern to the cause first, and you usually skip straight to the one fix that matters.

Common Mistakes to Avoid

1. 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.
2. Skipping the Relaunch prompt — Updates and settings changes do not apply until Chrome fully restarts. Clicking away from the prompt means the fix has not taken effect yet.
3. 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.
4. 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 Data will reload with the new install.
5. 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?
It means 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. When it hit me on every page at once, the fix turned out to be an outdated Chrome version that a relaunch sorted in seconds.

Does reinstalling Chrome delete my bookmarks and passwords?
No — if you are signed in to your Google account, bookmarks, passwords, and history sync back automatically after you reinstall and sign in. The one time I reinstalled while signed out, I had to export bookmarks first via Ctrl + Shift + O → menu → Export bookmarks, so do that before uninstalling if you are not synced.

Can malware cause Chrome to crash?
Yes. Malicious extensions or code injected into Chrome processes can cause crashes that look like ordinary bugs. On a machine where standard fixes did nothing, a Malwarebytes Free scan found a hijacked extension that was the real cause — so scan with Windows Defender or Malwarebytes before any 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. I keep a second browser installed for exactly this test; my notes on why Firefox runs slow and how to speed it up cover how troubleshooting differs between the two.

Why does Chrome crash only on certain websites?
A site-specific crash almost always points to a corrupted cache or a conflicting cookie for that domain. Clearing cache and cookies for All time fixes it most of the time; if a security warning shows up alongside the crash, my fix for the “Your connection is not private” error tackles a related root cause.

Conclusion

Chrome crashes are nearly always fixable without losing your bookmarks or data. I start with extensions and cache clearing every time — those two steps resolve the vast majority of cases in under five minutes. If you have worked through all six fixes and Chrome is still unstable, the problem has moved to the OS level, and a Windows SFC scan or macOS disk check is the logical next step. Bookmark this page so the routine is ready the next time “Aw, Snap!” appears.

Last updated: June 25, 2026