Recent Posts

91

Bug Reports / Re: BitDefender (Antivirus) Not Hard-Coded; Hangs w/Constant CPU Affinity Reset

« Last post by Jeremy Collake on April 26, 2020, 03:08:12 PM »

Open 'Options / CPU / Configure persistent CPU affinities' and uncheck 'Match command lines' at the bottom. That seems to be the source of your troubles. I am evaluating it now. This issue appeared in the last final version, 9.7.5.

That option may be removed now that regular expression matching covers it.

Update: This will be fixed as of 9.7.6.9 beta.

Thank you for reporting this!

92

Bug Reports / Re: BitDefender (Antivirus) Not Hard-Coded; Hangs w/Constant CPU Affinity Reset

« Last post by nah1982 on April 26, 2020, 02:54:23 PM »

As you'll note from the screenshot, the only rule set is a default restriction of 0-15; I didn't put that, and if I click to set "No Default Affinity" it keeps that. The X rule set is to have ProBalance ignore it. Otherwise, no other rules are applied. It still results in SYSTEM trying to set the affinity and it faulting out, as noted at the bottom of the screenshot. You can also see by the attached ini that they are cleared as well.

Any assistance or guidance is appreciated. Thank you.

Sincerely,
Nathaniel Hatten

93

Bug Reports / Re: Issues running governor-as-service with limited rights user

« Last post by Jeremy Collake on April 26, 2020, 07:02:00 AM »

Steamwebhelper.exe should not induce performance mode. The last user to report that had accidentally added steamwebhelper.exe to their automatic gaming list, but I don't think that is the case with you. I'll take a look and see if I can figure out how it could happen, and maybe prevent it from ever inducing even if it is in a user-configured gaming path.

You don't need to do anything special for updates. Those issues running as a Limited User were fixed.

Performance Mode used to be called Gaming Mode, but people use it for more than games, and I didn't want it to be confused with Windows Game Mode. So it isn't changing back .

Regular Expressions will eventually come to the Automatic Performance Mode list, though not for the next final version scheduled for May 1.

As for your two INI files, one may be a backup created in a previous update (no longer done), particularly if it is in that same folder. If it is in some other folder, then it is probably debris from past use.

Thanks for the feedback! Let me know if I missed any of your questions.

94

Bug Reports / Re: Issues running governor-as-service with limited rights user

« Last post by ranko on April 26, 2020, 05:01:40 AM »

Wait .. I started over to have this all a little bit more controlled, not that some weired old config stuff is present
and to make it better reproduceable for you.

What I did:
- deinstalled PL
- removed all config file stuff <VOL>:\name\Eigene Dokumente\process lasso\{configs,log}
- installed PL 9.7.5.44
- used default parameters except customized configuration folder: <VOL>:\name\Eigene Dokumente\process lasso\{config,log}
- re-activated license for Pro version
- rebooted system

The 1st thing that I noticed after fresh reboot and loggin in is:
Without having configured anything on my own, that the system switched to "performance mode".

Process Name: steamwebhelper.exe
Action: Automatic Performance Mode ON
Automatic Performance Mode was turned on because a specific game process was found running.

I think it is not useful to enter performance mode only because steam starts up some supportive background services.

Wondering, didn't it work already properly in the past ?!

But Steam is not the only content provider for games. So I would propose to call this feature "Gaming Mode".

In "gaming mode" the machine should enter a configurable power profile, default: "Bitsum Highest Performance".

In the config section for gaming mode the user can
- maintain a list of full paths to game executeables and/or regular expression for process names
- enable steam detection by one or more customizeable regular expressions, default: "steamapps/common"

Even support for different Steam Libraries (which is supported by steam if you run out of diskspace) would be supported by this automatically, because I assume that in each of the configured Steam libraries there will be such a subfolder "steamapps/common" or another regular expression will catch all other cases. Even if you have another known directory structure with games like "G:\games".

95

Bug Reports / Re: Issues running governor-as-service with limited rights user

« Last post by ranko on April 26, 2020, 03:30:54 AM »

Hi guys,
hope you are well. Sorry I did not have much time the last weeks.
I entirely switched to Windows 10 and switched back to Process Lasso -STABLE train, currently using 9.7.5.44.

I noticed three problems:

1. Steam detection stays in "performance mode", even if the game ended.
    The bad thing: as a result of this "IDLE saver" does not work anymore because performance mode is still enganged.

