Chrome crashing — where the browser completely closes without warning, or individual tabs show “Aw, Snap!” — covers several completely different problems with different solutions. The pattern of the crash is the most useful information you have. If you want the full context, see our Google Chrome Errors.
Chrome closes the moment you open it — Profile corruption or hung processes from a previous session. Kill all chrome.exe processes in Task Manager first, then try again. If it still crashes, rename the Default folder (see Fix 2).
Random crashes during normal use, no obvious trigger — Usually hardware acceleration conflicting with the GPU driver (Fix 3), or Chrome running out of memory (Fix 4).
“Aw, Snap!” on specific websites only — That page’s content is crashing the renderer. Either the site has a memory leak or bad JavaScript, or an extension is causing a conflict on that specific page. Test in Incognito to distinguish between them.
Chrome crashes after a recent update — Either the Chrome update introduced a bug, or a Windows update changed something Chrome depends on. Try disabling extensions first (they break more often than Chrome itself).
Step 1: Kill Hung Processes First
Before anything else — open Task Manager (Ctrl + Shift + Esc) and check for existing chrome.exe processes. If Chrome crashed without properly cleaning up its processes, ghost instances remain in memory. When you try to open Chrome again, it either tries to connect to the failed instances or conflicts with them.
Right-click every chrome.exe entry → End task. Wait 15 seconds for them all to clear, then try opening Chrome again. This resolves a large percentage of “Chrome won’t stay open” situations before any settings changes are needed.
Fix 1: Test in Incognito (60-Second Extension Check)
Press Ctrl + Shift + N to open Chrome in Incognito mode. Incognito disables all extensions by default and uses no cached profile state. Browse normally for a few minutes — ideally visiting the sites that were causing crashes.
If Chrome is stable in Incognito but crashes normally: an extension is causing it. Go to chrome://extensions, toggle every extension off, restart Chrome, test stability, then re-enable extensions one at a time until crashes return. The last extension enabled before a crash is the culprit.
If Chrome also crashes in Incognito: the problem is at the browser or system level, not extensions. Continue to the fixes below.
Fix 2: Rename the Chrome Profile
The Chrome profile stores all your browsing data, extension settings, preferences, and cached state. When any part of this accumulates corruption — which happens more often after power cuts, unexpected shutdowns, and Chrome crashes that didn’t close cleanly — it can cause Chrome to crash during startup or during normal use.
Close Chrome completely (Task Manager → end all chrome.exe). Navigate to %localappdata%GoogleChromeUser Data. Find the folder named “Default” and rename it to “Default.old.” Reopen Chrome — it creates a fresh Default folder and opens as if newly installed.
If Chrome is now stable: sign into your Google account to restore synced bookmarks, history, and passwords from the cloud. Extensions need to be reinstalled from the Chrome Web Store. If crashes return after reinstalling extensions, one of those extensions is the cause — reinstall them one at a time.
If Chrome still crashes with a renamed Default folder: the corruption is in the installation files, not the profile.
Fix 3: Hardware Acceleration
Chrome uses the GPU for rendering web content through hardware acceleration. When the GPU driver has a bug in a specific code path Chrome uses — a common occurrence after driver updates — Chrome’s GPU process crashes and takes the tab or the whole browser with it. This pattern produces crashes specifically during graphically intensive activities: scrolling through image-heavy pages, playing video, WebGL applications.
Disable hardware acceleration: Settings → System → toggle off “Use hardware acceleration when available” → Relaunch. Test for crashes over a full session. If crashes stop, the GPU driver is the underlying issue.
The permanent fix is updating the GPU driver from the manufacturer’s website (NVIDIA, AMD, or Intel), not through Windows Update — manufacturer drivers are more current and better tested. After updating, re-enable hardware acceleration and confirm stability.
Fix 4: Memory — Chrome Running Out of RAM
Chrome’s multi-process model means each tab runs as a separate process. On machines with 8 GB or less of RAM, running many tabs simultaneously pushes Chrome into memory exhaustion territory. When Chrome runs out, it starts killing renderer processes — which shows as “Aw, Snap!” errors on specific tabs, or as the whole browser becoming unstable and eventually crashing.
Check this: open Chrome’s task manager (Shift + Esc) and look at the Memory Footprint column. If you’re running multiple tabs with 200–400 MB each, and total memory adds up to close to your available RAM, memory pressure is the cause.
Enable Memory Saver: Settings → Performance → toggle Memory Saver on. This suspends inactive tabs, dropping their memory footprint to near-zero until you click on them. On 8 GB machines, Memory Saver often prevents the crashes entirely by keeping total Chrome memory usage within sustainable limits.
Fix 5: Update Chrome
Chrome updates automatically but sometimes falls behind — especially if it’s rarely restarted. An outdated Chrome version can have bugs that cause crashes, and those bugs may already be fixed in the current release. Check: three-dot menu → Help → About Google Chrome. Chrome checks for updates on this page and installs any available. Restart when prompted and test stability.
If crashes started after a Chrome update (rather than being resolved by one): search for the specific Chrome version number plus “crashing” in a browser — regression bugs in specific Chrome releases are quickly documented in community forums and often have workarounds while Google prepares a patch.
Fix 6: Clean Reinstall
When crashes persist through profile rename, hardware acceleration disable, extension elimination, and Chrome update: the Chrome binaries themselves are corrupted. A clean reinstall resolves this.
- Uninstall Chrome via Settings → Apps → Google Chrome → Uninstall
- Manually delete remaining folders:
C:Users[YourName]AppDataLocalGoogleChrome - Restart the PC
- Download a fresh installer from google.com/chrome and install
The manual folder deletion before reinstalling is critical — if you skip it, the reinstall restores the same corrupted data from the leftover folders.
Antivirus and Chrome Crashes
Security software that injects its own DLLs into Chrome’s process for web threat monitoring occasionally conflicts with Chrome’s sandbox and causes crashes. The crash tends to happen randomly or on specific types of pages (HTTPS sites with complex certificates, sites with embedded ads). Event Viewer captures this: Windows Logs → Application → look for Chrome crash entries — the “Faulting module name” field shows which DLL caused the crash. If it’s an antivirus DLL rather than a Chrome or Windows DLL, the security software is the cause.
Temporarily disabling the antivirus and testing whether crashes stop confirms this. The fix is adding Chrome to the antivirus’s trusted process list or disabling browser injection in the antivirus settings — not disabling the antivirus entirely.
chrome://crashes
Chrome maintains its own crash log accessible at chrome://crashes in the address bar. This page shows recent crash records with timestamps and crash signatures. The crash Signature field sometimes reveals whether crashes share a common component — if all crashes have the same signature involving a specific GPU component, a specific extension, or a specific Chrome subsystem, that’s a much faster path to the right fix than working through the general list. It’s also useful for comparing against known bugs if you search the crash signature online.
Our guide on Chrome not opening covers the launch failures where Chrome won’t start at all — a related but separate problem with some shared fixes. For the memory and tab management that prevents crashes under heavy use, our Chrome high memory guide covers Memory Saver configuration in more detail. Google’s Chrome stability documentation covers the crash reporting system and how to submit crash reports that help Google identify and fix widespread stability issues.
Renderer Process Crashes vs Browser Process Crashes
Chrome uses a multi-process architecture that separates the browser shell (chrome.exe parent process) from each tab’s renderer (separate chrome.exe child processes). Understanding which crashes is useful for diagnosis:
Renderer crash — A single tab shows “Aw, Snap!” while other tabs continue working. The browser itself is fine. The renderer for that specific tab crashed. Cause: usually memory exhaustion on that tab, a bad JavaScript execution on that page, a codec issue with media content, or an extension conflicting with that specific page’s content. Reloading the tab starts a fresh renderer process.
Browser process crash — Chrome disappears entirely. All tabs close. No “Aw, Snap!” — the whole application is gone. Cause: hardware acceleration crash that propagated to the parent process, antivirus DLL injection conflict, or severe memory exhaustion affecting the browser shell process itself. The fixes are different: hardware acceleration disable, antivirus exclusion, or reinstallation.
The distinction matters because renderer crashes are isolated — they only affect one tab and don’t indicate Chrome itself is unstable. Browser process crashes indicate a systemic problem that will affect all tabs simultaneously. If you’re seeing “Aw, Snap!” on individual tabs occasionally, that’s normal for tabs running heavy content. If Chrome disappears entirely and takes all tabs with it, that’s the more serious variety that needs fixing.
Specific Crash Patterns and What They Indicate
Crashes when opening new tabs — The new tab page extension or a startup extension is crashing. Try setting the startup page to a URL instead of the new tab page. Also try disabling extensions that run on new tab page (like custom new tab extensions).
Crashes when downloading files — Antivirus scanning the downloaded file before Chrome can use it is causing a conflict. Add Chrome’s download folder to antivirus exclusions, or try downloading to a different location.
Crashes specifically on video content — Hardware acceleration conflict with video decoding. Go to chrome://flags/#disable-accelerated-video-decode and enable “Disable Accelerated Video Decode.” This forces software video decoding rather than GPU-accelerated decoding, which resolves crashes on pages with video when the GPU driver has a bug in its video decode path.
Crashes after long sessions, not at startup — Memory leak in an extension or a specific website with poorly written JavaScript that allocates memory but never frees it. Monitor Chrome’s task manager (Shift + Esc) over a long session — the process consuming the most memory and growing consistently over time is the leak source.
Windows User Account Profile and Chrome
Chrome’s user profile is stored within the Windows user profile. When the Windows user account itself has corruption (not just Chrome’s own data), Chrome may crash in ways that don’t respond to profile renaming — because the underlying Windows profile is the problem rather than Chrome’s data within it.
Test this by creating a new Windows user account (Settings → Accounts → Other users → Add account) and installing Chrome fresh in that account. If Chrome is completely stable in the new account without any Chrome-specific fixes applied, the original Windows user account has corruption affecting Chrome’s ability to write and read its data. In this case, migrating to a new Windows account (transferring files from the old account via shared folder access) resolves the crashes permanently without any Chrome reinstallation needed.
Chrome Flags That Affect Stability
Chrome’s experimental flags at chrome://flags can dramatically affect stability. Flags that were stable in a previous Chrome version sometimes become unstable after a Chrome update changes the underlying implementation they were affecting. If you’ve previously enabled experimental flags, resetting them all is a quick stability test:
Navigate to chrome://flags → click “Reset all to default” in the top right → Relaunch Chrome. This restores all Chrome flags to their default values. If crashes stop after this, one of the experimental flags was causing instability. You can re-enable flags one at a time to identify which one was problematic.
When RAM Itself Is the Issue
Chrome is an effective RAM stress test. On machines with marginal or failing RAM, Chrome crashes may not be a Chrome problem at all — they’re RAM errors manifesting through Chrome because Chrome pushes memory harder than most applications. The clue: crashes happen in Chrome but also in other memory-intensive applications, or the crashes are accompanied by general system instability.
Run Windows Memory Diagnostic: search in Start → Windows Memory Diagnostic → Restart now and check for problems. MemTest86 (free, run from a USB drive) is more thorough and can identify RAM errors that the Windows diagnostic misses. If RAM errors are found, replacing the RAM resolves not just Chrome crashes but all the instability that’s been attributed to Chrome.
On machines with XMP or EXPO RAM overclocking profiles enabled in BIOS, disabling XMP/EXPO and running at stock speeds is a useful stability test — XMP profiles push RAM beyond its base specification and sometimes cause crashes in memory-intensive applications like Chrome that don’t appear during light use. See also Firefox Keeps Crashing for a related case.
