Chrome Aw Snap Error Fix: Why Pages Crash and How to Stop It

You are in the middle of something — reading an article, filling in a form, half-watching a page load — and the tab just gives up. In its place you get a sad folder icon, the message Aw, Snap!, and underneath it: Something went wrong while displaying this webpage.

It looks alarming, but it rarely means your computer is broken. Usually it is one tab, one extension, or one damaged file in your Chrome profile. That is why a simple chrome aw snap error fix normally works, without reinstalling anything.

Start simple: reload the page, close tabs you do not need, and restart Chrome. If the crash keeps coming back, work through the fixes below in order, from quickest to biggest.

What the ‘Aw, Snap!’ Page Actually Means

Chrome runs its tabs largely in separate processes, which is why one page can crash while the rest keep working. The Aw, Snap! page is what Chrome shows when the process for that tab stops unexpectedly.

The page gives you very little detail. In some cases a result code is mentioned alongside a crash — names like STATUS_ACCESS_VIOLATION come up, for example — but the exact code rarely changes your first steps. Treat it as a general crash warning, not a diagnosis.

A few causes account for most cases:

• Low memory. Chrome, other apps, or too many open tabs have used up the available RAM.
• A problem page. A heavy site or misbehaving script can crash while other sites work fine.
• A faulty extension. Extensions sit inside your tabs, so a buggy one can bring pages down with it.
• A corrupted Chrome profile. Your profile holds your cache, cookies, and settings. If part of it is damaged, crashes can follow you from site to site.
• Outdated Chrome. Crash bugs get fixed in updates, and an old build misses those fixes.

One clue helps a lot. If only one website crashes, the problem is probably that site or something cached for it. If almost every site crashes, look wider — at extensions, memory, your profile, or Chrome itself. If Chrome also feels slow before crashing, see our guide to a chrome high memory usage fix, because memory pressure and these crashes often go together. Google also covers this crash on its Fix “Aw, Snap!” page crashes and other page loading errors help page.

Start With These Quick Checks

Before you change any settings, rule out temporary glitches. These checks take a few minutes and fix many one-off crashes.

1. Click Reload on the Aw, Snap! page, or press Ctrl + R. If the page hit a short memory spike, it may load normally second time around.
2. Close tabs you are not using, especially tabs with video, large documents, or pages left open for hours.
3. Close other heavy apps too — games, photo or video editors, and other browsers — then try the page again.
4. Fully close Chrome and open it again. Make sure it has actually quit, rather than just closing one window.
5. If the crash still returns, restart the PC. Choose Start > Power > Restart, not Shut down, because Restart fully reloads Windows.

Either the page now loads and stays loaded, or the crash returns quickly and in the same way. If it returns, move on. A page that freezes instead of crashing is a different problem, covered in our chrome page unresponsive fix.

Start With a Simple Chrome Aw Snap Error Fix: Clear Cache and Cookies

Your cache stores pieces of pages so sites load faster next time, and cookies store sign-ins and preferences. If either holds damaged data for a site, Chrome can crash every time it tries to rebuild that page, even though the site itself is fine.

Clearing both gives the page a clean start. You will be signed out of most websites, so make sure you know your passwords first.

1. Click the three-dot menu in the top-right corner of Chrome.
2. Click Settings.
3. Click Privacy and security in the left-hand menu.
4. Click Clear browsing data.
5. Set Time range to All time.
6. Tick Cookies and other site data and Cached images and files. You can leave Browsing history unticked if you want to keep it.
7. Click Clear data.
8. Reopen Chrome and visit the page that was crashing.

If the page now works, bad cached data or a broken cookie was the likely cause.

Turn Off Extensions One by One

Extensions are the next most common culprit. Ad blockers, shopping helpers, and security add-ons all change how pages load, and one bad update can make a stable browser crash all day.

Turn them all off first, then switch them back on in small groups, so you can see which one is responsible.

