Forum Discussion

ianknight2023's avatar
ianknight2023
Copper Contributor
Sep 21, 2023
Solved

STATUS_ACCESS_VIOLATION on Edge

STATUS_ACCESS_VIOLATION on Edge Hi Everyone, Yesterday (20/09/2023) edge started to frequently crash with a STATUS_ACCESS_VIOLATION error. Only when using Microsoft Dynamics 365 Business Ce...
  • NatalieKarolak's avatar
    NatalieKarolak
    Sep 22, 2023
    The issue is already being worked on. I have gathered everything here:
    https://nataliekarolak.wordpress.com/2023/09/20/this-page-is-having-a-problem-in-bc-web-client/
ParentElement's avatar
ParentElement
Copper Contributor
Jan 10, 2024
There's a possibility it could be CPU or thread related. I saw a couple posts of people saying they fixed it by replacing their CPU. I have a hard time believing the CPU I just installed a couple months ago is the issue, but I have been running a test. I just stream a tik tok live in a tab and wait for it to crash and it reliably does so (in chrome, firefox, and edge). So, I started it again, located the process for the tab, and set the affinity to only use CPU 0.... it's been running awhile now and no crash.
Rumtintin24's avatar
Rumtintin24
Brass Contributor
Jan 10, 2024
Interesting - in the past, when certain sites like Reddit had the issue a lot, I'd set affinity for that tab's process to like CPU0-4, then 5-10 if the issue occurred, and so on, but was never able to find the right choice.

Please let me know how that goes!
  • ParentElement's avatar
    ParentElement
    Copper Contributor
    Jan 10, 2024
    Definitely seems to be the issue. I located the browser tab in task manager and set affinity to only use CPU 0 and 1 and it worked fine. Worked my way through blocks of CPUs and narrowed it down to one... CPU 6. If CPU 6 is enabled, either by itself or with others, the access violation occurs. If I disable CPU 6 and enable one or all other cores, everything still works just fine.
    • Rumtintin24's avatar
      Rumtintin24
      Brass Contributor
      Jan 10, 2024
      That's great research! Now the question is - are you able to make that 'sticky?' Like - so that you don't have to turn off CPU 6 every time?
      • ParentElement's avatar
        ParentElement
        Copper Contributor
        Jan 10, 2024
        Yes* Problem is that Windows lists the CPUs under affinity configuration 0 through 29. By my bios lists performance cores 0 through 7 and E Cores 0 through 22 or whatever. I can turn off cores individually, but evidently P-Core 6 does not equate to CPU 6 in Windows so it's trial and error to figure out which one I'd have to disable.