How to Fix STATUS_ACCESS_VIOLATION Error on Chrome and Edge — 6 Proven Solutions

You’re reading an article, watching a video, or halfway through writing something important — and Chrome crashes. Not a slow freeze. Not a gentle “this page isn’t responding.” A full, instant crash with a sad face emoji and a message that says:

Aw, Snap! Error code: STATUS_ACCESS_VIOLATION

You refresh. It crashes again. You try a different tab. Same thing. You open Edge instead — same error. And now you’re wondering if your computer is broken.

It’s not. Your browser is trying to access a piece of memory that it doesn’t have permission to touch, and the operating system is shutting it down before it can do any damage. That’s what STATUS_ACCESS_VIOLATION means — an unauthorized memory access attempt. Sounds scary, but the fix is usually straightforward.

I’m going to walk you through six fixes in order of effort. Most people solve this within the first two.

What’s Actually Happening

Every program on your computer gets assigned specific blocks of memory to work with. Your browser gets its space, your music player gets its space, Windows gets its space. When a program tries to read or write to memory that belongs to something else — or to memory that doesn’t exist — the operating system raises a protection fault and kills the process.

In browsers, this typically happens for three reasons:

A browser extension has buggy code that tries to access memory outside its sandbox. This is the most common cause — one bad extension can crash your entire browser.

The browser’s own executable file has become corrupted, usually after a failed update or a partial installation. The corrupted file contains invalid instructions that point to wrong memory addresses.

An experimental feature (Chrome flag) that you or an update enabled is interacting badly with your specific hardware or driver setup.

Let’s fix each one.

Fix 1: Isolate the Extension That’s Crashing Your Browser

This is fix number one because it’s the cause in the majority of cases. Extensions run code inside your browser, and a single poorly coded extension can trigger STATUS_ACCESS_VIOLATION on every page you visit.

The quick test:

chrome://extensions    (for Chrome)

edge://extensions      (for Edge)

Toggle off every single extension. All of them. Then restart the browser.

If the crashing stops, you’ve confirmed it’s an extension. Now turn them back on one at a time, restarting the browser after each one. When the crashing returns, you’ve found the culprit. Remove it.

Extensions that commonly cause this error:

Ad blockers with aggressive filtering rules, VPN/proxy extensions that modify network traffic, screenshot and screen recording tools, and any extension that injects JavaScript into web pages. This doesn’t mean these types of extensions are inherently bad — but specific versions of specific extensions can have memory bugs.

If you’re using Chrome, try this shortcut first: Open Chrome in Incognito mode (Ctrl + Shift + N). Incognito disables all extensions by default. If Chrome runs perfectly in Incognito but crashes in normal mode, it’s 100% an extension issue.

Fix 2: Update Your Browser

This should take 30 seconds and it fixes the problem when it’s caused by a known bug that’s already been patched.

Chrome:

Menu (three dots) → Help → About Google Chrome

Edge:

Menu (three dots) → Help and feedback → About Microsoft Edge

The browser checks for updates automatically. If one is available, it downloads and asks you to relaunch. Do it.

Memory handling bugs get discovered and fixed constantly. Chrome has already patched multiple zero-day memory vulnerabilities in 2026 alone. If you’re running an older version, you’re running code with known memory issues. Updating is the single easiest fix.

After updating, if the error persists, move to the next fix.

Fix 3: The .EXE Rename Trick (Strange but Effective)

This one sounds weird, but it works for a lot of people — and there’s a real reason why.

For Chrome:

1. Close Chrome completely (check Task Manager — make sure no Chrome processes are running)
2. Open File Explorer → navigate to C:\Program Files\Google\Chrome\Application\
3. Find chrome.exe
4. Rename it to chrome1.exe
5. Launch Chrome using the renamed file

For Edge:

1. Close Edge completely
2. Navigate to C:\Program Files (x86)\Microsoft\Edge\Application\
3. Find msedge.exe → rename to msedge1.exe
4. Launch Edge using the renamed file

