Jump to content

TrialUser

Members
  • Posts

    3
  • Joined

  • Last visited

About TrialUser

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    France
  1. Sorry to be so dense, but I see there are several protocol parameters in advanced setup, and they have to do with email and web access. Are these the ones I should try disabling? Which ones? Thanks again.
  2. Thank you for the quick reply. In your second step, did you mean with protocol filtereing *DIS*-abled? Or are you saying try two different things? That is, disable protocol filtering and see if problem goes away, and if not, then re-enable protocol filtering and uninstall Malwarebytes? And when you say “temporarily” uninstall malwarebytes, does it mean that if the problem goes away, I should leave malwarebytes permanently uninstalled? Is there overlap in functionality between ESET NOD32 and Malwarebytes? That is, do you think having Malwarebytes on the same system as ESET is redundant and I will be OK with ESET alone? The ESET trial was going fine for several days. So what is it that triggers this sudden CPU problem? It is important to me to know that this is not going to keep happening randomly. Thanks again.
  3. I developed the same problem about 30 minutes ago. Still going on. CPU usage is 97% for ekrn.exe. No scans going on that I can tell. Have tried pausing protection - no change. Have tried disabling various settings in Advanced settings as suggested my numerous web search results, - no change. Lots of hits on Google for this problem. I'm in the middle of my trial subscription and this is not good. Note that I do have Malwarebytes installed, but msmpeng.exe is not among the running processes, and Malwarebytes does not seem to be doing anything. If you know of an incompatibility between ESET and Malwarebytes, please share that concern here. Windows 7 64 bit Ultimate, 32 Gb ram. Thanks!
×
×
  • Create New...