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!!)…
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.
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:
Why the dichotomy, i.e, you want the .dmp file, but you can’t attach these types in this forum? and
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.)
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 (:KWL)
Windows Version/Bit and Service Packs - WinXP Pro SP2 64 Bit
Your realtime Antivirus/version,Spyware remover/Version, other Security Software/Version - CIS_Setup_3.5.55810.432_XP_Vista_x64.exe
Affected Driver/Software and Version (if the bug doesn’t affect window itself) - N/A
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.
Steps to reproduce the bug (if applicable) - Install Comodo CIS, reboot…
I think I’m going to use the CAV portion of CIS on my friend’s machine and will probably use an alternate firewall, maybe ZoneAlarm, till (if ever) the BSODs get fixed. It’s a shame, I was very exited when CIS came out. The more I’ve been reading about this problem (it’s been around since CFP 3.0), the more I’m starting to lean elswhere…
The environment of PC where the error occurred is as follows.
1.Windows XP Professional 32bit SP3
2.AVG 8.0.175,(BitDefender 8.0.202),(SpywareBlaster 4.1),(Spybot 1.6.0.30)
3.
4.SystemError 1000007e (c0000005,804f24fe,bacfba68,bacfb764)
This time, the dumping file of the error which occurred while operating iTunes is attached.
5.Operation under starting or PC operation or by iTunes(8.0.2)
Windows Version/Bit and Service Packs: WinXP Pro SP3 32bit v.5.1.2600
Your realtime Antivirus/version, Spyware remover/Version, other Security Software/Version: CIS 3.5.55810.432
Affected Driver/Software and Version (if the bug doesn’t affect window itself): N/A
Brief description of the problem (Attach Diagnostic report or crash dumps if needed): Intermittent BSOD when accessing CD/DVD drive (either directly or through a program)
Steps to reproduce the bug (if applicable): Access the drive.
Comodo CIS 3.5.55810.432 (firewall) / Eset Nod32 3.0.657
BSOD on reason conflict CIS and NetLimiter 2.0.10.1 (traffic shaper for win)
BugCheck 10000050, {814e7ff4, 0, 804ee011, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** WARNING: Unable to verify timestamp for cmdhlp.sys
*** ERROR: Module load completed but symbols could not be loaded for cmdhlp.sys
*** WARNING: Unable to verify timestamp for nltdi.sys
*** ERROR: Module load completed but symbols could not be loaded for nltdi.sys
*** WARNING: Unable to verify timestamp for afd.sys
*** ERROR: Module load completed but symbols could not be loaded for afd.sys
Probably caused by : cmdhlp.sys ( cmdhlp+2ebb )
Yesterday I updated CIS 64 to CIS 64 with Antivirus. (3.5.55810)
I’ve then had multiple BSODs under totally different conditions, mostly after running the system for about 20 minutes.
My system specs: XPS M1330 Notebook
Windows XP x64 SP2
4GB RAM
CIS 3.5.55810
No BSODs after deinstalling CIS… I’m going to install the old CIS again, I never had BSODs with it
Hi guys.
We are reading and trying to investigate all your BSoD’s but it would be much easier and faster if you add some more explanations to your minidump: other software (at least one that has own drivers like security, disc writing or special devices drivers) and steps that led to the BSoD (at least what did you do before it)