Recent posts

#41

Process Lasso / 24H2 7950X3D CPU Set Problems

Last post by Procha - August 28, 2024, 10:17:07 AM

Hello. So I upgraded my Windows 11 to 24H2 build 26120 and since then whenever I apply CPU Sets to any game to limit it to X3D CCD0, my CCD0 usage goes to 100% and my game freezes indefinitely, but if I don't set any CPU Sets the game runs fine. Any help with this? Before I upgraded there were not any problems like this. Thanks

#42

General / Re: Power plan switching, Park...

Last post by mattskiiau - August 27, 2024, 11:23:47 PM

Thanks Jeremy,

I've been able to figure it out. Setting freq to 1% via PCP allowed balance profile to down clock correctly. For some reason 5% wasn't lowering it for some reason.

Happy with the setup now, thanks!

#43

Process Lasso / Re: 24h2 Ryzen performance lif...

Last post by pixelcowboy - August 27, 2024, 01:28:13 PM

Thanks!

#44

General / Re: Power plan switching, Park...

Last post by Jeremy Collake - August 27, 2024, 07:22:58 AM

Use Process Lasso's IdleSaver or ParkControl's Dynamic Boost, but don't use both. If you try to use both, Dynamic Boost will be disabled.

They do the same thing and detect idle the same way.

Process Lasso doesn't directly affect CPU downclocking. That is controlled by the power plan attributes. If your target idle power plan is configured as desired, it should be working. If you continue to encounter that, we can try to ferret out what you're seeing.

#45

Process Lasso / Re: 24h2 Ryzen performance lif...

Last post by Jeremy Collake - August 27, 2024, 06:56:57 AM

We don't expect any change to Process Lasso specifically resulting from the AMD optimizations present in 24H2. Those improvements are at a lower level than the tuning you'd do with Process Lasso, so are simply a benefit.

#46

Process Lasso / 24h2 Ryzen performance lift/br...

Last post by pixelcowboy - August 27, 2024, 12:47:50 AM

So, I was wondering how the development of 24h2 build of Windows increasing performance affects or works with Process Lasso? Will Process Lasso need an update for 24h2? Or will nothing need to change?

#47

General / Power plan switching, ParkCont...

Last post by mattskiiau - August 26, 2024, 09:25:11 PM

Hey all,

Just wondering what your preferred or most optimized way of doing this is.

Currently, I have my own custom made power plan which down clocks and in turn, lowers voltages for my cpu in idle states very quickly.

I want to stop using it and have an out of the box solution, something like Highest Perf -> Balance plan in 1 sec timeout.
Should provide the same type of scenario of lowering clocks and voltages while browsing and watching youtube (I hope).

Would it be better to use Lasso for this or ParkControl?
Do they recognize "idle" differently?
Any other differences that are documented with Idlesaver(Lasso) vs Dynamic Boost(ParkControl)?

Thank you.

EDIT:
I have found a difference between the Lasso and PCP.
It seems Lasso is preventing Balance mode from downclocking the CPU, even with performance mode disabled and Freq Scaling set to 5% in PCP.
Is there a feature I'm missing in Lasso to prevent down clocking? 

#48

Process Lasso / Re: Terminate during recording...

Last post by Jeremy Collake - August 24, 2024, 08:56:47 AM

I'm sorry, but that is not currently a capability of Process Lasso.

#49

Process Lasso / Re: Process Lasso constantly c...

Last post by Chiru - August 23, 2024, 09:07:12 PM

Yikes! There aren't any known issues that would account for that. It actually sounds like both the GUI (ProcessLasso.exe) and Governor are being terminated, possibly by an external actor, then relaunched.

Can you copy/paste your INI file from menu item "File / Manually Edit Configuration"?

Then, in the log pane, select all rows with CTRL+A and copy/paste those here.

You can also optionally check to see if any dumps were created. See https://bitsum.com/diag/ for instructions to find them. I don't suspect there are, else you'd have gotten a message box about it.

Finally, if you are getting any other crashes or weird behavior from other apps, run some extended system stress tests to ensure the build integrity of your system.

You can use our contact form to upload this data if you desire more privacy.