Why this works: Windows caches information about executable files — their location, their permissions, their memory allocation patterns. When you rename the .exe, Windows treats it as a new program and loads it with fresh cached data. If the old cache contained corrupted metadata that was pointing to invalid memory addresses, the rename bypasses it entirely.

You can rename it back to the original name afterward if you want, though some users report that the fix only sticks while using the renamed version.

Fix 4: Clear Your Cache and Cookies

Corrupted cache files are a sneaky cause of STATUS_ACCESS_VIOLATION because the browser tries to load them into memory, and if the file is corrupted, the memory read fails.

Settings → Privacy and Security → Clear browsing data

Set the time range to All time. Check these boxes:

• Cached images and files
• Cookies and other site data

Click Clear data. Restart the browser.

This forces the browser to rebuild its cache from scratch. Every website will need to reload fresh content, and any corrupted files that were causing memory errors are gone.

If you can’t even access Settings because Chrome keeps crashing:

Delete the cache manually. Navigate to:

C:\Users\[YourUsername]\AppData\Local\Google\Chrome\User Data\Default\Cache

Delete everything inside the Cache folder. Don’t delete the folder itself — just the contents. Then launch Chrome.

For Edge, the equivalent path is:

C:\Users\[YourUsername]\AppData\Local\Microsoft\Edge\User Data\Default\Cache

Fix 5: Reset Chrome Flags

Chrome flags are experimental features hidden behind chrome://flags. You might have enabled some yourself, or an update might have changed their defaults. Some flags modify how Chrome handles memory, rendering, or GPU processes — and they can conflict with your specific hardware.

chrome://flags

At the top of the page, click “Reset all”. This sets every experimental flag back to its default state. Restart Chrome.

For Edge, use:

edge://flags

Same process — Reset all, restart.

This is particularly effective if the error started after you enabled a specific flag or after a browser update changed flag defaults behind the scenes. You won’t lose any bookmarks, passwords, or settings — flags are separate from your profile data.

Fix 6: Reset Your Browser to Factory Defaults

If none of the above worked, the nuclear option is a complete reset.

Chrome:

Settings → Reset settings → Restore settings to their original defaults → Reset settings

Edge:

Settings → Reset settings → Restore settings to their default values → Reset

This resets your homepage, startup pages, search engine, new tab page, pinned tabs, content settings, cookies, and extensions. It disables all extensions and clears temporary data.

What it doesn’t delete: bookmarks, history, and saved passwords. Those are preserved.

After the reset, Chrome or Edge starts clean — like a fresh install without actually uninstalling. If a corrupted setting or data file was causing the memory access violation, this eliminates it.

When It’s a Hardware Acceleration Problem

There’s one more thing worth checking if the error specifically occurs on graphics-heavy pages — videos, games, complex animations:

Settings → System → "Use hardware acceleration when available" → turn OFF

Hardware acceleration offloads rendering from your CPU to your GPU. If your graphics driver has a bug or is outdated, the GPU can return invalid memory addresses to the browser, triggering STATUS_ACCESS_VIOLATION. Turning off hardware acceleration forces the CPU to handle everything, which is slower but more stable.

If disabling hardware acceleration fixes the crashing, update your graphics driver from your GPU manufacturer’s website (NVIDIA, AMD, or Intel). After updating the driver, you can try re-enabling hardware acceleration.

The Worst Case: Completely Reinstall

If absolutely nothing works — extensions disabled, browser updated, cache cleared, flags reset, settings reset, hardware acceleration off — and you’re still getting STATUS_ACCESS_VIOLATION:

1. Uninstall Chrome or Edge through Control Panel → Programs and Features
2. Restart your computer
3. Download the latest version from the official website (google.com/chrome or microsoft.com/edge)
4. Install fresh

This is the last resort because it removes everything — including your profile data if you’re not synced to a Google or Microsoft account. Make sure your bookmarks and passwords are synced before uninstalling.

But in my experience, you won’t need to go this far. Fix 1 (extension isolation) or Fix 2 (updating) solves the problem for the vast majority of users.