Therefore I disabled Steam detection and simply configured everything that I need based on the X4.exe binary and get a 2nd problem.

2. X4.exe has been startet, in PL under active processes you see all the applied PL features in the rules column.
And although I configured, that the Power Profile "Bitsum Highest Performance" should "Always" be used for X4.exe
the Power Profile stays at "balanced" and "performance mode" is not being activated.
I noticed in the PL log that the power profile has not been changed.
And I see it also in the Windows Gadget, that the Profile stays at "Balanced", otherwise on unknown power profiles the Gadget would have shown nothing.
It only displays the three Windows default profiles or "nothing" = dark, nothing is lit.

3. Sometimes during gaming I notice that PC is in IDLE mode

4. After disabling Steam game detection mode and configuring all based on the X4 executeable "X4.exe" sometimes PC stays in balanced power profile.
I tried "forced mode" but this didn't change anything.
I stopped and restarted X4.exe then it worked, that Bitsum Highest Priority / Performance mode became active.

You can see it in this screenshot:


Question 1: is that correct behaviour, that performance mode stays on after a steam game has ended ?

If I remember right then it worked already "correct" in the past, that
- an ending steam game brings power profile back to balanced
- after the configured IDLE timer the PC is being set to IDLE
- that during a game IDLE saver does not put the PC into the chosen power profile "power saving"

Question 2: Or did I remember wrong, that Steam detection always worked based on recognition of the steam executable that you see in the Windows info bar.
But that would be bad, because in default installation it will be started automatically.
I tweaked it already by disabling the startup entry, but it will startup once I start a steam game and then runs in the background.

Question 3: is it still required under Win10, to fully install PL after update ? We had an issue where front/backend were out of sync, something didnt work,
and then you asked me to perform an over-installation of the real installer. Or do the update procedures work under Win10 ?

Question 4: I can't remember having worked with profiles in my new setup after reinstallation. Why do I have two different prolasso.ini files ?
According to the time stamps both become updated.

I am running PL in service mode and the config is in a folder under "documents" that I fully own.
Here is my current config:

<VOL>:\name\Eigene Dokumente\process lasso\configs\prolasso.ini

[Administration]
Version=4680500
ConfigPasswordMD5=
[OutOfControlProcessRestraint]
OocOn=true
ExcludeChildrenOfActiveForeground_2=false
DisableProBalanceWhenSysIdle=false
ProBalanceDropOneRandomCore=false
OocDisableCoreParkingWhileIn=false
DisableProBalanceIfSysIdleThisManyMS=30000
TotalProcessorUsageBeforeRestraint=9
PerProcessUsageBeforeRestraint=7
TimeOverQuotaBeforeRestraint=1100
PerProcessUsageForRestore=3
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
RoundRobinAffinitySelection=false
LowerIOPriorityDuringRestraint=false
MatchExclusionsByPathnameToo=false
OocExclusions=
OocHardCodedExclusionOverrides=
[GUI]
ClearLogAtExit=false
ShowGraphLegend=true
ShowGraphCPU=true
ShowGraphResponsiveness=true
ShowGraphMemoryLoad=true
ShowGraphProBalanceEvents=true
ShowGraphSelectedProcessesCPUHistory=true
ProBalanceCountersOnGraph=true
ShowGraphLicenseName=true
[Advanced]
AutomaticUpdate=false
RoundRobinSkipCore0=false
[Performance]
DefaultsLevel=327942
GracefulWaitTimeInMs=5000
UpdateSpeedGUI=1000
UpdateSpeedCore=1000
ManageOnlyCurrentUser=false
ExitOnCloseWindow=false
SoundsOff=true
AggressivelyTrimProcessLassoWorkingSet=true
IsConfigWritable=true
ForcedMode=false
IgnoreProtectedProcesses=true
IgnoreSuspendedProcesses=false
[ForegroundBoosting]
BoostForegroundThread=false
BoostForegroundProcess=false
ForegroundBoostExclusions=
[SystemTrayIcon]
UseStaticIcon=false
ShowResponsivnessInTrayInsteadOfProcessorUsage=false
[Logging]
LogDisable=false
LogSmartTrim=true
LogCPULimiter=true
LogEmitCSV=false
LogPruning=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
ClearStandbyFreeRAMThresholdMB=1024
ClearStandbyOnlyInPerfMode=true
SmartTrimAutoMinimumRAMLoad=65
MinimumProcessWSSInMb=196
SmartTrimIntervalMins=15
[SysTrayBalloons]
EnableSystemTrayNotification=false
BalloonTipDuration=10000
ShowBalloonsForOocPriorityRestoration=false
[ProcessAllowances]
ApplyInstanceCountLimitsToAllUsers=false
AllowedProcesses=
DisallowedProcesses=
InstanceLimitedProcesses=
InstanceManagedCPUAffinities=
ProcessThrottles=
OneTimeProcessThrottles=
CPULimitRules=
[ProcessDefaults]
DefaultPriorities=
DefaultIOPriorities=
DefaultMemoryPriorities=
DisableThreadPriorityBoost=
DefaultAffinities=
KeepRunningProcesses=
MatchWildcardsToPathnames=true
MatchOnCommandLine=false
[AdvancedRules]
DivideCPUPercentThresholdsBySystemCPUCount=false
ProcessorGroupExtended=
WatchdogRules2=
[GamingMode]
GamingModeEnabled=false
GamingChangePowerPlan=true
TargetPowerPlan=Bitsum Highest Performance
GamingModeEngageForSteam=true
AutomaticGamingModeProcessPaths=
[MemoryManagement]
SmartTrimExclusions=
[PowerManagement]
Display=
PC=
[PowerSaver]
ShowNotificationWhenActivePowerSchemeChanges=true
PowerSaver_IdleTime=0
EnergySaverEnabled=false
EnergySaverForceActivePowerProfile=false
EnergySaverUpPowerProfileName=
EnergySaverEvents=true
DisableEnergySaverDuringGamingMode=true
PowerSaver_Exclusions=

