Chrome has been reported to crash on some people with STATUS_ACCESS_VIOLATION errors that were also affected by the latest version of Chrome Canary. Google is aware of the stability and canary problems. Google previously activated the “Renderer Code Integrity” security function in the Chrome browser on Windows 10. The company then deactivated the function and reactivated it after a while.
Chrome Help Forum users have reported that Chrome crashes frequently and has STATUS_ACCESS_VIOLATION (access status violations) errors. The user checked many things to fix the problem, but it didn’t work. The end user completely removed and reinstalled the Chrome browser, but the problem persists. Users can still use Chrome, but every time they use it, it crashes and users have to refresh the page 10 to 20 times to get it working again.
In contrast to the recommended answer, the access violation error in “Problems and error codes when loading pages” does not exist in AW_Snap! Help page.
The latest Chrome Canray v86.0.4195.0 is also affected and completely unusable.
It crashes every time you try to open a new tab or check for updates in the Help menu, which shows “Aw snap” and “This page could not be opened” with the error code Status_Access_Voilation.
- Start menu> Run> regedit
- Go to “\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome” (create a “Chrome” folder if it doesn’t exist
- Create an element called “RendererCodeIntegrityEnabled” (DWORD 32).
- Set the value 0 to “RendererCodeIntegrityEnabled”.
- Restart Chrome
Creating a New User Profile
- Close the Chrome browser and press “Windows-E” on the keyboard to start Windows Explorer.
- Type “% LOCALAPPDATA% \ Google \ Chrome \ User Data \” (without the quotes) in the address bar at the top of the window.
- In the window that opens, locate the “Standard” folder, right-click on the folder and select “Rename”. Name the folder “Standard Backup” (without the quotation marks).
- Start Chrome and try loading the webpage again.
At this time, Google hasn’t yet identified the issues, but they are getting a significant number of votes in Google’s official Chrome support forums. I have contacted Google and will update this article when I receive an update. If you are running the latest version of Chrome (three points> Help> Information) without any problems, you are clear, otherwise you may want to wait a little longer.
NEW UPDATE: The update of the Canary update 86.0.4196.2 solved the problem.