[ol]- BSOD. BugCheck 19. BAD_POOL_HEADER (19). inspect.sys and cmdguard.sys
Can U reproduce the problem & if so how reliably?:Random, sometimes happens during boot
If U can, exact steps to reproduce. If not, exactly what U did & what happened:Rebooted
If not obvious, what U expected to happen: NO BSOD
If a software compatibility problem have U tried the conflict FAQ?: I have read the conflict FAQ. I didnāt find there a decision to my problem.
Any software except CIS/OS involved? If so - name, & exact version: Avast 8.0.1483
Any other information, eg your guess at the cause, how U tried to fix it etc: I donāt know how to fix it.
Always attach - Diagnostics file, Watch Activity process list, dump if freeze/crash. (If complex - CIS logs & config, screenshots, video, zipped program - not māware): Crash dumps are in attachment
The full dump is here
[/ol]
B. MY SETUP
[ol]- Exact CIS version & configuration:Comodo Firewall 5.12.256249.2599, Proactive Security
Have U made any other changes to the default config? (egs here.): Of course yes, I added rules for applications in Firewall and Defence+
Have U updated (without uninstall) from a CIS 5?: I have CIS 5 initially
[li]if so, have U tried a a clean reinstall - if not please do?: Tried
[/li]- Have U imported a config from a previous version of CIS: No
[li]if so, have U tried a standard config - if not please do: Tried
[/li]- OS version, SP, 32/64 bit, UAC setting, account type, V.Machine used: Windows 7, SP1, 64bit, UAC=on, admin, VM not used
Other security/sābox software a) currently installed b) installed since OS: a=Avast 8.0.1483, b=None
[/ol]
Yes Comfireuser, we would be very grateful if you wold do as Ronny requested, as the devs may not be able to fix this otherwise.
We are not in general forwarding 5.x bugs any more, but this is a critical bug and you have supplied enough info to make it format verified, so Iāll forward it now.
Thank you very much for your report in standard format, with all information (except full dump!) supplied. The care you have taken is much appreciated by Comodo, and will increase the likelihood that this bug can be fixed.
Developers may or may or may not communicate with you in the forum or by PM/IM, depending on time availability and need. Because you have supplied complete information they may be able to replicate and fix the bug without doing so.
I will set up, but i think that minidumps are quite enough to find the issue. If I would have symbols for cmdguard.sys or inspect.sys I would find the function what cause the error. Moreover if i would have source files I can find the line of code what produce the error. Developers have symbols and source files.
Probably a language problem See my above quoted below, with added emphasis.
We are not in general forwarding 5.x bugs any more,[b] but[/b] this is a critical bug and you have supplied enough info to make it format verified, [b]so I'll forward it[/b] now.
Mainly they are adding a summary screen, and a few other things, and trying to make sure that there are as few bugs as possible before sending the update to V5 users.
Too many BUGS in v6! And my crash dumps were downloaded only onceā¦
Do you still interesting in fixing this BUG?
I have a full kernel dump and a BSOD caused by cmdguard.sys
Thanks very much for appending all this information, it is very much appreciated.
Please note the below, quoted from this topic:
Developers may or may or may not communicate with you in the forum or by PM/IM, depending on time availability and need. Because you have supplied complete information they may be able to replicate and fix the bug without doing so.
Iām sorry. I believe that a large part of the problem is the lack of a full memory dump. From what I understand for many BSOD cases this is needed in order for the devs to identify and fix the issue.
Please set your computer to create full memory dumps. Then, the next time the BSOD happens please upload the full memory dump to this page and paste the download link in this topic.