1. Click the three-dot menu and choose Settings.
2. Click Extensions in the left-hand menu, or type chrome://extensions in the address bar and press Enter.
3. Switch off the toggle on every extension card. You do not need to remove them.
4. Restart Chrome and use the sites that were crashing for a few minutes.
5. If the crashes stop, return to Extensions and turn on one or two at a time, restarting Chrome and testing after each group.
6. When the crash returns, the last group you enabled contains the problem. Leave that extension off, click Remove on its card if you do not need it, or open its Details to look for an update.

If pages still crash with every extension off, extensions are not your problem. Turn the ones you trust back on and keep going.

Update Chrome to the Latest Version

An outdated browser can carry bugs that have already been fixed. Chrome normally updates in the background, but an update sometimes waits for a restart, or never quite finishes.

1. Click the three-dot menu and open Settings.
2. Click About Chrome at the bottom of the left-hand menu.
3. Chrome checks for updates automatically. If one is available, it starts downloading.
4. Click Relaunch when it appears, to finish the update.
5. Return to About Chrome and confirm it says Chrome is up to date.

If Chrome was several versions behind, browse normally for a while before changing anything else, so you know whether the update fixed it.

Turn Off Hardware Acceleration

Hardware acceleration lets Chrome hand graphics work to your computer’s graphics chip. On most PCs this makes pages smoother. On some, especially with older or buggy graphics drivers, it causes flickering, black pages, and tab crashes. Turning it off is a safe, reversible test.

1. Open Chrome Settings.
2. Click System in the left-hand menu.
3. Switch off Use graphics acceleration when available.
4. Click Relaunch when Chrome asks, so the change takes effect.
5. Use Chrome normally and watch whether the crashes stop.

If they stop, leave the setting off — most people notice little difference day to day.

Test in an Incognito Window and With a Fresh Profile

This step separates problems tied to your current profile from problems affecting Chrome as a whole. An Incognito window starts without most extensions and without your usual cookies and site data, so it makes a quick first test.

1. Press Ctrl + Shift + N to open an Incognito window.
2. Visit the site that keeps crashing and use it for a few minutes.
3. If it works fine here, your regular profile — its extensions, cache, or cookies — is involved.

If Incognito still crashes, try a completely fresh profile. A profile is simply a separate set of bookmarks, history, and settings inside the same Chrome install.

1. Click your profile picture or initial in the top-right corner of Chrome.
2. Click Add or Add Chrome profile, depending on your version.
3. Choose Continue without an account if you only want to test.
4. Open the crashing site in this new profile and use it for a while.

If the fresh profile is stable, your main profile is likely damaged — the final section below explains what to do. If even a fresh profile crashes, the problem sits deeper, in the Chrome install, Windows, security software, or hardware. Crashes affecting every tab are also covered in our guide on chrome tabs keep crashing.

Run Chrome’s Safety Check

Chrome has a built-in Safety Check that checks whether Chrome is up to date, whether Safe Browsing is on, and whether any harmful extensions are installed. It will not repair a damaged profile, but it is quick and can flag something you would otherwise miss.

1. Open Chrome Settings.
2. Click Privacy and security.
3. Under Safety Check, click Check now.
4. Wait for the check to finish and read each result.
5. Follow any prompt it gives you, such as updating Chrome or removing a flagged extension.

A clean result is useful too: it makes a simple update or security problem less likely.

If the Crashes Started After an Update

Timing matters. If the Aw, Snap! page only appeared after a Chrome or Windows update, do not assume you broke something. Updates occasionally introduce a bug — and often a smaller follow-up update corrects it.

1. Open Settings > About Chrome and check again. If a newer build is waiting, install it and click Relaunch.
2. Check for a pending Windows restart. Go to Start > Settings > Windows Update and look for a restart message. If there is one, restart the PC, then test Chrome.
3. On the Extensions page, look for an extension that updated around the same time. Switch it off for a day and see whether the crashes stop.
4. If everything else works, give it a little time. A widely shared update bug is normally fixed by the next Chrome build.

