The bug/issue
1. What you did:- ran chkdsk c:/f/r
2. What actually happened or you actually saw:- BSOD 0x24 and Can not boot in safe mode BSOD every time
3. What you expected to happen or see:: No BSOD
4. How you tried to fix it & what happened: : ran chkdsk from PE, after that i can boot in safe mode but not in normal mode, disabling cmdguard.sys helped in booting to desktop. chkdsk was run one more time a bad cluster was found in sfi.dat, as a result it was taking forever( 2hr and no sucess) to boot
Deleted sfi.dat did the reinstall of CIS
5. If its an application compatibility problem have you tried the application fixes here?: No
6. Details & exact version of any application (execpt CIS) involved with download link: N/A
7. Whether you can make the problem happen again, and if so exact steps to make it happen: Not sure
8. Any other information (eg your guess regarding the cause, with reasons): cmdguard was locking sfi.dat similar issues were also observed while running defrag.
Files appended. (Please zip unless screenshots).
1. Screenshots illustrating the bug: N/A
2. Screenshots of related CIS event logs and the Defense+ Active Processes List: N/a
3. A CIS config report or file. n/a
4. Crash or freeze dump file: n/a
Your set-up
- CIS version, AV database version & configuration used:5.3.174622.1216.7377
- a) Have you updated (without uninstall) from CIS 3 or 4: no
b) if so, have you tried a clean reinstall (without losing settings - if not please do)?:no - a) Have you imported a config from a previous version of CIS:
b) if so, have U tried a standard config (without losing settings - if not please do)?: no - Have you made any other major changes to the default config? (eg ticked ‘block all unknown requests’, other egs here.): no
- Defense+, Sandbox, Firewall & AV security levels: D+= disabled, Sandbox= n/a, Firewall = custom , AV = stateful
- OS version, service pack, number of bits, UAC setting, & account type: xp pro sp3 fully updated
- Other security and utility software installed: nil
- Virtual machine used (Please do NOT use Virtual box):no
cmdguard load very ealy in boot sequence, by modifying the logic so that it does not locks its critical file when essential windows file checking utilities are scheduled to run, also it can use checksum to check integrity of sfi.dat before discarding it