Blue screen of death issue.

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.

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.

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.

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?

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.

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

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?

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.