Nod32 conflicting with PG and creatin problem to Boclean???

[Atomas31]

Hi,

After sending an email to Kevin from Boclean concerning the pick of CPU usage of Boclean (with version 4.12.003 around 16%) and the conflict with Process Guard, he send me the following message :

" the problem is NOT BOClean and it is NOT process guard. The PROBLEM is NOD32 conflicting with Process Guard. The two are INCOMPATIBLE at the kernel driver level and that's what folks who don't use NOD32 have no problems with PG and BOClean."

Can someone explain to me how can NOD32 conflicting with PG can create only problem to Boclean? I am kind of loss there!!!!

Does NOD32 are aware of this conflict and are they working on it?

By the way, I have the french version of NOD32 wich mean I still have version 2.12.3 so maybe the situation is rectified with the latest version of NOD32.

Thank you,
Atomas31

[GuruGuy]

Nevermind..........I must be hallucinating!

[DonKid]

I use PG since NOD32 version 2.12.3 and never had a problem with them.
Best Regards,

DonKid.

[Atomas31]

Hi Donkid,

I don't see any problem between NOD32 and PG either but I see some CPU peek with Boclean and if I am understanting correctly what Kevin (from Boclean) as send me : the problem with the CPU peek of Boclean is related to a "conflict" between NOD32 and PG?? I'm not expert but it seems that Kevin has giving me a very strange answer to the peek problem of Boclean.... ain't it?


Atomas31

[Bubba]

Originally Posted by Atomas31

I'm not expert but it seems that Kevin has giving me a very strange answer to the peek problem of Boclean.... ain't it?

No disrespect to Kevin when I say this since it's my slowness in understanding....but after one reads Kevins posts and shakes his\her head a few times and then re-reads his post again....it usually becomes very clear what he is saying.

In any case....this whole thread is well worth a read....but to get to the explanation by Kevin of his thoughts concerning PG\BOclean\CPU spikes....see this post.

[The Hammer]

Originally Posted by Bubba

No disrespect to Kevin when I say this since it's my slowness in understanding....but after one reads Kevins posts and shakes his\her head a few times and then re-reads his post again....it usually becomes very clear what he is saying.

Maybe I'm to tired but I'm not getting it.

[BlueZannetti]

Originally Posted by The Hammer

Maybe I'm to tired but I'm not getting it.

Here's the same basic message, using somewhat different words, that Kevin sent to me in response to some comments some time ago...

As it turns out, the problem is *NOT* BOClean, but rather the interaction of PG and several antiviruses using KAV's style of kernel driver. A number of them (most noticeably NOD32) are doing the same thing, suspending threads until they can run through their databases. Since BOClean works with a systemwide hook in its historic design, this means that EVERYTHING gets suspended as a result of the antivirus and PG battling one another for thread stop control at the kernel level. And this was made even more pronounced by BOClean looking to refresh its own threads table in order to spot memory injections without an associated process or library.

Does this help?

Blue

[Mongol]

The latest version Nod32 and PG have been working fine for some time now on my desktop. No conflicts at all noted here.

[The Hammer]

Yes Blue thanks.

[The Hammer]

Originally Posted by Mongol

The latest version Nod32 and PG have been working fine for some time now on my desktop. No conflicts at all noted here.

Are you running BOClean as well?

[Mongol]

Originally Posted by The Hammer

Are you running BOClean as well?

Nope I have the newest Ewido 3.5 here along with Counterspy..