Avast WEBforum

Avast Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: jraju on January 05, 2019, 02:01:55 PM

Title: BSOD DUE TO ASWBIDDRIVER.SYS give the fix
Post by: jraju on January 05, 2019, 02:01:55 PM
Hi, Of late for a few days, my pc hang at every startup. The mouse would also vanish.
i checked memory and sfc no errors.
i also did chkdsk /r.
I had three times BSOD and the log read by nisrsot, pointed to aswbidsdriver.sys on all the three occasions.
Is this a recent things.
i have enabled auto update and so my present version is the latest version of the program.
Then why this happens, and what is the fix for it.
i am having windows 7 ultimate 32 bit
Title: Re: BSOD DUE TO ASWBIDDRIVER.SYS give the fix
Post by: Asyn on January 05, 2019, 03:24:30 PM
Follow instructions: https://support.avast.com/article/33/ and post your File-ID here afterwards.
Title: Re: BSOD DUE TO ASWBIDDRIVER.SYS give the fix
Post by: jraju on January 06, 2019, 03:12:59 AM
Hi, Asyn,
I want to clarify with you one thing before raising the ticket
Could the BSOD would result exclusively by the said avast driver
Or is it a indication that avast shows this alert of any other program.
I raise this query, because , when i checked misconfig and startup tab, after hiding msoft , besides avast and my trusted programs, there was a new entry
called WC assistant by lavasoft
i had not downloaded anything from Lavasoft
I just unchecked the program there , and also found the same program in program and features in control panel. I tried uninstalling it. I got a yellow triangle and ok box.
I noticed that it is weird and so, downloaded the revo uninstaller.
When i use revo uninstaller, then scanned, it shows some inside entries in registry and computer locations, and i selected all to delete.
I am using revo free edition
Then on the next reboot, i found the system boots normally without any hiccups, except, tje cursor just there at the centre of the desktop without moving.
on next reboot, i could log on normally
My crux of the query, would the avast driver become the cause of BSOD for some other program other than AVast.
Would this WC assistant, be the cause of the freeze and BSOD
because before this , the computer would boot with startup repair and then end iwith looping or sometimes alert to opt for system restore to get the normal boot.
I just thought of checking the BSOD log and it shows, the cause is AVAst avastbidsdriver.sys
Title: Re: BSOD DUE TO ASWBIDDRIVER.SYS give the fix
Post by: Asyn on January 06, 2019, 06:45:46 AM
To answer your questions, the devs would need your logs.
Title: Re: BSOD DUE TO ASWBIDDRIVER.SYS give the fix
Post by: igor on January 06, 2019, 06:18:28 PM
Yes, I believe IDP developers would need to see the .dmp file in question.
Btw, did you intentionally enable Driver Verifier on your machine? That's a Microsoft driver verification tool... it checks for various (possibly even kinda unimportant) issues happening - and if it detects something it doesn't like, it causes a BSoD (so that a dump is created or a debugger it notified if one is connected).

In other words, I can't say whether there's a bug in aswbidsdriver.sys (the .dmp file would be needed to say that), but it's quite likely that if you didn't have Driver Verifier enabled, nothing would happen.
Title: Re: BSOD DUE TO ASWBIDDRIVER.SYS give the fix
Post by: azzaroc on January 07, 2019, 02:43:26 PM
I have the same problem with Windows 7 Ultimate 32Bit crashing with an BSOD since update to the latest AVAST version 19.1.2360. I'm using an Thinkpad T60 and the problem can be reproduced by connecting an secondary monitor via DVI cable causing an BSOD immediately.

NirSoft BluescreenView Points to aswbidsdriver.sys


aswbidsdriver.sys   aswbidsdriver.sys+2823624c   0x8bc7b000   0x8bca8000   0x0002d000   0x5c0a6d51
atikmdag.sys   atikmdag.sys+1ec85070   0x9522d000   0x958ce000   0x006a1000   0x45ccea6f
cdd.dll   cdd.dll+316b3ab4   0x82800000   0x8281e000   0x0001e000   0x5b946c95
dxgkrnl.sys   dxgkrnl.sys+1e5e55dc   0x958ce000   0x95986000   0x000b8000   0x5b94664d
ntoskrnl.exe   ntoskrnl.exe+306759a0   0x8383c000   0x83c64000   0x00428000   0x5be855d0


