Status Access Violation issues

i9 13900kf and replaced it with same. only way i figured it out was from these posts you can try limiting cores but i just decided to replace cpu as a whole.

browser occasionally displays a status_access_violation error. - Intel Community -doubt intel will replace it unless your persistent

BrowSer Keeps Crashing "STATUS_ACCESS_VIOLATION" & Artifacts - Troubleshooting - Linus Tech Tips

[SOLVED] - Cursed Computer - Chromium Status_Access_Violation and More | Tom's Hardware Forum (tomshardware.com)

seems like quite a few i9 13900 are affected

It's not Intel that's doing this. I have a Ryzen 5 5600X and I've been dealing with this for months now. So, the issue is still lurking - for me at least. I have a laptop that has a 6800U and I never ran into any of this status access nonsense. I tried inspecting all the extensions, settings, and what not and none of them were the culprit.

But for whatever reason, I seem to get this STATUS_ACCESS_VIOLATION a lot when watching YouTube videos. Almost no other pages seems to go trigger happy and trigger that message, so I'm so confused as to what YouTube could possibly be doing in the background that triggers this message on my desktop, but not my laptop and I'm getting sick of it.

It's not Intel specific but does point to a CPU issue. I finally replaced my CPU as well and the problem disappeared

Prior to that I had replaced the motherboard and gpu and gone through multiple reinstalls.

I had a similar issue with my PC. YouTube in particular, plus the login function on several websites. On both Edge and Chrome. For many months, after a few months post getting a new PC.

I also tried deleting cookies, resetting flags, hiding extensions, etc, etc. Seemed strange that it was both browsers.

Games and other apps were all fine.

Then I got a new symptom that gave more information. The login failures, which were not always failures - about 70% - got worse after I finished playing a game and tried logging in. Then it was about 99% failure, at random times while typing login info. This pointed to something physical, e.g. the hardware still being warm.

I found information elsewhere about disabling particular CPU cores. This has completely cured it for me, instantly.

Setting CPU Affinity for several of my cores using Project Lasso, means that Chrome and Edge won't use those particular cores.

And that has completely solved it.

For me it was in the low numbered cores.

(I have a 13900K with plenty more cores so that's not an issue for me!)

I suspect that's also why a CPU change fixes it for others. There's some combination of hardware, heat, timing plus the particular instructions that some programs run, on some particular cores (which are perhaps a bit weaker or less tolerant), that causes a timeout or error in the software.

FYI that I'm a software, hardware and systems engineer.

Perhaps we're pushing miniaturisation, number of cores, timing and spacing to such extremes that we're now getting these interactions. Needs better testing in the factories I think. :)

While it's easy to say it's the processer. It's not the processors' fault. It's the way windows 11 interacts with the hardware.
I have a dell g17 with RTX4070 i9 13900HX 64GB ram [non dell]. I forcefully wiped and downgraded my OS to windows 10 and the issue was gone 600 hours of chrome/edge usage no issue. Upgraded to windows 11 issue was back in 2 days.

So the only really fix is move back to 10 or move back to win 11 21h2 [my issue started after I moved to 22h2 and persisted in 23h2].

@Microsoft you should be publishing the root cause of this error instead of the 30 generic useless steps give to FIX the issue