Avast WEBforum

Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: greatfox42 on September 06, 2019, 02:31:55 AM

Title: BSoD casued by avast
Post by: greatfox42 on September 06, 2019, 02:31:55 AM
Don't know if this should go into this forum or the beta subforum (there only seems to be topic by avast staff there), so if I guessed wrong please feel free to move it.

I am running the beta branch of avast, current version as of this post (19.8.2390). According to BlueScreenView, the fault is Avast. Considering the first thing that happened after a reboot is the avast window pulled up unprompted, I might agree.


I've sent the BSoD dump to the servers under the filename GreatFox422_9_5_19.zip. I realize this is unprompted but I'm planning on shutting this system down before further damage can be caused, so I want to provide what I expect to be necessary in advance. No Avast crash dumps were generated.


EDIT: Why am I 42 now instead of 422? What?
Title: Re: BSoD casued by avast
Post by: kwiq on September 06, 2019, 08:54:46 AM
Hi greatfox42,
dump forwarded to responsible dev team.
Thank you for report !
Title: Re: BSoD casued by avast
Post by: DavidR on September 06, 2019, 09:46:45 AM
<snip>
EDIT: Why am I 42 now instead of 422? What?

Because that username is already in use from April 2019 under a different email address.

If that is also you, you would have to logon with those credentials.
Title: Re: BSoD casued by avast
Post by: greatfox42 on September 12, 2019, 04:52:31 PM
Are there any updates?
Title: Re: BSoD casued by avast
Post by: kwiq on September 12, 2019, 08:00:34 PM
Hi
19.8 is still in beta channel yes we are working on rc candidate which contains a fix.
Title: Re: BSoD casued by avast
Post by: greatfox42 on September 13, 2019, 01:26:00 AM
Hi
19.8 is still in beta channel yes we are working on rc candidate which comtains a fix.

Thank you.

Title: Re: BSoD casued by avast
Post by: greatfox42 on September 13, 2019, 08:21:30 PM
Is the fix in today's update? If so, could I request information on what went wrong for the purposes of testing the fix by replicating the circumstances?