Forum Discussion

javiergualix's avatar
javiergualix
Copper Contributor
Jul 20, 2020

STATUS_ACCESS_VIOLATION after Edge 84 Update

Hi,   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 w...
BUG
Edge 84
Stable
STATUS_ACCESS_VIOLATION
Da5h-au's avatar
Da5h-au
Copper Contributor
Jul 24, 2020

I am getting the same, I think it has to do with Chromium as the same on Chrome but not on Firefox.

 

If not fixed soon will change default to Firefox.

  • Steves_Computer_Repair's avatar
    Steves_Computer_Repair
    Copper Contributor
    Sep 14, 2020

    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

    • cmir93's avatar
      cmir93
      Copper Contributor
      Apr 16, 2021
      Hey, I hope you get this. I have a very very similar problem to your customer. I found it to effect all chromium based applications. Chrome, discord, League of Legends game launcher. I find Status Access Violation, crashes, and video artifacts (during videos on Chrome). I have performed multiple full wipes and reinstallations of Windows 10. I have memchecked the RAM and tried each RAM stick on its own. I have replaced the motherboard. I have enabled Intel Integrated Graphics, plugged my monitor into the IO panel on the motherboard, and disabled the GPU in Device Manager (trying to isolate the issue to the GPU). I have replaced SATA cables. I have uninstalled antiviruses. NONE of these have solved anything. The only options I have left are changing the CPU and changing the boot drive.
      • Senghor's avatar
        Senghor
        Copper Contributor
        Jun 03, 2022
        2000
    • Rob84MK's avatar
      Rob84MK
      Brass Contributor
      Sep 22, 2020

      Steves_Computer_Repair 

       

      Edge 87.0.640+  and "STATUS_ACCESS_VIOLATION" it exists again on random pages like deviantart.

       

      Windows 10 20H2 19042.508

      • benpal's avatar
        benpal
        Iron Contributor
        Oct 15, 2020

        Rob84MK 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

  • JamoSA's avatar
    JamoSA
    Copper Contributor
    Sep 03, 2020
    I am also getting this error and it now looks like it is in FireFox as well. Getting very frustrated trying to find a solution to this issue.

Resources