Google Chrome recently added specific error codes to the “Aw snap” crash pages. You can see a collection of Chrome and Edge error codes here. My attempt is to document each of them and provide workarounds and fixes whenever possible.
Now that Edge is also based on Chromium, you will see similar error messages there too. We will look at troubleshooting steps for Microsoft Edge (Chromium) as well.
Google is actively working on resolving this issue. The first troubleshooting step that you must do is updating Google Chrome.
If you are on an older version, update it to the latest version, restart Chrome and try again. If you are still getting the error, continue with the workarounds provided in this article.
status_access_violation – Workaround
status_access_violation is an error message that I could not find any workarounds or fixes for. However, on one of the Chrome forum threads, user Will B 7332 has provided the following workaround. Looking at the responses, there are a few users who found this useful.
- Locate the Chrome application. You will most likely find this in c;\Program Files (x86)\Google\Chrome\Application.
- Rename the Chrome executable to anything other than Chrome. For example, chm.
- Open Chrome again and test.
If this workaround resolves your issue, please let us know in the comments section. It will be useful for other readers.
Review Extensions -Tampermonkey
Review your Chrome extensions. Visit chrome://extensions on a new tab and check all the installed extensions.
If you have Tampermonkey extension installed, uninstall this, restart Chrome and try again. If you find any other extensions that you no longer use, uninstall them as well.
I will update this article when more workarounds or a permanent fix becomes available.
status_access_violation – Microsoft Edge
The first thing you should do is to update Edge to the latest version. Check this by going to Settings > Help and Feedback > About Microsoft Edge.
If that does not work, we can try a workaround.
For the status_access_violation error on Edge, we can try the same workaround as Chrome. Here is what you should do:
- Open C:\Program Files (x86)\Microsoft\Edge\Application
- Rename the msedge.exe to something else, anything other than its current name.
- Restart Edge.
Update: This bug is already reported to Google. You can track the status here.