NOD32 and Comodo BOClean 4.25

Hi,

I've been having problems with BOClean using 98% of the CPU and the only way to close it is by killing the process in Process Explorer.
I posted a help request over at Comodo forums http://forums.comodo.com/comodo_boclean_antimalware/boclean_425_running_at_98_cpu-t11492.0.html and Kevin McAleavey asked me to post my problem here...

here's his reply to my post...

"The only thing that changed in BOClean 4.25 from the earlier 4.24 is two lines of code which handle memory allocation. Certainly wouldn't cause threadlock like that. I know that COMODO is taking care of letting their apps know about BOClean - might want to send a copy to the NOD folks and let them know it's OK and is a new version - they might not yet be aware of it since they use an MD5 for known stuff. It's most likely either the firewall or memory guardian or NOD32 hammering it. But nothing of any circumstance has changed in 4.25 other than the MD5 which seems to be the big magic of how a lot of preventatives do things nowadays, and it's probably just a matter of a couple of days for things to catch up.

I'll let OUR people know about it if you can let NOD know about it ... but definitely ain't BOClean other than it being an unknown new version I'll bet ..."


I've added the BOClean folder to my NOD exclusions list and will see how it goes.

Thanks

 

Whilst this does not help you - I have nod and downloaded the latest BOClean. I have no issues what so ever.

Was BOClean a clean install?

 

Just to echo this, I am running BOClean 4.25 with NOD32 and they are working in perfect harmony as far as I am aware.

 

Hi,

Quoting to Kevin McAleavey: (at Comodo Forums)

running Boclean + NOD32 ... no memory/cpu issues

 

Immediately after the download of 4.25 I noticed some excess RAM usage, however, it pretty much is the same now as before 4.25.

 

Hi,

Would it perhaps help to do it like we did it in the old days?

Exclusion in AMON:
BOClean folder in long and short format.
BOClean files in long and short format.

Examples (version 4.22.002):
Folder:
C:\PROGRAM FILES\NSCLEAN\BOCLEAN\
C:\PROGRA~1\NSCLEAN\BOCLEAN\
File:
C:\PROGRAM FILES\NSCLEAN\BOCLEAN\BOC422.EXE
C:\PROGRA~1\NSCLEAN\BOCLEAN\BOC422.EXE
etc. etc.

And the other way around:
Excluding the important NOD-files in the BOClean-excluder.

Well, just only an idea.

 

Update.

Ran the PC with BOClean in the NOD exclusion list for a day or two and have had no problems. I know others haven't added it to the exclusion list and it works fine, however I appear to be unique! Dunno if that's a good thing or not but everything's sweet now.

Thanks to all who replied.