Jump to content


  • Posts

  • Joined

  • Last visited

About 50040Leviathan

  • Rank

Profile Information

  • Location
  1. Hi Peter Thanks for helping with this. I have uploaded the (zipped) Procdump output to DropBox and sent you a PM with the link. I have not included any log output, as EOS v2 has never successfully completed a run on my PC. The only logs I can find date back to May and version 1, although there are quarantine files under AppData dating from 9th August -- this must have been the time when I stopped the v2 scan early (see original post). Do let me know where I might look for any other useful information for you. Regards
  2. Since ESET Online Scanner has been updated to version 2, I have not been able to use it on my PC. Version 1 worked fine. I ran it once a month to give a 'second opinion' to Comodo suite (installed and active) and MBAM (run manually once a week). Version 2 downloads, installs, starts, downloads virus descriptions, and starts scanning. (But that's all I know: the scan takes over 5 hours, so I run it overnight and have never seen it at scan completion.) When I come back to it, there is an incomplete and unresponsive GUI window, sometimes showing one or two lines of text indicating that a threat has been identified. Clicking on the window generates the Windows pop-up 'EOS_v2 has stopped working'. On Tuesday I stopped the scan early to deal with two or three already identified threats. This all worked fine, so I restarted it, but the problem (eventually) recurred. This suggests that the error may be occurring after the scan has completed? Yesterday I decided to search ESET Forums for advice, and found this thread: https://forum.eset.com/topic/8542-online-scanner-crashes/ It recommended downloading Procdump and running this to capture the crash. I have tried this. The crash actually occurs when you mouse-click on the unresponsive window. So, I now have a 384MB Procdump file... ...what now? PC is an elderly Dell Dimension E520 running Vista SP2 (32-bit). Can you help please?
  3. This is exactly why I created an ESET Forum account. In my case, the system is Vista 32-bit (yes, I know, but unlike my other (Win7) computers, it is still working!) EOS Version 1 worked fine. EOS Version 2 downloads, installs and starts OK, but crashes at some point, displaying an almost blank window. (Windows reports 'EOS_v2 has stopped working'.) Yesterday I managed to stop it part way to quarantine some files it had found in an archive area, then I restarted it. So, fundamentally it IS working, up to a point... I have downloaded procdump and will follow the above procedure overnight -- the ESET scan takes 5 hours to complete! -- then I'll start a new thread to request help. Edit: New thread may be found here: "Online Scanner v2 Crashes before completion"
  • Create New...