STATUS_ACCESS_VIOLATION usually means a process tried to access memory it was not allowed to use. In Chrome or Edge, it can appear when a tab or browser component crashes. The wording does not identify one cause, prove a virus infection or mean a website intentionally blocked you.
Last updated:
Microsoft‘s access-violation explanation describes that memory-access error. The code is a starting point for troubleshooting, not a cause by itself.
Start with these low-disruption checks
- Reload the page once and try another ordinary website.
- Close unnecessary tabs and apps, then restart the browser.
- Install the current browser update and relaunch it.
- Restart Windows if a pending update or stuck process may be involved.
In Chrome, open Help > About Google Chrome. In Edge, use Help and feedback > About Microsoft Edge. Google’s browser-crash guide covers common checks.
Check whether an extension or profile is involved
Try the page in a private window, noting that some extensions can still be allowed there. If that works, temporarily disable nonessential extensions and restore them one at a time to find a conflict. Avoid changing many settings at once, or you will not know which change helped.
A separate temporary browser profile can help compare behavior without deleting your current profile. Make sure important bookmarks and account-recovery details are safe before considering a reset. Google’s page-loading troubleshooting explains extension and memory checks.
Use the pattern to narrow it down
| Pattern | Useful next check |
|---|---|
| One page fails in several browsers | Try another network or device and check the site’s support information. |
| One profile fails | Compare extensions and saved site data. |
| One browser fails everywhere | Update or repair that browser through its official installer. |
| Several unrelated apps crash | Check Windows, drivers and hardware stability. |
If the problem is an unwanted search provider rather than a crash, our default search-engine guide addresses that different setting.
Does antivirus software cause this error?
A conflict is one possibility, not a diagnosis from the error code alone. If crashes began after a security-product update, check that vendor’s current support advice and update the product. Do not leave protection disabled as a routine workaround. The same caution applies to disabling the browser sandbox or adding unknown command-line flags.
Renaming the browser’s EXE is not a general repair and can interfere with updates or shortcuts. Use supported update, repair or reinstall procedures instead.
When should you check the PC itself?
If unrelated programs also fail, note any recent driver, hardware or memory-setting changes. Start with supported updates and a clear description of the failures rather than assuming all memory errors have one fix.
Our DxDiag guide helps collect system and graphics details for support. Our RAMMap guide explains memory use; emptying a standby list is not a guaranteed cure for a browser crash.