Bitsum Community Forum

Hello. A few months back I had an issue with Battlefield 1 where I would get really bad intermittent audio pops and robotic crackle. I spent ages trying to find the issue until I ran into an old reddit post where they also had an issue on some EA games. Specifically Battlefield games. He said it was process lasso and recommended to uninstall it to eliminate the issue. Process lasso is very useful to me so that was a no no. To test it I tried different things like stopping the governor process, closing lasso, force closing lasso etc. and nothing worked. Finally decided to change the start up process and selected (Do not start at login) and core engine to (have it launched by the gui when it is run). Restarted my computer, booted BF1 for an hour without opening lasso and didn't have a single pop or crackle for hours. I reverted these settings, restarted pc, booted BF1 WITH lasso running and the pops and crackles came back. I did it multiple times to make sure it was process lasso that was causing these issues. I was able to identify and reproduce the issue 10/10 times. I left it alone because I stopped playing BF1 but now I am getting the same issues in Battlefield 6 beta. Now my question is why does this happen with these games? I'd would love for someone more experience with the program to help me find the root issue with lasso and these games so I don't have to shut down lasso at boot and restart the computer every single time I want to play a battlefield game. The action logs do not report anything on games exe's.

If the actions log reports no adjustments to that process and you've set no process rules, then there shouldn't have been any effect. It is, however, conceivable that some rule you've set on another process is impacting Battlefield.

Something that can also change when Process Lasso is removed is the power plan you're in. So, be cognizant of which power plan you're in when you are experiencing the crackling.

We'd need your config, which you can copy/paste from menu item "File / Manually Edit Configuration" and/or some complete logs to better assess what you're experiencing.

Quote from: Jeremy Collake on August 18, 2025, 12:37:55 PMIf the actions log reports no adjustments to that process and you've set no process rules, then there shouldn't have been any effect. It is, however, conceivable that some rule you've set on another process is impacting Battlefield.

Something that can also change when Process Lasso is removed is the power plan you're in. So, be cognizant of which power plan you're in when you are experiencing the crackling.

We'd need your config, which you can copy/paste from menu item "File / Manually Edit Configuration" and/or some complete logs to better assess what you're experiencing.

I just saw this sorry. Had email notifications off. I've been testing again and same thing. My settings are default. The only change I have is  a audiodg.exe rule. In a whole hour of gaming these are the only logs that appear. (attached image) It's always the same result. ProBalance Begun at launch and ProBalance restraint ended when I close the game. Only battlefield games are affected. Screenshot 2025-09-27 155427.png

