Chrome Keeps Crashing, Freezing or Going Black? Start From the Symptom
Sort the crash by what you actually see, decode Chrome's error codes, test Guest and a fresh profile safely, and fix freezes and black windows without losing data.

When Chrome keeps crashing, what you see on screen points to the cause. A vanishing window, an “Aw, Snap!” tab, a freeze and a black window each lead somewhere different; find yours in the table below.
First, Google’s quick checks: close tabs, extensions and apps you don’t need, since memory may have run out. Quit Chrome fully (More > Exit, or Cmd+Q on a Mac), reopen tabs with Ctrl/Cmd+Shift+T and restart the computer. Also update Chrome under More > Help > About Google Chrome.
Chrome keeps crashing on one site only? Try it in another browser; if it fails there too, blame the site or your connection.
| What happens | Look at first |
|---|---|
| Window closes or won’t open | A leftover process, your profile |
| One tab shows “Aw, Snap!” | That page, memory, an extension |
| An error code such as STATUS_ACCESS_VIOLATION | Whatever the code names |
| Page Unresponsive or (Not Responding) | A runaway tab or extension |
| Black, white or flickering window | Graphics acceleration, display settings |
| Crashes on a phone | Updates, cache, memory |
Chrome Keeps Crashing on Startup or Closes by Itself
If Chrome won’t open, a copy may still be running. On Windows, press Ctrl+Shift+Esc and end each Google Chrome task; turning off Continue running background apps when Google Chrome is closed (Settings > System) prevents this. On a Mac, press Option+Command+Esc and force quit Chrome.
Still nothing? Look for Chrome in your antivirus’s quarantine list, then try the throwaway profile.
If Chrome keeps crashing minutes after it opens, collect evidence. chrome://crashes lists only crashes recorded while reporting was on, so turn on Help improve Chrome’s features and performance (Settings > You and Google > Google services) and let it crash again. Google notes reports can include passwords and payment details, so consider turning it off afterward.
What “Aw, Snap!” and Chrome’s Error Codes Mean
“Aw, Snap!” means one tab’s page crashed, not the browser. Reload it, check your connection, then try Incognito, where extensions stay off unless you allowed them. If the page loads there, run the extension test or delete your cache and cookies (this signs you out of sites).
If Chrome keeps crashing on the same tab, close other tabs and restart Chrome, then the device. On Windows, Error code: Out of Memory points to the memory checks.
If Chrome keeps crashing with the same code on every site, the code matters more than the page:
- STATUS_ACCESS_VIOLATION (0xC0000005). Chrome, or code loaded into it, tried to use memory it couldn’t read or write. Only in Chrome? Run the Guest and extension tests. Other apps too? Undo any overclock and run Windows Memory Diagnostic (Win+R, then
mdsched). - STATUS_BREAKPOINT (0x80000003) or STATUS_STACK_BUFFER_OVERRUN (0xC0000409). Usually a deliberate stop after an error the process couldn’t safely recover from. Update Chrome, then run the same tests.
- STATUS_INVALID_IMAGE_HASH (0xC0000428). A module failed Windows’ hash check, usually unsigned third-party code (often security software) loading into Chrome’s page processes. Update or remove that program.
- RESULT_CODE_HUNG or RESULT_CODE_KILLED. A process stopped responding, or you, another program or the system ended it. See Chrome’s Task Manager.
- RESULT_CODE_GPU_DEAD_ON_ARRIVAL. The GPU process failed to start. See the graphics checks.
Test Guest Mode, Extensions and a Fresh Profile
These tests show whether Chrome keeps crashing because of your profile, an extension or the rest of the computer.
Removing a profile erases its bookmarks, history and passwords from the computer. Confirm sync is on, or export bookmarks (Bookmark Manager > More > Export Bookmarks) and passwords (Google Password Manager > Settings > Export passwords); delete that plain-text password file afterward. Rename folders; never delete User Data.
Open a Guest window
Profile icon > Open Guest profile (not on Chromebooks): no extensions, none of your data. If Chrome keeps crashing in your window but not here, blame your profile or an extension. Incognito still uses your profile.
Switch off extensions
In chrome://extensions, turn them all off, then back on one at a time until the crash returns.
Try a new profile
Profile icon > Add Chrome profile. Skip sign-in so sync can’t restore extensions. Stable here? The problem lives in the old profile.
Rebuild the old one
Quit Chrome, add .old to the profile folder’s name (Default becomes Default.old) and reopen Chrome. Quit again, then copy files such as Bookmarks over from the .old folder.
User Data lives at %LOCALAPPDATA%\Google\Chrome\User Data on Windows, ~/Library/Application Support/Google/Chrome on a Mac and ~/.config/google-chrome on Linux. The first profile is Default and added ones are Profile 1, Profile 2 and so on; chrome://version shows yours under Profile Path.
If Chrome keeps crashing too fast to reach Guest, start a throwaway profile from Command Prompt on Windows:start chrome --user-data-dir="%TEMP%\chrome-test-profile"
If that window stays stable, your profile is the problem.