I would attach a dmp file, if somebody tells me how ...
Title: Re: BSOD DUE TO ASWBIDDRIVER.SYS give the fix
Post by: Pondus on January 07, 2019, 02:47:33 PM
Quote
I would attach a dmp file, if somebody tells me how ...
Below the box you write in see  >>  Attachments and other options

also see/click link posted above by @Asyn


Title: Re: BSOD DUE TO ASWBIDDRIVER.SYS give the fix
Post by: azzaroc on January 07, 2019, 02:58:08 PM
Quote
I would attach a dmp file, if somebody tells me how ...
Below the box you write in see  >>  Attachments and other options

also see/click link posted above by @Asyn



Thanks, renamed it to *.dmp.gif, otherwise it won't allow upload
Title: Re: BSOD DUE TO ASWBIDDRIVER.SYS give the fix
Post by: kwiq on January 07, 2019, 03:26:51 PM
Hi azzaroc,
Just zip the dump file as azzaroc_bsod_7_1_2018.zip and upload on ftp://ftp.avast.com/incoming/ 
Thank you
Title: Re: BSOD DUE TO ASWBIDDRIVER.SYS give the fix
Post by: azzaroc on January 07, 2019, 03:43:35 PM
Hi azzaroc,
Just zip the dump file as azzaroc_bsod_7_1_2018.zip and upload on ftp://ftp.avast.com/incoming/ 
Thank you
FTP upload was done ... Thanks
Title: Re: BSOD DUE TO ASWBIDDRIVER.SYS give the fix
Post by: kwiq on January 07, 2019, 04:16:04 PM
Hi jraju,
can you also upload your dump file for analysis the picture you attached pointed to bad handle usage but  azzaroc's dump is about stack overflow.
Thank you !
 
Title: Re: BSOD DUE TO ASWBIDDRIVER.SYS give the fix
Post by: jraju on January 08, 2019, 02:29:45 AM
Hi,igur,
Your point is correct.
In order to fix the driver, i googled it and found an article to uses windows tool verifier . i just enabnled it and ofcourse, this produces the said BSOD on all the three times, as in the log.
Do you mean to say that the BSOD is purposely created by the verifier to give the logs, or in otherwords, bsod is a created one by the verifiere tool.
My other query is : even assuming that the tool creates the log, it should be presumed that it gives the avastsbids driver.sys as a kind of bug driver.
I also wish to state that the problem of system hangs on the next reboot after i remove the lavasoft adaware by webcompanisans.com is gone. i have to verify still further about, it being the cause for sure. i am sending reply from the other laptop.
I have not been receiving email alerts, for all the post in my inbox from avast, even when i enabled to get the email replies. why
i also know the adaware is a PuP. Would it cause this kind of mouse vansihing and windows hanging and freezing in the start screen itself.
i want your detailed reply on the points i raised.
My query is even assuming that the said adaware PuP is supposed to cause the hang on, why the verifier puts avastbidsdriver'sys as the problematic driver capable of causing BSOD.i VISITED this page after not getting any response in my inbox the replies alerts.
Title: Re: BSOD DUE TO ASWBIDDRIVER.SYS give the fix
Post by: jraju on January 08, 2019, 02:36:43 AM
Hi, azzaroc, did you receive any reply from avast team. Sometimes, they reply to the individual concerned.
What i mean is avast staff could check the avastbidsdriver.sys behaviour with the logs that would produce in their system. Verifier,if produces BSOD on avast driver, they  could themselve see the logs for forwarding to avast team.
Why cannot they use the verifier tool  and see the logs themselves.
Please see my query: i asked any third party programs could cause the BSOD using avastbidsdriver.sys. there is no answer to that query
Title: Re: BSOD DUE TO ASWBIDDRIVER.SYS give the fix
Post by: igor on January 08, 2019, 09:04:04 AM
Do you mean to say that the BSOD is purposely created by the verifier to give the logs, or in otherwords, bsod is a created one by the verifiere tool.

Yes, that is exactly the case.

