AV Definition update caused error

[ThomasAdams]

I received this error (see attached) immediately after Nod32 update the AV definitions. Virus signature database: 5418 (20100902).

Windows XP w/SP3 32-bit

Anyone else getting the same error?

Edit:
Version 4.0.437.0 (updating now, I had not realized there was an update).

This issue seems to have been corrected with subsequent AV definition updates, and restarts. I was unable to come back and reply as my machine had went down for a bit. However I appreciate the quick response! Thank you Eset.

[Marcos]

If you are using the latest version 4.2.64, download Procdump and run it with the parameters "procdump -ma ekrn.exe". When you have the dump ready, let me know so that I can provide you with further instructions.

[zloyDi]

Originally Posted by Marcos

If you are using the latest version 4.2.64, download Procdump and run it with the parameters "procdump -ma ekrn.exe". When you have the dump ready, let me know so that I can provide you with further instructions.

Hi Marcos!
I have this problem too
After run procdump with the parameters "procdump -ma ekrn.exe"
I have error Error opening ekrn.exe (1080)

What to do?

[Marcos]

Originally Posted by zloyDi

Hi Marcos!
I have this problem too
After run procdump with the parameters "procdump -ma ekrn.exe"
I have error Error opening ekrn.exe (1080)
What to do?

That could be due to active Self-defense. If it's possible to reproduce the crash easily, disable self-defense, restart the computer, reproduce the crash and generate an application dump using Procdump.

[PhoenixUA]

Same error with 5418.
NOD32 4.2.40

[Phonemes]

I am also having these memory errors with def update 5418. It happened during the def update itself, once during a reboot, and after right clicking the trash bin, after which my computer froze and I had to use the power button to shut the system down.

Next I got a warning that a serious error had occured in Outlook when the addin eset\esetno~\eplgou~1.dll was last opened.

NOD32 is wreaking havoc on my computer.

Edit: forgot to tell that I also got a message from Eset that my windows update software was outdated. Checked that on the windows update site and no updates whatsoever showed up.

Win XP Pro SP3

[mastj25]

Same error with 3.0.695 and 3.0.684 Sig 5418

[minerat]

A lot of our XP SP3 machines are just flat out locking up with this update ( 5418 ). We're on the 4.0.437 client. How do we roll back?

[yadnom]

We are having the same issue with the PCs on our network. Latest update 5418 causing lockups and getting blank threat alert triggers.

Running Windows XP SP3 workstations.

[dwood]

Yeah we are seeing this error on a few machines 4.2.35 installed.

We are seeing these error in the System log.

Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Date: 02/09/2010
Time: 14:22:31
User: N/A
Computer:
Description:
Application popup: ekrn.exe - Application Error : The instruction at "0x7c809823" referenced memory at "0x009b2f00". The memory could not be "written".

Click on OK to terminate the program
Click on CANCEL to debug the program

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Date: 02/09/2010
Time: 14:24:28
User: N/A
Computer:
Description:
Application popup: ekrn.exe - Application Error : The instruction at "0x7c809823" referenced memory at "0x009b2a68". The memory could not be "written".

Click on OK to terminate the program
Click on CANCEL to debug the program

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

[brou]

Same behavior here. I've been resetting machines (all happened to be XP SP3) for the past 30 minutes. Phone doesn't stop ringing for this.

[webyourbusiness]

I have had eset service shut down on a machine with XP SP3 - it manifested itself with an error between ESET & Outlook plugin when Quickbooks 2008 tried to send an email on another XP SP3 machine, and on my personal Win 7 Ultimate the eset service ended abruptly as well - 5418 on all machines.

[AndrewGVS]

Good grief, 5418 has done the business, not only PC's hanging, but unable to log onto Terminal Servers with RPC not available errors...

Interferring with internet explorer as well...

Everythings hit the wall... phones going mental...

[the6thday]

Hi,

we are experiencing the same issues on our network, right after the pc's update to 5418 some of them freeze for ~30 seconds multiple times, others have issues with webbrowsing(http traffic), and some of them send false reports:
"02.09.2010 15:54:02 - Modul Echtzeit-Dateischutz - Alarm ausgelost auf Computer xxxxxx: enthalt ."

we are using windows xp SP3(32bit) and Windows 7(32bit)

nod 32 AV BE 4.2.64

[Colditzz]

Arghhh...

Have the same problem appearing, 30 + servers suffering already

[stridert]

Also having the lockup problem. Affecting 25 PCs so far however no servers as of yet.

[Mister Natural]

Same here, I have a number of systems becoming unresponsive and forcing a cold boot to recover.

[grdotnet]

Same here - 4.2.64 client that have all been pushed the 5418 update. Server 2003 R2 and Windows XP clients (with a handful of Win7 clients also).

[rembert]

Here several servers gone down already due to 5418 (win2003). Reboot solved problem. Some workstation froze as well. Terminated the remote administrator server so updates wouldn't be spread for now so people can just continue to work. Hopefully a new update will be available soon.

[simplicissimus]

Same here, nearly all PCs (XP SP3) freeze and must be resseted.

[jamesb]

We have a large number of customers on Windows XP workgroups, SBS 2003 networks and 64bit SBS 2008 networks all calling up because of the same problem, not helped by the fact that a large proportion of our staff cannot access customer records because our TS server is also suffering from the issue.

Has anyone had any luck resolving this problem yes? Cold reboot does not seem to be working in most cases.

[outsider73]

4.0.437.0 + 5418 (20100902) = same issues on some of the PCs.
My Outlook froze and the scan started by itself thinking I was starting my computer...
Worse case : lots of XP SP2 and SP3 do not have anymore internet connection.

Anyone knows how to rollback a patch and to force to redeploy the previous one ?

Thanks for sharing any thoughts.

[mastj25]

Marcos, can't Eset just repackage up and earlier sig file that didn't have this issue and release it as the next version? We have many servers and clients experiencing issues.

[Carbonyl]

Hi everyone - I just wanted to let everyone know that ESET most certainly must have taken notice. I just flipped on my machine just now, and I'm seeing that definitions 5416 are the most current according to my ESET. So the 5418 definitions have most likely been suspended and ESET are hard at work.

[orton]

No error message here, but when 5418 downloaded my machine totally locked up. Had to do a hard reboot, all seems normal now. XP SP3