Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: Arnold72 on May 25, 2013, 12:10:19 AM
-
Hello avast forum and sincere greetings to all.
Just a little problem that i hope someone will help me with.
When i was using avast 8 version 1483 the program ran just fine with no issues on my computer at all.
I then updated to the latest version internally and this ran fine for a few days and then suddenly i was getting blue screens regularly at boot up.
I was running avast alongside comodo firewall 5.12 and by a process of elimination i have narrowed the culprit down to avast.
This has saddened me slightly as i love avast and i have unwillingly had to uninstall avast and use another av.
At some point i want to install avast again.
Could somebody please explain why there were bluescreens and could the issue be caused because i updated internally.?
Is it advisable to do a fresh install with every update as i suspect it was because of me updating internally that may have been the issue.
I really like avast and i love the protection offered and i want to try again with a clean install.
Thank You.
-
hey a clean installation is a good choose to do.
download the latest version of avast to your desktop from avast.com
second download and run the avast uninstall tool which can be found here
http://www.avast.com/en-se/uninstall-utility
reboot your computer
install the fresh copy you downloaded to your desktop.
a quick question how do you know your problem is avast related and not comodo?
-
Please check for the corresponding minidump files (in C:\Windows\Minidump) and upload them to ftp://ftp.avast.com/incoming
-
Hello.
Thank you for the replies.
Yes im quite certain the latest version of avast was the culprit for the blue screens as i removed comodo and the bsods were still occuring.
But saying that i updated avast internally and this might be a factor in the blue screens.
Prior to the blue screens on the log on window an extra window appeared which belonged to the software updater module.Then it disappeared for some reason.
im going to attempt a clean install of avast and see if this cures the problem.
Does the latest version of avast use a different kernel driver from the previous version as there could be conflicts arising.
Thanks.
-
The BSOD was causing only in Avast v8.0.1488 and they've fixed the bug problem relating to the BSOD for W7 & W8 64bit to a new Avast v8.0.1489, so make sure you download the latest version 8.0.1489 only stay away from version 8.0.1488.
See link to download the latest version http://forum.avast.com/index.php?topic=123563.msg937973#msg937973 It safe to install over the top of v8.0.1483 just make sure you backup you're Avast setting first before you start.
-
The BSOD was causing only in Avast v8.0.1488 and they've fixed the bug problem relating to the BSOD for W7 & W8 64bit to a new Avast v8.0.1489, so make sure you download the latest version 8.0.1489 only stay away from version 8.0.1488.
Hello speedy and thank you.
I have used comodo for years and never had a blue screen from it so im very certain comodo was not the issue.
Also i noticed avast was not informing me of any program updates at all and i only discovered there was an update from this forum.
It was version 1489 i was using.
But i believe the problem was caused by not performing a clean install.
As i said before i installed internally and this seems to be the problem.
Thanks again.
-
The BSOD was causing only in Avast v8.0.1488 and they've fixed the bug problem relating to the BSOD for W7 & W8 64bit to a new Avast v8.0.1489, so make sure you download the latest version 8.0.1489 only stay away from version 8.0.1488.
Hello speedy and thank you.
I have used comodo for years and never had a blue screen from it so im very certain comodo was not the issue.
Also i noticed avast was not informing me of any program updates at all and i only discovered there was an update from this forum.
It was version 1489 i was using.
But i believe the problem was caused by not performing a clean install.
As i said before i installed internally and this seems to be the problem.
Thanks again.
Turn off Comodo Behavior Blocker because they both conflict with Avast Behavior Blocker if you have both running at the time.
Edit: Keep mind Avast Behavior Blocker is stronger and better than Comodo Behavior Blocker from my understanding not to have both running.
-
The BSOD was causing only in Avast v8.0.1488 and they've fixed the bug problem relating to the BSOD for W7 & W8 64bit to a new Avast v8.0.1489, so make sure you download the latest version 8.0.1489 only stay away from version 8.0.1488.
Hello speedy and thank you.
I have used comodo for years and never had a blue screen from it so im very certain comodo was not the issue.
Also i noticed avast was not informing me of any program updates at all and i only discovered there was an update from this forum.
It was version 1489 i was using.
But i believe the problem was caused by not performing a clean install.
As i said before i installed internally and this seems to be the problem.
Thanks again.
Turn off Comodo Behavior Blocker because they both conflict with Avast Behavior Blocker if you have both running at the time.
Edit: Keep mind Avast Behavior Blocker is stronger and better than Comodo Behavior Blocker from my understanding not to have both running.
Hello speedy.
I must apologise as i should of stated im not using version 6.
Im using v5.12 which i consider has a better layout than v6.
Seems to be a lot of problems with v6 at the moment so im staying clear for a while.
Thanks again.
-
True their was a lot of problem in v6.0 and not v6.1 and that is you're choice I wasn't to sure IF their was a BB in v5.12 as I cannot tell from the end of my tail, try and excluded applications for Comodo FW in Avast and try and excluded applications for Avast in Comodo and see IF this solve the issue.
-
True their was a lot of problem in v6.0 and not v6.1 and that is you're choice I wasn't to sure IF their was a BB in v5.12 as I cannot tell from the end of my tail, try and excluded applications for Comodo FW in Avast and try and excluded applications for Avast in Comodo and see IF this solve the issue.
Hi speedy.
Yes i did all the mutual exclusions with both programs.
No BB in 5.12 but i just prefer this versions layout and usability.
Thanks.
-
I'm not sure if Defense+ should be turn off otherwise I can't help you any further to solve the issue sorry, you might want to check the issue for answer through Comodo forum you might not get enough information here on Avast forum relate to Comodo FW issue with the latest version of Avast. Just sit tight and maybe another Comodo FW user might be able to help you with you're issue as I'm using the full package of CIS for a while, and then I coming back to Avast Free asap.
-
I'm not sure if Defense+ should be turn off otherwise I can't help you any further to solve the issue sorry, you might want to check the issue for answer through Comodo forum you might not get enough information here on Avast forum relate to Comodo FW issue with the latest version of Avast. Just sit tight and maybe another Comodo FW user might be able to help you with you're issue as I'm using the full package of CIS for a while, and then I coming back to Avast Free asap.
Hi speedy,
Thank you kindly for your input.
Im going to attempt a clean install of avast and see how it goes.
I am quite convinced updating internally may have been the issue.I like avast and its a great av and im not going to bash it at all as it may be just me that was at fault.
Thanks again.
-
This is the problem when you combine security products. Back in the XP days the need for a 3rd party of firewall was necessary. But ever since Vista it is not longer needed. Best suggestion is to COMPLETELY uninstall both products. Only install Avast and run for days. Use Avast with Windows firewall. If you never have a BSOD then go ahead and install Comodo. See what happens. If you have a BSOD then the two programs are not playing nice together. Did you exclude Comodo from Avast? Did you exclude Avast from Comodo?
-
This is the problem when you combine security products. Back in the XP days the need for a 3rd party of firewall was necessary. But ever since Vista it is not longer needed. Best suggestion is to COMPLETELY uninstall both products. Only install Avast and run for days. Use Avast with Windows firewall. If you never have a BSOD then go ahead and install Comodo. See what happens. If you have a BSOD then the two programs are not playing nice together. Did you exclude Comodo from Avast? Did you exclude Avast from Comodo?
Hello Aventador.
Yes i did all the mutual exclusions in both programs.
I firstly removed comodo as you suggested and ran it with windows firewall but then i discovered i was having connectivity issues.
I then installed comodo firewall and the network problems disappeared.
As ive said before everything was running ok until i updated to the latest version.
I was running v1483 with comodo and there were no issues.
I then updated to v1488 and there were no problems.
I then updated to v1489 and then the blue screens started occuring on a regular basis at boot up so its plainly obvious that v1489 is the culprit.
I removed avast v1489 and there have been n bluescreens ever since.
My conclusion is that there was/is a conflict between comodo 5.12 and the latest version of avast.
Thank You.
-
My conclusion is that there was/is a conflict between comodo 5.12 and the latest version of avast.
Thank You.
Can you please try Comodo FW v6.1 with Avast v8.0.1489, because v6.1 has fix the compatibility with Avast and Comodo together all I'm saying is try it without Comodo BB.
-
So its neither an Avast issue or a Comdo issue. Its an issue on your part trying to use both programs together. The reason you probably could not connect after uninstalling Comodo is that it probably never uninstalled cleanly. Comodo leaves a lot of left overs. Did you remove all the drivers? Using something like Revo Uninstaller in Advanced Mode often works great.
-
Don't touch Revo Uninstaller is a bloody nightmare >:( >:( >:( >:( >:(
Edit: Please used CCleaner to clean out you're left over registry file because it very safe after you uninstall through Windows and not Revo Uninstaller. http://www.piriform.com/ccleaner/download/slim
-
Don't touch Revo Uninstaller is a bloody nightmare >:( >:( >:( >:( >:(
No not true at all. Used it a million times. Now a days I use Advanced Uninstaller Pro.
But by now he has uninstalled a reinstalled so many times the registry is probably corrupted. A fresh OS install with cure that problem. Did you purge the old rules from Windows Firewall?
-
So its neither an Avast issue or a Comdo issue. Its an issue on your part trying to use both programs together. The reason you probably could not connect after uninstalling Comodo is that it probably never uninstalled cleanly. Comodo leaves a lot of left overs. Did you remove all the drivers? Using something like Revo Uninstaller in Advanced Mode often works great.
Im sorry but i simply must disagree with this.
Please explain the concept of a "layered security defense" the same principle applies throughout.
And with all due respect i believe it is an avast issue,notably with the latest version.
How come the previous 2 versions ran just fine with comodo and yet the new one does not..?
I did remove comodo cleanly and via CMD i removed all phantom drivers.
But i will say that the comodo uninstaller utility does leave a lot to be desired.
But after saying all this i did have comodo programs manager installed too so that maybe a contributing factor also.
As i have said before i am going to try a clean install as i strongly believe it was the internal update hindering things.
Thanks.
-
Hi arnold72,
So you know for certain, you could try using either one of these to determine which driver caused the crash.
http://www.resplendence.com/whocrashed
http://www.nirsoft.net/utils/blue_screen_view.html
I would do as Dwarden recommended and upload the minidump to the folks at avast so they can fix it if it is a BSOD caused by avast.
-
Don't touch Revo Uninstaller is a bloody nightmare >:( >:( >:( >:( >:(
No not true at all. Used it a million times. Now a days I use Advanced Uninstaller Pro.
But by now he has uninstalled a reinstalled so many times the registry is probably corrupted. A fresh OS install with cure that problem. Did you purge the old rules from Windows Firewall?
And when a program that you haven't used for month no longer works when you finally need it,
you might be surprised to find out that Revo has uninstalled a shared DLL when it removed that other program.
Stay away from generic uninstallers unless you're looking for a problem.
-
Hi arnold72,
So you know for certain, you could try using either one of these to determine which driver caused the crash.
http://www.resplendence.com/whocrashed
http://www.nirsoft.net/utils/blue_screen_view.html
I would do as Dwarden recommended and upload the minidump to the folks at avast so they can fix it if it is a BSOD caused by avast.
Okay upon a review of what exact software i had installed.
Maybe and its a big maybe that comodo programs manager could of have been involved as it performs a force delete at reboot.
But from an earlier post i am fairly certain avast was the cause but i am openminded with this.
I will perform a clean install and see what happens.
Thanks.
-
Nothing should ever be installed or uninstalled on ANY pc without having a decent backup. ToolWiz Time Freeze is a great tool for trying out software.
-
Here's how to install the Comodo Firewall http://www.knightwithapc.com/2011/11/download-comodo-firewall/ 8)
As SpeedyPC stated disable the CFW "behavior blocker" since avast has a solid "behavior shield".
I'm running CFW 6.0 w/D+ and no behavior blocker with no issues. :)
-
Hmm I prefer version 5 of comodo myself.far easier to navigate and find settings etc.
Version 6 is a swamp of mouse clicks and the interface needs a revamp.
-
I'm having the exact same issue with random BSOD's on boot. It started when I upgraded Avast to version 8 six weeks ago. I had a look at the minidumps with whocrashed and it said the problem was an Avast driver aswsnx.sys.
-
@Arnold,
Have you sent in the mini-dump as suggested in reply #2 or aren't you really interested in solving the problem ?
@Dumper,
If you're interested in solving the problem, then please also send in the mini-dump.
Complaining for the sake of complaining has never solved a single problem. ;) [size=78%] [/size]
-
@Arnold,
Have you sent in the mini-dump as suggested in reply #2 or aren't you really interested in solving the problem ?
@Dumper,
If you're interested in solving the problem, then please also send in the mini-dump.
Complaining for the sake of complaining has never solved a single problem. ;) [size=78%] [/size]
When i get round to it im going to try a fresh clean re-install of the latest avast to see what happens.
Upon browsing the web to research this issue it seems that quite a substantial amount of people are having this problem so obviously the latest version of avast was not tested vigorously enough during the beta stage.
I dont want to hear about uploading dump files as all this will reveal is that the avast driver is at fault.
What i would like to hear is what can be done about it.
This is not half a dozen incidents of blue screen we are talking about.
The amounts of problems with the virtualization driver alone are quite substantial.
I understand that avast cannot be tested on every configuration but the majority of blue screens are occuring at boot-up.
So it should not be too hard to narrow down what part of avast is at fault.
As @dumper stated the driver in question seems to be the virtualization driver.
Hope this problem gets corrected soon with an update.
Thank You.
-
I was having the BSOD problem too. I disabled the Behavior Shield and that seems to have stopped the problem for now.
-
@Dumper,
If you're interested in solving the problem, then please also send in the mini-dump.
Complaining for the sake of complaining has never solved a single problem. ;) [size=78%] [/size]
I wasn't complaining, just explaining I have a problem which is what I thought these forums were for.
-
@Arnold,
Have you sent in the mini-dump as suggested in reply #2 or aren't you really interested in solving the problem ?
@Dumper,
If you're interested in solving the problem, then please also send in the mini-dump.
Complaining for the sake of complaining has never solved a single problem. ;) [size=78%] [/size]
Nobody is complaining.
Just stating there is a problem with avast installation.
It seems to me that the latest version of avast and BSOD seem quite synonymous.
I know what some vendors are like when it comes to "free" software.
Its a free program so the users can suffer the bugs and crashes.
Not here.
I have uninstalled and await a fix.
Thanks.
-
Nobody is complaining.Just stating there is a problem with avast installation.
If you aren't willing to do anything about resolving your problem, then I'd call it complaining.
Help is a two way street which starts by stating the problem and continues by supplying requested information.
-
Nobody is complaining.Just stating there is a problem with avast installation.
If you aren't willing to do anything about resolving your problem, then I'd call it complaining.
Help is a two way street which starts by stating the problem and continues by supplying requested information.
That is a totally unacceptable and patronising reply.
The blue screen issues have been quite widespread and an acknowledgement from avast that there is a problem with their latest version would be a healthy start.
I cannot upload any dumps pf any kind now because avast is uninstalled at the moment and this was done for the sake of the computers health.
I do not feel that uploading dumpfiles of any sort would be of any benefit.
As i have stated before,i will attempt another clean install of avast when i observe that substantial efforts have been made to rectify what seems a common issue and sweeping it under the carpet and pretending an issue does not exist will not do this.
Thank You.
-
@Arnold72 without that dump-files and you've already uninstall Avast software is because the dump-files is the only clue to give the Avast Staff to investigate you're problems and issue such as BSOD for example, so I strongly agree with Bob as you aren't willing to do anything to help yourself about resolving your problems and issue without that dump-files because we ask you to uploaded ASAP and to allow the Avast Staff to help. Suddenly you couldn't be bothered because it's too hard for you and Bob is 100% correct the more you complain you're issue and problems will never be resolved, so you've wasted your time and the Avast Forum Teams for their time and not been able to help you fine.
Just remember this Arnold72 when I see you're issue from my own point of view is without the help they offer to you in friendly kind way, and you're behaviour is becoming and a complete "PRICK" so when you're complaining for the sake of complaining has never solved a single problem as Bob is 100% correct.
-
@Arnold72 without that dump-files and you've already uninstall Avast software is because the dump-files is the only clue to give the Avast Staff to investigate you're problems and issue such as BSOD for example, so I strongly agree with Bob as you aren't willing to do anything to help yourself about resolving your problems and issue without that dump-files because we ask you to uploaded ASAP and to allow the Avast Staff to help. Suddenly you couldn't be bothered because it's too hard for you and Bob is 100% correct the more you complain you're issue and problems will never be resolved, so you've wasted your time and the Avast Forum Teams for their time and not been able to help you fine.
Just remember this Arnold72 when I see you're issue from my own point of view is without the help they offer to you in friendly kind way, and you're behaviour is becoming an complete "PRICK" so when you're complaining for the sake of complaining has never solved a single problem as Bob is 100% correct.
Now look speedy gonzales.!!!
I am not going to have a f***ing bitching contest with you.
I am going to do a CLEAN INSTALL!!!!
Then i will report on the outcome.
Do you understand???
And would you kindly keep your insults to yourself and refrain from terming me a P&&&k.
The only P***K is you when you post such garbage.
-
@Arnold72 without that dump-files and you've already uninstall Avast software is because the dump-files is the only clue to give the Avast Staff to investigate you're problems and issue such as BSOD for example, so I strongly agree with Bob as you aren't willing to do anything to help yourself about resolving your problems and issue without that dump-files because we ask you to uploaded ASAP and to allow the Avast Staff to help. Suddenly you couldn't be bothered because it's too hard for you and Bob is 100% correct the more you complain you're issue and problems will never be resolved, so you've wasted your time and the Avast Forum Teams for their time and not been able to help you fine.
Just remember this Arnold72 when I see you're issue from my own point of view is without the help they offer to you in friendly kind way, and you're behaviour is becoming and a complete "PRICK" so when you're complaining for the sake of complaining has never solved a single problem as Bob is 100% correct.
That's completely uncalled for, the guy asks for help and you insult him.
-
I would just like to add that due to the insulting and aggressive attitude of some of the forum members i have decided not to attempt any further installation of avast.
As good as an av it is i feel the support from this forum is grossly unfair to the reputation of avast.
I just hope that the avast staff are nothing like the condescending and arrogant fools who call themselves avast evangelists.
Thank You.
-
I would just like to add that due to the insulting and aggressive attitude of some of the forum members i have decided not to attempt any further installation of avast.
As good as an av it is i feel the support from this forum is grossly unfair to the reputation of avast.
I just hope that the avast staff are nothing like the condescending and arrogant fools who call themselves avast evangelists.
Thank You.
Sorry to see you go Arnold72, most people here are friendly and helpful, it's a pity a few aren't. Hopefully in time you will change your mind and give Avast and its forums another try. :)
-
Could someone tell me how to upload minidump files as mentioned in Reply#2, the link is a webpage.
-
Look for the latest minidump in C:\WINDOWS\Minidump or in C:\Windows\MEMORY.DMP. Compress it with ZIP, RAR or 7Zip and give it an original name. Add a text ( use notepad ) with your Forum e-mail and your post URL.
Open Windows Explorer and copy/paste this:
ftp://ftp.avast.com/incoming
Drag/drop compressed dump file into the right open window. Wait for transmission to conclude.
You can also do it like this:
Start > Run.
Copy/paste
explorer ftp://ftp.avast.com/incoming
Drag dump file into the ftb window.
-
Thank you iroc9555.
-
Thank you iroc9555.
You are welcome. Good luck.
-
Hi there,
I received BSOD with the same symptoms. Here are some of my minidumps (I also uploaded a support package in Avast):
On Sat 15.06.2013 09:36:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061513-19063-01.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x4D9F1)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800A0703B8, 0xFFFFF8800A06FC10, 0xFFFFF80002ED83C9)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\aswsnx.sys
product: avast! Antivirus
company: AVAST Software
description: avast! Virtualization Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: aswsnx.sys (avast! Virtualization Driver, AVAST Software).
Google query: AVAST Software NTFS_FILE_SYSTEM
On Sun 16.06.2013 09:11:34 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x261B1)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002F7C11F, 0xFFFFF88006C75D40, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\aswsnx.sys
product: avast! Antivirus
company: AVAST Software
description: avast! Virtualization Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: aswsnx.sys (avast! Virtualization Driver, AVAST Software).
Google query: AVAST Software SYSTEM_SERVICE_EXCEPTION
-
Hi lutzio,
please upload support package again and write me package name, otherwise I'm not able to find it here.
or send me (C:\Windows\Minidump\061513-19063-01.dmp) to kurtin@avast.com
Thanks, Petr
-
Hello avast forum and sincere greetings to all.
Just a little problem that i hope someone will help me with.
When i was using avast 8 version 1483 the program ran just fine with no issues on my computer at all.
I then updated to the latest version internally and this ran fine for a few days and then suddenly i was getting blue screens regularly at boot up.
I was running avast alongside comodo firewall 5.12 and by a process of elimination i have narrowed the culprit down to avast.
This has saddened me slightly as i love avast and i have unwillingly had to uninstall avast and use another av.
At some point i want to install avast again.
Could somebody please explain why there were bluescreens and could the issue be caused because i updated internally.?
Is it advisable to do a fresh install with every update as i suspect it was because of me updating internally that may have been the issue.
I really like avast and i love the protection offered and i want to try again with a clean install.
Thank You.
Please Arnold72, have you resolve this problem of incompatibility of avast last versione and comodo 5.12?
I'm in your same situation... same version program, same RANDOM bsod at windows both :(
MAYBE I ca n help you for solve the problem and preserve comodo 5 + avast 2014. Now I testing and maybe i solve the pronlem.
The problem is avast at 110%
Contact me if you can.
Thanks and sorry for my english
Answer of avast support: the problem it's that I need install avast only after windows update patch
(so I imagine that everytime that microsoft publish new windows patches I have to uninstall avast, install patches, reinstall avast -.- )
that assistance is this?
It 's a clear problem of avast 2014, they treated me badly, I will inform the major comparative company
-
Please Arnold72, have you resolve this problem of incompatibility of avast last versione and comodo 5.12?
I'm in your same situation... same version program, same RANDOM bsod at windows both :(
MAYBE I ca n help you for solve the problem and preserve comodo 5 + avast 2014. Now I testing and maybe i solve the pronlem.
The problem is avast at 110%
Contact me if you can.
Thanks and sorry for my english
Answer of avast support: the problem it's that I need install avast only after windows update patch
(so I imagine that everytime that microsoft publish new windows patches I have to uninstall avast, install patches, reinstall avast -.- )
that assistance is this?
It 's a clear problem of avast 2014, they treated me badly, I will inform the major comparative company
This hasn't been resolved, I've been getting random BSOD at login for many months. Whocrashed says sometimes it's Avast, sometimes Comodo.
-
It's avast *14* to cause instability at windows startup.
With avast "13" it was all ok.
I solved the problem at 100%. Disabling a function in comodo.. in this moment, after 70 reboot, I never see the blue screen, before, after 8-12 reboot, I received random blue screen... If you want, contact me in pvt. Hi
-
It's avast *14* to cause instability at windows startup.
With avast "13" it was all ok.
I solved the problem at 99,9%. Disabling a function in comodo.. in this moment, after 70 reboot, I never see the blue screen, before, after 8-12 reboot, I received random blue screen... If you want, contact me in pvt. Hi
This is an open forum for the benefit of all. If you have something to share, then please do it here on the forum.