[Administration]
Version=6320600
ConfigPasswordMD5=
[OutOfControlProcessRestraint]
OocOn=true
ExcludeChildrenOfForeground=true
DisableProBalanceWhenSysIdle=false
ProBalanceDropOneRandomCore=false
DoNotAdjustAffinityIfCustomized=true
OocDisableCoreParkingWhileIn=false
UseEfficiencyMode=false
DisableProBalanceIfSysIdleThisManyMS=30000
TotalProcessorUsageBeforeRestraint=10
PerProcessUsageBeforeRestraint=5
TimeOverQuotaBeforeRestraint=900
PerProcessUsageForRestore=2
PlayOnRestraint=C:\WINDOWS\media\Windows Pop-up Blocked.wav
PlayOnRestore=C:\WINDOWS\media\Windows Feed Discovered.wav
MinimumTimeOfRestraint=4200
MaximumTimeOfRestraint=0
TameOnlyNormal=true
LowerToIdleInsteadOfBelowNormal=false
ExcludeServices=true
PlaySoundOnRestraint=false
PlaySoundOnRestore=false
RestrainByAffinity=false
RestraintAffinity=
ExcludeForegroundProcesses2=true
DoNotLowerPriorityClass=false
LowerIOPriorityDuringRestraint=false
MatchExclusionsByPathnameToo=false
ChangeTrayIconOnRestraint=true
OocExclusions=
OocHardCodedExclusionOverrides=
[GUI]
ClearLogAtExit=false
ShowCPUCoreUtilGraphs=true
ShowGraphLegend=true
ShowGraphCPU=true
ShowGraphResponsiveness=true
ShowGraphMemoryLoad=true
ShowGraphProBalanceEvents=true
ShowGraphSelectedProcessesCPUHistory=true
ProBalanceCountersOnGraph=true
ShowGraphLicenseName=false
ShowPowerProfile=true
GraphShowTooltips=true
ShowCPUUtilityAsPrimary=true
[Advanced]
AutomaticUpdate=false
[Performance]
DefaultsLevel=327942
GracefulWaitTimeInMs=5000
UpdateSpeedGUI=1000
UpdateSpeedCore=1000
[Sampling]
SamplingEnabled=false
SamplingIntervalSeconds=900
SamplingOutputPath=
SamplingIncludePattern=*
SamplingExcludePattern=
[Performance]
ManageOnlyCurrentUser=false
ExitOnCloseWindow=false
SoundsOff=true
IsConfigWritable=true
ForcedMode=false
IgnoreProblematicProcesses=false
IgnoreSuspendedProcesses=false
SetTimerResolutionAtStartup=0
[ForegroundBoosting]
BoostForegroundProcess=false
ForegroundBoostPriorityClass=0x8000
ForegroundBoostGPU=-1
BoostOnlyNormal=true
BoostOnlyNormalGPU=true
ForegroundBoostExclusions=
[SystemTrayIcon]
UseStaticIcon=false
ShowResponsivnessInTrayInsteadOfProcessorUsage=false
[Logging]
LogDisable=false
IncludeCommandLines=false
LogSmartTrim=true
LogCPULimiter=true
LogEfficiencyMode=true
LogGroupExtender=true
LogCPUSets=true
LogProBalanceParkingChanges=true
LogProcessExecutions=false
LogProcessTerminations=false
LogProcessesDisallowed=true
LogDefaultPriorityAdjustments=true
LogDefaultAffinityAdjustments=true
LogProBalanceBegin=true
LogProBalanceEnd=true
LogInstanceLimitTerminations=true
LogPowerProfileChanges=true
[MemoryManagement]
SmartTrimIsEnabled=false
SmartTrimWorkingSetTrims=false
SmartTrimClearStandbyList=false
SmartTrimClearFileCache=false
ClearStandbyFreeRAMThresholdMB=1024
ClearStandbyOnlyInPerfMode=true
SmartTrimExclusions=
SmartTrimAutoMinimumRAMLoad=65
MinimumProcessWSSInMb=196
SmartTrimIntervalMins=15
[SysTrayBalloons]
EnableSystemTrayNotification=false
BalloonTipDuration=10000
ShowBalloonsForOocPriorityRestoration=false
[ProcessAllowances]
ApplyInstanceCountLimitsToAllUsers=false
AllowedProcesses=
DisallowedProcesses=
InstanceLimitedProcesses=
InstanceManagedCPUAffinities=
ProcessThrottles=
OneTimeProcessThrottles=
CPULimitRules=
[ProcessDefaults]
NamedAffinities=
DefaultPriorities=audiodg.exe,high
DefaultIOPriorities=
DefaultGPUPriorities=
DefaultMemoryPriorities=
ThreadPriorityBoosts=
DefaultAffinitiesEx=audiodg.exe,0,2
CPUSets=
KeepRunningProcessesEx=
[ProcessAllowances]
EfficiencyMode=
[ProcessDefaults]
MatchWildcardsToPathnames=true
MatchOnCommandLine=false
[AdvancedRules]
DivideCPUPercentThresholdsBySystemCPUCount=false
ProcessorGroupExtended=
ProhibitInternetExplorerExceptWhenAny=
WatchdogRules2=
[GamingMode]
GamingModeEnabled=false
GamingChangePowerPlan=true
TargetPowerPlan=Bitsum Highest Performance
GamingModeEngageForSteam=true
AutomaticGamingModeProcessPaths=
AutomaticGamingModeUserExclusions=
[PowerManagement]
StartWithPowerPlan=
Display=
PC=
[PowerSaver]
PowerSaver_IdleTime=0
EnergySaverEnabled=false
EnergySaverForceActivePowerProfile=false
EnergySaverUpPowerProfileName=
EnergySaverEvents=true
DisableEnergySaverDuringGamingMode=true
PowerSaver_Exclusions=

