Forum Discussion
ianknight2023
Sep 21, 2023Copper Contributor
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...
- Sep 22, 2023The 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/
NatalieKarolak
Sep 22, 2023Copper Contributor
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/
https://nataliekarolak.wordpress.com/2023/09/20/this-page-is-having-a-problem-in-bc-web-client/
- Rumtintin24Jan 10, 2024Brass Contributor
NatalieKarolak Hi there - any new updates on this? I see the last one was in Sep. I've tried all of the commonly reported solutions (rename executable, extensions, disable code integrity, etc.) to no avail. I still regularly get the error on Edge and I'm going to need to go to (shudder) Firefox soon.
Incredibly frustrating, considering how commonly this seems to be happening, based upon the reports across Reddit, here, etc.
Asus Z790 Maximus Hero
Windows 11
Intel i9-14900k
64G RAM
NVIDIA 4090
Thank you!
- radwocDec 10, 2024Copper Contributor
Hi all,
In my case problem is strictly connected to Intel i9 oxidation failure - as I know my processor i9-14900k is affected by this issue and what helped me to set in bios setting all cores to sync wtth 55 ratio. This temporary solved my problem untli new processor will arrive on warranty.
- ParentElementJan 10, 2024Copper Contributor
Rumtintin24 I have almost the same setup as you (except the CPU):
ASUS ROG Maximus Z790 Hero
64 GB DDR-6400 (G.Skill with XMP II Profile)
i9-13900K
RTX-4090
The problems started after the 23H2 update. I thought I had a hardware issue because there were other things failing as well. I replaced the motherboard AND the GPU (was using an RTX-3090 previously) because I couldn't install Video Card drivers. Everything else is running relatively smoothly (and was perfect prior to the update), but now I get browser tab crashes with STATUS_ACCESS_VIOLATION in both Edge and Chrome. Interestingly, tabs crash in Firefox while watching video as well. I've tested with my 4090, 3090, and a 2080 Ti I had lying around with no difference. CPU, RAM, and storage drives all test good with no errors. I'm baffled.- Rumtintin24Jan 10, 2024Brass ContributorThank you for that, it's incredibly frustrating. I did a full reset on Edge today - no luck. I have changed the executable name, I've disabled code integrity, CPU affinity, I've done the accessibility thing, none of it has worked. It happens with zero extensions enabled, also.
- NatalieKarolakJan 10, 2024Copper ContributorMy blog posts really reflects the very last information that I have collected: There has never been any official announcement again, or I was unable to find it.
However, I neither know about any other user who is still unhappy after a browser update.
Are you really using the latest Edge version 120.0.2210.121?- Rumtintin24Jan 10, 2024Brass Contributor
I'm on Version 120.0.2210.121 (Official build) (64-bit)
- ianknight2023Sep 22, 2023Copper Contributor
Thanks for the update. I did spot this before I started this discussion. The fix mentioned did not work me.
- NatalieKarolakSep 22, 2023Copper ContributorEven not the updated browser shortcut? People reported that (only) this worked for them.
- ianknight2023Sep 26, 2023Copper ContributorIn my Business Central Admin Center this morning there was a message about this issue. It restated the fixes you mentioned and also had instructions to turn off the windows accessibility feature "Text cursor indicator" which I had on. With that off Edge now works fine for me.
Thank you for your assistance.
Here is the full message
Message Summary
Following a recent update of Chromium based web browsers (Such as Edge and Chrome) to Chromium v117+ that took place in September 2023, some users may see error pages displaying Error Code: STATUS_ACCESS_VIOLATION when using the Business Central web client, regardless of Business Central version.
What action do I need to take?
If you encounter this issue, there are two potential workaround options to resolve the problem:
Disable the Accessibility feature:
If you are working in Windows, verify that the "Text cursor indicator" setting is turned off.
In Edge, open edge://accessibility in a new tab.
In Chrome, open chrome://accessibility in a new tab.
Disable Text metrics, Screen reader support, and HTML. Or try to disable Web accessibility instead, which might turn off the other options. (Note that your company admin settings might prevent changing these settings or cause the old setting to be restored shortly thereafter.)
Alternatively, add --disable-renderer-accessibility to your browser shortcut and restart the browser.
Why is this action needed?
We have identified that the update to Chromium v117+ introduced an accessibility feature which interferes with Business Central web client functionality. We have confirmed the issue with both the Edge and Chrome teams who are actively working on fixes for their browsers.