<VOL>:\name\Eigene Dokumente\process lasso\configs\<SUBDIR>\prolasso.ini:

[Administration]
Version=4630100
ConfigPasswordMD5=
[OutOfControlProcessRestraint]
OocOn=true
ExcludeChildrenOfActiveForeground_2=false
DisableProBalanceWhenSysIdle=false
ProBalanceDropOneRandomCore=false
OocDisableCoreParkingWhileIn=false
DisableProBalanceIfSysIdleThisManyMS=30000
TotalProcessorUsageBeforeRestraint=9
PerProcessUsageBeforeRestraint=20
TimeOverQuotaBeforeRestraint=1100
PerProcessUsageForRestore=3
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=
ExcludeForegroundProcesses=true
DoNotLowerPriorityClass=false
RoundRobinAffinitySelection=false
LowerIOPriorityDuringRestraint=false
MatchExclusionsByPathnameToo=false
OocExclusions=
OocHardCodedExclusionOverrides=
[GUI]
ClearLogAtExit=false
ShowGraphLegend=true
ShowGraphCPU=true
ShowGraphResponsiveness=true
ShowGraphMemoryLoad=true
ShowGraphProBalanceEvents=true
ShowGraphSelectedProcessesCPUHistory=true
ProBalanceCountersOnGraph=true
ShowGraphLicenseName=true
[Advanced]
AutomaticUpdate=false
RoundRobinSkipCore0=false
[Performance]
DefaultsLevel=327942
GracefulWaitTimeInMs=1000
UpdateSpeedGUI=1000
UpdateSpeedCore=1000
ManageOnlyCurrentUser=false
ExitOnCloseWindow=false
SoundsOff=true
AggressivelyTrimProcessLassoWorkingSet=true
IsConfigWritable=true
ForcedMode=false
IgnoreProtectedProcesses=true
HideSuspendedProcesses2=false
[ForegroundBoosting]
BoostForegroundThread=false
BoostForegroundProcess=false
ForegroundBoostExclusions=
[SystemTrayIcon]
UseStaticIcon=false
ShowResponsivnessInTrayInsteadOfProcessorUsage=false
[Logging]
LogDisable=false
LogSmartTrim=true
LogCPULimiter=true
LogEmitCSV=false
LogPruning=true
LogProBalanceParkingChanges=false
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
ClearStandbyFreeRAMThresholdMB=0
ClearStandbyOnlyInPerfMode=true
SmartTrimAutoMinimumRAMLoad=65
MinimumProcessWSSInMb=196
SmartTrimIntervalMins=15
[SysTrayBalloons]
EnableSystemTrayNotification=false
BalloonTipDuration=10000
ShowBalloonsForOocPriorityRestoration=false
[ProcessAllowances]
ApplyInstanceCountLimitsToAllUsers=false
AllowedProcesses=
DisallowedProcesses=
InstanceLimitedProcesses=
InstanceManagedCPUAffinities=
ProcessThrottles=
OneTimeProcessThrottles=
CPULimitRules=
[ProcessDefaults]
DefaultPriorities=x4.exe,above normal
DefaultIOPriorities=x4.exe,3
DefaultMemoryPriorities=
DisableThreadPriorityBoost=
DefaultAffinities=x4.exe,1-11
KeepRunningProcesses=
MatchWildcardsToPathnames=true
MatchOnCommandLine=false
[AdvancedRules]
DivideCPUPercentThresholdsBySystemCPUCount=false
ProcessorGroupExtended=
WatchdogRules2=
[GamingMode]
GamingModeEnabled=false
GamingChangePowerPlan=true
TargetPowerPlan=Bitsum Highest Performance
GamingModeEngageForSteam=true
AutomaticGamingModeProcessPaths=
[MemoryManagement]
SmartTrimExclusions=
[PowerManagement]
Display=x4.exe
PC=
[PowerSaver]
ShowNotificationWhenActivePowerSchemeChanges=true
[ProcessDefaults]
DefaultPowerSchemes=x4.exe;bitsum highest performance
[PowerSaver]
PowerSaver_IdleTime=0
EnergySaverEnabled=false
EnergySaverForceActivePowerProfile=false
EnergySaverUpPowerProfileName=
EnergySaverEvents=true
DisableEnergySaverDuringGamingMode=true
PowerSaver_Exclusions=

