BSODs: Please add your minidump files here [CLOSED]

[Guest]

[valmont_al]

And another BSOD (conflict Comodo & Netlimiter2)
WinXP SP3, Comodo 3.0.22.349, NetLimiter 2.0.10.1, Nod32 3.0.621.0

Unable to load image tcpip.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys

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+1d4b )

[valmont_al]

In addition to previous post.

[sano88]

BAD_POOL_CALLER

STOP: 0x000000C2 (0x0000007,0x00000CD4,0x14020401,0xE3191298)

On windows XP Prof. SP2 with Nod32 3.0 on  HP nc6220
(After Comodo installation my Bluetooth device did not work either)

This happens during the last stage of shutdown/reboot just when the machine suppose to restart....

I get a similar error on my X61 tablet running Vista Business 32-bit.
I get:
BAD_POOL_CALLER
0x000000c2 (0x00000007, 0x0000110b, 0x0854000f, 0x8f8283a0)

This error only happens when I'm trying to resume from sleep after extended periods of inactivity.
The minidump is attached.  I'm pretty sure it's Comodo related because when I uninstall Comodo the problem goes away..

UPDATE:
I installed an reinstalled and the problems went away for a little while.  A couple of days ago the BSODs came back with a vengeance.  I had been putting off doing the windows debugging, and I still never got the symbols quite right, but the current evidence points towards "inspect.sys".  I'm going to try to make sure that there are no strange windows firewall interactions and then if the crashes remain, I think Comodo will have to go until the next version which addresses these issues...


BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 00000007, Attempt to free pool which was already freed
Arg2: 0000113d, (reserved)
Arg3: 08540006, Memory contents of the pool block
Arg4: aaef6810, Address of the block of pool being deallocated

