A. THE BUG/ISSUE (Varies from issue to issue) Can you reproduce the problem & if so how reliably?:
Yes, assumed 100% reliably. If you can, exact steps to reproduce. If not, exactly what you did & what happened:
1: Start the computer
2: Create a large amount of traffic (eg. transfer large files from another machine via ethernet on local network) One or two sentences explaining what actually happened:
The computer bluescreens after several minutes, several codes have been observed (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED, KMODE_EXCEPTION_NOT_HANDLED, SYSTEM_SERVICE_EXCEPTION) One or two sentences explaining what you expected to happen:
The computer remains stable. If a software compatibility problem have you tried the advice to make programs work with CIS?:
Not a software compatibility problem. Any software except CIS/OS involved? If so - name, & exact version:
No. Any other information, eg your guess at the cause, how you tried to fix it etc:
B. YOUR SETUP Exact CIS version & configuration:
18.104.22.16844, Firewall Security config. Modules enabled & level. D+/HIPS, Autosandbox/BBlocker, Firewall, & AV:
Safe mode HIPS, Autosandbox disabled, Custom Ruleset firewall, Viruscope disabled. Have you made any other changes to the default config? (egs here.):
None. Have you updated (without uninstall) from CIS 5 or CIS6?:
No. if so, have you tried a a a clean reinstall - if not please do?:
Not applicable. Have you imported a config from a previous version of CIS:
Yes. if so, have you tried a standard config - if not please do:
Yes. OS version, SP, 32/64 bit, UAC setting, account type, V.Machine used:
Win8.1, 64-bit, Notify on changes (no dim), administrator, not a VM Other security/s’box software a) currently installed b) installed since OS, including initial trial security software included with system:
a=Microsoft Security Essentials b=None
I have also experienced a lot of different STOP errors since updating to CIS v8. I have now disabled cmdguard.sys via registry and was able to uninstall CIS and the system seems stable again.
I am afraid I only have a few Kernel dumps of the different errors here.
Should I upload them (new topic because i am using Win7), or would they not help anyway?
The errors seem to have appeared in random modules and with random Error Codes. It seems like something corrupted kernel memory.
Thank you very much for your report in standard format, with all information 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 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 haven’t sent the dump to Flykite explicitly but in any case thanks for the forward. I should mention that this problem is not exclusive to transferring large files over the LAN as you have named it in the title; the system will happily crash during other network-intensive operations such as using the BitTorrent protocol as well.
If the devs need additional follow-ups from me, I should be available often enough. I would really like to see this problem fixed.
As it turns out, this was a driver issue all along. Microsoft pushed an update for the NIC driver a few days ago and the system has been rock solid since, so the firewall was probably simply triggering the old driver misbehaving.
That’s about it, nothing more to see here. The nearest mod may move this to resolved.