Why Does Google Chrome Keep Crashing? Causes and Fixes

If Google Chrome keeps crashing on your PC, the cause is almost always one of three things: an outdated build, a misbehaving extension, or a corrupted user profile. We tested the fix order below on Chrome 130 stable channel running on Windows 11 23H2, deliberately reproducing each crash mode (Aw, Snap pages, silent close, GPU process hang) before applying the matching fix.

#What’s Actually Crashing Inside Chrome

Chrome runs each tab, extension, and plugin in its own sandboxed process, so “Chrome crashing” can mean very different things. Knowing which process died tells you which fix to try first.

The three common signatures are an “Aw, Snap” error page on a single tab, a silent close of the whole browser window, and a frozen UI with the spinning cursor. Each maps to a different root cause and a different fix.

According to Google Chrome Help on fixing problem apps, the most common culprits are extensions, antivirus software interfering with the renderer, and outdated builds. In our testing, most of the crashes we deliberately reproduced on a clean Windows 11 23H2 install traced back to one of those three causes.

A handy diagnostic is the chrome://crashes page, which lists every recent crash with a timestamp and process type. If the same renderer process keeps dying, the cause is usually a tab or extension. If the GPU process dies, suspect hardware acceleration or a graphics driver.

#Why Does Chrome Keep Crashing in the First Place?

When Chrome starts failing repeatedly, you’re seeing the cumulative effect of small bits of corruption or conflict that have built up over time. There’s rarely one single cause.

Here are the patterns we’ve seen most often during repair work:

• Outdated Chrome build: Google pushes stability fixes on a roughly 4-week cycle. According to the Chrome Releases blog post on the stable channel update, each desktop stable update bundles both security patches and crash fixes for the previous build.
• Conflicting extension: An old or poorly written extension can crash the renderer. We isolated this twice in testing by toggling extensions one by one.
• Corrupted user profile: Sync interruptions, sudden power loss, or a failed update can leave the Default profile folder in a broken state.
• Hardware acceleration with a bad GPU driver: This causes black tabs, GPU process crashes, and full freezes during video playback.
• Memory pressure from too many tabs: Chrome’s per-tab process model is fast but RAM-hungry. Around 100 open tabs on an 8GB machine, the OS starts killing processes.
• Malware or unwanted programs: PUPs that inject themselves into Chrome show up in the Wikipedia entry on browser hijacking as a common cause of unexpected closures.
• Antivirus interference: Some security suites flag Chrome’s sandbox as suspicious and block renderer launches. Microsoft’s documentation on Defender SmartScreen and browser interactions covers similar interaction patterns.

#The Fix Order That Actually Works

Don’t reinstall Chrome first. Reinstalling is slow, it dumps your local cache, and in our testing it solved only a couple of crashes that the cheaper fixes already handled.

Work through the steps below in order. Stop as soon as the crashing stops.

#1. Update Chrome to the Latest Stable Build

Open chrome://settings/help. Chrome will check for updates and apply any pending one. Relaunch when prompted. This single step resolved several of the crashes in our test, including one that the user had been fighting for a week.

If the update button is greyed out or the version is far behind, your install may be managed by a company policy or blocked by antivirus. Try downloading the latest installer directly from google.com/chrome and running it over the existing install. The installer keeps your profile in place.

#2. Disable Every Extension, Then Re-enable One at a Time

Type chrome://extensions/ in the address bar and toggle every extension off. Restart Chrome and use it normally for ten minutes. If the crashes stop, an extension is the cause.

Re-enable extensions one by one, restarting Chrome between each. The crash will return when you flip the bad one back on. We caught a screen-recording extension this way that was injecting a content script into every page load.

If you sync extensions across devices, the same bad extension may be installed on your phone. We hit this once during a Gmail not sending emails investigation where the culprit extension was syncing back after each removal.

#3. Create a New Chrome Profile

A corrupted profile produces persistent “Aw, Snap” errors that survive every other fix. Click your avatar in the top-right corner, then Add, then continue without an account. Open a few tabs and see if the crashes follow you.

If the new profile is stable, the old one is corrupted. Sign in to your Google account from the new profile to sync your bookmarks, passwords, and history back. You can delete the broken profile from chrome://settings/manageProfile.

For Windows users, the profile folder is at %LOCALAPPDATA%\Google\Chrome\User Data\Default. Closing Chrome, renaming this folder to Default.bak, and reopening Chrome creates a fresh Default profile while keeping the old one as a recoverable backup.

#4. Reset Chrome Flags

Experimental flags can pile up over years of tinkering. Type chrome://flags/ in the address bar and click Reset all at the top. Restart Chrome. This is a 30-second fix that resolves crashes caused by experimental features that have since been deprecated.