My other query is : even assuming that the tool creates the log, it should be presumed that it gives the avastsbids driver.sys as a kind of bug driver.

There could be a bug, sure. On the other hand, the bug may be so tiny (without any actual effects on the system) that it really wouldn't cause any malfunction - without verifier enabled. Impossible to say without the corresponding dump.

What i mean is avast staff could check the avastbidsdriver.sys behaviour with the logs that would produce in their system. Verifier,if produces BSOD on avast driver, they  could themselve see the logs for forwarding to avast team.

The dump from azzaroc is not related to your issue, it's (almost certainly) a different problem (caused by big stack usage - partly by ATI drivers, partly by Avast - which, in sum, goes too high).

Why cannot they use the verifier tool  and see the logs themselves.

It's not that easy - the specific condition where the driver verifier detects the bug may depend on other drivers you have in the system, versions of software, configuration...
Title: Re: BSOD DUE TO ASWBIDDRIVER.SYS give the fix
Post by: kwiq on January 08, 2019, 09:12:06 AM
Hi jraju,
driver verifier is standard tool used and provided by microsoft to test device drivers (their own and also third party drivers). We use it for development and also for testing but it is not recommended to have it enabled on common pc's without knowing what it does. For more details see (https://docs.microsoft.com/en-us/windows-hardware/drivers/devtest/driver-verifier)
Whenever driver verifier finds some kind of bug/error/warning it crashes your PC to create memory dump !

Here is description of your issue :
https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0xc4--driver-verifier-detected-violation

0xF6 (Windows 7 operating systems and later)   Handle value being referenced   Address of the current process   Address inside the driver that performs the incorrect reference   A driver references a user-mode handle as kernel mode.

Your dump is still worth for us !
Title: Re: BSOD DUE TO ASWBIDDRIVER.SYS give the fix
Post by: jraju on January 08, 2019, 10:02:27 AM
Hi, valuable information.
i tried to find a problematic driver, device driver, for my system hanging problem.
Here i have chosen the verifier tool.
So, probably it should have produced the  bsod logs, i understand.
My query is simple
Why it shows avast driver.
Should i make avast not start with computer start?
it seems peculiar that every time i start the computer, the screen hangs indefinitely at starting windows, and if i press the pwer off button , there is a screen warning that computer did not shut down correctly , with two options start repair and normal start. if i prefer normal start, it goes to the normal desktop and if i choose start up repair, it goes on looping and nothing happens. Even it does not alert system restore option. Even if i get the sr option, it just loops and never end.
i will try.
I have not send the bsod total logs, as i do not know specifically that avast driver gives me this problem.
Title: Re: BSOD DUE TO ASWBIDDRIVER.SYS give the fix
Post by: jraju on January 08, 2019, 11:59:20 AM
Hi, I uploaded the log files as per the 2nd post.
file id :989e4
can i expect a reply.
I still think that it is a driver issue.
The BSOD even generated by verifier does not include other drivers.
One more query: avast is a software and not a hardware
please
Title: Re: BSOD DUE TO ASWBIDDRIVER.SYS give the fix
Post by: kwiq on January 09, 2019, 10:57:53 AM
Hi,
avast av is software solution.
Please can you upload also this file : C:\Windows\MEMORY.DMP mentioned in event log
The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000c4 (0x000000f6, 0x0000082c, 0x8fcd2d28, 0x8f765276). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 010519-24234-01.


Title: Re: BSOD DUE TO ASWBIDDRIVER.SYS give the fix
Post by: jraju on January 10, 2019, 02:53:06 AM
hi, kwig, itried to attach from c:, could not
copied to d: drive and then tried to send, the forum rules did not permit this type
So, i renamed those as txt files, rename themto .dmp and then analyse
if any personal content is found in log, just delete those
i will try to attach the renamed files as you suggested
Attached: i found a small information, that this driver is orignially with AVG, when avast is running separately.
The bsod list the problem of address and also the crash address.
i would like to have the solultion.
could i rename the driver
i am having trouble to noraml start of windows.
the cause may be something else, but if i could receive the solution , well and good, kwig
Title: Re: BSOD DUE TO ASWBIDDRIVER.SYS give the fix
Post by: igor on January 11, 2019, 10:32:27 AM
I'm afraid the renaming to .txt and uploading them as a text file to forum corrupted those dumps - so we can't use them.
Would you be able to upload them to the FTP, as mentioned before in this thread?
Thanks.
Title: Re: BSOD DUE TO ASWBIDDRIVER.SYS give the fix
Post by: jraju on January 15, 2019, 02:17:13 AM
Hi, igor,
     tried to send tro ftp, but connection failed message alert always . i do not know how to proceed.