... [some symbol errors I can't seem to fix]

MODULE_NAME: inspect

FAULTING_MODULE: 82000000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4802dc3c

POOL_ADDRESS:  aaef6810

BUGCHECK_STR:  0xc2_7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WRONG_SYMBOLS

LAST_CONTROL_TRANSFER:  from 820e7ce8 to 820d8765

STACK_TEXT: 
WARNING: Stack unwind information not available. Following frames may be wrong.
af0cb984 820e7ce8 000000c2 00000007 0000113d nt+0xd8765
af0cb9f8 81f175b8 aaef6810 00000000 af0cbb58 nt+0xe7ce8
af0cba08 8eb1058d aaef6810 00000000 00000000 ndis+0x1b5b8
af0cbb58 81fd261f af0cbbf4 af0cbb80 86694f8c inspect+0x258d
af0cbbec 81fd11ab c0000001 84f15b98 00000000 ndis+0xd661f
af0cbc78 81fe2eb0 866d4488 00000000 00000000 ndis+0xd51ab
af0cbd34 81fcb013 85ead268 866d4488 af0cbd7c ndis+0xe6eb0
af0cbd44 82078fa4 85ead268 00000000 a63ec6f0 ndis+0xcf013
af0cbd7c 822256f4 85ead268 af0c0680 00000000 nt+0x78fa4
af0cbdc0 820915de 82078ea7 80000001 00000000 nt+0x2256f4
00000000 00000000 00000000 00000000 00000000 nt+0x915de


STACK_COMMAND:  kb

FOLLOWUP_IP:
inspect+258d
8eb1058d ??             

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  inspect+258d

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  inspect.sys

BUCKET_ID:  WRONG_SYMBOLS

Followup: MachineOwner
---------

eax=8a01113c ebx=0000113d ecx=000021c9 edx=8212943c esi=8a011120 edi=aaef6808
eip=820d8765 esp=af0cb968 ebp=af0cb984 iopl=0         nv up ei ng nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00000286
nt+0xd8765:
820d8765 8be5            mov     esp,ebp
ChildEBP RetAddr  Args to Child             
WARNING: Stack unwind information not available. Following frames may be wrong.
af0cb984 820e7ce8 000000c2 00000007 0000113d nt+0xd8765
af0cb9f8 81f175b8 aaef6810 00000000 af0cbb58 nt+0xe7ce8
af0cba08 8eb1058d aaef6810 00000000 00000000 ndis+0x1b5b8
af0cbb58 81fd261f af0cbbf4 af0cbb80 86694f8c inspect+0x258d
af0cbbec 81fd11ab c0000001 84f15b98 00000000 ndis+0xd661f
af0cbc78 81fe2eb0 866d4488 00000000 00000000 ndis+0xd51ab
af0cbd34 81fcb013 85ead268 866d4488 af0cbd7c ndis+0xe6eb0
af0cbd44 82078fa4 85ead268 00000000 a63ec6f0 ndis+0xcf013
af0cbd7c 822256f4 85ead268 af0c0680 00000000 nt+0x78fa4
af0cbdc0 820915de 82078ea7 80000001 00000000 nt+0x2256f4
00000000 00000000 00000000 00000000 00000000 nt+0x915de

[SHADOW-XIII]

I had just BSOD with CACHE_MANAGER in cmdguard.sys
Interesting: Pressing "Diagnostics" in Miscellaneous of CPF freezes computer completly in around 15 seconds

1. Vista Home Premium Version 6.0 (Build 6001: Service Pack 1)
2. No Antivirus, Only Microsoft Defender:
Windows Defender Version:  1.1.1600.0
Engine Version: 1.1.3520.0
Definition Version:  1.33.9651.0
3. CPF: 3.0.22.349
4. Mini memory dump attached
5. No steps, was random (1st time seen this error)
6. Gmer raport attached

[bron]

Hi, I have a problem with net send and Comodo.

http://forums.comodo.com/empty-t22967.0.html

This is my minidump:

IRP_STACK_LOCATIONS (35)
A higher level driver has attempted to call a lower level driver through
the IoCallDriver() interface, but there are no more stack locations in the
packet, hence, the lower level driver would not be able to access its
parameters, as there are no parameters for it.  This is a disasterous
situation, since the higher level driver "thinks" it has filled in the
parameters for the lower level driver (something it MUST do before it calls
it), but since there is no stack location for the latter driver, the former
has written off of the end of the packet.  This means that some other memory
has probably been trashed at this point.
Arguments:
Arg1: 88925660, Address of the IRP
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
MODULE_NAME: nt

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  48025eab

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WRONG_SYMBOLS

BUGCHECK_STR:  0x35

LAST_CONTROL_TRANSFER:  from 8051bdea to 8053380e

STACK_TEXT: 
WARNING: Stack unwind information not available. Following frames may be wrong.
b5a59a60 8051bdea 00000035 88925660 00000000 nt+0x5c80e
00000000 00000000 00000000 00000000 00000000 nt+0x44dea


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt+5c80e
8053380e 5d              pop     ebp

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt+5c80e

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  ntoskrnl.exe

BUCKET_ID:  WRONG_SYMBOLS

Followup: MachineOwner

[dzjepp]

Hello,

I am running a legit version of Vista Ultimate SP1 x64 OEM and tried to install Comodo Firewall with a nasty BSOD that appeared during the "kernel driver install" portion of the installer. I was able to disable the comodo service in safe mode and boot the system normally but I wonder if there is any way to fix this or if I will have to use a different firewall.

I have all updates from Windows Update, Windows Security Center components disabled (firewall, defender) as I prefer to use 3rd party apps for that job.

Details of the BSOD log:

INSPECT.SYS

DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS

STOP: 0x000000CE (0xFFFFFA60118E5A2C, 0x0000000000000008, 0xFFFFFA60118E5A2C, 0x0000000000000000)

INSPECT.SYS

Specs:

Intel Q6600
nVIDIA nForce 680i
Muskin 991580
GeForce 8800 GTS

[sano88]

Bump! (New info added to my last post)

[layman]

Oops, the BSOD returned on my update to .364!!! The catch however is, the computer logs on perfectly without any BSOD, but once broadband is connected, it just restart. I feel it has something to do with new added feature of Memory buffer.

XP Professional (SP 2) 32 bit
Comodo Antivirus
Spyware Terminator

Mini dump added.

[tok]

I have avg 8.0 with built in firewall, spysweeper, and when after installing comodo I get the bsod after a few minutes of working on the computer.  As soon as I remove comodo, all is normal.
I can't stand avg's firewall and this is the first problem I've had with comodo.  The only way I know to disable avg's security sweet's firewall is to disable it in the services panel.  This seems to have no affect though. windows firewall is disabled but I cannot get the system to run stable with comodo installed.  I don't see a way to completely remove the avg firewall.  What do I need to do to get comodo to run stable?  This is on a XP box.

[SS26]

1. Windows XP Home SP3 x32 (all latest updates).
2. CF 3.0.24 + CMF 2.0.4.20.
3. Windbg tells "probably caused by cmdguard.sys".
4. Dump attached.
5. Random BSoD, no steps to reproduce.

[sano88]

I don't believe anyone is actually reading this forum or looking at minidumps anymore.  There are uploaded dumps from December that have never been downloaded.  It is unfortunate, but I think I will have to say goodbye to Comodo-- life's too short to spend hours debugging your firewall.  Adieu!

[sano88]

BTW I should mention that I think Comodo is an amazing program.. I'm going to continue using it wherever I can, but on my particular setup (X61 Tablet combined with Cisco VPN) the crashes are just a little out of control.

[dail]

1: Windows Version/Bit and Service Packs
xp home SP3 32-bit

2Your realtime Antivirus/version,Spyware remover/Version, other Security Software/Version
any version later then COMODO Firewall pro 3.0.21.329

3. Affected Driver/Software and Version (if the bug doesn't affect window itself)
nProtect GameGuard  2007.2.21.1

4.Brief description of the problem (Attach Diagnostic report or crash dumps if needed)
instant reboot occurs as soon as i launch some game ( the game will firstly launch the gameguard.)
The reboot does not occur with comodo firewall 3.0.21.329.  but when i update to later versions, the reboot occurs. so i have to remain to current version.
BTW, if i uninstall comodo firewall, there is no reboot anymore when i launch the same game.

5. Steps to reproduce the bug (if applicable)
as above

6. Gmer report (download) Only for 32bit platforms

[valmont_al]

Again BSOD on reason conflict Comodo & Netlimiter2
WinXP SP3, Comodo 3.0.24, NetLimiter 2.0.10.1, Nod32 3.0.657.0

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+1e87 )

[Bowman]

Alienware M9700 laptop.

Comodo Firewall installation on VISTA Ultimate SP1 drive does not work properly, it gets part way through installing the Firewall Kernel and then a BSOD IRQL_NOT_EQUAL-OR_LESS occurs. During the Kernel install I get 2 x RED boxes but these flash up and disappear before they can be read.

Tried install with and without AVG Free 8.0 installed, fails both times.

Ad-Ware 2007 and Spybot S&D loaded.


Laptop also has dual boot with XP loaded on 2nd drive, Comodo Firewall runs fine on the XP drive.

Mini dump attached.

[Tags:]