[Administration]
Version=6100200
ConfigPasswordMD5=
[OutOfControlProcessRestraint]
OocOn=true
ExcludeChildrenOfForeground=true
DisableProBalanceWhenSysIdle=false
ProBalanceDropOneRandomCore=false
DoNotAdjustAffinityIfCustomized=true
OocDisableCoreParkingWhileIn=false
UseEfficiencyMode=false
DisableProBalanceIfSysIdleThisManyMS=30000
TotalProcessorUsageBeforeRestraint=23
PerProcessUsageBeforeRestraint=20
TimeOverQuotaBeforeRestraint=900
PerProcessUsageForRestore=5
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=true
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
BoostOnlyNormal=true
ForegroundBoostExclusions=
[SystemTrayIcon]
UseStaticIcon=false
ShowResponsivnessInTrayInsteadOfProcessorUsage=false
[Logging]
LogDisable=false
IncludeCommandLines=false
LogSmartTrim=true
LogCPULimiter=true
LogEfficiencyMode=true
LogGroupExtender=true
LogCPUSets=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=true
SmartTrimClearFileCache=false
ClearStandbyFreeRAMThresholdMB=2048
ClearStandbyOnlyInPerfMode=true
SmartTrimExclusions=overwatch.exe,rustclient.exe
SmartTrimAutoMinimumRAMLoad=65
MinimumProcessWSSInMb=196
SmartTrimIntervalMins=1
[SysTrayBalloons]
EnableSystemTrayNotification=false
BalloonTipDuration=10000
ShowBalloonsForOocPriorityRestoration=false
[ProcessAllowances]
ApplyInstanceCountLimitsToAllUsers=false
AllowedProcesses=
DisallowedProcesses=
InstanceLimitedProcesses=
InstanceManagedCPUAffinities=
ProcessThrottles=
OneTimeProcessThrottles=
CPULimitRules=
[ProcessDefaults]
NamedAffinities=
DefaultPriorities=discord.exe,above normal,m1-win64-shipping.exe,high,audiodg.exe,high,voicemeeterpro.exe,above normal,scpsl.exe,high,valorant-win64-shipping.exe,high,aimlab_tb.exe,high,insightscapture.exe,above normal,ow-obs.exe,above normal,thefirstdescendant.exe,high,cs2.exe,high,rustclient.exe,high,overwatch.exe,high
DefaultIOPriorities=overwatch.exe,4,voicemeeterpro.exe,3,discord.exe,3,valorant-win64-shipping.exe,3
DefaultMemoryPriorities=overwatch.exe,5
ThreadPriorityBoosts=
DefaultAffinitiesEx=audiodg.exe,0,2,overwatch.exe,0,1-11,valorant-win64-shipping.exe,0,1-11
CPUSets=
KeepRunningProcesses=
[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=nierautomata.exe,overwatch.exe,r5apex.exe,resolve.exe,rust.exe,rustclient.exe,valorant-win64-shipping.exe,vrchat.exe,m1-win64-shipping.exe
[PowerManagement]
StartWithPowerPlan=High performance
Display=
PC=
[ProcessDefaults]
DefaultPowerSchemes=scpsl.exe;bitsum highest performance
[PowerSaver]
PowerSaver_IdleTime=300
EnergySaverEnabled=false
EnergySaverForceActivePowerProfile=false
EnergySaverUpPowerProfileName=
EnergySaverEvents=true
DisableEnergySaverDuringGamingMode=false
PowerSaver_TargetGUID=Balanced
PowerSaver_Exclusions=

here you go ! sorry for the late response thank you looking into this i do have a file in the logs folder but did not get any in the temp folders. And also I have been using process lasso for quite some time the crashing just happened recently so I'm sure it's not a hardware issue as I haven't changed my hardware for about 2 years. TT

#50

Process Lasso / Terminate during recording ses...

Last post by eurocatgames - August 23, 2024, 06:12:37 PM

Is there a function or setting that will allow a process (non-system) to be terminated or paused while my recording software or game processes are active? Or maybe a when a power profile is active? Because I do have a few games set up to change the power plan to the Bitsum Highest Performance plan when they are active. I would just like to terminate or pause a process when that power plan is active.

Please let me know if this is possible! 

Thanks,

Kelly