Jump to content

Willtech

Members
  • Posts

    6
  • Joined

  • Last visited

About Willtech

  • Rank
    Newbie
    Newbie

Contact Methods

  • Website URL
    http://www.willtech.com.au/

Profile Information

  • Gender
    Not Telling
  • Location
    Australia
  1. 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
  2. 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
  3. 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
  4. 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 
  5. 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.
  6. 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 . 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. 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
×
×
  • Create New...