BSODs: Please add your minidump files here

[Guest]

[churlock]

* Windows Version/Bit and Service Packs
XP Pro 32 bit, sp 2

    * Your realtime Antivirus/version,Spyware remover/Version, other Security Software/Version
Trendmicro Internet Security 2006, prog ver 14.00.1341, engine ver 8.910.1002

    * Affected Driver/Software and Version (if the bug doesn't affect window itself)
cmdguard.sys, ver 3.5.53861.423
 
    * Brief description of the problem
Two, seemingly random BSOD's since installation
See attached "CHURLOCK_Mini110608-01.txt"

    * Steps to reproduce the bug (if applicable)
random

    * Gmer report (download) Only for 32bit platforms
See attached "CHURLOCK_gmer.txt"

Since reverting back to 3.0 from 3.5, I've had no BSOD's. It's been several days now, and I'd ordinarily see one. So knock on wood. If I should get one while running 3.0, I will report back here. I'm fairly confident 3.5 was the problem.
Which raises a question: will 3.5 be "fixed", and how would I know?? I doubt they will come out and say "...problem identified and fixed bsod's for Win xp, sp2..."

[josh797]

Knock on wood, but since upgrading to .427 I haven't seen any bsod's almost at all.
Just want to say thanks for the effort and leave some feedback since I've submitted quite a few minidumps to the previous thread as well.

Josh

[churlock]

Knock on wood, but since upgrading to .427 I haven't seen any bsod's almost at all.
Just want to say thanks for the effort and leave some feedback since I've submitted quite a few minidumps to the previous thread as well.

Josh

Just to be clear, when you say "...almost...", does that mean you are still getting them, but at a lesser frequency??

I have as yet to this day (11/18) gotten any since reverting back to 3.0, which has now been a couple of weeks, so I hate to update if the bug is still there. It's a pain to do the uninstall, etc., etc. plus any bsod can be bad for windows, rather like walking on thin ice......

[josh797]

Just to be clear, when you say "...almost...", does that mean you are still getting them, but at a lesser frequency??

I have as yet to this day (11/18) gotten any since reverting back to 3.0, which has now been a couple of weeks, so I hate to update if the bug is still there. It's a pain to do the uninstall, etc., etc. plus any bsod can be bad for windows, rather like walking on thin ice......

I know exactly what you mean, upgrading and reinstalling is a real letdown... though
latest 3.5 allowed me to keep the previous preferences and upgrading was a charm
thanks to another poster in this forum.

Just to clarify, it crashed once but it was entirely my fault. Opened waaay to many connections
for it to handle and probably that's why. Under normal circumstances, only 1/3rd of that
amount of open connections (that crashed it) are used. The problem with previous version,
was that even 1/3rd of that number, caused it to give a blue screen almost on a daily basis.

Good luck if you upgrade, I think it's worth it, imo.
btw, there's an even newer version out I have yet to try...

Josh

[kennyb24]

I tried V.432 and got 3 BSODs over 2 days. I went back to V. 3.0 and have had no problems since. For me is isn't fixed yet.

[L.A.R. Grizzly]

I tried V.432 and got 3 BSODs over 2 days. I went back to V. 3.0 and have had no problems since. For me is isn't fixed yet.

Thanks for the heads-up! I was waiting to see if the BSODs were fixed in this newest version. Now I don't have to go through trying it out. I guess I'll have to wait for an upcoming release!

[churlock]

I tried V.432 and got 3 BSODs over 2 days. I went back to V. 3.0 and have had no problems since. For me is isn't fixed yet.

Just aside, this bug seems to be related to just Win XP. I have a new Dell laptop (M1530) running Vista, with cfp 3.5. No problems with it.

So (cfp 3.5 + XP = bsod), but (cfp 3.0 + XP = no problems), and (cfp 3.5 + Vista = no problems).

Maybe, because XP is an "old" and "retired" op sys, it isn't getting the attention it deserves. But I'm not complaining--after all, it's free, and 3.0 is still a good product (thank you Comodo!!).........

[Kurt_Aust]

1. Allow *.dmp files as uploads and/or
2. Fix the forums so that when an invalid file type is detected and one is returned to their reply form, all their entered text is not lost.

* Windows Version/Bit and Service Packs
XP Pro x64, sp 2

    * Your realtime Antivirus/version,Spyware remover/Version, other Security Software/Version
Avast 4.8.1290, Spybot 1.6, Win Defender

     * Brief description of the problem
BSOD when logging into account

    * Steps to reproduce the bug (if applicable)
Upgrade from 3.0.25.378_XP

[freshhh]

Windows XP x64 SP2 Fully Updated
CII 3.5.55810.432

[L.A.R. Grizzly]

Windows XP x64 SP2 Fully Updated
CII 3.5.55810.432

Just when I thought it was an XP problem! A friend of mine is the newest member of the BSOD club. I installed CIS on his machine during the Beta stages and he told me today that he has been having numerous BSODs daily. He is running WinXP Pro on that machine. I installed CIS on his 64bit Vista machine and, so far, it has been running smoothly. This week, I'm going to remove CIS from his XP machine and reinstall Norton Internet Security. I'll post any minidumps he has, here, in hopes that this will help the developers find the problem.

[churlock]

Mr. Comodo guy:

I think some clarification is needed here. Per the instructions re dump files, it says to attach them here along with other, pertinent data. However (and it was reported earlier here), .dmp are not allowed and are reported  as "forbidden" file types when one tries to attach this kind of file type (.txt, and others are ok).

So this is a two part question:

1) Why the dichotomy, i.e, you want the .dmp file, but you can't attach these types in this forum? and

2) It's a bit of work to put the relevant stuff together, but while wanting to help you find the bug any way we can help, is there someone really looking at these?? It's hard to know, because of the lack of any acknowledgment that you are indeed using them. (leaving this post unanswered will, in an indirect way, answer my questions too.)

[freshhh]

i think the way dump are sended make us to skip the process...  outlook (or other email manager is opened) it would be better if it was semi-transparent without the need to send them as an email...  just my two cents 

[L.A.R. Grizzly]

1) Why the dichotomy, i.e, you want the .dmp file, but you can't attach these types in this forum?

Simply attach them zipped (.zip, .rar, .tar, etc.).

[L.A.R. Grizzly]

I'm wondering if the BSOD problems could be attributed to AMD processors. Both of the machines I'm experiencing BSODs on have AMD CPUs.

[DeeGeeFi]

1.  Windows Version/Bit and Service Packs - WinXP Pro SP2 64 Bit
2.  Your realtime Antivirus/version,Spyware remover/Version, other Security Software/Version - CIS_Setup_3.5.55810.432_XP_Vista_x64.exe
4.  Affected Driver/Software and Version (if the bug doesn't affect window itself) - N/A
5. Brief description of the problem (Attach Diagnostic report or crash dumps if needed) - Consistent BSOD/Instacrash (driver irql not less or equal)  on windows startup. Windows loads up to "Starting up Windows" message, just before login screen comes. Had to do uninstall in safe mode.
6. Steps to reproduce the bug (if applicable) - Install Comodo CIS, reboot...

crashdump

[Tags:]