Forum Discussion
Solved
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 Central (other web apps work fine). Any help for fixing this is appreciated!
Edge Version: 117.0.2045.36 (Official build) (64-bit)
OS: Windows 10 Pro
Version: 22H2
OS Build: 19045.3448
Experience: Windows Feature Experience Pack 1000.19044.1000.0
Microsoft Dynamics 365
Cloud version
Application Version: 22.4.59114.59220
Platform Version: 22.0
- 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/
ianknight2023 Our organization resolved this issue by updating the system bios.
- I have added a section to my blog post to gather what you have found out:
https://nataliekarolak.wordpress.com/2023/09/20/this-page-is-having-a-problem-in-bc-web-client/#solution-beyond-business-central - who even uses edge 💀
- 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/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!
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.
Thanks for the update. I did spot this before I started this discussion. The fix mentioned did not work me.
- Even not the updated browser shortcut? People reported that (only) this worked for them.
ianknight2023 we're having exact same issues (for 1 user currently). Latest version of Edge, and W22H2
