Firefox + NOD32 Antivirus = CPU overuse/overheat & reduced browsing speed?
Are there any known issues between NOD32 Antivirus and Mozilla Firefox?
Description of the problem: Each time I'm browsing with Firefox, a process called "ekrn.exe" (I'm assuming this is NOD32) begins to consume close to 50% of CPU resources (otherwise its CPU usage is negligible). This noticeably reduces browsing speed and overall PC performance and causes CPU to heat up rapidly (from the usual 40°C to about 60°C in seconds). The issue does not occur when using other browsers (tested with Google Chrome and Opera 11, same web sites) .
I'm using Eset NOD32 Antivirus version 4.2.64.12 running on Windows XP (32-bit) version 5.1.2600 Service Pack 3 and Mozilla Firefox version 3.6.13.
Alle Antworten (6)
Ye, i had same problem with windows 7 i found this: http://www.exe-error-fixes.com/ekrnexe-high-amount-cpu/ and used method 4.
working but i think it is not good solution on long-term
Do you have "Yet Another Smooth Scrolling" addon instaled? Try to disable it. It's helped in my case.
Sorry that's helped just for a while. The only way I've found - clear recent history.
Ye, i had same problem with windows 7 i found this: http://www.exe-error-fixes.com/ekrnexe-high-amount-cpu/ and used method 4.
working but i think it is not good solution on long-term
Method 4 worked for me too. I am running FF4 RC2, Win7 SP1 and NOD32 4.0.424. I don't like that I have to disable some of my antivirus functions. Until the FF4 RC2 update, FF worked just fine... I hope they fix it real soon!
Creating a new profile seems to have worked also. I reset the altered options in NOD32 back to their normal state and FF4 RC2 is starting up as per normal.
Nice job guys, you really can't make something without having to fix it later can't you ?
Anyways... I had this shit too (firefox 4.0 rtm / win7 x64)... And actually "ovidescu" bumped me to playing with profile... So ye, that's what I've been doing, manually copy/pasting all files from my 3.6 profile into the new profile on 4.0 and after pasting each file I started the browser to see did this file create the glitch or not... And well I think I found the files responsible for this glitch, they are all sessionstore.js's... I don't know why, but these files cause this glitch with NOD32, at least on my system... In the end I copy/pasted all of my profile files, except for these and sessionstore.bak and the problem was solved...
So when you back up your profile - don't copy these files)))
Geändert am von Ancient