BSOD happened during My Computer scan.
I had a same problem with 4 previous non-beta versions.
Doesn’t happen always. Sometimes scanning goes without a problem.
Error shown on blue screen:
*** stop: 0x00000024 (0x001902FE, 0xB564F21C, 0xB564EF18, 0xB5A0649E)
*** US30XP.SYS - Adress B5A0649E base at B5FA00000, Date Stamp 48bfefbc
Windows Vista Ultimate 32 bit
* Your realtime Antivirus/version,Spyware remover/Version, other Security Software/Version
Comodo Internet Security 3.8.65951.477
* Affected Driver/Software and Version (if the bug doesn’t affect window itself)
A game called Exteel -I know this doesn’t seem very important, but MANY people are getting it and are removing Comodo from their computers… Please help :-X-
* Brief description of the problem (Attach Diagnostic report or crash dumps)
Once the game is installed and you launch it, the splash screen pop up, and a few seconds later, BSOD.
* Steps to reproduce the bug (if applicable)
Install the game, and launch the game with Comodo in the background.
* Gmer report (download) Only for 32bit platforms
Other notes:
Some people I know actually don’t have this problem, but most do.
I’ve snooped around Comodo’s files and services and when I remove cmdguard.sys from my system32 directory, the game works fine, but some of Comodo’s components are not functional, so I’d assume the problem is there.
My system:
Asus P5QL Pro motherboard
Intel Core 2 Duo E8400
4GB of ram
EVGA 9800GTX+
I put four different minidumps because I have no clue which one is needed, and they’re the only ones that were there, and the log file saved from GMER after a scan into the zip.
Malware protection: Spybot S&D (real time scan disabed)
Malware protection: Malwarebytes Anti-Malware (no real time)
Affected: VmWare server 2.0.1-156745 (latest)
System: HP nx7300, w Broadcom 440x 10/100, Broadcom 802.11b/g WLAN
Description of this problem:
when trying to run some network applications on virtual mascnines getting BSOD with problems about inspect.sys
(minidump attached)
I love Comodo Firewall and I want it to work on my notebook again!!! When I started using Comodo Firewall v3 I would get the BSOD every now and then when turning on my computer after a shutdown. I don’t remember when it started happening but I remember distinctly that it got worse when Comodo updated itself from the 3.0.* version to whatever version came after that (3.5.* maybe?). With the latest versions I get the BSOD every single time I turn on or restart my laptop. Sometimes after 5 or more reboots it will go into Windows successfully without a BSOD. Other times I have been unable to go into Windows w/o first going into Safe Mode and uninstalling Comodo. Currently I am not running Comodo.
I suspect that there may be a conflict between Comodo and Cisco’s VPN software. This suspicion comes from the fact that the last time I installed the latest version of the VPN app I would get a BSOD everytime I would connect to the VPN using that app. After I uninstalled Comodo I stopped having that problem.
My last minidump is attached.
Here is my info:
Win XP Media Center with SP2 and all latest updates
Symantic AV v 10.1.6.6010
Spyware Sweeper 5.3.2.2361
Cisco VPN 5.0.05.0290
Your realtime Antivirus/version,Spyware remover/Version, other Security Software/Version
Affected Driver/Software and Version (if the bug doesn’t affect window itself)
Brief description of the problem (Attach Diagnostic report or crash dumps)
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: 80042000
Arg3: 00000000
Arg4: 00000000
This never happens. How did you get this BSOD? Have you tries to UNDO some HOOKS CIS applied with any of your tools? This is the only explanation for this. Something overwrote cmdguard hooks screwing up everything.
Can you try uninstalling other security software and see?
“BSODs” occurs though “Setpoint” is uninstalled and 3.9 was installed again.
Another problem, OS freezes or crashes when start-up according to the same timing.
Same problem with CIS 3.9.x.509; after installation, a loop of BSOD’s crashes:
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000007f (0x00000008, 0x80042000, 0x00000000, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini051509-02.dmp.
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: 80042000
Arg3: 00000000
Arg4: 00000000
As I said, your BSODs never happen. Something is screwing up with CIS hooks. One of the programs you have installed is clearly doing something cathastrophic. Can you please uninstall one by one and tell us which one is responsible for this?
Thank you egemen for taking a look at this.
I guess I’ll keep using 3.8.x.471 for the time being as I can not afford to remove my other security software, may be with the exception of ThreatFire.
the programs that should not interfere with comodo are avira, gmer, peeerguardian and spybot (as long as you leave the tea timer off). Avast might even if it is on-demand, threatfire might, and I have not used snoopfree or unlocker.
So far I uninstalled ThreatFire, but no change; still BSOD crash loop.
I’ll try to uninstall some of the other tools in the next few days, and will post updates on this thread.
CIS 3.8.xx works fine.
Oh, I guess I haven’t described the problem clearly:
The problem is after upgrading to CIS 3.9 and rebooting, the pc goes into continuous BSOD blue screens and keeps rebooting continuously in a loop. That is to say, the pc never boots up completely, it always BSOD just before the Windows log on screen.
Then I have to boot into safe mode and uninstall CIS 3.9, reboot. After that I can reinstall CIS 3.8 which works fine.
I tried to remove one software that could potentially be conflicting with CIS 3.9, and that is ThreatFire. So after uninstalling CIS 3.8 and ThreatFire, rebooting, and then installing CIS 3.9, rebooting, the pc goes into BSOD blue screen and keeps rebooting in a loop.
So for now I know that ThreatFire is not conflicting with CIS 3.9
Edit: there are 3 other users who have reported the exact same BSOD crash loop:
