Author Topic: ashMaiSv not working  (Read 4857 times)

0 Members and 1 Guest are viewing this topic.

zoch

  • Guest
ashMaiSv not working
« on: October 24, 2004, 03:05:05 AM »
Home Edition. After installing new iAvs i can`t run ashMaiSv ( Internet Mial scaning ) . I have XP SP2. New installed Avast works Ok, until I update program . Please help me !

Jacek

Offline Eddy

  • Avast Evangelist
  • Maybe Bot
  • ***
  • Posts: 31222
  • Watching (over?) you
    • Malware removal, Biljart and other things.
Re:ashMaiSv not working
« Reply #1 on: October 24, 2004, 10:10:15 AM »
- What is the exact error you are getting?
- What version of Avast? (4.1 or 4.5)
- Any error(s) in Avast's log file? If so what is the exact error there?

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 86543
  • No support PMs thanks
Re:ashMaiSv not working
« Reply #2 on: October 24, 2004, 01:56:58 PM »
What email program?
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 22.2.6003 (build 22.2.7013.717) UI 1.0.697/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

zoch

  • Guest
Re:ashMaiSv not working
« Reply #3 on: October 24, 2004, 06:32:18 PM »
Outlook Express

zoch

  • Guest
Re:ashMaiSv not working
« Reply #4 on: October 24, 2004, 06:36:19 PM »
1. It happend in 4.1, after upgrading to beta 4.5 it is now Ok, but how long ?
2. It is internal error - program can`t start
Some information from log :
Crash list of Avast Antivirus, v.4.5.494
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

------------------
System Information
------------------
Time of this report: 2004-10-24, 03:34:09
      Computer name: »OCH
   Operating System: Microsoft Windows XP Professional (Build 2600) Dodatek Service Pack 2
          Processor:               Intel(R) Pentium(R) 4 CPU 3.00GHz, MMX, ~2979Mhz
      System memory: 1048048 KB (installed), 826344 KB (available), 2097024 KB (virtual)
           Language: 0415-0415-0415-0415 (SLangID, SLCID, ULangID, ULCID), 0415-0415 (SUILang, UUILang)

Fault source
------------
D:\Avast4\ashServ.exe caused an Access Violation at location 6538108e Reading from location 6538108e.

-----------
Crash place
-----------


   don't have read access to the specified range of memory

----------------
Register content
----------------
EAX=00000000 EBX=7C802530 ECX=7C802600 EDX=7C90EB94 ESI=00000003 EDI=7C809C28
EIP=6538108E ESP=02A8FFA8 EBP=65004060 IOPL=0         NV UP EI PL NZ NA PE NC
CS=001B  SS=0023  DS=0023  ES=0023  FS=003B  GS=0000             FLG=00010202

----------
Call stack
----------
AddrPC     AddrReturn AddrFrame  AddrStack  Params
6538108E   0018E6A8   02A8FFA4   02A8FFA8   00000008   02A8FFEC   00000000   7C80B50B
6538108E
0018E6A8   C4353B08   65004060   02A8FFA8   726501AE   5EC03304   3C8D57C3   FD3C8D76
0018E6A8
C4353B08   00000000   24748B56   02A8FFA8   00000000   00000000   00000000   00000000
C4353B08

-----------
Stack frame
-----------
[02A8FFA8]: A8E61800 08000000 ECFFA802 00000000 0BB5807C 00000000 A8E61800 08000000     ĘŠ......ý.Ę......Á.|....ĘŠ......
[02A8FFC8]: 00000000 0050FD7F 050000C0 C0FFA802 CCFBA802 FFFFFFFF F399837C 18B5807C     .....Př....└└.Ę.╠űĘ.....ˇ..|.Á.|
[02A8FFE8]: 00000000 00000000 00000000 60103865 00000000 00000000
error: don't have read access to the specifies range of memory

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67241
Re:ashMaiSv not working
« Reply #5 on: October 24, 2004, 10:39:17 PM »
It is now Ok, but how long?

What about waiting a little?  ;D
Zoch, no problem here with OE and XP Pro SP2.
Let us know if you have more troubles (I hope not).
Maybe someone from Alwil team could interpretate the memory dump  ;)
The best things in life are free.

zoch

  • Guest
Re:ashMaiSv not working
« Reply #6 on: October 25, 2004, 01:57:17 AM »
I hope it will be Ok :-)


Offline Eddy

  • Avast Evangelist
  • Maybe Bot
  • ***
  • Posts: 31222
  • Watching (over?) you
    • Malware removal, Biljart and other things.
Re:ashMaiSv not working
« Reply #7 on: October 25, 2004, 02:06:45 AM »
Keep us informed please. If the problem is not gone we can give other suggestions. If the problem is solved it is always nice to hear and others who read this thread can benefit from it. ;)