Status Access Violation issues

Anonymous
2023-12-01T01:16:57+00:00

Hello, i am getting Status_Access_Violation while watching youtube, twitch and browsing other sites on windows 11.

I reinstalled windows multiple times, reinstalled edge and chrome, cleared and reset browsers, deleted all cookies/history, reset flags, deleted all extensions, up to date on browsers, changed browser name extensions, text cursor indicator is off, did sfc /scannow, disabled hardware acceleration, happens with non updated drivers and updated drivers

Microsoft Edge | Website issues | Windows 11

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

80 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2024-06-10T17:52:00+00:00

    How did you identify which cores to avoid using?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-06-10T18:01:14+00:00

    The person who referenced the Ryzen sounded like they were having the same error but entirely different circumstances so it's probably not the same. Identifying the core(s) is trial and error. Disable specific sets and narrow it down until you find which are causing the issue.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. Anonymous
    2024-06-10T18:32:21+00:00

    You can set the process affinity in task manager or use process lasso to achieve the same.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2024-06-12T03:25:04+00:00

    You can use task manager, however, process lasso allows for selecting multiple processes at once, which is helpful.

    Unfortunately, setting the process affinity didn't solve the issue for me. I tried various combinations of different cores selected as well as disabling hyperthreading, but didn't have any luck.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2024-06-12T07:39:04+00:00

    Hey Dusty,

    Someone else on a different site said that it was a low numbered core that had the issue for them.

    That seemed likely for me also, since it occurred reasonably regularly, and I took a punt it would use lower numbered cores more often (I have no idea if this is true, but took a chance).

    In any case, with Lasso it's really quick and easy to deselect cores. I did that for the first 6 cores and the problem went away instantly on every browser, every app, every mode, for ever.

    I couldn't even bother narrowing it down further. I have lots of cores, and surely browsers can still work with 20+..!

    ps. I have no relationship to Lasso or any other app maker. Just worked for me and others.

    m

    Was this answer helpful?

    0 comments