[Problems since definition 8766 with 3ware Controller]

 

Hello,

 

our dev team found probable root cause for this issue and prepared a fix.

It is included in Virus signature database 8868P and higher (the P is also important).

So please switch from regular update to pre-release in update settings, check if your ESET product has updated to Virus signature database 8868P or higher and let us know.

 

Thank you for the cooperation.

 

 

Hi Peter,

 

All OK here with update 8868P and above.

 

Please advise when released into normal updates and let us know which signature version?

 

Many thanks for your and ESET's assistance in identifying and resolving this issue.

 

Best Regards

Damian Williamson

[Problems since definition 8766 with 3ware Controller]

Hi All,

 

Can confirm that this issue only causes BSOD if scanning of Boot Sectors is enabled for the particular scan configuration Objects. With Boot Sectors un-checked the issue goes away. Have not bisected that further by Scan Options yet if it makes any difference but please feel free to do so.

 

At least this narrows it down a bit.

 

Cheers

 

[Problems since definition 8766 with 3ware Controller]

Hi all,

 

think this problem is sleeping here, this is my solution: 

 

Install 3Ware Patch on Hyper-V Host or physical Server and restart: https://www.3ware.com/3warekb/article.aspx?id=14869&cNode=4F4F0V

After this install newest ESET File Security on all Server and VM.

 

Thanks all for posting here and big thanks to german support ... it seems to work (if not, I will post it the next days. 

 

Greetings,

Peter 

 

Hi Peter,

 

If that is the solution then the problem is why all of a sudden after a particular signature update on the VM does it cause the buffer on the VM Host to be not aligned?

 

I would rather work to resolve the cause of the problem than implement a workaround.

 

Cheers

[Problems since definition 8766 with 3ware Controller]

Hello,

 

@drhex2000 just send me download link to packed memory dump. 

@c3direct so what are the steps to reproduce the BSOD, please describe them step-by-stem with as many details as possible.

 

Thank you.

 

Hi Peter,

 

I have created Memory Dumps for one Server 2008 R2 x64 VM and one Windows XP x86 VM.

 

It is not so straight forward to create a memory dump for the Hyper-V VM, the BSOD goes through the motions but without the .dmp file actually being created.

 

For my future reference and the use of others if it helps, the procedure is basically as follows;

• Install "Debugging Tools for Windows" (as a Standalone component if you like) on the HOST machine:

  hxxp://bit.ly/157iH5d

   

• Add the "Microsoft Hyper-V VM State to Memory Dump Converter" to the folder on the HOST machine where symsrv.dll for your platform is located (e.g. C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\ on a 64-bit system):

  hxxp://bit.ly/17Ky0Uw

   

• Run the VM and then Save State (in this instance you must trigger BSOD first).

   

• Execute the vm2dmp.exe on the HOST machine to create the dump:

  C:\Path>vm2dmp.exe -vm "{vm name}" -dmp C:\VM\Memory.dmp

 

Zipped up the files that I have are around 600MB so I will upload them on an FTP for you and PM the details to collect when that is done.

 

If you would like a fresh SysInspector log also then please let me know?

 

Cheers 

[Problems since definition 8766 with 3ware Controller]

UPDATE:  I have received some information from our supplier that ESET may know what is causing this issue.  I am not 100% sure if this is a direct correlation, and I have not yet had a chance to try the solution, but there may be a problem with the eamonm.sys driver file.  There is a development release out that he sent me to try, but it may be a day or two since I can only do this after hours.  There is not currently an installation package fix for this issue.

 

I did try enabling the DoubleBuffer registry key on the host machines this evening, and ESET was able to install and run without the crash.  I am running with that as the workaround until implementing a complete fix.  Thank you, socha, for the suggestion!

 

 

I am able to try a dev release immediately if ESET will make it available for me to do so, please let me know?

 

- have been stuck on my own support calls, requested logs incoming via PM shortly.

... No crash dump is available but after Sysinspector is finished performing the loading sequence I will send that.

[Problems since definition 8766 with 3ware Controller]

Hi Peter and All,

 

Reporting same issue as OP, with EAV BE, EEA and EFS on all Hyper-V machines running both 2008 r2 and XP .

 

Hello,

 

since 05.09.2013 and definition 8766 there are big trouble with ESET File Security and Mail Security on many Server with 3ware 9650 Controller. ...

... but on Hyper-V (2008r2) the VMs running in a BlueScreen.

Only uninstall ESET helps ...

 

Any one see this fresh error with this Hardware?

 

Also have 3ware (9650?) Controller installed and the issue is Hyper-V machines die with BSOD a few minutes after bootup / login.

 

In Safe Mode disabling the ekrn service for troubleshooting resolves the BSOD issue even after normal reboot until ekrn service is re-started. Even uninstalling, meticulously cleaning all traces of EAV BE / eea / efs from file system and registry and then re-installing does not resolve the issue once updates are collected again from ESET using choose automatically.

 

Hello Socha,

 

in case you experience BSOD please provide us with full memory dump and SysInspector log for further analysis.

 

 

I will endeavour also to collect the logs that you have requested in the morning, it is two hours past knock-off time here already and I'm late for beer.

 

If there is anything else I should know before then please let me know.

 

Cheers