Forum Discussion
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 work without any problem.
I'm not using any third party antivirus software, just Windows Security.
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.
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
Edge 87.0.640+ and "STATUS_ACCESS_VIOLATION" it exists again on random pages like deviantart.
Windows 10 20H2 19042.508
- 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.
javiergualix the same problem in
Version 87.0.664.12 (Official build) beta (64-bit)pablodiloreto
I confirm for version 88.0.673.0 (Official build) dev (64-bit). Less frequently it seems, but the same nuisance.
javiergualix It happens to me too.
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.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.
javiergualix I struggled with this all afternoon and evening today on an older laptop I was trying to setup for my son till I found the problem was with the CPU and the solution the problem. On a fresh Windows 10 or 11 install, with nothing else but the OS installed, Edge would throw the STATUS_ACCESS_VIOLATION on every web page I tried to visit. Chrome would also do it on every web page. So it had to be a hardware problem since it was both browsers on fresh OS Win 10 and 11 installs. I swapped the RAM. Still did it. I ran the Windows mem test, which the memory passed. I swapped the SSD and did more fresh installs of 10 and 11, still STATUS_ACCESS_VIOLATION. The only thing left was the motherboard and CPU. I ran the Intel CPU Diagnostic Tool and it passed all tests. But I was thinking about one of the cores somehow being bad, or the hyperthreading. So I went to the Search Bar on the Win 10 taskbar and ran msconfig.exe, then to the "Boot" tab and then "Advanced Options." Here's where you can set the number of physical cores that are used by the Win 10 or 11 OS. You check the box for Number of Processors and then you can use the drop down to start limiting the OS to lower number of cores. My laptop CPU is older and has 2 cores and 2 hyperthreads so 4 cores show up in the drop down. When I set that to 2 and restarted, my STATUS_ACCESS_VIOLATION went away and the laptop would load every website without any issues. I tested it again by setting the Number of Processors to 3, restarted, and both Chrome and Edge immediately began again with STATUS_ACCESS_VIOLATION on every webpage. There's no need to test 4 cores, since that's the number of cores and threads on the CPU. So, apparently, there's a problem with one of the two cores on this Dell older laptop. Something that isn't picked up by the Intel Diagnostic Tool. The laptop feels noticeably slower. It's running at 50% cores. But it's a laptop for my 8 year old to do his school work and practice his typing class. It's a Dell Inspiron 7537 and the CPU seems to be soldered to the motherboard, or else I would try and swap the CPU. I hope this helps you. There's definitely something weird going on with the coding to the processor that's causing so many people to have STATUS_ACCESS_VIOLATION errors caused by a faulty core on a CPU.
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.
Nothing helps!Fresh installation of Windows 10 20H2
without Third-Party Software or other extensions
javiergualix Just installed Version 88.0.685.3 (Official build) dev (64-bit) which seems to cure the problem. As far as I can see after an hour of navigating and typing text in FB.
- The STATUS_ACCESS_VIOLATION Also deployed an unexpected error code: 0xC0000005 (0x00000000)
javiergualixDoes it keep happening when in Safe Mode with Networking? For me it stopped. Not a real solution, but it does seem to indicate it's not a hardware issue. Also, I've read elsewhere that some people have fixed it by uninstalling their 64bit browser and installing the 32bit version. Others changed the name of the browser .exe file. I will be trying these later.
Good morning,
I'm still convinced it was all hardware on the CPU. At least it was for me It's been awhile since I replaced mine and have not had the issue since. When before it was often enough to make me wipe my drives and start fresh, try basic drivers, all different chipset drivers. Different memory, different boot drive and the issue was always there for me right away.
For me though I'm thinking I still had the issue in safe mode. I don't remember 100% but I'm thinking I did. You can always turn off all non Microsoft services and roll back drivers. It seems you are getting close! It will be nice when you are done with it.
