Which CPU process handles Bluetooth?

[Sarra]

I'm running Process Lasso, and I'm trying to fix an issue with bluetooth dropping and lagging.

 

I just started using Process Lasso, and I've got my entire system running on 4C/8T, with games running on other cores/threads, depending on the number of threads these games typically use. However, I'm still having intermittent stutters, which coincide with my game controller dropping button inputs.

 

I'd like to move the CPU process off the 8T that the OS is using, and put it on it's own, unused threads, as a diagnostic.

[Agall]

12 minutes ago, Sarra said:

I'm running Process Lasso, and I'm trying to fix an issue with bluetooth dropping and lagging.

 

I just started using Process Lasso, and I've got my entire system running on 4C/8T, with games running on other cores/threads, depending on the number of threads these games typically use. However, I'm still having intermittent stutters, which coincide with my game controller dropping button inputs.

 

I'd like to move the CPU process off the 8T that the OS is using, and put it on it's own, unused threads, as a diagnostic.

 

I'm not seeing anything for bluetooth, but you could always try toggling it from the bottom right menu from the taskbar and see if you can spot a singular difference when it enabled versus disabled. Other than the driver that runs it, its looking like svchost.exe runs it.

[Sarra]

58 minutes ago, Agall said:

 

I'm not seeing anything for bluetooth, but you could always try toggling it from the bottom right menu from the taskbar and see if you can spot a singular difference when it enabled versus disabled. Other than the driver that runs it, its looking like svchost.exe runs it.

I typed 'bluetooth' into the search bar in Process Lasso, and it pulled up 3 processes. I dropped these onto their own 1c/2t group, changed the class from low to normal, and gave that a shot. Pretty cool, it reduced the frequency of dropped inputs drastically, though it still happens; going to chalk it up to local interferance, possibly from my mouse, or my Steam Deck trying to connect to headphones.