Avast bug with GPU (nvidia)

Build 2015.10.2.2214

For years I have use Max Performance in NVCP and never once had this probably till this build.

Ever since the build which now has 2 Avastui.exe process my GPU will run 3D clock speeds on desktop. So as test I uninstalled Avast reboot and sure enough GPU would be at idle speeds on desktop. I reinstalled Avast no soon was the install done, GPU was running 3d clock speeds again.

So i went and made NVCP profile for Avast (avastui.exe) and set it to adaptive. reboot PC and sure enough gpu was running idle speeds on desktop again…

I dont know if this problem with Avast end and its new 2nd process of avastui.exe that is gui related or not. but there no reason for this to be happening.

The two instances of avastui.exe are by design.

I suggest to perform a clean installation of the latest avast version and see if the problem remains or not.

Reading skills??

I already mentioned I did a clean install, when I “uninstalled” avast and reboot and watched my gpu drop to idle speeds on desktop.

I then Installed avast the build 2015.10.2.2214 and soon as it was done installed my gpu no longer dropped to idle speeds on desktop.

I then made NVCP profile for Avast (avastui.exe) and manual set that to adaptive. and rebooted

Only then did my gpu idle at correct speeds, with Max performance setting in global profile. when on desktop

I know this is the internet and all and people dont like to read but seriously reading goes a long way.

Avastui is keeping NVCP global profile with max performance set from downclocking to idle speeds on the desktop. So once more

AVASTUI.EXE is preventing gpu from droping to idle speeds on desktop unless one makes a NVCP profile for AVAST (avastui.exe) and setting to adaptive, plain and simple, there no reason for the avastui.exe to be even using the gpu let alone keeping it from drop to idle speeds.

Did you use the uninstall tool ?

yes and tested on 3 diffrent nvidia desktops pc.

Avastui.exe is forcing the gpu in to 3d clock speeds while siting on desktop with nothing open if the said system using max performance on global profile. forcing me to make profile for avastui.exe and setting to adaptive reboot does sitting on desktop with nothing open actual downclock the gpu to idle speeds this has to be done every time i change gpu drivers…

There is no reason for AV program to be causing gpu to go in to 3d clock speeds when sitting on desktop with nothing open, when nvidia max performance is used in global, and this started with the build i mentioned before thise build and before 2nd avastui.exe being added max performance under global profiles worked fine and down clocked to idle speeds with PREVIOUS avast build 5+ years of using avast and this first time i seen this happen. in fact it first time i seen any antivirus program ever force full 3d clock speeds on any pc i ever had and they all been set to max performance in global.

It seems like a driver problem to me and suggest you also report it to avast through:
https://support.avast.com

Definitely something for avast to have a look at in my opinion.

not driver problem i test this on 5 drivers the other day and it happened on all the drivers, probably is sololy with avastui.exe and the 2015.10.2.2214 update making the gpu run in 3d mode IF max performance is set in nvcp global profile. where as it never had the behavior before the update

Seems you do not know that avast is using drivers also. :wink:

Hello,

this issue will be fixed in upcoming service pack.

Noticed exactly this as well. Using GTX 970. Posted about it but no luck.

Only fix I have found so far is rolling back to a previous version of avast.
If it is true that with the next service pack update this issue will be fixed then that is great news though.

Well, I would say see if it is fixed.
Perform a clean installation of the latest avast version which has been released just a few hours ago.
https://forum.avast.com/index.php?topic=168189.0

I’ve experienced crashes with Avast and have an Nvidia card. I wonder if it’s related.

Try the new BETA version that Eddy linked above.

It most likely will fix your issue. It’s stable.

Would seem the 2015.10.2.2215 has fix this issue, even better there no longer 2 avastui.exe :-*