How to Fix Chrome That Keeps Crashing on Windows
Chrome crashing on Windows is usually a bad extension, the cache, graphics acceleration, or a damaged profile. Fix it in order with these steps.

When Chrome keeps crashing on Windows, the cause is almost always one of five things: an out-of-date build, a misbehaving extension, corrupted cache or profile data, graphics acceleration fighting your display driver, or malware on the PC. Work through the fixes below in order, from the fastest to the most involved, and stop as soon as Chrome stays up. Most people are sorted within the first three steps.
Rule out the quick causes first
Before you touch any settings, do the cheap fixes, because they clear the bulk of crashes. Update first. Chrome updates in the background, but a stalled update can strand you on a buggy build. Open the three-dot More menu at the top right, then Help > About Google Chrome. That page checks for an update and downloads it; when it finishes, select Relaunch, which reopens your tabs and windows automatically, per Google’s update guide. A colored dot on the More menu is Chrome’s own nudge that an update is waiting: green means it arrived in the last couple of days, orange about four days, red a week or more.
If Chrome froze instead of closing cleanly, force it to quit so the next launch is truly fresh. Press Ctrl+Alt+Delete, open Task Manager, select every Google Chrome process, and choose End task, then reopen. Restart the whole PC as well, since a stuck driver or background app is a common reason a page will not load, as Google notes.
When the crashes hit heavy pages, one tab or extension eating all your memory is often behind it. Chrome has its own task manager: press Shift+Esc (or More menu > More tools > Task manager), sort by Memory footprint, and end the row that towers over the rest. If Chrome runs slow as well as crashing, the same memory pressure usually drives both.
| Symptom | Likely cause | Fix to try first |
|---|---|---|
| “Aw, Snap” on a single page | Corrupted cache or a bad extension | Reload; clear cache; test in Incognito |
| Every tab crashes at once | Outdated build or display driver | Update Chrome; turn off graphics acceleration |
| Crashes only on certain sites | Extension or cached-data conflict | Disable extensions one by one; clear cookies |
| Crashes seconds after launch | Damaged user profile | Create a fresh profile or reset settings |
| Crashes plus pop-ups across the PC | Malware or a conflicting antivirus | Run a full Windows Security scan |
| Chrome will not open at all | Blocked by antivirus or a broken install | Allow-list Chrome; uninstall and reinstall |
Find the extension that keeps crashing Chrome
Extensions are the most common cause of repeat crashes, because a single poorly written or outdated add-on can take down a tab or the whole browser. Test the theory in an Incognito window (Ctrl+Shift+N), where extensions are off by default. If Chrome holds steady there, an extension is your problem.
Open the More menu > Extensions > Manage Extensions. Turn every extension off with its toggle, confirm Chrome stays up, then switch them back on one at a time, using the browser normally for a few minutes after each, until the crash returns. Remove the add-on that brings it back and check the developer’s listing for an update or a reported bug before you reinstall it. Google’s own crash guidance points to this same isolate-and-disable routine.
Clear the cache and cookies
A corrupted cache makes Chrome try to render half-broken files, which surfaces as the “Aw, Snap” crash on pages that load fine on other machines. Clearing it forces fresh copies.
Press Ctrl+Shift+Delete, or open the More menu > Delete browsing data. Set the time range to All time, check Cached images and files and Cookies and other site data, then select Delete data, following Google’s delete-browsing-data steps. Clearing cookies signs you out of sites, so keep your passwords handy; our walkthrough on clearing cookies in Chrome covers exactly what each option wipes. If a crash closed tabs before you could act, reopening closed Chrome tabs brings them back with Ctrl+Shift+T.
Turn off graphics (hardware) acceleration
Chrome offloads some rendering to your GPU to feel faster, but on a flaky or outdated display driver that offload is a frequent crash source. Turning it off is a standard fix that Google recommends for crashes.
Open the More menu > Settings > System and turn off Use graphics acceleration when available; older versions label the same switch Use hardware acceleration when available. Select Relaunch afterward. If the crashes stop, update your graphics driver from the PC or GPU maker before you turn the setting back on, because the toggle is only masking a driver bug rather than curing it.
Reset settings or switch to a fresh profile
When crashes begin right after launch or follow you regardless of which page you open, the profile itself, the folder that holds your settings, extensions, and cache, is probably damaged. You have two ways to handle it.
Create a fresh profile to test without disturbing your old one. Click the profile icon to the right of the address bar, choose Add, then Continue without an account for a quick local profile, per Google’s multiple-profiles guide. If the new profile is stable, the old one was corrupt.
To repair your main profile instead, reset Chrome. Open More menu > Settings > Reset settings > Restore settings to their original defaults > Reset settings. A reset returns your search engine, homepage, startup tabs, and new-tab page to default, turns off your extensions, and clears cookies and temporary site data, while leaving your bookmarks, history, and saved passwords untouched, as Google spells out.
| Option | Bookmarks and passwords | Extensions | Cookies and site data |
|---|---|---|---|
| Reset settings | Kept | Turned off | Cleared |
| New profile | Old profile untouched | None in the new one | Fresh and empty |
| Reinstall with data deleted | Removed if you delete data | Removed | Removed |
Rule out malware and an antivirus conflict
If the crashes come with pop-ups, a hijacked search engine, or ads spilling outside the browser, treat it as malware on the PC rather than a Chrome setting. Run a deep scan: open the Windows Security app, go to Virus & threat protection, select Scan options, pick Full scan, and let it finish, following Microsoft’s scan instructions. Removing software you do not recognize from Settings > Apps > Installed apps helps too; the same cleanup shows up in stopping ads and pop-ups in Chrome.
The reverse is just as real: a third-party antivirus can sandbox or block Chrome hard enough to crash it or stop it opening. If the trouble started after you installed security software, add Chrome to that program’s exceptions or allow-list, or briefly disable the antivirus to test, then turn it back on. Google flags antivirus interference as a reason Chrome will not open.
Reinstall Chrome as a last resort
If nothing above holds, the installation is likely damaged, and a clean reinstall replaces every program file. Uninstall first: open Settings > Apps > Installed apps, find Google Chrome, and choose Uninstall. Check the box to also delete your browsing data, so a corrupt profile does not survive the reinstall, which is exactly what Google advises. Then download a fresh copy from Google’s official Chrome page and install it. Turn sync back on to pull your bookmarks and passwords down again if you had it enabled.
To keep Chrome stable afterward, let it update on its own and relaunch when the colored dot appears, keep your extension list short and sourced from trusted developers, and install graphics-driver updates when Windows Update or the GPU maker offers them. If crashing returns, note which step fixed it last time and start there, because the same machine tends to fail the same way. And when Chrome still will not launch after a reinstall, the fault is usually the Windows user account or a system file rather than the browser, which fixing an app that will not open on Windows walks through.