ekrn.exe Crashes on New Signature Uptades or Incompatibility with VS2005?

Hi,

This is a reproduce able error I've been having with ekrn.exe crashing(?) after updating since Wed May 24. Now I'm not 100% sure that it is actually crashing as the only indication that I have of this is that after a new update is downloaded I get a Visual Studio 2005 prompt for debugging the program that when used freezes my computer before any information is displayed in VS. There are also no logs of this crash from drwtsn32 or in the event viewer and ekrn.exe seems to continue to run afterwards even though in the Services manager I've indicated to not restart the service after a failure so it doesn't seem to be even though VS says it is. Has anyone else had or heard of this problem?

Cheers,

Lithium

 

Reinstall the program following these instructions and keep watching it for some days to see if it will happen again:

1. Download fresh new version of ESET Smart Security / ESET NOD32 Antivirus 3.0 from
http://www.eset.com/download . Make sure that you choose the correct version.

2. Uninstall your current version from Control Panel
3. Reboot the computer when prompted
4. Delete manually these folders:

for XP:
- C:\Program files\ESET
- C:\Documents and Settings\All users\Application data\Eset
- C:\Documents and Settings\~username~\Local Settings\Application data\Eset

for Vista:
- C:\Program files\ESET
- C:\Program data\Eset
- C:\Users\~username~\AppData\Local\Eset

5. Reinstall your ESET software using the file you downloaded in step1 . Use typical install.

 

I have the same problem except my computer isn't freezing. You obviously have VS 2005 installed and you're seeing the "just in time" debugger because ekrn.exe has crashed.

I get a Service Control Manager error under Xp's System event viewer saying:

The Eset Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 0 milliseconds: Restart the service.

This has only occured since the updates were applied as mentioned in your post.

 

HiTech_boy: I've tried your suggestion, did a manual update after reinstall and the problem seems to be resolved.

Cage: Yeah it was the Just in time debugger. HiTech_boy's suggestion seemed to work for me maybe you should give it a try.