Status Access Violation issues

Hey Youssef,

You can tell Lasso which cores to use it on, and which processes to use it on. Just select the processes from its big list, and set CPU Affinity.

I have found it best to just define one Affinity list using Options -> CPU -> CPU Affinities, and then right click on a process (or select multiple) and use that predefined one.

Mark

Hey Jami.

When you're setting CPU Affinity, you can choose Current or Always.

Current means Lasso will keep it like that until the process goes away (or your PC is rebooted).

Always means that Lasso will cleverly remember to use it for that process always, whenever it is active (even on different PC boots).

Note that you can highlight many processes (or even all of them with Ctrl-A) and set CPU Affinity for all at once.

(This will not work for low level Windows and system processes though, but it does capture everything else.)

I've found I only really need to use it for some browser sessions.

Mark

OMf**kingG,
Finally this fixed it for me.
Thank you all for sharing this
Error free browsing bliss

I'm so happy I had to write a poem XD

Here is the magic sauce

• Download Process Lasso
• Open Process Lasso and right click on chrome or any app giving you problems 🤞
• Choose from the dropdowns - CPU Affinity - Always - Select CPU Affinity
• Deselect first 6 cores
• Click Okay
• One less Microsoft curse per day

i now know what the problem is, i just dont know how to fix it.

it is to do with how many cores your CPU has and if you set affinity of your browser to 1-2 core it wont happen but you have to do it every time you launch the browser so if anyone have any solution to that problem then nice

Thank you for this response, just following up on the use of Project Lasso as I've never used it before. Did you disable these cores specifically for chrome and the other browsers or was there some global setting somewhere?

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