Fix Chrome and Microsoft Edge’s ‘Status_Access_Violation’ Error

Chrome is reportedly crashing for some with STATUS_ACCESS_VIOLATION error, the latest Chrome Canary is also affected by this. Google is aware of the issue in the stable as well as the Canary. Since Microsoft Edge based on Chromium, it can also throw this error.

Aw, Snap! error always takes you back to issues users faced when Google enabled the “Renderer Code Integrity’ security feature in Chrome on Windows 10. The company disabled the feature later and re-enabled again after some time.

There are reports on Chrome help forums [1] [2] from users that Chrome crashes constantly and shows Status Access Violation as the error code for the crash.

I have looked up a lot of things in an attempt to fix this with none of them working. I eventually deleted chrome in its entirety and reinstalled it and the issue is still occurring. I can still use chrome but it crashes whenever I use it and I have to refresh the page 10-20 times before it starts working again.

I have this issue on my chrome browser “STATUS_ACCESS_VIOLATION”. How do I fix this? can someone help me, how can I fix this?

Both threads have a ‘Recommended answer’ from Platinum Product Expert that says, Chrome team has added two new sub-error codes to Aw Snap crashes page to find the cause for the crashes in the Chrome browser.

Hi all,

The Chrome team recently added these new sub-error codes to the “Aw, Snap!” error page to better diagnose the cause of crashes in Chrome. The best thing to do if you see these errors is to go to the Aw, Snap! help article which should resolve most of these issues.

Contrary to the recommended answer, Access violation error doesn’t exist under “Page loading error codes and issue” in the AW_Snap! help page.

The latest Chrome Canray v86.0.4195.0 is also affected and is totally unusable.

It is crashing whenever you try to open a new tab or check for updates in the Help menu by showing “Aw snap” and “can’t open this page” with Error code: Status_Access_Voilation (check the screenshot below).

The Chromium team is aware of Canary’s issue, expect it to fix this soon. You’ll likely get a working Canary with the next update.

UPDATE: Canary update 86.0.4196.2 has fixed the issue.

It’s worth noting that Google yet to find a fix for Chrome issues on Windows 10 2004.

If the release version of Chrome or Microsoft Edge browser is affected with this issue, follow the steps given below to see it resolves the problem for you.

Fix Status_Access_Violation error on Chrome and Microsoft Edge

Google Chrome

1. Right click on Chrome shortcut on desktop, select Properties
2. Click open File Location
3. Rename Chrome.exe  to Chrom.exe or something else. This is the super trick that fixed and worked for most users that affected by aw snap error.

Microsoft Edge

1. Right click on Microsoft Edge shortcut on desktop, select  Properties
2. Click on Open File Locaiton
3. Rename msedge.exe to msed.exe or something else.

Has your Chrome or new Edge is giving this error? Let us know in the comments below.

Related articles:

Google disables Renderer Code Integrity feature in Chrome 78 after Aw, Snap! Crashes

Fix Chrome 79 crashes with Aw, Snap! error

Google investigates Chrome’s Sign out/Sync Issues on Windows 10 2004