Should i log in anonymously, as in the figure.
Then how do you know, that it is from me.
please say the solution to the connection issue
mere;y say connnnction failure trying to reestablish conncetion
i do not have any internet problem
Title: Re: BSOD DUE TO ASWBIDDRIVER.SYS give the fix
Post by: DavidR on January 15, 2019, 03:01:06 AM
@ jraju
Yes log in anonymously.

Give it a unique name as suggested by kwiq (see quote below for another users upload) e.g. your forum name, bsod and the date of your confirmation it is uploaded (the date of your post) jraju_bsod_15_1_2019.zip

Hi azzaroc,
Just zip the dump file as azzaroc_bsod_7_1_2018.zip and upload on ftp://ftp.avast.com/incoming/ 
Thank you
Title: Re: BSOD DUE TO ASWBIDDRIVER.SYS give the fix
Post by: jraju on January 15, 2019, 03:33:39 AM
Hi, david,
i tried for some more time, but when i select upload file/s, created by 7zip, i get a error message error sending file, cannot create a file.
Now i am trying with win rar in zip format.
Ok, i will name it in such a way, that avast team members would find it easy to locate in their servers
what is the error in sending, i do not know, new to ftp sending
Title: Re: BSOD DUE TO ASWBIDDRIVER.SYS give the fix
Post by: jraju on January 15, 2019, 03:55:16 AM
Hi, oK FOUND THE  error. i hsould have added incoming to the general ftp address provided in the avast instructions.
Ok, file uploaded
i have not received any alert of upload was complete or not.
Had the files have been uploaded
how to know
Avast team kindly inform me about the receipt of zip files and following actions.
Note: After disabling the avast in msconfig and also enabling delayed start in settings, the bsod stops. i have to doubly sure . i will try more boots.
Certainly, it is an issue on the said driver, originally used in AVS, and subsequently updated by AVAST.
i have seen some forums whether edperts , advised just uninstall of this glorious free antivirus program
i never do
please analyse and give the solultion.
Title: Re: BSOD DUE TO ASWBIDDRIVER.SYS give the fix
Post by: kwiq on January 15, 2019, 09:36:28 AM
Hi jraju,
all dumps are valid and were forwarded to devs.
Thank you !
Title: Re: BSOD DUE TO ASWBIDDRIVER.SYS give the fix
Post by: jraju on January 28, 2019, 03:04:32 AM
hi, anything you found out,avast team.
eagerly awaiting reply
Title: Re: BSOD DUE TO ASWBIDDRIVER.SYS give the fix
Post by: kwiq on January 28, 2019, 08:52:36 AM
Hi,
fix is included in 19.2 update which will be released 5.2 2019 (Beta users already have 19.2 versions)
Title: Re: BSOD DUE TO ASWBIDDRIVER.SYS give the fix
Post by: jraju on January 28, 2019, 11:46:13 AM
Hi thanks . But you could say what is the bug. What is found in my minidumps.
This driver was also noted in eventid.net atleast say a few words on the bug,avast team.
Title: Re: BSOD DUE TO ASWBIDDRIVER.SYS give the fix
Post by: jraju on February 05, 2019, 12:57:02 PM
Hi, Could i expect a reply to the bug question  i raised. Avast team said that fix is under progress and would be released for BSOD problem in a specific driver. i have sent minidump and all other logs.. When the fix is expected? Had it already been done in daily updates or expected in new upgrade.
Title: Re: BSOD DUE TO ASWBIDDRIVER.SYS give the fix
Post by: kwiq on February 05, 2019, 01:30:40 PM
Hi jraju,
fix is a part of upcoming 19.2 update.
It is already available in beta channel for brave users :-) 
Title: Re: BSOD DUE TO ASWBIDDRIVER.SYS give the fix
Post by: jraju on February 05, 2019, 01:59:15 PM
Hi, What is the differnece between beta and my stable version.
When do i expect the stable version to have it.
Can i use beta version
Is that something having advanced features.
i only download the latest from the avast site.
should i uninstall andand download beta version and reinstall
when the update is expected for the general public like meYou are silent on what is the bug.
Title: Re: BSOD DUE TO ASWBIDDRIVER.SYS give the fix
Post by: Be Secure on February 05, 2019, 03:53:13 PM
Quote
What is the differnece between beta and my stable version.
A Beta version may have unfixed bugs,many new changes in GUI etc.It is better to stay way from beta if you are a normal user not a beta tester.

