The STATUS_ACCESS_VIOLATION error, also logged as an Access Violation or General Protection Fault (GPF) in some diagnostic tools, crashes Chrome or Edge mid-session and shows the “Aw, Snap!” page with an error code instead of your content. An access violation occurs when a program tries to read or write to a memory address it does not have permission to use. Windows blocks the operation and kills the tab to prevent further damage. The error appears on single tabs, specific sites, or sometimes across the entire browser depending on the cause.

Fix STATUS_ACCESS_VIOLATION Error
Before trying any fix below, refresh the page two or three times. A temporary memory conflict causes the error in many cases, and a quick reload clears it. If the crash keeps returning, work through the fixes in order.
1. Update Chrome or Edge
An outdated browser version carries unpatched memory management bugs that trigger STATUS_ACCESS_VIOLATION. Updating takes under two minutes and resolves the error for most users.
For Google Chrome:
- Click the three-dot menu in the top-right corner.
- Go to Help and select About Google Chrome.
- Chrome checks for updates automatically and downloads them.
- Click Relaunch to apply the update.
For Microsoft Edge:
- Click the three-dot menu in the top-right corner.
- Go to Help and feedback and select About Microsoft Edge.
- Edge downloads any available update automatically.
- Click Restart to finish the update.
2. Rename the Browser .exe File
Windows Exploit Protection sometimes flags the browser executable and triggers the access violation. Renaming the .exe file bypasses that flag without disabling any security features. This fix works on both Chrome and Edge.
For Google Chrome:
- Right-click the Chrome shortcut on your desktop and select Open file location. If you cannot find a shortcut, press Win + S, search for Chrome, right-click the result, and select Open file location.
- Alternatively, press Win + E to open File Explorer and paste this path in the address bar:
C:\Program Files\Google\Chrome\Application - Right-click chrome.exe and select Rename.
- Change the name to chrome1.exe or any other name.
- Relaunch Chrome and check if the error is gone.
For Microsoft Edge:
- Press Win + E to open File Explorer.
- Paste this path in the address bar:
C:\Program Files (x86)\Microsoft\Edge\Application - Right-click msedge.exe and select Rename.
- Change the name to msedge1.exe or any other name.
- Relaunch Edge and check if the error is gone.
Note: Some versions of Chrome install under Program Files (x86). If the path above returns empty, check that folder instead.
3. Disable Browser Extensions
Faulty or outdated extensions interfere with the browser’s memory handling and cause crashes. GhostPoster malicious browser extensions infected over 840,000 users across Chrome, Firefox, and Edge, which shows how much damage a single bad extension can cause. Disable extensions one by one to find the problem extension.
For Google Chrome:
- Click the three-dot menu.
- Go to Extensions and select Manage Extensions.
- Toggle off each extension individually.
- Restart Chrome after disabling each one and check if the error returns.
For Microsoft Edge:
- Click the three-dot menu.
- Select Extensions and then Manage Extensions.
- Toggle off extensions one by one.
- Restart Edge after each change and test the browser.
Remove any extension that triggers the error. If you added a new extension recently, start with that one.
4. Disable Hardware Acceleration
Hardware acceleration offloads rendering tasks to your GPU. On some systems, this causes memory conflicts that produce the STATUS_ACCESS_VIOLATION error, especially after a driver update or Windows update.
For Google Chrome:
- Click the three-dot menu and open Settings.
- Scroll down and click Advanced.
- Under System, toggle off Use hardware acceleration when available.
- Click Relaunch.
For Microsoft Edge:
- Click the three-dot menu and open Settings.
- Scroll down and click System and performance.
- Toggle off Use hardware acceleration when available.
- Click Restart.
Test the browser after restarting. If pages load without crashing, the GPU was causing the conflict.
5. Clear Browser Cache and Cookies
Corrupted cache files and cookies cause repeated crashes on specific sites or pages. Clearing them removes the damaged data and forces the browser to reload everything fresh.
For Google Chrome:
- Click the three-dot menu.
- Go to More tools and select Clear browsing data.
- Set the time range to All time.
- Check Cookies and other site data and Cached images and files.
- Click Clear data.
For Microsoft Edge:
- Click the three-dot menu and open Settings.
- Go to Privacy, search, and services.
- Under Clear browsing data, click Choose what to clear.
- Select Cookies and other site data and Cached images and files.
- Set the time range to All time and click Clear now.
6. Create a New Browser Profile
A corrupted user profile stores damaged session data, preferences, or cookies that crash the browser every time it loads. Creating a new profile gives the browser a clean slate to work from.
For Google Chrome:
- Click the profile icon in the top-right corner of the browser.
- Click Add to create a new profile.
- Set up the new profile and test if the error persists.
For Microsoft Edge:
- Click the profile icon in the top-right corner.
- Select Add profile and then Add.
- Follow the prompts to finish setup.
If the error stops on the new profile, your original profile was corrupted. You can import Chrome passwords to Microsoft Edge and other saved data to avoid starting from zero.
7. Reset Browser Settings to Default
Incorrect or conflicting browser settings trigger STATUS_ACCESS_VIOLATION in some cases. Resetting to default clears all custom flags, startup pages, and search engine settings without deleting bookmarks or saved passwords.
For Google Chrome:
- Click the three-dot menu and open Settings.
- Click Reset settings in the left sidebar.
- Select Restore settings to their original defaults.
- Read the notice and click Reset settings to confirm.
For Microsoft Edge:
- Click the three-dot menu and open Settings.
- Scroll to Reset settings in the left sidebar.
- Click Restore settings to their default values and confirm.
8. Run an SFC Scan to Repair System Files
Corrupted Windows system files cause browser memory errors that no browser-level fix can solve. The System File Checker scans and repairs damaged files automatically.
- Press Win + S, type cmd, right-click Command Prompt, and select Run as administrator.
- Type the following command and press Enter:
sfc /scannow- Wait for the scan to finish. It may take several minutes.
- Restart your PC after the scan completes.
- Reopen Chrome or Edge and test for the error.
If SFC finds and repairs files, the browser should load pages without crashing after the restart.
9. Check for Malware
Malware modifies browser memory and injects code that causes access violations. Run a full scan with Windows Defender or your installed antivirus to check for threats.
- Open Windows Security from the Start menu.
- Go to Virus and threat protection.
- Click Scan options and select Full scan.
- Click Scan now and wait for the process to complete.
- Remove or quarantine any detected threats.
- Restart your PC and test the browser.
If you prefer a dedicated tool, a STATUS STACK BUFFER OVERRUN error can sometimes appear alongside STATUS_ACCESS_VIOLATION when a third-party security product interferes with browser memory. Check if any antivirus or firewall application is flagging the browser process and add it to the exceptions list if needed.
10. Reinstall the Browser
If none of the above fixes work, a fresh installation removes all corrupted files and registry entries. Reinstalling takes about five minutes and resets everything cleanly.
For Google Chrome:
- Press Win + R, type appwiz.cpl, and press Enter.
- Find Google Chrome in the list and click Uninstall.
- Download the latest version from the official Chrome website.
- Run the installer and relaunch Chrome.
For Microsoft Edge:
- Open Settings and go to Apps.
- Find Microsoft Edge, click the three-dot menu next to it, and select Modify.
- Choose Repair first. If the error continues, return and select Uninstall.
- Download the latest version from the official Edge website.
- Run the installer and relaunch Edge.
Frequently Asked Questions
What causes STATUS_ACCESS_VIOLATION in Chrome?
The most common causes are an outdated browser version, a faulty or malicious extension, GPU hardware acceleration conflicts, a corrupted user profile, and damaged Windows system files. In some cases, Windows Exploit Protection flags the browser executable directly. Work through the fixes above starting with the browser update, then extension isolation.
What is the STATUS_ACCESS_VIOLATION error in Chrome?
The STATUS_ACCESS_VIOLATION error means Chrome tried to read or write to a memory address it does not have permission to access. Windows also logs this as an Access Violation or General Protection Fault (GPF) in some diagnostic tools. The browser kills the tab and shows the “Aw, Snap!” page with the error code in place of the content.
How do I fix STATUS_ACCESS_VIOLATION quickly?
Refresh the page two or three times first. That clears most temporary memory conflicts without any other steps. If the crash returns, rename the browser .exe file, then disable extensions one by one to find the problem.
Why does STATUS_ACCESS_VIOLATION keep happening on YouTube?
YouTube pages use heavy GPU rendering, which makes them more sensitive to hardware acceleration conflicts. Open Chrome or Edge settings, disable hardware acceleration under System, and relaunch the browser. The YouTube crashes stop for most users after that single change.
Does STATUS_ACCESS_VIOLATION happen in Edge too?
Yes. Chrome and Edge share the same Chromium engine, so the error appears in both browsers for the same reasons. Every fix in this guide works for both. Rename msedge.exe instead of chrome.exe when following the .exe rename method.
Can extensions cause STATUS_ACCESS_VIOLATION?
Yes. Extensions that hook into page rendering or network requests often trigger access violations. Go to Manage Extensions, toggle each one off, and restart the browser after disabling each. The extension that stops the crash is the problem one. Remove it permanently.
