after a while I decided to give avast a go aqgain , wanted to team it up with comodo free firewall , so I followed VALENTIN N’S instructions on youtube (just to be absolutely shure the two wouldent conflict…last night everything runned smoothly , but when I restarded today , I got 2 BSODS IN A ROW!!!
REALLY NICE JOB AVAST…
so you won’t be seeing me here again , fix up this prehistoric bug guys!!!
Why do you think it is on avast side?
By the way, if you won’t upload the memory dump file, well, you won’t help or receive help.
There are a lot of users with both avast and Comodo, starting by Valentin
@OP, no offense, but if you can’t read Dumps, then you have no idea if Avast! is at fault.
And no, just because everything was fine before you installed Avast! then it went in the toilet, does not place Avast! at fault (if only computers were that simple…)
Try to analyse the minidump files from the computer and find who is the culprit. You can use Whocrashed software to analyse the minidump files in the computer. You can download it from
I have been running Comodo and Avast since last year without a hitch. Running very good actually. Maybe you have some left-over of your former AV or some other security apps that are conflicting with the install. On my side I have no memory of having problems with installing/using Comodo with AvastFree and AIS(no firewall).
Custom installation on the new ver5.8 installer should be done. Don’t install the AV/Geek Buddy(Avast’s is better). For safety or to rule-out possible conflicts try to exclude Avast folders in Comodo and then narrow them to just the major processes and vice versa with Avast. Some have no issues even when exclusions are not placed but on my experience I place exclusions first then narrow it down.
And Comodo with D+ is actually a great app next to Online Armor Premium/Free. If Avast allows connection termination then the firewall is gonna go places. When using Avast’s firewall I team it up with Process Hacker version2.
I used Comodo + Avast on a new clean WIN 7 SP1 installation.
As time went by, it became obvious that Comodo has issues on a WIN 7 platform. I also got nailed by malware a couple times with one case being so severe I had to do an image restore.
Personally, the only firewall I have found to be compatiable with WIN 7 is the WIN 7 native firewall. This is especially true of inbound protection. WIN 7 uses IPv6 internally extensively and turns on tunneling, primarily Teredo 6to4 tunneling by default. It has even created a specially protocol to handle HTTP in a tunnel.
Comodo’s solution to the IPv6, and tunnel enhancemenst is to recommend you turn them off.
Comodo is a great firewall for XP. For WIN 7, look elsewhere.
I rather doubt we will get any, since presumably he has removed avast there isn’t a whole lot that we can do to investigate, if he isn’t prepared to submit the dump files from the BSOD for analysis.
I’ve had 6 BSOD’s all on startup since I updated Comodo on 23rd October. Once I deselected Comodo’s ‘Enhanced protection mode’ I haven’t had any problems.
Yes, but the helpful posts will still be here for someone else who wants the help. For instance, the post by Dumper (thanks for that useful insight :)). While it probably wont get a response, gives a good direction to start looking for the root cause of the issue, for anyone else that stumbles onto it.
Someone who has a similar issue may find this thread, and find the info/help useful.
The chance of the OP not returning is always there in a forum. One thing is for certain, there will always be someone who can benefit from the help.
Another free firewall know to work well with WIN 7 is PrivateFirewall. Unfortunately, I could not get it to run with Avast 6 on my WIN 7 installation. I might try it again however since it has some really great features.