ESET Antivirus 3.0.667.0 causes Windows XP SP 3 computer to reboot on startup

i've seen this issue reported in vista, basically upon start up, my computer will reboot and do a bugcheck.

http://www.gorillaenterprises.co.uk/upload/uploadFiles/Mini062108-01.dmp
http://www.gorillaenterprises.co.uk/upload/uploadFiles/Mini062208-01.dmp

running through the windows debug tools, both dumps report that the module eamon.sys was responsible.

my pc has never crashed during start up like this, and it happend the day after i installed the 667 update.

i'm now going to go through the kb article "Help: My PC is freezing during startup " and delete the updates to see if that helps, is there anything i can do to fix this?

 

i have to say, so far, following the instructions in this kb article: http://training.eset.com/kb/index.php?option=com_kb&Itemid=29&page=articles&articleid=812

has solved the problem. it hasn't rebooted at all now, so it might have been caused by a corrupt definition file.

will see how things go and report back.

 

I just started having this problem with 3.0.657.0 under Win2Kpro. I've tried the fix in the article; so far, so good.

[edit]After another restart, the problem came back. Maybe NOD32 was regenerating the corrupt file. I was finally able to uninstall manually in Safe mode.

 

My W2K did this last week. NOD updated just before I shut the pc down - next day 2K wouldn't start right. There would be a message about Windows not finding the ESET kernel, then windows would start a memory dump. I rebooted the pc into the XP drive, and everything worked as normal. XP isn't allowed online. I don't want Adobe trying to sneak in updates. I pull the ethernet plug if I want to use Photoshop CS3. Since I can scan the XP drive from the 2K drive, I only installed Online Armor to keep HP, Adobe, and MS from calling out.
I finally uninstalled NOD in safe mode, redownloaded 3 and reinstalled. It was working after a restart yesterday, haven't checked today. I think I changed to version 3 right after I renewed subscriptions in February. 2K has been behaving ever since. I think it was a definition of some kind that buggered 2K
Would it be better to go back to 2.7? I'm running 3.0.642 on my XP laptop.
BTW, none of our XP machines were affected. 3 are running 3.0 and 2 are running 2.7.
Thanks,
Weezy

 

I think I was using 642 something - downloaded it in March 2008.
Have 667 running now on 2K - Where do I find 650? Also am running trial version now just to check, how do I switch it to subscription? I had one on the 2K pc, but had to delete. Now I need username and password again.
Thanks,
Weezy