Avast WEBforum

Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: leap on July 07, 2020, 12:17:41 PM

Title: Windows 10 BSOD issue
Post by: leap on July 07, 2020, 12:17:41 PM
I would like to report a Windows 10 BSOD (Blue Screen of Death) issue on your network filter driver (aswArPot.sys) while spacedesk (https://spacedesk.net/) is connected over USB tethering connection.
Please check the dump analysis here:

It seems that your network filter driver (aswArPot.sys) is crashing when doing network transfer over RNDIS driver (USB tethering connection).
Title: Re: Windows 10 BSOD issue
Post by: Asyn on July 08, 2020, 06:35:07 AM
Dev-Info: From the attached stack aswArpot is not to blame for BSOD, aswArPot.sys is filtering Afd and it is not the reason of BSOD in this case.
Title: Re: Windows 10 BSOD issue
Post by: leap on July 08, 2020, 11:59:32 AM
CORRECT: Avast driver software aswArPot.sys is filtering Microsoft driver software afd.sys

So you say it is Microsoft's fault??? afd.sys is not only coming from Microsoft but actually comes as in integral part with the Windows 10 operating System.

Then why do we NEVER hear of Microsoft afd.sys crashing WITHOUT Avastas aswArPot.sys?
FYI: Microsoft afd.sys is installed on EVERY Windows 10 machine! More than 1 BILLION.
On how many less is Avast aswArPot.sys installed? 
Why do we never hear of Microsoft afd.sys crashing on more than 1 BILLION of machines?
Why do we only hear of it crashing in these rare cases when Avast aswArPot.sys is also present?

Avast aswArPot.sys network filter driver is filtering another driver. This poor other filtered driver is crashing. Who's fault is it? ALWAYS THE FILTER DRIVER'S FAULT! This is basic knowledge of Windows device driver software development which can be learned at any reasonable driver developer seminar.
Title: Re: Windows 10 BSOD issue
Post by: Spec8472 on July 08, 2020, 12:59:18 PM
Hello Leap,

aswArpot.sys is filtering Afd driver, that's true, but the crash is much lower in callstack Afd -> Tcpit -> Ndis -> Rndismp6 -> Usb80236(Crash). The aswArpot.sys processing is basically pass-through here. MS always blames first non-MS driver found in upper stack frames, which is pretty allibistic approach. In such situation 3rd party filter (if present) is always guilty according to MS. I'd suspect Usb80236 first, but this still could be caused by other Avast WFP network filter. It is hard to say without complete memory dump.