96

General / Re: Thanks for your fine product Jeremy!

« Last post by Jeremy Collake on April 25, 2020, 10:33:19 AM »

You are very welcome, and thank you for the encouraging words!

Development is definitely continuous. I've tried to keep final versions on a 3 week schedule, though have violated that a little this month. The last year has been a productive one; the product has advanced substantially, and there is a lot more work planned.

The beta channel is fast and furious, so I hope it doesn't overwhelm you . I do get complaints about that sometimes, but that is what the beta channel is for.

97

General / Thanks for your fine product Jeremy!

« Last post by jeksleinew on April 25, 2020, 10:20:05 AM »

I think I've have had the ProLasso installed on all my OS's since you were just coming out with it. You've got to be the hardest working software designer/builer/idealist in the business - you're always coming on with an update... I have my ProLasso set up for auto-install for beta's.

ProLasso is a great tool and compliment to my Core 2 Quad 2.66Ghz. I use your application to tune my system for the best performance. In itself, It uses hardly any resources.

Thank you for you integrity and hard work Jeremy,

Sincerely,

98

Bug Reports / Re: BitDefender (Antivirus) Not Hard-Coded; Hangs w/Constant CPU Affinity Reset

« Last post by Jeremy Collake on April 25, 2020, 10:08:42 AM »

You definitely don't want to try to set their CPU affinities or other attributes. Security suites protect their processes from tampering so that malware can't mess with them.

Do you have some all-inclusive wildcard set, and that is the problem? If so, you'll need to whittle that down to more selective rules.

99

Bug Reports / BitDefender (Antivirus) Not Hard-Coded; Hangs w/Constant CPU Affinity Reset

« Last post by nah1982 on April 25, 2020, 04:04:07 AM »

I noted that BitDefender (the antivirus) and it's sub-processes don't appear to be hard coded to be excluded. I set them to be ignored, or tried to set CPU affinity broad so they would be ignored. It just constantly trys to set their affinity and errors out every couples minutes. If I set "More strictly enforce default affinities" it literally constantly is trying for it, and freezing up the system; I have to disable for it to default to every couple minutes. If there is a way to force it to ignore them in all instances, your feedback is appreciated.

Otherwise, to fix them and hard-code to be ignored, the list of processes are:

bdredline.exe
bdagent.exe
bdservicehost.exe
bdtrackersnmh.exe
BdVpnApp.exe
BdVpnService.exe
bdwtxag.exe
bdwtxcr.exe
DevMgmtService.exe
updatesrv.exe
DiscoverySrv.exe
ProductAgentService.exe

Sincerely,
nah1982

100

General / Re: How To Get Back To My Paid Version??

« Last post by Jeremy Collake on April 23, 2020, 06:57:38 AM »

If you haven't already, submit a support request at https://bitsum.com/contact/ . If you have, please hold for response. We will get you taken care of.

Thanks