BSODs: Please add your minidump files here [CLOSED]

[Guest]

[GuyD]

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!

You are 100% perfectly right. Over the last month I tried several times to install the COMODO firewall; I always got a BSOD. The last time I tried it again and the only thing I noticed was that the BSOD came later in the install process. On the contrary to what you say that COMODO is a great program.. I have some serious doubts. The list of ppl in this thread that have BSOD's is enormous. And like you say practically no replies to the many BSOD's. There are of course the happy few that have no problem with it. But there are much to much conflicts with COMODO.

BTW did you see what's needed to adjust COMODO to work with torrent files/client ? By accident I found the list of rules. Ridiculous is all I can say.

So unless someone can change my mind, I ask is it worth the trouble to post my *.dmp file for the continuous BSOD's one gets trying to install COMODO ? 

[valmont_al]

GuyD, You wrong. This top is read.

BSOD on reason conflict Comodo & Netlimiter2 (It unique remaining bsod. Other no longer disturb.)
1)WinXP SP3 (32bit),
2)No steps to reproduce
3)Comodo 3.0.25.378 (Firewall - custom policy mode),
NetLimiter 2.0.10.1, Eset 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
*** WARNING: Unable to verify timestamp for msgpc.sys
*** ERROR: Module load completed but symbols could not be loaded for msgpc.sys
Probably caused by : cmdhlp.sys ( cmdhlp+1e87 )

[Agent24]

Well it better be getting read, because I'm getting a really annoying problem... I am trying to use vLite to edit a vista image, but it only gets as far as letting me choose which version of vista I want to customise - and then upon clicking OK, I get a BSOD.

I've attached 2 minidumps, but according to microsoft they may be corrupt.

Running XP Sp3 Home, not sure if it's CFP (although google seems to think so) because I also have CMF and BOClean too

[wlp]

Hi,

WinXP Home SP2 (fully up to date), AVG v8, Zonealarm, Spybot SD

I experienced an issue as follows.  Did anyone experience similar?

I have a wireless lasermouse TRUST MI-7700R.  That mouse needs a driver called KMWDFILTER.SYS.  This driver has been running on my PC for many months, along with Zonealarm.

I uninstalled Zonealarm and installed COMODO FIREWALL Pro 3.0.25.378 after deactivating my AVG8 and Spybot-SD Resident.  The install did not give any error messages.

At the end of the process, it requests to boot the PC again, which I did.

After my XP Home started and I logged to my account, I got a BSOD specifying KMWDFILTER.SYS

I rebooted and started Windows in safe mode, deleted the three files called KMWDFILTER.SYS (2 in Program files, 1 in driver DB) and rebooted (this remedy is mentioned on another forum).

Now everything looks OK, but I cannot use my wireless mouse.

I reinstalled the mouse driver.  Still the mouse does not function, but I don't get the BSOD after booting either!

Update:

Sorry, I was too quick in stating that I did not get the BSOD's anymore after the reinstall of the driver.  I DID after a reboot!
The msg in the BSOD was:
STOP 0X0000008E (0XC0000005, 0XBAB81D10, 0XA93C1BC0, 0X00000000)
KMWDFILTER.SYS Address BAB81D10 base at BAB80000 DATESTAMP 460b63fe

After I rebooted in SAFE mode my wireless mouse functioned again.

Then in SAFE mode I removed KMWDFILTER.SYS from C:\WINDOWS\system32\drivers and KMWDSRV.EXE-078331FC.pf from C:\WINDOWS\Prefetch.
After reboot, no BSOD anymore, but of course my mouse does not function anymore.

End of update

Anyone experienced similar?

[Agent24]

No, but have you tried updating your mouse drivers?

http://drivers.trust.com/MOUSE/R%20series_02.exe (direct driver link)

or product page if the above doesn't work: http://www.trust.com/products/product_detail.aspx?item=15206

[wlp]

Yes I did.  Because the mouse was delivered without a CD, I installed the mouse driver from the TRUST website.  When I had the BSOD after the COMODO install procedure rebooted the system, I reinstalled the mouse driver using a fresh download from the link that you mention.

