Nod32/ekrn.exe hammering cpu usage.

Post by **Dr. kitteny berk** » March 21st, 2008, 0:33

Sucks, hard, any ideas?

Wiggy · Post by **Wiggy** » March 21st, 2008, 1:36

What's EKRN? Not heard of that one - not having any problems with NOD32 either.

Post by **HereComesPete** » March 21st, 2008, 1:52

It's nod32's active scanner jobby. It has known conflicts with IE, FF and some messaging/email stuff. They generally fix it quite fast though. Modifying the settings sometimes makes it go crazy too. This or this might help.

Fear · Post by **Fear** » March 21st, 2008, 1:59

I had this - I found it was scanning network drives by default, and cd-rom I think. I added them as exceptions, and the cpu dropped away.

I still never liked NOD32 much tho, narf. It seems to hook into far too much stuff.

Post by **Dr. kitteny berk** » March 21st, 2008, 7:20

it's mostly on downloads completing / rars extracting for me.

I'm about ready to buy nod32, apart from that issue

cheeseandham · Post by **cheeseandham** » March 21st, 2008, 15:36

Trust you to find this issue berk

I run 2.7 on my home machine still, so not come across this issue, thanks for the heads up.
My thoughts are to add rars as an extension that will not be scanned for threats. I'm sure they will still be scanned at extraction time. (Don't just take my word for it though, switch your AV off and download EICAR, rar it and then test it out.) and/or exclude your download location from automated scanning.

Post by **FatherJack** » March 22nd, 2008, 23:39

I've started getting this too, when big downloads have completed, FF goes white and stops responding for about 1 minute/100MB, although it doesn't especially cane the CPU.

Disabling RAR scanning isn't really an ideal solution, as it does it with EXEs too, and I download into different folder locations each time.

I used to always use download managers for big files and didn't notice this occuring, but have got cocky since having the 20M broadband.

I'm using 3.0.621.0 64-bit.

cheeseandham · Post by **cheeseandham** » March 23rd, 2008, 1:17

Sorry to hear this guys. I dunno, you'll have to fiddle with the settings.
By the sound of it, it's tying up the CPU because it's scanning a large rar everytime it gets modified (as it does when you download) so maybe switching that behaviour off will help, perhaps under

Antivirus and antispyware > Realtime file system protection > Additional Threatsesnse parameters for newly created and modified files.

Otherwise keep an eye on Wildersecurity they tend to know what their on about

Either that or stick to 2.7 in the meantime.