Chrome Crashes On One Site But Not Others
Short answer
Open the same site in a Guest window (profile icon → Guest). If it loads cleanly there, the cause is an extension or that site's stored data in your profile, not Chrome. If it crashes in Guest too, turn off Settings → System → Use graphics acceleration when available and retest — a broken GPU driver crashes tabs on sites that use video or canvas.
On this page
Every other site loads. One does not. It either shows “Aw, Snap!”, goes blank white, or hangs long enough that Chrome offers to kill the page.
This is a better problem to have than general instability, because the cause is narrow. A crash confined to one site means some specific thing that site does — a video codec, a WebGL canvas, a large table, a particular script — is colliding with something specific on your machine. Finding which takes about ten minutes and the order matters.
Read the error code first
When the crash page appears, look at the small text under the message. Chrome names the failure, and the name tells you where to start.
| Error code | Usual meaning | Start with |
|---|---|---|
STATUS_ACCESS_VIOLATION |
Renderer touched memory it should not | Extensions, then GPU |
STATUS_BREAKPOINT |
Hit a debug trap, often an extension | Extensions |
Out of Memory |
The page genuinely exhausted the tab | Close other tabs, 64-bit check |
STATUS_STACK_BUFFER_OVERRUN |
Security software or a bad injection | Antivirus, extensions |
| No code shown | Renderer hung rather than crashed | Hardware acceleration |
Do not read too much into the exact code. It narrows the search; it does not identify the culprit.
The test that answers it fastest
Click your profile icon in the top right and choose Guest. A Guest window runs with no extensions, no cookies, no stored site data and default settings, and it takes five seconds to open.
Load the problem site in it.
- Loads fine in Guest — the cause is in your profile. An extension, or the site data Chrome has stored for that domain.
- Crashes in Guest too — the cause is Chrome-wide: hardware acceleration, the graphics driver, or something hooking into Chrome from outside.
That single result cuts the remaining work in half, which is why it goes first rather than after a cache clear.
If Guest worked: your profile
Clear the data for that one site
Site-specific crashes are regularly caused by a corrupted IndexedDB store or service worker for that domain. You can clear exactly one site without touching anything else.
Open the site, click the icon to the left of the address bar, then Cookies and site data → Manage on-device site data → Delete. Chrome recent versions phrase this slightly differently between releases, but the control lives behind that icon in all of them.
You will be signed out of that site. Nothing else is affected, which is the point — a blanket clear would sign you out of everything for no extra benefit.
Disable extensions in halves
Open chrome://extensions. Rather than toggling one at a time, turn off the top
half, restart Chrome and test. If the crash is gone, the culprit is in that
half; if not, it is in the other. Repeat on whichever half contains it.
With sixteen extensions that is four tests instead of sixteen. Ad blockers, script managers, password managers and anything that rewrites page content are the usual offenders, because they inject code into the page before it finishes loading.
Once you have the name, check its Site access setting under Details. An extension set to run On all sites can be restricted to On click, which often keeps the extension useful while removing the collision.
If you find yourself doing this often, the systematic version is in how to find which Chrome extension is slowing you down.
If Guest also crashed: Chrome and the machine
Hardware acceleration
Sites that crash in every profile are usually doing something graphical — video, WebGL, a map, a canvas-heavy dashboard. Chrome hands that work to the GPU, and a driver that mishandles it takes the renderer down with it.
Go to Settings → System and turn off Use graphics acceleration when available. Close every Chrome window — properly, not just the one — and reopen. Test the site.
If it now works, you have confirmed the graphics path. Leave acceleration off only as a temporary measure: update the driver from NVIDIA, AMD or Intel directly rather than through Windows Update, then turn acceleration back on and retest. Chrome is noticeably better with it on, and permanently disabling it trades the symptom for slower video on every site.
chrome://gpu shows what Chrome currently believes. Entries reading “Software
only, hardware acceleration unavailable” mean Chrome has already blocklisted
your driver version.
Security software
Antivirus products that inject into browser processes to scan pages are a real
cause of STATUS_STACK_BUFFER_OVERRUN and similar crashes. Do not disable your
antivirus to test this. Add an exclusion for Chrome’s profile directory instead,
or check the vendor’s own settings for a “browser protection” or “web shield”
module and turn off that module alone.
Check you are on 64-bit Chrome
Open chrome://version and look for “64-bit” after the version number. A
32-bit Chrome on a 64-bit Windows install is limited to roughly 4GB of address
space per process and will hit out-of-memory crashes on heavy sites that 64-bit
Chrome handles. Reinstall from Google’s site if you find 32-bit.
When the site is simply at fault
Some crashes are the site’s. A page with an infinite loop, a 50,000-row table, or a video stream in a codec your machine cannot decode in hardware will fail for a lot of people, not only you.
Two quick confirmations: open the site in a different browser, and open it on your phone. If it fails everywhere, you have found a broken website and there is nothing on your machine to fix. The wider version of that diagnosis is in when a website works in one browser but not another.
Reporting it is worth sixty seconds if the site matters to you. Most will never know otherwise.
What to expect
In practice, most single-site crashes come down to one extension or the stored data for that domain, and the Guest-window test plus a halving search finds both inside fifteen minutes.
Graphics-driver crashes are the stubborn category. They tend to affect several video or map sites at once rather than exactly one, and they genuinely do get fixed by driver updates — which is unsatisfying advice right up until it works.
If a site crashes in Guest, in another browser, with acceleration off and on a second machine, stop troubleshooting. It is their bug, and no setting on your computer will change it.