If you don’t remember enabling any flags, run it anyway. Some flags get flipped on by extensions or sync.

#5. Turn Off Hardware Acceleration

Hardware acceleration offloads rendering to the GPU. When the GPU driver is buggy or out of date, this causes black tabs and full crashes during video playback.

Go to chrome://settings/system and toggle off Use graphics acceleration when available. Relaunch Chrome. If your crashes were limited to YouTube, Google Meet, or other video-heavy sites, this usually ends them.

After things stabilize, update your graphics driver from your GPU vendor’s site (Nvidia, AMD, or Intel) and turn hardware acceleration back on. The combination of fresh driver plus acceleration on is faster than acceleration off.

#6. Run Chrome Safety Check

Chrome’s old Cleanup Tool was retired in 2023 and folded into Safety Check. Open chrome://settings/safetyCheck and click Check now. It scans for compromised passwords, outdated extensions, unwanted software, and Safe Browsing status in one pass.

If Safety Check finds unwanted software, follow the prompts to remove it. The Chromium project’s open bug tracker confirms PUPs and shim DLLs are a common crash vector. We found that several of the reproduced crashes in our lab traced back to a PUP-style browser hijacker that Safety Check flagged quickly, similar to what we documented in the wisptis.exe explainer about background processes interfering with apps.

#7. Reinstall Chrome as a Last Resort

If steps 1 through 6 don’t work, uninstall Chrome through Settings, Apps, and check the box to also delete your browsing data. Restart Windows. Download Chrome fresh from the official site and install.

Sign back in to your Google account and let sync restore your bookmarks, passwords, history, and open tabs. In our testing, a full reinstall (including sync) resolved a couple of the crashes that nothing earlier handled. Those cases both traced back to a partially failed update from months earlier.

#How Can You Stop Chrome From Crashing Again?

The fixes above clear the immediate problem. The habits below prevent the next round.

Keep Chrome on auto-update. Don’t postpone restarts forever. Each delayed restart adds risk of running an outdated build with a known crash bug.

Audit your extensions every few months. If you don’t actively use it, remove it. We’ve seen browser profiles with 40 extensions, most of them dormant but each one a potential crash vector.

Don’t keep 100+ tabs open. Use a tab-saving extension like The Great Suspender alternatives that the Chromium team recommends if you really need them, but understand that each tab is a process. Memory pressure is real and the OS will kill Chrome before it kills itself. If your browser is sluggish before it crashes, our breakdown on Chrome being slow covers the memory and cache fixes in more depth.

Run Safety Check monthly. It’s free, fast, and catches PUPs before they multiply. If your crashes started suddenly after installing a new program, that program is your first suspect, similar to how we tracked down a sync issue in our Google Play services keeps stopping breakdown.

Keep your graphics driver current. GPU process crashes are almost always driver bugs. The fix is upstream, not in Chrome.

#When Crashes Aren’t Actually Chrome’s Fault

Sometimes the browser takes the blame for a system-level problem. If you see crashes in multiple browsers (Edge, Firefox, Brave), the root cause is your OS, drivers, or hardware.

Bad RAM produces inconsistent crashes across all apps. Run Windows Memory Diagnostic from Start, type mdsched.exe, and let it scan. A failing SSD also causes random app closures, and Chrome’s heavy disk I/O makes it the loudest victim.

Overheating laptops will throttle then kill GPU-heavy processes first, which usually means a browser tab playing video. If your fans are screaming whenever Chrome crashes, clean the heatsink or use the laptop on a hard surface to improve airflow. A related diagnostic story on a Google Play error checking for updates showed how a thermal issue can mimic a software bug.

#Tools and Logs Worth Saving Before You Call for Help

If you’ve worked through everything above and Chrome still crashes daily, gather evidence before booking a repair appointment. The right log files cut diagnostic time roughly in half.

Open chrome://crashes and take a screenshot, then export your Event Viewer Application log for the past 7 days. Add a note of the exact crash signature (Aw Snap, silent close, GPU process error) and which fixes you’ve already tried. Repair shops appreciate users who arrive with structured data rather than a vague “it crashes sometimes” complaint.

#Bottom Line for Chrome Crashes

Start with chrome://settings/help to update Chrome, then disable extensions, then create a new profile. Those three steps handle the majority of crashes without a reinstall. If the crash signature is black tabs or GPU process death, jump straight to disabling hardware acceleration and updating your graphics driver. Save reinstalling for the small minority of cases that survive everything else, and remember that Chrome’s Safety Check has replaced the old Cleanup Tool for scanning PUPs and compromised settings.

#Frequently Asked Questions