When Chrome Keeps Freezing or Says Not Responding
Many “Chrome keeps crashing” complaints are really freezes. A Page Unresponsive dialog (Wait or Exit page) means one page’s script hung; “(Not Responding)” in the title bar is Windows saying the whole browser stalled. If it never recovers, end it in Windows Task Manager.
Once Chrome responds, open its Task Manager: Shift+Esc on Windows and Linux, or More > More tools > Task manager. Sort by Memory footprint or CPU, select a Tab or Extension row far above the rest and click End process (unsaved work in it is lost).
Then turn on Memory Saver (Settings > Performance, desktop only) at Moderate, Balanced or Maximum. Inactive tabs reload when you return; tabs playing media or holding a half-filled form stay active.
On Windows 11, a leaf beside Chrome’s background processes is usually Chrome’s own Efficiency mode for inactive tabs, not a fault. Undo it only where you set it by hand; Microsoft notes the mode can make some processes unstable.
Black, White or Flickering Chrome Window
Graphics are the suspect if Chrome keeps crashing with RESULT_CODE_GPU_DEAD_ON_ARRIVAL, or the window goes black, flashes white or flickers. On Windows, start with Microsoft’s flicker test: press Ctrl+Shift+Esc, and if Task Manager flickers too, suspect the display driver (Win+Ctrl+Shift+B resets it).
If only Chrome misbehaves, open chrome://gpu: “Software only” lines under Graphics Feature Status, or entries under Problems Detected, show where it struggles with your GPU or driver.
Next, turn off Use graphics acceleration when available in Settings > System (older versions and Google’s help say “hardware acceleration”) and relaunch, expecting higher CPU use while it’s off. If that fixes it, update the GPU driver and turn acceleration back on.
Still flickering? On a laptop with two GPUs, open Settings > System > Display > Graphics, pick Chrome (or add it with Browse) and try the other GPU: Power saving (usually integrated) or High performance (usually dedicated). Then, one at a time, turn off Use HDR (Settings > System > Display; the screen may go black briefly) and Variable refresh rate (the Graphics page’s default settings), and unplug any second monitor.

Chrome Keeps Crashing Everywhere? Security Software, Reset, Reinstall
Software that injects code into Chrome is a known crash source. In 2017 the Chromium team reported that Windows users with such software, often antivirus, were 15% more likely to have crashes; Chrome now blocks most of it, except Microsoft-signed, accessibility and input-method software. If your security suite appears in chrome://conflicts (Windows only), update it.
Next, run a full scan with Windows Security (Virus & threat protection > Scan options > Full scan) or your own antivirus, and uninstall programs you don’t recognize (Settings > Apps > Installed apps on Windows 11, Finder > Applications on a Mac). Search engine keeps changing too? See our guide to Chrome switching to Yahoo.
If Chrome keeps crashing after that, uninstall your security suite as a short test and check that Windows Security’s real-time protection is on. Then reinstall its latest version, or keep Windows Security if the crashes stopped.
Chrome keeps crashing even after the scan? Reset it: Settings > Reset settings > Restore settings to their original defaults. Per Google’s reset page, it keeps bookmarks and passwords but resets your search engine, startup pages, site settings and cookies, and turns off extensions, on every signed-in device. Reinstall last, ticking the delete-browsing-data box only after a backup.
Don’t start Chrome with --no-sandbox: Chrome itself warns that stability and security will suffer. The RendererCodeIntegrityEnabled policy, an old INVALID_IMAGE_HASH workaround, was removed in Chrome 118 and is ignored.
Chrome Keeps Crashing on Android or iPhone
On a phone, close other apps, pause downloads, swipe Chrome away and restart the phone, then update Chrome from Google Play or the App Store.
On Android, open Settings > Apps > Chrome and its storage page. Clear cache removes only temporary data. Manage space > Clear All Data (Chrome’s version of Clear storage) permanently deletes everything Chrome keeps on the phone, so save it for last; synced bookmarks and passwords return when you sign in.
On an iPhone, close Chrome in the App Switcher, then reinstall it if it still fails; turn on sync first if you can, since deleting the app erases anything stored only on the phone. Pop-ups or unfamiliar apps too? See how to remove a virus from your phone.
Frequently Asked Questions
Chrome keeps crashing, but Edge and Firefox work fine. Why?
Then the cause sits in Chrome’s own setup: your profile, an extension or injected software. Edge shares the engine but keeps its own profile and extensions.
Chrome keeps crashing on Android. Can I uninstall it?
Usually not: most Android devices can only disable Chrome, even though Google’s Android crash steps say to reinstall. Update it and clear its cache instead.
Why does Chrome keep saying Out of Memory?
A page needed more memory than its process could get. Close heavy tabs in Chrome’s Task Manager and turn on Memory Saver. On Windows, check that chrome://version shows (64-bit); a 32-bit build gets far less memory.
Start From the Symptom, Then Report It
Match the symptom first, and save the reset and reinstall for last, after a backup. If Chrome keeps crashing after that, post the crash ID from chrome://crashes on the Chrome Help Community, or browse our software and apps guides.





Leave a comment