- What you did: nothing special
- What actually happened or you actually saw: BSOD
- What you expected to happen or see: no BSOD
- How you tried to fix it & what happened: installed newest MB-Network and -Sound drivers.
- If its an application compatibility problem have you tried the application fixes?: -
- Details (exact version) of any application involved with download link: -
- Whether you can make the problem happen again, and if so exact steps to make it happen: BSOD occurs randomly when comodo firewall is running.
- Any other information (eg your guess regarding the cause, with reasons): Problem occurs since i am using a new attached Wireless device ( Netgear WNA1100 (newest drivers installed(USB Device))), my guess is it has something to do with it.
- Screenshots illustrating the bug: -
- Screenshots of related event logs or the active processes list: attached in rar
- A CIS config report or file: attached in rar
- Crash or freeze dump file: attached in rar
- CIS version, AV database version & configuration used: newest Comodo Firewall Version
- Have you updated (without uninstall) from CIS 3 or 4, if so have you tried reinstalling?: cant remember, no
- Have you imported a config from a previous version of CIS, if so have U tried a preset config?: -
- Defense+ and Sandbox OR Firewall security level: both on Training-Mode, no Sandbox activated
- OS version, service pack, no of bits, UAC setting, & account type: Win7, 64 bits, Standard UAC setting, Administrator
- Other security and utility software running: AvastAntivirus, ShrewSoft VPN
- Virtual machine used (Please do NOT use Virtual box): -
- I am using the ShrewSoft VPN client to connect to my University´s W-Lan.
- The big memorydump is refering to the inspect.sys file which is connected to Comodo, the minidump is refering to the tcpip.sys file, i have no idea which one is right please help …
-The included minidump file was automatically created by Windows without me having it activated in the system settings, now its activated i will add the newest minidump after the next crash occurs.[/b]
[attachment deleted by admin]