When Chrome crashed, the fastest fix is usually to just reopen it: close any leftover Chrome process, launch it again, and look for a prompt offering to restore your tabs. If that does not happen, Ctrl+Shift+T (Cmd+Shift+T on Mac) reopens tabs one at a time, and History (Ctrl+H) has the full list of pages you had open. If Chrome keeps crashing, the exact error message (a plain “Aw, Snap!” page or a code like STATUS_ACCESS_VIOLATION) tells you whether the problem is one page, an extension, or something deeper on your device.
This guide covers what a genuine Chrome crash looks like, what the error codes mean, how to restart safely, how to get your tabs back, and what to do if it keeps happening. It also covers the gap every browser’s own recovery leaves open: tabs that were never visited, and windows a crash happened to catch between saves.
A crash is different from a slow page, a frozen window, or Chrome simply asking to update. Knowing which one you are dealing with saves time, because each has a different first fix. A Chrome browser crash can come from a single bad tab, a graphics driver, or something on your device — the sections below walk through each.
What Does It Mean When Chrome Crashed?
A crash means the Chrome process itself closed unexpectedly (the window disappears, or you see an “Aw, Snap!” page) rather than Chrome staying open but becoming unresponsive. Chrome runs each tab, and many extensions, in their own separate process, so a crash in one of them does not necessarily bring the whole browser down with it.
That design is also why crashes vary so much in severity. Sometimes you lose a single tab and everything else keeps running; other times the main browser process itself goes down and the whole window disappears. The table below is a quick map from your situation to the right first step.
| Situation | What to do first |
|---|---|
| Chrome crashed once; only one tab shows an error | Reload the tab. If it fails again, try it with extensions off |
| The whole Chrome window closed on its own | Reopen Chrome — most versions restore your tabs automatically |
| Chrome will not reopen at all | Force-quit any leftover Chrome process, then relaunch |
| Chrome crashes every time it starts | Relaunch with extensions disabled, or check chrome://crashes |
| Tabs are missing and no restore prompt appeared | Check History (Ctrl+H) and Recently closed tabs (Ctrl+Shift+T) |
Crash, not freeze. A crash closes the Chrome process. If your window is still open but nothing responds when you click, that is a freeze, not a crash — see our guide to Chrome freezing for the right first steps there.
For Google’s own troubleshooting steps, start with Fix Chrome if it crashes or won’t open on support.google.com.
What Do Chrome’s Crash Codes and Error Pages Actually Mean?
Chrome’s crash pages give you a short label, not a full explanation, but the label narrows down what went wrong. Here is what the common ones point to.
| What you see | What it generally means |
|---|---|
| “Aw, Snap!” with no code | A single tab or page crashed; the rest of Chrome is unaffected |
| STATUS_ACCESS_VIOLATION | A Windows memory-access error. Frequently linked to graphics drivers, a damaged profile, or an extension, per widespread reports in Google’s Chrome Help Community |
| “Out of Memory” under the sad-page icon | The page, or your device, ran out of available memory — often from too many tabs or one memory-heavy site |
| Chrome window disappears, no message at all | Usually a full browser crash; check chrome://crashes after reopening for a report ID |
| Chrome opens, then closes immediately | Often a corrupted profile or a conflicting extension or startup item |
STATUS_ACCESS_VIOLATION is not one single cause. This code shows up across many different root causes, from GPU drivers to specific extensions. Treat it as a starting point for troubleshooting, not a diagnosis on its own.
For a formal record of what happened, type chrome://crashes into the address bar (crash reporting needs to be turned on). It lists recent crash report IDs you can reference when searching for a fix or reporting the bug to Google. If you want Google to see the specific crash, use the Chrome menu, then Help, then Report an issue, and mention the crash and, if you have one, the report ID.
Not every crash produces a code at all. A quiet crash with no message, where the window simply closes, is still worth checking chrome://crashes for afterward, since Chrome sometimes logs more detail there than it shows you on screen at the time. Google’s own page on page loading errors covers the “Aw, Snap!” message specifically, including steps for when it happens on a single page rather than the whole browser.
How Do I Restart Chrome After a Crash?
Reopen Chrome the normal way first; if the window or process is stuck instead of gone, force-close it before you try again.
- Give it a moment. Some crashes recover in place, or a single tab shows “Aw, Snap!” while the rest of Chrome keeps running.
- Reopen Chrome normally. Click the icon or use your usual launcher. This is enough after most one-off crashes.
- Force-close a stuck Chrome on Windows. Press Ctrl + Shift + Esc, find Google Chrome in the list, and click End Task. Then relaunch.
- Force-close a stuck Chrome on Mac. Press Cmd + Option + Esc, select Chrome, and click Force Quit. Then relaunch.
- Try a clean relaunch. Typing chrome://restart into the address bar closes and reopens Chrome in one step, which is useful after installing an update or a driver fix.
Relaunch beats reboot. A full computer restart can fix a crash, but it is rarely necessary. Force-closing Chrome and reopening it solves the same problem in far less time.
If you were filling out a form or writing a long comment when Chrome crashed, that text is usually gone once the process closes, since it lived only in memory. Chrome cannot recover typed text the way it can recover a list of open tabs, which is one more reason it is worth reloading a page the moment you notice trouble rather than continuing to type into a tab that is already failing.
How Do I Get My Tabs Back After Chrome Crashes?
Chrome usually tries to restore your last session on its own; if it does not, History and Recently closed tabs almost always still have your pages. For a broader walkthrough of every restore method Chrome offers, see our full guide to restoring tabs in Chrome.
- Look for the restore prompt. After a crash, Chrome often shows a prompt or reopens your tabs automatically when you relaunch it.
- Turn on “Continue where you left off.” Open Settings, go to On startup, and choose Continue where you left off, so this happens by default after any future crash.
- Check History. Press Ctrl + H (Cmd + Y on Mac) for the full list of pages you had open, in order.
- Reopen recently closed tabs. Press Ctrl + Shift + T (Cmd + Shift + T on Mac) repeatedly to step back through the tabs from this session, one at a time. See how to reopen closed tabs for the equivalent shortcut in other browsers.
- Check chrome://crashes if pages are still missing. It will not bring tabs back, but the report ID helps if you need to search for the specific cause.
Restoring a session, whether through Chrome or BelayTab, is not always instant if you had a very large number of tabs open. BelayTab opens large sessions in batches of 20 so the browser does not stall trying to load everything at once, and tab groups, pinned tabs, and tab order are preserved rather than flattened into one long strip.
Chrome Crashed vs. Chrome Frozen: What Is the Difference?
A crash closes Chrome; a freeze leaves the window open but unresponsive to clicks or typing. They need different first steps, so it is worth telling them apart before you start troubleshooting.
If your Chrome window vanished, or you landed on an “Aw, Snap!” page, that is a crash — the fixes in this guide apply. If Chrome is still on screen but will not respond, close, or switch tabs, that is a freeze, and the right first move is usually Chrome’s own Task Manager rather than a force-quit. Our other guide covers that scenario, plus every other reason Chrome stops responding, step by step.
The two can also look similar from a distance: a browser that is about to crash sometimes freezes for a few seconds first, as a tab or extension consumes memory or CPU right up until Chrome gives up on it. If Chrome is slow to respond and then closes entirely a moment later, you were watching the lead-up to a crash rather than a separate problem.
Why Does Chrome Keep Crashing on Windows?
Repeated crashes on Windows most often come down to graphics drivers, an extension, or a low-memory device, in roughly that order of likelihood.
- Outdated GPU driver. Chrome uses your graphics driver for rendering. An old or mismatched driver is a common cause of STATUS_ACCESS_VIOLATION-style crashes.
- A misbehaving extension. Extensions that run on every page are a frequent culprit. Disable them all, then re-enable one at a time.
- A corrupted profile. Creating a new Chrome profile and seeing if the crashes follow you tells you whether the profile itself is damaged.
- Too little free memory. Many open tabs, heavy sites, or other running apps can starve Chrome of the memory it needs.
Update drivers from the manufacturer, not blindly. Only install graphics driver updates from your PC or GPU manufacturer’s own site or Windows Update. Skip anything a random pop-up or search result recommends.
Work through the four causes above in order, testing after each change rather than changing everything at once. That way, if the crashes stop, you know exactly what fixed it, and if a later Windows or Chrome update reintroduces the problem, you know where to look first.
Why Does Chrome Keep Crashing on a Mac?
On a Mac, recurring crashes usually trace to an extension, a corrupted profile, or macOS itself needing an update, since Chrome relies on the operating system’s own graphics and memory handling.
Start with the same isolation steps as Windows: disable all extensions and re-enable them one at a time, then try a new Chrome profile to rule out a damaged one. If crashes continue in a clean profile with no extensions, check for a pending macOS update, since Chrome depends on current system libraries to run reliably.
If Force Quit does not seem to fully close Chrome — for example, the icon disappears from the Dock but a Chrome Helper process is still using CPU — open Activity Monitor, search for Chrome, and end any remaining Chrome or Chrome Helper processes before you relaunch. A leftover helper process can make it look like Chrome crashed again immediately, when it never fully closed the first time.
Why Does Only One Tab or Site Crash Chrome?
A single site crashing Chrome usually means that page is asking for more memory or graphics processing than its own process, or your device, can supply, rather than a problem with Chrome as a whole.
Heavy pages (long video calls, graphics-intensive web apps, or sites running many scripts) are the most common repeat offenders. If the same site keeps crashing its tab, closing other tabs to free memory before reopening it is a reasonable first test.
It is also worth checking whether an extension is active specifically on that site. Extensions that inject their own scripts into every page you visit can conflict with a site’s own code in ways that only show up on certain pages, which is why a site-specific crash can still be an extension problem in disguise.
What if Chrome Crashes Every Time It Opens?
A crash on every launch usually points to a startup extension, a damaged profile, or a leftover Chrome process that never fully closed, and each has its own quick test.
First, make sure no Chrome process is stuck in the background using Task Manager or Force Quit, then relaunch. If it still crashes immediately, try opening Chrome with extensions disabled, since a broken startup extension is a common cause of this specific pattern. If neither helps, a new Chrome profile isolates whether your existing profile itself is the problem, and reinstalling Chrome is the last resort after ruling out drivers, extensions, and the profile.
A new profile is a genuinely useful test because it starts with none of your extensions, saved settings, or history, so it tells you immediately whether the crash is caused by something in your existing setup or by Chrome itself. If Chrome runs fine in a brand-new profile, the fix is narrowing down which extension or setting in your old profile to remove, rather than reinstalling the whole browser.
Can I Recover Tabs That Were Never in Chrome’s History?
Sometimes yes, but only with a tool that saved them before the crash, since Chrome’s own History only records pages you actually visited, not blank or unloaded tabs sitting in the background.
Tabs you opened but never navigated away from a new-tab page, or tabs Chrome had not finished loading, will not show up in History or Recently closed tabs, because Chrome never logged a visit for them. This is the gap that catches people most often after a real crash.
Sleeping or discarded tabs (ones Chrome unloaded from memory to save resources while you were not using them) are also easy to lose track of, since they look identical to a normal tab until you notice their content has not loaded. If a crash happens while several tabs are in that state, Chrome’s restore may bring back a blank placeholder rather than the page you expected, and History will only show pages that had finished loading at some point.
A second safety net for exactly this gap. BelayTab does not read page content or depend on History. It snapshots the tabs themselves (including ones you never navigated on) every 5 minutes and whenever a window closes, so they show up in its Recovery screen even when Chrome’s own tools have nothing to offer.
How Do I Stop Losing Tabs the Next Time Chrome Crashes?
The most reliable fix is not to depend on any single recovery method: combine Chrome’s own “Continue where you left off” setting with a tool that saves your sessions independently of the browser.
Turning on Continue where you left off under On startup is worth doing regardless, since it is free and built in. But it only helps when Chrome detects an improper shutdown and only restores what Chrome itself tracked. BelayTab adds a layer underneath that: automatic snapshots every 5 minutes and whenever a window closes, unlimited sessions and tabs with no account required, and a single Recovery screen that combines those snapshots with deleted sessions and the browser’s own recently closed windows.
Chrome’s built-in Sync, if you are signed in, is a different tool for a different problem: it carries your bookmarks and history to another device, and can show tabs open on other devices, but it is not a session-by-session snapshot of every window the way BelayTab’s automatic saves are. BelayTab’s own optional Sync is a paid add-on for people who want their saved sessions themselves, not just history, available across browsers and on the web at app.belaytab.com; the free, local snapshot and recovery features work fully without it.
BelayTab cannot fix or prevent a Chrome crash — nothing running inside the browser can. What it does is make sure that whatever tabs you had open before the crash are still somewhere you can find them afterward.
How Do I Prevent This From Happening Again?
Reduce how often Chrome crashes by keeping it and your graphics drivers updated, reviewing extensions periodically, and not letting sessions grow so large that a single window is carrying more tabs than your device comfortably handles.
Chrome updates itself automatically in most setups, but a full restart is sometimes needed for an update to finish applying, which itself can look like an unrelated crash. Pruning extensions you no longer use, and saving heavy research sessions as separate named sessions you can close and reopen later, keeps any one window lighter and less likely to be the one that goes down.
A short routine covers most of it: keep Chrome and your OS on the latest version, review extensions every few months and remove ones you no longer use, and split large research projects into their own saved sessions instead of one window that keeps growing. None of that guarantees Chrome will never crash again (no browser can promise that) but it reduces how often it happens, and a saved session means a crash costs you a restart, not your tabs.