Forum Discussion
STATUS_ACCESS_VIOLATION after Edge 84 Update
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
- SenghorJun 03, 2022Copper Contributor2000
 - MovandJul 07, 2021Copper ContributorHey man did you find any solutions I have exactly the same issues ,Cpu R95950 x ,Mainbord X570f , Vga 3080 giga , pls let me know
- DaneGerousJul 07, 2021Copper Contributor
We have a very similar setup,
Ryzen 5000 series/x570/3080.
see my previous post and give the downcore in BIOS a shot to test or if you have another compatible CPU to run & test. I sent my findings to AMD and RMA'd the CPU. Haven't had one issue since.
- MovandJul 07, 2021Copper ContributorThanks man yeah I did same and now it's ok I just don't know is it bad to downcore CPU or not , btw Thanks again
 
 
 - DaneGerousMay 09, 2021Copper Contributor
I have struggled with this same issue and have gone through everything as you have. I have found my culprit and wanted to share. For me the issue is with the Hardware level of the CPU. Using the same CPU I downcore'd it in the BIOS (All the way to 2.) With no other changes, my errors in browsers have gone away, Errors in loaders have gone away. For me it is time to RMA this CPU, Good luck.
 - Steves_Computer_RepairApr 27, 2021Copper Contributor
As mentioned in my update, I suspect the root cause lies in either a single or combination of motherboard components such as the chipset, audio, networking, or storage controllers and the associated firmware and drivers. My workaround was to use the conservatively developed SlimJet Chromium-based browser as well as Firefox. Alternatively, upgrading the motherboard to a newer generation platform or even an AMD-based system will most likely be the fix in this case. Just make sure you have the latest firmware and drivers installed for all the hardware components before deciding on a new motherboard which will of course require newer types of RAM and CPU.
If you have the time and patience, you could also go back and install a really old version of Windows 10, say, 1803 or 1809 and see what impact Windows 10 has had on this issue.
Hope that helps,
Steve
 - MikeTApr 24, 2021Brass Contributor
I've been getting this often recently in the past few months.
I notice playing a video on Steam's store pages for any game will trigger the error, here's an example: https://store.steampowered.com/app/1113560/NieR_Replicant_ver122474487139/I've sent a feedback report to Edge.