Author Topic: avast.setup entcountered a problem and needed to close  (Read 5821 times)

0 Members and 1 Guest are viewing this topic.

MrX1980

  • Guest
avast.setup entcountered a problem and needed to close
« on: May 30, 2010, 10:41:40 PM »
hello

After Windows start and user login:





Windows XP Pro x64 SP2

Hint: Rename Avast.Setup.log to Avast.Setup.zip

MrX1980

  • Guest
Re: avast.setup entcountered a problem and needed to close
« Reply #1 on: June 06, 2010, 04:40:40 PM »
today again  :(

rename "WERd0b8.dir00.zip.log" to "WERd0b8.dir00.zip"

If you need more informations like dxdiag, just ask me.

idler4

  • Guest
Re: avast.setup entcountered a problem and needed to close
« Reply #2 on: June 10, 2010, 07:12:53 PM »
Hello. I have the same problem. Today I got 3 of those messages in a row upon logging in.

I am also running Win XP x64 Pro SP2...

Furthermore, I was getting an error message from AVG antivirus after boot before this. This was actually why I switched to Avast. Neither AVG nor Avast, nor Malwarebytes has detected any issues or threats to my system. All of these were the latest, currently available versions, and updated etc.

Help would be much appreciated!

Offline pk

  • Avast team
  • Super Poster
  • *
  • Posts: 2078
Re: avast.setup entcountered a problem and needed to close
« Reply #3 on: June 10, 2010, 08:18:31 PM »
MrX1980: thanks for dumps; hard to say ??? do you use IE7 ?


MrX1980

  • Guest
Re: avast.setup entcountered a problem and needed to close
« Reply #4 on: June 10, 2010, 08:30:47 PM »
MrX1980: thanks for dumps; hard to say ??? do you use IE7 ?

No, IE8 with all updates and Firefox 3.6.4

And this is not always. I think 2 or 3 times since 5.0.545 free was released.

Thanks for your effort!
« Last Edit: June 10, 2010, 09:29:29 PM by MrX1980 »

idler4

  • Guest
Re: avast.setup entcountered a problem and needed to close
« Reply #5 on: June 10, 2010, 08:54:06 PM »
IE8 for me too.

MrX1980

  • Guest
Re: avast.setup entcountered a problem and needed to close
« Reply #6 on: June 10, 2010, 09:42:23 PM »
Event Type:   Error
Event Source:   Application Error
Event Category:   (100)
Event ID:   1000
Date:      30.05.2010
Time:      22:13:43
User:      N/A
Computer:   AMD64X2WINXP64
Description:
Faulting application avast.setup, version 5.0.0.0, faulting module ntdll.dll, version 5.2.3790.4455, fault address 0x0004f053.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74   Applicat
0008: 69 6f 6e 20 46 61 69 6c   ion Fail
0010: 75 72 65 20 20 61 76 61   ure  ava
0018: 73 74 2e 73 65 74 75 70   st.setup
0020: 20 35 2e 30 2e 30 2e 30    5.0.0.0
0028: 20 69 6e 20 6e 74 64 6c    in ntdl
0030: 6c 2e 64 6c 6c 20 35 2e   l.dll 5.
0038: 32 2e 33 37 39 30 2e 34   2.3790.4
0040: 34 35 35 20 61 74 20 6f   455 at o
0048: 66 66 73 65 74 20 30 30   ffset 00
0050: 30 34 66 30 35 33         04f053 



Event Type:   Error
Event Source:   Application Error
Event Category:   None
Event ID:   1001
Date:      30.05.2010
Time:      22:19:26
User:      N/A
Computer:   AMD64X2WINXP64
Description:
Fault bucket 1437815387.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 42 75 63 6b 65 74 3a 20   Bucket:
0008: 31 34 33 37 38 31 35 33   14378153
0010: 38 37 0d 0a               87..   







Event Type:   Error
Event Source:   Application Error
Event Category:   (100)
Event ID:   1000
Date:      06.06.2010
Time:      16:31:02
User:      N/A
Computer:   AMD64X2WINXP64
Description:
Faulting application avast.setup, version 5.0.0.0, faulting module ntdll.dll, version 5.2.3790.4455, fault address 0x0004f053.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74   Applicat
0008: 69 6f 6e 20 46 61 69 6c   ion Fail
0010: 75 72 65 20 20 61 76 61   ure  ava
0018: 73 74 2e 73 65 74 75 70   st.setup
0020: 20 35 2e 30 2e 30 2e 30    5.0.0.0
0028: 20 69 6e 20 6e 74 64 6c    in ntdl
0030: 6c 2e 64 6c 6c 20 35 2e   l.dll 5.
0038: 32 2e 33 37 39 30 2e 34   2.3790.4
0040: 34 35 35 20 61 74 20 6f   455 at o
0048: 66 66 73 65 74 20 30 30   ffset 00
0050: 30 34 66 30 35 33         04f053 


Event Type:   Error
Event Source:   Application Error
Event Category:   None
Event ID:   1001
Date:      06.06.2010
Time:      16:37:04
User:      N/A
Computer:   AMD64X2WINXP64
Description:
Fault bucket 1437815387.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 42 75 63 6b 65 74 3a 20   Bucket:
0008: 31 34 33 37 38 31 35 33   14378153
0010: 38 37 0d 0a               87..

Offline pk

  • Avast team
  • Super Poster
  • *
  • Posts: 2078
Re: avast.setup entcountered a problem and needed to close
« Reply #7 on: June 14, 2010, 10:34:08 AM »
Please go to Settings/Updates/Proxy Settings and switch from auto-detect to direct, it should help you. Thanks.

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67194
Re: avast.setup entcountered a problem and needed to close
« Reply #8 on: June 14, 2010, 02:46:16 PM »
Please go to Settings/Updates/Proxy Settings and switch from auto-detect to direct, it should help you. Thanks.
Why doesn't avast do it automatically, i.e., check if the user is using a proxy and which type of connection does he/she use and solve it transparently?
The best things in life are free.

Niteme

  • Guest
Re: avast.setup entcountered a problem and needed to close
« Reply #9 on: January 08, 2011, 09:27:13 AM »
Have windows XP x64 too and had problems with avast.  Thank you for learning me ;)  Some "free" support guy that connected to my computer wanted $$$ to service windows.  No thanks, I'll do it myself so wow such an easy fix. 

However, I'm running the new beta 5.1.874 and when I had the older version 5.0.677.1 (I think) and after I updated into whatever it went to it wouldn't load my video drivers so my monitor and TV such off due to no signal.  Also, around the point where its loading all the drivers and the log in screen is about to load is when this would happen, which was nothing (sort of).  It didn't take me to log in screen but it rebooted, and would continue to do so until I shut her off hard.