New
#1
Affinity for program stuck at 0000FFFF
Hello all.
I used Process Lasso to set the bulk of my user processes to only use the E cores of my 13900k, that way the only programs that should have been using the P cores would have been games, and system processes.
Unfortunately, it seems this cause some strange bug with some programs, such that ALL programs now when launched for the first time are set to "/affinity 0000FFFF". Or at least, what should be that. All programs launch with only affinity for cores 16-31.
Some of my programs also seem to be STUCK in this affinity setting. Most of them are games.
Of course, this means since my programs only launch with the setting of 16-31 affinity, pretty much every game runs like crap, because these are all E-Cores. The P-cores are Cores 0-15. And worst of all, it has to be changed every time, and is NOT persistent.
Process Lasso seems to have lost control of the affinity for these programs that are stuck, leading me to believe there is some registry setting that is forcing this affinity.
Despite my efforts, google cannot find me how I fix this. And I can't find anyone else having this issue.
Here is an example of what happens:
1. Launch cod.exe (Call of Duty).
2. CPU Affinity is stuck in 16-31.
3. Attempt to use Process Lasso or any other program that can set affinity to set core affinity to "None" or "0-31".
4. Process Lasso says "Error 0x62 - Unable to change cod.exe affinity."
5. Open Task Manager.
6. Navigate to the process, set "Affinity" to "All Processors".
7. Performance issue is fixed. HOWEVER!
8. Close the program (in this case, cod.exe).
9. Close Process Lasso.
10. Re-open cod.exe.
11. Process is BACK in Affinity for only cores 16-31.
So what's going on! It's clearly not Process Lasso doing this, and the only program that seems to have any control over the Affinity for programs with this bug is Task Manager.
Any ideas?
Quote