The driver that I installed lately is the third download (for WXP 32bit) on http://www.trust.com/products/product_detail.aspx?item=15206

[Agent24]

Yeah It probably is an issue with Comodo Firewall...

[WTH]

I'm also having this problem with KMWDFILTER.SYS and Comodo (it seems to be an incompatibility with Comodo because I get the BSOD at startup after right Comodo icon shows up in the system tray)

However, I managed to get the Trust mouse to work without the driver (so it uses a system default driver). Follow these steps (in safe mode):

- Uninstall the Trust driver from the control panel
- Run from a command prompt "sc delete kmwdfilter"
- Reboot
- Delete "C:\windows\system32\kmwdfilter.sys" and leftover files in "C:\Program Files\Trust"
- Open the device manager (Start / Execute / "C:\WINDOWS\system32\devmgmt.msc")
- If you see an item under "Human Interface Devices (HID)" with a yellow exclamation mark, right click on it a select uninstall
- Reboot
- Wait for the new hardware to install at startup

[wlp]

Thank you WTH.  I followed your instructions (though saw you mentioning "in safe mode" to late, and thus did it in normal mode!).  Now COMODO functions well and (most of) the mouse functions.     I have the impression that the add-on buttons on the mouse don't function , but before I can say that for sure I have to test a bit more.

Anyhow, if these additional buttons don't function, that's no big deal.  The most important is that I can use my wireless mouse again.

COMODO support:  since my problem has a work around, the resolution of this issue is not urgent anymore (for me).  However, probably you investigate further and resolve the incompatibilty in a future release of your great product.  "Great product", as in "much better and easier to use than Zonealarm", is my impression after 5 days of trialing.  If my impression changes, I'll let you know!  If I can help with more dumps or trials, please tell me via this way.

[WTH]

My mouse only have 3 special buttons (a DPI one and two to go back and forward in the browser history) and they work ok (at least in Firefox)

BTW, the kmwdfilter.sys is in C:\windows\system32\drivers\kmwdfilter.sys

[injvstice]

Unfortunate I don't have a minidump, I have a full dump. So I thought I'd just post the analysys and see if this is an already known bug.

basically I get a BSOD about 50% of the time when I resume from standby. This is the only time I get crashes, other than that the system has been very stable.

Here's what windbg says. Can someone tell me if this is a known bug? I actually think I get two different crashes in this scenario, but this is the latest one.

This is with 3.0.25.378. Unfortunately if I can't get this fixed, I will need to get comodo uninstalled, because this is a laptop and it goes to sleep quite often.



*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: ae6a1f66, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 8a6a0015, address which referenced memory

Debugging Details:
------------------






READ_ADDRESS:  ae6a1f66 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP:
ndis!ndisFreePacketPoolHdr+25
8a6a0015 0fb7481e        movzx   ecx,word ptr [eax+1Eh]

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  8b567724 -- (.trap 0xffffffff8b567724)
ErrCode = 00000000
eax=ae6a1f48 ebx=0000858a ecx=00000000 edx=82146700 esi=821469ac edi=ae6a1f10
eip=8a6a0015 esp=8b567798 ebp=8b5677a4 iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
ndis!ndisFreePacketPoolHdr+0x25:
8a6a0015 0fb7481e        movzx   ecx,word ptr [eax+1Eh]   ds:0023:ae6a1f66=?
Resetting default scope

LAST_CONTROL_TRANSFER:  from 8a6a0015 to 8209ed84

