I’d like to add that I have the exact same BSOD error and so does another user in my house, but I’m a tech noob and have no idea how to post any relevant info, etc.
Hello Muffin,
If you had a BSOD and your system recorded it then it should be in c:\windows\minidump*.dmp
A file with a date/time stamp in the name, you can post it here by using “Additional Options” in the message post and select, Attach, Browse, Select the file you like to attach and upload it here.
I think you have to rename the .dmp file to something like .dmp.txt to get it accepted by the forum.
If you need further help feel free to PM me.
Hello Nubiatec,
I would like to give a test driver to see if it resolves this issue. Would you be willing to do this with me over MSN? If so, pls PM me your MSN ID.
Thanks,
Egemen
Ive had the same prob as everyone else. Downloaded the supposedly fixed version but still the same prob.
My windows\minidump file is empty. Does ■■■■ cleaner clean that out? I have it set to run at startup
I have AVG, SpywareBlaster, Spyware Guard, Snoopfree and MBAM on demand installed
Here’s what I’ve got.
OS: WinXP 32 Home SP3
Software: AVG, SnoopFree, Unlocker, PeerGuardian2
I can’t upgrade or downgrade CIS without getting the BSOD loop… and I can’t remove it then install a different firewall either, or the same error occurs. The only way I’ve found to get my pc running is to do a rollback to before I downloaded the last update. 
Edit, I notice my minidump file is bigger than other people’s… I just copied it out of the minidump folder and changed the extension from .dmp to .txt, was that right?
[attachment deleted by admin]
I can’t load it in windows debugger, complains about invalid file format even if i rename to .dmp
Can you try again and zip the .dmp file ?
This is the exact file from \Minidump, zipped
[attachment deleted by admin]
Yes this one works:
UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: f771fd70
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: winlogon.exe
LAST_CONTROL_TRANSFER: from b864b131 to 80551012
STACK_TEXT:
b6b6a024 b864b131 00000000 00000500 72747052 nt!ExAllocatePoolWithTag+0xd
b6b6a038 b490a51d b6b6a050 00000500 72747052 NDIS!NdisAllocateMemoryWithTag+0x13
WARNING: Stack unwind information not available. Following frames may be wrong.
b6b6a054 b4908813 b60237a6 00000314 89b8d5f8 cmdguard+0x951d
b6b6a094 b490895f 00010024 00000081 00000000 cmdguard+0x7813
b6b6a0f0 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6a14c b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6a1a8 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6a204 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6a260 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6a2bc b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6a318 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6a374 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6a3d0 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6a42c b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6a488 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6a4e4 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6a540 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6a59c b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6a5f8 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6a654 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6a6b0 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6a70c b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6a768 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6a7c4 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6a820 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6a87c b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6a8d8 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6a934 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6a990 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6a9ec b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6aa48 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6aaa4 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6ab00 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6ab5c b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6abb8 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6ac14 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6ac70 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6accc b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6ad28 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6ad84 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6ade0 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6ae3c b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6ae98 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6aef4 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6af50 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6afac b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6b008 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6b064 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6b0c0 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6b11c b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6b178 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6b1d4 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6b230 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6b28c b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6b2e8 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6b344 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6b3a0 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6b3fc b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6b458 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6b4b4 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6b510 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6b56c b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6b5c8 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6b624 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6b680 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6b6dc b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6b738 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6b794 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6b7f0 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6b84c b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6b8a8 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6b904 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6b960 b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6b9bc b490895f 00010024 00000081 00000000 cmdguard+0x795f
b6b6ba18 b490895f 00010024 00000081 00000000 cmdguard+0x795f
STACK_COMMAND: kb
FOLLOWUP_IP:
cmdguard+951d
b490a51d ?? ???
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: cmdguard+951d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: cmdguard
IMAGE_NAME: cmdguard.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a0d8f24
FAILURE_BUCKET_ID: 0x7f_8_cmdguard+951d
BUCKET_ID: 0x7f_8_cmdguard+951d
Followup: MachineOwner
---------
Thanks !
This will pretty much mirror exactly what I’ve already read a number of other users are complaining about… 
Yesterday/a few days ago I updated to CIS 3.9, but today after downloading latest update which required rebooting, the pc goes into continuous BSOD blue screens and keeps rebooting continuously in a loop. (the pc never boots up completely, it always BSOD just before the Windows log on screen.)
I’ve booted into safe mode 3 times now, the first time uninstalling CIS completely, restarting and pc worked/booted perfectly normally, so I reinstalled CIS 3.9, re-downloaded latest update, rebooted as requried, and SAME EXACT continuous rebooting loop. So I booted into safe mode a second time and uninstalled the AV portion of CIS, got the SAME BSOD rebooting loop, so I booted into safe mode for a 3rd time, uninstalled CIS completely, and everything works perfectly fine again!! I guess I’ll download ZoneAlarm and AVG in the mean time till this is fixed because otherwise I am just running Comodo Memory Firewall, Spybot SD 1.62 with Tea Timer enabled, and SnoopFree as I uninstalled BOClean because CIS 3.9 integrated it…
I’m not sure exactly what to do as I don’t have time to comb through the forums extensively, but hopefully someone can give me an answer/help me out 
Cheers!
yeah try this download (.509) please, it should help the BSOD https://forums.comodo.com/feedbackcommentsannouncementsnews_cis/comodo_internet_security_3995478509_released-t39202.0.html
I get a strong feeling that SnoopFree could have something to do with this, all other users having the problem are also using that, could you test with SnoopFree uninstalled and install CIS 3.9.x after that to see if that helps ?
Ok - I’ll do that before I install the other programs - I LOVE CIS, but perhaps SnoopFree is the hang-up… I’m just getting tired of BSOD and safemode boots!!! :-\
Perhaps Comodo can integrate something like SnoopFree just like they did with BOClean… now THAT would be REALLY great!!! 
Just followed this link, and it’s the same one I downloaded from a few days ago - It worked great until I allowed the latest automatic update today and allowed the required reboot… Then it just doesn’t stop rebooting!!! So this isn’t the problem - it’s something in today’s virus database update! At least that’s what it seems for me :S I’m going to uninstall SnoopFree here in a little bit and reinstall one more time, and if I get the BSOD rebooting loop, I’ll be back here letting you know
Hi Guys,
This is related to SnoopFree. It is attacking and undoing cmdguard.sys hooks. Please uninstall it before using CIS.
:-TU
Thanks egemen for confirming ;D
Should they contact the developer to fix this ? or is it going to be on the incompatible software list ?
Sure. We will be including it in our black list as it attacks our program and does not differentiate between security software and a rootkit.
Hi all!
I had this problem too, and had originally wanted to post that Snoopfree was the problem, but I see that others got to it before me. 
Hmm… can Comodo developers explain this new component in CIS? Also, would this conflict between Snoopfree and CIS be applicable to any other software? Or is it just CIS?
There’s a CIS blacklist?
Best Regards
It can conflict with any security software if the race condition occurs. It is unhooking shadow table and overwriting CIS hooks. No security software can perform unhooking once shadow table is hooked. It is not safe as seen in this example.
There is nothing new in CIS. With this CIS, race condition happens thats it.
Thanks for clarifying! Even though it was a little too technical for me… 
Hmm… what other software are incompatible with Comodo?