Jump to content

Error Communicating with Kernel


Recommended Posts

Hi,

 

Upon booting my computer I am getting the error message: "Error Communicating with Kernel". Eset is not starting. I have followed all the steps in this kb article. 'Eset Service' is listed in Services as 'Automatic' but it is not 'Started'. I've manually started it and rebooted, but after reboot is it not started again. I downloaded and ran both Win32/Sirefef (Zero.Access rootkit) & Win32/IRCBot.ANR removal programs. Win32/Sirefef (Zero.Access rootkit) removal program reported that I wasn't infected. Win32/IRCBot.ANR cleaner didn't report any infection although it wasn't clear as it doesn't specifically state that you're not infected.

 

I was running V6 of Smart Security. I updated to V7 using the in-app update option. I still have the same "Error Communication with Kernel" though.

 

Any ideas on how to fix this?

Link to comment
Share on other sites

Hello FlexiPack

 

You can try this: Go to C:\Program Files\ESET\ESET Smart Security, and rename the file em001_32.dat  to em001_32.dat.bak . Then reboot your system. Then  should eset servise start.

 

Regards Janus :-))

Link to comment
Share on other sites

  • Administrators

 

You can try this: Go to C:\Program Files\ESET\ESET Smart Security, and rename the file em001_32.dat  to em001_32.dat.bak . Then reboot your system. Then  should eset servise start.

 

That's not a good idea, doing so would most likely cause modules not to load.

 

Do you get the error if you attempt to open ESET's gui after installation or only after a restart? What operating system do you use?

Link to comment
Share on other sites

 

 

You can try this: Go to C:\Program Files\ESET\ESET Smart Security, and rename the file em001_32.dat  to em001_32.dat.bak . Then reboot your system. Then  should eset servise start.

 

That's not a good idea, doing so would most likely cause modules not to load.

 

Do you get the error if you attempt to open ESET's gui after installation or only after a restart? What operating system do you use?

 

I'm using Windows 7 64bit. If I try to open the ESET GUI whilst the Eset Service module is not started, I get the Kernel Error. However once I manually start the Eset Service module, I can then open the ESET GUI. ESET will then continue to run normally until my next reboot.

Edited by FlexiPack
Link to comment
Share on other sites

I'd really appreciate some help with this. It's an ongoing problem. A couple of times ESET has started normally after booting but the majority of the time it doesn't and I have to start it manually.

Link to comment
Share on other sites

  • ESET Insiders

Flexi,

 

 

Can you send SysInternals Autoruns log?

Or you can take a look at it yourself for what is starting with Windows and spot the unwanted modules...

 

In addition - save & clean Application and System eventlogs, restart computer and check or send those logs.

 

 

Tomo

Link to comment
Share on other sites

 Here's the result from 'sc query ekrn' when 'ekrn' isn't running:

 

hxxp://i.imgur.com/VxcBBHP.jpg

 

 

 

For reference, this is what it says if I run the same command whilst 'ekrn' is running:

 

hxxp://i.imgur.com/Dg3W9qb.jpg

Edited by FlexiPack
Link to comment
Share on other sites

  • Administrators

Please enable creation of complete application memory dumps under Tools -> Diagnostics, reproduce the issue and then check the Diagnostics folder if there are some dumps created.

Link to comment
Share on other sites

Since my last post I have not had the error. I have booted the computer around 8 times since then. This happened previously though, it went for a couple of days where it worked as it should and then kernel error came back. It's very strange. I have not changed anything since yesterday. I have enabled the diagnostic dump, when/if it happens again I will post the dump if there is one. What would cause a diagnostic dump? So far the folder is empty.

Link to comment
Share on other sites

  • Administrators

What would cause a diagnostic dump? So far the folder is empty.

 

When ekrn.exe crashes, a dump will be created in the Diagnostics folder.

Link to comment
Share on other sites

The error just occurred again. First time in 3 days. There is unfortunately no dump in the diagnostics folder.

 

Dump type is set to: Complete memory dump

 

Target Directory is: C:\ProgramData\ESET\ESET Smart Security\Diagnostics\

 

The only thing in that folder is a folder called 'modules' which is empty.

Link to comment
Share on other sites

  • 2 years later...

I received a notice to "turn on antivirus."   When I go to ESET it gives me the notice "error communicating with kernel."  What do I do?  I need to use my computer on-line and the office help number only works Mon-Fri.

 

 

Link to comment
Share on other sites

  • Administrators

The error indicates that ekrn.exe is not running. Please check the Task manager if the process is listed there. Also check the system event log for possible errors as well as C:\ProgramData\ESET\ESET Smart Security\Diagnostics. Are there any dump files in that folder? Try uninstalling and re-installing ESS v9 and see  if it helps.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...