Jul 20 2020 12:03 AM
Jul 20 2020 12:03 AM
I'm receiving the error STATUS_ACCESS_VIOLATION when browsing after update to Edge 84. I'm trying to repro the issue, but it seems to happen randomly. If I hit "Refresh", the web returns to work without any problem.
I'm not using any third party antivirus software, just Windows Security.
Sep 13 2020 11:46 PM - edited Sep 22 2020 05:47 PM
@Da5h-au I am working on a customer's Windows 10 system and have observed the same issue but it actually extends to all Chromium-based browsers, even newly installed ones so the problem therefore logically resides in some shared code that all Chromium-based browsers access on a Windows-based computer, possibly in the registry or some other area. Some posts have suggested changing the browser executable file name to anything other than what it is named. Ex. Chrome.exe >> Chrme.exe, apparently this has worked for some but not for the system I am working on. I then fired up Chromium Edge version 81.xxx and the problem disappeared at least for Edge, I have yet to try Chrome and Opera earlier versions. This is definitely a software bug introduced into either the Chromium code base and or Windows and only affects computers that have a unique set of circumstances otherwise this problem would have broken the Internet with outrage on all of Social Media and support blogs around the globe.
I will update my post if I find a solution and of course anyone please feel free to reply with a bug fix or workaround.
UPDATE: I reformatted and performed a clean install of Windows 10 Home and the exact same problem occurred.
The system was a Lenovo IdeaCentre Desktop, Intel Core i7-4790, DDR3-12800 RAM, Samsung EVO 860 SSD, Nvidia GeForce GTX 760 GPU.
I suspect that either the GPU or the motherboard or one of its components(chipset,NIC,sound, etc) is to blame given that I have refurbished or upgraded other systems with the same CPU,RAM, and SSD with no problems.
My workaround was to install a Chromium-based clone called Slimjet browser >>>https://www.slimjet.com/ and to also use Mozilla FireFox.
Hope that helps someone
Oct 15 2020 08:30 AM
@Robert84MK Happens almost once every few minutes on Facebook, almost systematically when invoking "Notifications". Sometimes also when I leave Facebook open idling in the foreground to get my coffee.
Both on a DELL Pro PC and on a Surface Pro. Both Windows 10 Dev
Nov 01 2020 07:51 AM
I have the same error with Edge and also Chrome.
The problem exists since version 78 of Chrome. Probably due to the renderer Code Integrity Feature.
See attached video.
Fresh installation of Windows 10 20H2
without Third-Party Software or other extensions
Nov 02 2020 08:34 AM
@javiergualix Problem persist in Version 88.0.680.1 (Official build) dev (64-bit).
Especially annoying, when you enter text and lose everything.
The issue is almost systematically reproducible when you click on Notifications in Facebook. But it also happens when a FB webpage is just sitting idle.
Nov 02 2020 12:28 PM
@benpal This is the bane of my existence. Azure DevOps crashes ALL the time and usually right as I'm done typing and about to save my comment/post.
I'm running Version 87.0.664.18 (Official build) beta (64-bit) and it's been crashing since 2-3 builds ago.
Nov 03 2020 12:33 PM
@DaveB89 Over the last hour I have been trying to write several comments in FB. I have lost several of them, some rather lengthy, due to this error. It happens quite frequently when hitting the Notifications bell, but also when Edge is idling with FB open or while typing text.
Six times in one hour, a record and a serious nuisance. Makes me want to change to a more reliable browser.
Dec 14 2020 05:14 PM
Apr 15 2021 09:14 PM