Change one thing at a time here, and test before moving on. Otherwise, when the crashes stop, you will not know what helped.

When a Fresh Profile or Reinstall Is the Real Answer

If you have cleared the cache, tested extensions, updated Chrome, tried hardware acceleration off, and the fresh profile worked perfectly, your old profile is almost certainly the problem.

The gentler option is to keep using the new profile and move your important things across:

1. In your old profile, press Ctrl + Shift + O to open the Bookmarks Manager.
2. Click the three-dot menu there and choose Export bookmarks. Save the file somewhere easy to find.
3. Switch to the new profile, open the Bookmarks Manager again, and choose Import bookmarks from the same menu.
4. Sign in with your Google account if you use sync, and reinstall only the extensions you actually need, one at a time.

The stronger option is a full reinstall, which also makes sense if even a fresh profile crashes or Chrome will not update properly. Google’s Chrome won’t start or crashes help page covers the same situation from the won’t-open side.

1. Export your bookmarks first, using the steps above.
2. Close Chrome completely.
3. In Windows, open Settings > Apps > Installed apps.
4. Find Google Chrome, click the three dots next to it, and choose Uninstall.
5. Restart your PC.
6. Download Chrome again from Google’s Chrome download page and install it.
7. Import your bookmarks, and browse for a while before adding extensions back.

There is also a middle step: resetting Chrome’s settings. Type chrome://settings/reset in the address bar. Restore settings to their original defaults turns off extensions and clears temporary data, while keeping your bookmarks, history, and saved passwords. Try it before a reinstall if your fresh-profile test was unclear.

Do not reinstall Windows for a browser crash — that is a last resort for system-wide problems.

Frequently Asked Questions

Why does Aw, Snap! keep happening on the same website?

Usually because something stored for that site — a damaged cached file or cookie — is broken, or the page itself is unusually heavy. Clearing cache and cookies often fixes a single-site crash. Try the site in an Incognito window too. If it crashes there and on a fresh profile, the problem may be on the website’s side.

Will I lose my bookmarks if I reinstall Chrome?

Not if you prepare first. With sync on, your bookmarks and passwords return when you sign in again after reinstalling. To be safe, export your bookmarks to a file before you uninstall, as described above.

Can my antivirus cause Aw, Snap! crashes?

It can. Security software sometimes works inside browser traffic to scan pages, and if that clashes with Chrome or an extension, tabs can crash. If the crashes started after your antivirus updated, temporarily turn off only its web protection and test Chrome. If the crashes stop, check its settings for a browser compatibility option.

Does Aw, Snap! mean I have a virus?

On its own, no. It is Chrome’s general crash page, and the usual causes are memory, extensions, cached data, or a damaged profile. Run Safety Check and a scan with your security software if the crashes come with other odd signs, like a changed homepage or pop-ups.

How do I stop Aw, Snap! on a PC with very little RAM?

Keep fewer tabs open, and close other apps before using heavy sites like video platforms and online editors. Turn off extensions you do not use, as each uses memory even when idle. Restarting Chrome once a day helps too. Adding RAM is the only permanent fix, but these habits make a low-memory PC far more usable.

Why does only one tab crash while the others are fine?

Because Chrome keeps tabs in separate processes. One page can run out of memory, hit a script error, or trip over a bad extension while the rest carry on. That separation is deliberate — it stops one bad page taking the whole browser down.

What Usually Fixes It

For most people, the Aw, Snap! page has an ordinary cause. Low memory and too many tabs account for many one-off crashes, and extensions and damaged cached data for most repeat ones. A corrupted profile is less common, but when the fresh-profile test works and nothing else does, that is usually the answer.

So work in order: reload, close things down, restart. Then clear the cache, test extensions, update Chrome, and try hardware acceleration off. Move to a new profile or reinstall only once those fail. That order is, in practice, the chrome aw snap error fix that works — because it finds the actual cause instead of throwing every fix at the browser at once.