You should right-click bf1.exe and check "Exclude from ProBalance". You can alternatively add the exclusion via menu item "Options > CPU > ProBalance > Configure Exclusions...".

We are going to look into this further, as normally games wouldn't be acted on while they are in the foreground.  Can you check to see if bitsumsessionagent.exe is running? That process facilitates foreground process detection when the Governor is run as a service. Rarely, we've seen cases where its startup task was inadvertently disabled. It's also possible that there is something unique about this game.

Quote from: Jeremy Collake on September 29, 2025, 09:39:18 AMYou should right-click bf1.exe and check "Exclude from ProBalance". You can alternatively add the exclusion via menu item "Options > CPU > ProBalance > Configure Exclusions...".

We are going to look into this further, as normally games wouldn't be acted on while they are in the foreground.  Can you check to see if bitsumsessionagent.exe is running? That process facilitates foreground process detection when the Governor is run as a service. Rarely, we've seen cases where its startup task was inadvertently disabled. It's also possible that there is something unique about this game.

I excluded ProBalance from bf1.exe, restarted computer and the issue persists. I removed audiodg.exe rule as as well just to have Lasso run at default settings. bitsumsessionagent.exe runs at start up and remains running while playing the game. By the way, I had this issue on BF6 beta too. I'm expecting it to return with the official release. I also had issues on WWZ game months back but I haven't played since. Not sure if it was Lasso  related but BF1 and BF6 Beta sure were. There might be a conflict with Lasso the Frostbite Engine after 2016. Older Battlefield games don't have this issue. I'm going to test Battlefield 2042 which runs on the Frostbite Engine to see if I get the same audio pops with Lasso running. This is the post (https://old.reddit.com/r/pcmasterrace/comments/1gzbg0j/battlefield_1_audio_pops_skips_and_causes/) I ran into that helped me figure out it was Lasso. Here's the same guy(attached image) on a different post with someone else in comments saying they had the issue on the BF1.exe and also had Lasso installed.

Based on the logs and your rules, the only way Process Lasso would impact the game is through that ProBalance action. Therefore, I'm skeptical that this is the sole factor. The sporadic nature of the effect may make it difficult to correlate to a specific cause or adjustment.

In any event, we'll make sure that it is excluded from ProBalance under all scenarios. That said, it should be noted that normally ProBalance taking action on a process won't impact its performance.

Which game platform are you playing Battlefield games on? Steam or EA app?

Quote from: Jeremy Collake on September 30, 2025, 11:03:05 AMBased on the logs and your rules, the only way Process Lasso would impact the game is through that ProBalance action. Therefore, I'm skeptical that this is the sole factor. The sporadic nature of the effect may make it difficult to correlate to a specific cause or adjustment.

In any event, we'll make sure that it is excluded from ProBalance under all scenarios. That said, it should be noted that normally ProBalance taking action on a process won't impact its performance.

Which game platform are you playing Battlefield games on? Steam or EA app?

I launch on Steam and it opens the EA app. That's just the way it's configured at the moment. No way around it. I installed and tested Battlefield 2042 multiple times today the same way I tested BF1. Audio buzzing and pops when lasso is running and none after a PC restart and after setting auto start up off. I even uninstalled and played throughout the day for hours and didn't have audio issues. Reinstalled in the evening and started getting pops and buzzes in the first session of gaming. All my background programs remain the same so I doubt it's anything else. I think it's impossible to find the root issue honestly unless lasso was conflicting with other processes but I don't see any.