STACK_TEXT: 
8b567724 8a6a0015 badb0d00 82146700 8213c920 nt!KiTrap0E+0x2ac
8b5677a4 8a6a06ea ae6927d8 821469ac 8a6af928 ndis!ndisFreePacketPoolHdr+0x25
8b5677c0 8a6a07a6 001469ac 00000000 8743ae7c ndis!ndisFreePacketPool+0x2e
8b5677dc 8f52e552 821469ac 876d0008 874e10e8 ndis!NdisFreePacketPool+0x46
WARNING: Stack unwind information not available. Following frames may be wrong.
8b567924 8a74f4b1 8b5679c0 8b56794c 8743ae7c inspect+0x2552
8b5679b8 8a74f129 c0000001 84b57c70 8a6af918 ndis!ndisInitializeBinding+0x23b
8b567a44 8a75df67 874e10e8 00000000 00000000 ndis!ndisCheckAdapterBindings+0x170
8b567a68 8a75e1e1 00000000 86883008 00000000 ndis!ndisIMInitializeDeviceInstance+0x93
8b567a88 8f9c1a83 8743a4d8 89c781c0 86883008 ndis!NdisIMInitializeDeviceInstanceEx+0x100
8b567b4c 8f9c4cef 8720be64 8b567be0 8a74f4b1 VMNetSrv+0x2a83
00000000 00000000 00000000 00000000 00000000 VMNetSrv+0x5cef


STACK_COMMAND:  kb

FOLLOWUP_IP:
inspect+2552
8f52e552 8b85f8feffff    mov     eax,dword ptr [ebp-108h]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  inspect+2552

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: inspect

IMAGE_NAME:  inspect.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4834413f

FAILURE_BUCKET_ID:  0xD1_inspect+2552

BUCKET_ID:  0xD1_inspect+2552

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

[huub]

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..

  .... text deleted ....

Exactly the same happened to me! I recently purchased a brand new HP laptop PC (dv9860ed). Created the recovery disks and started to apply my personal software and settings onto Vista! First step was to remove the supplied firewall and virusscanner software. Because I use now for almost 2 years the COMODO Suite on my XP systems you can guess what I installed first. So far I have been very happy with almost all COMODO software on XP platforms.

Unfortunately I must say that I kept BLUE SCREENS almost everytime when the system woke up from standby or sleep mode. I reinstalled 3 times Vista from scratch, including all the other software I use (each session lasted somewhere between 4 and 8 hours)! And the crashes / stopcode 0X2C didn't disappear. Now I removed today BOClean and CFP3 and I can use powersafe again!

HOPE THAT COMODO WILL FIX THE ISSUE(S) SOON WITH BOCLEAN AND CPF V3, AND MAKES AVAILABLE THEIR VIRUSSCANNER WHICH IS NOT YET SUPPORTED ON VISTA (WHICH FORCED ME TO START USING AVG)!!!!!

[jcmac]

I'm getting a random bsod with error "STOP: 0x0000007E (0x0000005, 0x804E37F3, 0xF8B398E8, 0xF8B395E4)" on restarts and shutdowns. I am unable to recreate the error, it just happens every so often. The last software change I made was to install COMODO Firewall 3.0. That's my prime suspect, since the problem started soon after it was installed. I'm also running Avira AntiVir Classic, which I installed a couple of days prior to installing COMODO. COMODO is installed as a standard firewall with leak protection (no hips).  I have no other security app's resident.

My configuration is:

HP Pavilion 7960
Win XP, SP2
1.8 gHz P4 (socket 423)
512 Mb RAM
Hitech Radeon 9550SE

Minidump attached (I had to change the .dmp to .txt to get it to attach).

[injvstice]

The analysis I posted earlier also shows up as BAD_POOL_CALLER on he blue screen, at least sometimes.
It is definitely Comodo. I've looked at it with windbg a few times to make sure there is no other suspect.

I also have an HP product (laptop, workstation line, 8510w). Would be nice to know if someone on non-hp hardware is seeing it.

I have since uninstalled comodo and the crash has gone away. Sorry, but no cigar. It may be a nice product, but blue screens are unnaceptable.

[jcmac]

About a week ago I uninstalled both Avira and COMODO and then reinstalled COMODO with avast.  I ran the COMODO/avast combination for 4 days without any problems, so on Sunday afternoon I uninstalled avast and reinstalled Avira.  I have been running that for 3 days and the problem has not reoccured.  I assume the reinstall of either COMODO or Avira cured the problem.

[Tags:]