Google Chrome is the world's most popular browser — and one of the most common sources of tech frustration when it starts crashing, freezing, or showing the "Aw, Snap!" error repeatedly. Whether you are on Windows, Mac, or Android, the good news is that most Chrome crashes have a clear, fixable cause. This guide walks through 12 proven fixes, ordered from quickest to most thorough.
chrome://crashes to see a log of recent crashes with timestamps. Then check chrome://conflicts (Windows only) to see if any third-party software is injecting code into Chrome — this is a major crash cause that most guides overlook.
Why Does Chrome Keep Crashing?
Chrome crashes for several distinct reasons depending on your platform:
- Outdated Chrome version — Chrome auto-updates in the background, but pending restarts mean you are running old code with known bugs.
- Corrupt cache or profile data — corrupted cached files cause specific pages or all pages to crash on load.
- Bad extensions — a single broken extension can destabilize the entire browser, especially ad blockers, VPN extensions, and password managers.
- Insufficient RAM — Chrome's multi-process architecture means each tab runs in its own process. With 20 tabs and 8 GB RAM, Chrome regularly runs out of memory.
- GPU/hardware acceleration conflicts — on machines with older or integrated GPUs, hardware acceleration causes crashes on graphics-heavy pages.
- Malware — browser hijackers and adware inject code directly into Chrome's renderer process.
- OS-level conflicts — antivirus software, Windows security features, and other browsers can interfere with Chrome's processes.
Fix 1 — Update Chrome
Chrome updates silently in the background, but the update does not apply until you restart the browser. If you leave Chrome open for days, you could be running a version that is weeks behind.
Check Your Chrome Version and Update
Go to chrome://settings/help (type it in the address bar and press Enter). Chrome will automatically check for updates and show the current version. If an update is available, it installs automatically. Click Relaunch to apply it. As of 2026, Chrome stable is version 124+.
On Mac:
Same process — navigate to chrome://settings/help. Alternatively, close Chrome completely and reopen it; Chrome applies pending updates on next launch.
On Android:
Open the Google Play Store, tap your profile icon, tap Manage apps & device, then Updates available. Find Chrome and tap Update.
Fix 2 — Clear Cache and Cookies
A large or corrupt browser cache is a common cause of "Aw, Snap!" crashes on specific pages. Clearing it forces Chrome to re-fetch all page resources fresh.
Clear Chrome Cache (All Platforms)
Press Ctrl + Shift + Del (Windows/Linux) or Cmd + Shift + Del (Mac). Set the Time range to All time. Check Cached images and files and Cookies and other site data. Click Clear data. Relaunch Chrome and test.
On Android:
Go to Settings > Apps > Chrome > Storage > Clear Cache. Do not tap "Clear Data" unless you want to reset all site logins — that wipes cookies and stored passwords from the device.
Fix 3 — Disable Extensions One by One
Extensions are the most common cause of Chrome crashes that cannot be reproduced in Incognito mode. A single broken extension — especially after a Chrome update changes an API — can crash the entire browser.
Test in Incognito First
Press Ctrl + Shift + N (Windows/Mac) to open an Incognito window. Extensions are disabled by default in Incognito. If Chrome is stable there, an extension is your culprit.
Disable Extensions and Re-enable One by One
Go to chrome://extensions/. Toggle off all extensions. Relaunch Chrome. If crashes stop, re-enable extensions one at a time, relaunching after each one, until the crash recurs — that is your problematic extension. Delete it or check for an update.
Fix 4 — Reset Chrome Settings
A Chrome settings reset clears startup page overrides, search engine hijacks, cookie permissions, and extension configurations that can accumulate into instability — without deleting your bookmarks or synced data.
Run the Chrome Reset
Go to chrome://settings/reset. Click Restore settings to their original defaults. Read what will be reset (search engine, homepage, pinned tabs, extensions disabled, cookies cleared). Click Reset settings. Your bookmarks and passwords synced to Google are not affected.
Fix 5 — Reinstall Chrome Completely
If Chrome crashes immediately on launch, the installation itself may be corrupt. A clean reinstall replaces all Chrome binaries.
Uninstall Chrome (Windows)
Go to Settings > Apps > Installed apps. Find Google Chrome and uninstall it. Then manually delete the remaining Chrome folder at C:\Users\[YourName]\AppData\Local\Google\Chrome (press Win + R, type %LOCALAPPDATA%\Google\Chrome). Download fresh from google.com/chrome.
Uninstall Chrome (Mac)
Drag Chrome from Applications to the Trash. Then open Finder, press Cmd + Shift + G, go to ~/Library/Application Support/Google/Chrome and delete the Chrome folder. Empty Trash. Download fresh from google.com/chrome and reinstall.
Fix 6 — Check RAM Usage
Chrome is famously RAM-hungry. Each tab, extension, and browser process runs in its own sandbox. With 20+ tabs open, Chrome can consume 4–8 GB of RAM, crowding out other applications and causing out-of-memory crashes.
Use Chrome's Built-in Task Manager
Press Shift + Esc inside Chrome to open Chrome's own Task Manager. It shows memory usage per tab and per extension. Close the biggest memory consumers. You can also set a memory limit in Chrome flags: go to chrome://flags and search for "Memory Saver" — enable it to automatically suspend inactive tabs.
chrome://settings/performance and enable Memory Saver. This automatically discards inactive tabs from memory, reducing Chrome's RAM footprint by up to 40% while keeping tabs accessible. It is one of the best Chrome settings to enable in 2026.
Fix 7 — Disable Hardware Acceleration
Hardware acceleration offloads page rendering to your GPU. On machines with outdated GPU drivers or integrated graphics with limited VRAM, this causes crashes when loading video-heavy or WebGL pages.
Disable Hardware Acceleration
Go to chrome://settings/system. Toggle off Use hardware acceleration when available. Click Relaunch. Test Chrome — if it no longer crashes, update your GPU drivers (see Fix 9) and then re-enable it.
On Mac:
Same path: Chrome Menu > Settings > System > toggle off hardware acceleration. This is especially effective on older MacBooks with AMD Radeon GPU driver issues.
Fix 8 — Scan for Malware
Browser hijackers, adware, and cryptominers inject themselves into Chrome's processes, causing crashes, redirects, and mysterious slowdowns. Chrome has a built-in malware scanner on Windows.
Run Chrome's Built-in Cleanup (Windows)
Go to chrome://settings/cleanup. Click Find harmful software. Chrome will scan for software known to interfere with the browser and offer to remove it. This tool specifically targets software that injects into Chrome — things Windows Defender may not flag.
Run a Full System Malware Scan
Run Windows Defender Full Scan from Windows Security, or use Malwarebytes Free as a second-opinion scanner. On Mac, use Malwarebytes for Mac or the built-in XProtect is usually sufficient.
Fix 9 — Update Your Operating System and GPU Drivers
Chrome uses operating system APIs for rendering, networking, and security. An outdated OS or GPU driver can cause crashes that look like Chrome problems but are actually system-level issues.
Windows:
Go to Settings > Windows Update and install all pending updates. For GPU drivers: if you have NVIDIA, update via GeForce Experience. AMD users: update via AMD Software: Adrenalin. Intel graphics: update via Intel Driver and Support Assistant (intel.com/content/www/us/en/support/detect.html).
Mac:
Go to System Settings > General > Software Update. macOS updates include GPU and security patches. Chrome on Mac also depends on the system's Metal GPU framework — an outdated macOS can cause Chrome GPU process crashes.
Fix 10 — Create a New Chrome Profile
Your Chrome profile stores local data including cached extensions, settings, web storage, and IndexedDB databases. A corrupt profile causes persistent crashes that survive cache clearing and reinstallation.
Add a New Profile
Click your profile icon (top-right corner of Chrome). Click Add at the bottom. Create a new profile with your Google account. Open Chrome with the new profile. If Chrome is stable in the new profile, your old profile data is corrupt.
Rename the Old Profile Folder Manually
Close Chrome. Navigate to %LOCALAPPDATA%\Google\Chrome\User Data\ (Windows) or ~/Library/Application Support/Google/Chrome/ (Mac). Rename the Default folder to Default.bak. Relaunch Chrome — it creates a fresh Default folder. Sign back in with your Google account to restore synced bookmarks and passwords.
Fix 11 — Check for Software Conflicts (chrome://conflicts)
This is one of the most underused Chrome diagnostic pages. On Windows, many third-party applications inject DLLs into Chrome's processes — antivirus software, screen recorders, clipboard managers, and even some printer drivers. These injections frequently cause crashes.
View Loaded Modules
Type chrome://conflicts in your address bar. This page shows all third-party modules loaded into Chrome's processes. Any module listed as "conflicting" should be investigated. Common culprits include older versions of Skype, RealPlayer browser extensions, and outdated antivirus browser helpers. Update or uninstall the software associated with any conflicting module.
Fix 12 — Use Chrome Canary for Testing (Advanced)
Chrome Canary is Google's nightly development build — it receives updates ahead of stable Chrome. If your crash is caused by a recently introduced bug in stable Chrome, it may already be patched in Canary. Conversely, if Canary also crashes in the same way, it confirms the issue is not a Chrome code bug but something in your system.
Download and Test Chrome Canary
Download from google.com/chrome/canary. Canary installs alongside stable Chrome without overwriting it. Sign in with your Google account and test whether the crash still occurs. If Canary is stable, wait for the fix to roll out to stable Chrome (usually 2–4 weeks). If Canary also crashes, report the bug at crbug.com with your chrome://crashes log.
Chrome Crash Fixes — Quick Reference Table
| Fix | Windows | Mac | Android | Difficulty |
|---|---|---|---|---|
| 1. Update Chrome | Yes | Yes | Yes | Easy |
| 2. Clear cache & cookies | Yes | Yes | Yes | Easy |
| 3. Disable extensions | Yes | Yes | N/A | Easy |
| 4. Reset Chrome settings | Yes | Yes | N/A | Easy |
| 5. Reinstall Chrome | Yes | Yes | Yes | Medium |
| 6. Manage RAM / Memory Saver | Yes | Yes | Partial | Easy |
| 7. Disable hardware acceleration | Yes | Yes | N/A | Easy |
| 8. Malware scan | Yes | Yes | Yes | Easy |
| 9. Update OS & GPU drivers | Yes | Yes | Yes | Medium |
| 10. New Chrome profile | Yes | Yes | N/A | Medium |
| 11. Check conflicts page | Yes | N/A | N/A | Advanced |
| 12. Test with Chrome Canary | Yes | Yes | N/A | Advanced |
Chrome Still Crashing After All 12 Fixes?
Persistent Chrome crashes sometimes point to deeper issues — failing RAM, driver conflicts, or malware that standard tools cannot remove. IT Cares diagnoses and fixes these remotely, usually in under an hour. We serve Montreal and all of Canada remotely.
Frequently Asked Questions
The most common causes are: a corrupt or outdated Chrome installation, incompatible extensions, insufficient RAM, malware injecting code into Chrome's processes, and conflicts with third-party apps. Check chrome://crashes for crash logs and chrome://conflicts to see if any software is injecting modules into Chrome.
A Chrome settings reset (chrome://settings/reset) preserves bookmarks and clears problematic settings. Sign into Chrome with your Google account first — this backs up bookmarks, passwords, and history to Google's servers automatically. Even a full reinstall will restore everything when you sign back in.
Yes, on many machines — especially those with older or integrated GPUs. Hardware acceleration offloads rendering to the GPU, which normally improves performance. But with outdated GPU drivers or limited GPU memory, it causes crashes on graphics-heavy pages. Disabling it forces CPU rendering instead, which is more stable on problematic hardware.
Site-specific crashes are usually caused by heavy JavaScript or WebGL content overwhelming available RAM, or an extension conflicting with that site's scripts. Try the site in Incognito mode (Ctrl+Shift+N) — extensions are disabled there. If it loads fine in Incognito, use chrome://extensions/ to find the conflicting extension by disabling them one at a time.
Android Chrome crashes are usually caused by insufficient storage (Android needs free space to write temp browser data), too many open tabs consuming RAM, or an outdated Chrome or Android System WebView. Fix: update Chrome and Android System WebView via Play Store, clear Chrome's cache in Settings > Apps > Chrome > Storage, and close tabs you do not need.
Comments
The chrome://conflicts page was a revelation. I had an old Skype plugin from 2019 showing as a conflicting module — I had no idea it was even still installed. Uninstalled Skype completely and Chrome has not crashed once in two weeks. I would never have found that without this article.
Disabling hardware acceleration fixed my Chrome immediately. It was crashing every time I opened YouTube or any page with video. My laptop has Intel integrated graphics and apparently the driver was the issue. Updated the Intel driver after and re-enabled acceleration — still working fine now.
The Memory Saver tip from Fix 6 changed my Chrome experience completely. I work with 40+ tabs open and Chrome used to crash several times a day. With Memory Saver enabled, inactive tabs are suspended and I have not had a crash in over a month. Why is this not on by default?
Leave a Comment