Jump to content

a2start beta 10204 crashed trying to start a custom scan


JeremyNicoll
 Share

Recommended Posts

Win 8.1, 64 bit.    Unfortunately debug logging was not on, after yesterday's experiments.

I used the GUI to try to start a custom scan, loaded predefined scan settings, and clicked NEXT.  Immediately got a "Emsisoft Security Centre has stopped working" pane, [with the usual misleading info that Windows is going to phone a friend and see if they can fix it (which has never ever worked for anything as far as I know)].

I was not offered a chance to send a dump to Emsisoft.   Windows did save a small crash dump - I'll PM its location to @Frank H

Event log has:

Log Name:      Application
Source:        Application Error
Date:          30/05/2020 11:09:24
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SAMSUNG-NP350
Description:
Faulting application name: a2start.exe, version: 2020.6.0.10204, time stamp: 0x5ecea8fc
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000005410fd8
Faulting process ID: 0x1ea0
Faulting application start time: 0x01d635bb1682db2e
Faulting application path: C:\Program Files\Emsisoft Internet Security\a2start.exe
Faulting module path: unknown
Report ID: a2cdc279-a25d-11ea-822f-50b7c3e8a12a
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2020-05-30T10:09:24.000000000Z" />
    <EventRecordID>250243</EventRecordID>
    <Channel>Application</Channel>
    <Computer>SAMSUNG-NP350</Computer>
    <Security />
  </System>
  <EventData>
    <Data>a2start.exe</Data>
    <Data>2020.6.0.10204</Data>
    <Data>5ecea8fc</Data>
    <Data>unknown</Data>
    <Data>0.0.0.0</Data>
    <Data>00000000</Data>
    <Data>c0000005</Data>
    <Data>0000000005410fd8</Data>
    <Data>1ea0</Data>
    <Data>01d635bb1682db2e</Data>
    <Data>C:\Program Files\Emsisoft Internet Security\a2start.exe</Data>
    <Data>unknown</Data>
    <Data>a2cdc279-a25d-11ea-822f-50b7c3e8a12a</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

Link to comment
Share on other sites

I always start my custom scans (usually done once per week) by importing settings, and what's more it's normal for me to import first a set of settings I don't plan to use, then import the set I do wish to use.  I know that's odd, but I do it because it means I always see something change in the GUI regardless of whatever was displayed before the import. 

I have a scan running now, which I started in exactly the same way as this morning's attempted one... except this time I do have debug logging on...

Link to comment
Share on other sites

  • 3 weeks later...
On 6/20/2020 at 10:38 AM, JeremyNicoll said:

This happened again this morning, albeit with a slightly newer version of a2start.  I've PMed Arthur with the location of the dump, debug logs, eventlog records etc.

yes we got the logs thanks

Link to comment
Share on other sites

  • 3 months later...
Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...