STATUS_ACCESS_VIOLATION after Edge 84 Update

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.