Quote
When do i expect the stable version to have it./when the update is expected for the general public like me
When they are sure almost all known bugs and issues are fixed.

Quote
Can i use beta version
Yes any time.
Quote
should i uninstall andand download beta version and reinstall
It is better to do a clean install of avast always and after finishing the update do a reboot.




Title: Re: BSOD DUE TO ASWBIDDRIVER.SYS give the fix
Post by: kwiq on February 06, 2019, 08:48:38 AM
Hi jraju,
beta is really only for brave and experienced users because it contains bugs and new features!
It is not product meant to used by common users !
19.2 should be released within 1 week.
Title: Re: BSOD DUE TO ASWBIDDRIVER.SYS give the fix
Post by: Be Secure on February 06, 2019, 01:18:02 PM
New stable version 19.2.2364 has just been released.https://forum.avast.com/index.php?topic=225096.0 (https://forum.avast.com/index.php?topic=225096.0)
Title: Re: BSOD DUE TO ASWBIDDRIVER.SYS give the fix
Post by: jraju on February 09, 2019, 12:41:46 PM
Hi,, Kwig and Be secure, thanks for the new version.
I am a brave user and supplying logs to you.
Hope that you have fixed both bugs usb not safely ejecting and windows freeze on startup or in login.
So i will download your beta version and be using from now
Brave users, you mean  akind of programming skllled devel9pers or userrs knowing the risk of anything happens to windows.
Once i started using avast, i do not switch to any other product.
Recently i had seen a lengthy conversation in a user forum about choosing between avast and one other free antivirus. Quite  interresting to read point by point appraisal of avast and theother av and finally vote for avast.
what we need is a non intrusive non agressive antivirus
i download the latest standard version
Title: Re: BSOD DUE TO ASWBIDDRIVER.SYS give the fix
Post by: mapomaraca on February 10, 2019, 09:34:19 PM
I also get this same exact blue screen error message, even with the new update(!), when I try to start my VPN app. The computer restarts. But when I run avast with minimal security, without the firewall option, it works as normal.
Title: Re: BSOD DUE TO ASWBIDDRIVER.SYS give the fix
Post by: bob3160 on February 10, 2019, 11:31:58 PM
I also get this same exact blue screen error message, even with the new update(!), when I try to start my VPN app. The computer restarts. But when I run avast with minimal security, without the firewall option, it works as normal.
The problem has already been reported to the developers.
Title: Re: BSOD DUE TO ASWBIDDRIVER.SYS give the fix
Post by: jraju on February 11, 2019, 02:56:59 AM
Hi, but Bob avast team said that they have fixed this bug in  the latest updated version.
So, it seems that that the bug still exists.
Let us hope that avast fixes this issue.
this deiver, when used with AVG has created so much bsod then. I read , could not quote link now that avg forums and other forums did have so much threads on this problem.
I think , B'SOD is a serious problem for normal users as normal users do not know the prcoess of recoveriing their pc.
Please, avast team try to fix  this major error. I will see the 225 logs i quoted in the first post of this thread and report.
Has usb safe removal bug been fixed ?
Title: Re: BSOD DUE TO ASWBIDDRIVER.SYS give the fix
Post by: Asyn on February 11, 2019, 05:20:23 AM
I also get this same exact blue screen error message, even with the new update(!), when I try to start my VPN app. The computer restarts. But when I run avast with minimal security, without the firewall option, it works as normal.
The problem has already been reported to the developers.
-> https://forum.avast.com/index.php?topic=225112.0