Unfortunately, I’ve had to return to Norton Internet Security to get away from the BSODs. When my subscription runs out in a year, I’ll give CIS another try. BOClean works seamlessly with Norton. I’m still a happy camper!
I have returned to windows firewall and my router firewall and avast antivirus till this bug is rendered. as it made my computer unusable i could not even play music cd or dvd. I will revisit comodo products when bugs worked out. i wish you all luck.
1 Windows Version/Bit and Service Packs = XP Pro SP3 - 32bit
2 Your realtime Antivirus/version,Spyware remover/Version, other Security Software/Version = Norton Corporate Anti-Virus 10.1.5.5000
3 Affected Driver/Software and Version (if the bug doesn’t affect window itself)= cmdguard.sys
4 Brief description of the problem (Attach Diagnostic report or crash dumps if needed) - stop 0x7e and 0xf4 (csrss.exe)
5 Steps to reproduce the bug (if applicable) - reboot and wait 5 or 10 minutes, no login needed
Application hungs and turned off. Below is report from windows logging:
cfp.exe - Application Popup - application error: There was unknown software exception (0x40000015) under address 0x0044b831.
[ Name] Application Popup
[ Qualifiers] 16384
[ SystemTime] 2008-11-04T09:06:45.000Z
It was first time application hungs. I attached gmer logs created after crash.
Seems that waves of BSoDs are caused of some periodical application activity. Do you have any application that might have scheduled tasks or performs updates with same period? Could you tell the period timing more precisely.
Does the game have any game protecting mechanisms or anti-cheats.
If you are sure the game itself is safe - try to set Defense+ in training mode, launch the game, exit and switch back to the mode you use. CIS should learn the game behavior and not crash.
* Windows Version/Bit and Service Packs
XP - Home SP2 32 Bit.
* Your realtime Antivirus/version,Spyware remover/Version, other Security Software/Version
CIS - 3.5 Proactive security D+ CleanPC mode Firewall Custom Mode, BoClean 4.27,
* Affected Driver/Software and Version (if the bug doesn't affect window itself)
* Brief description of the problem (Attach Diagnostic report or crash dumps if needed)
Clicked on "lookup' for my pending files. Immediate BSOD
* Steps to reproduce the bug (if applicable)
Have not attempted to reproduce it yet. I will as soon as this is reported.
STOP: 0X000000D1 (0XB8217C30, 0X00000002, 0X00000000, 0XF7A127F8)
cmdhlp.sys - address F7A127F8 base at F7A12000 ,datestamp 48ff8da8
No minidump produced - possible reason:
The paging file is not on the %systemroot% partition. When the STOP error occurs, the system crash dump is written out to the pagefile on the root of the %systemroot% drive.
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…”
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.
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…