Sorry to hear about this problems. They are very serious.
Did the first computer crash after rebooting after you had it cleaned with CSC? For the second computer (laptop) did the crash happen after you had used CSC and rebooted?
I seriously doubt whether CSC caused this problem. This type of problems usually points to either funky hardware or some serious instability on driver level.
Next time it happens try Last Known Good Configuration. To get that choice you need to start pushing F8 towards the end of the BIOS routine until you get a screen with boot options. Then choose Last Known Good Configuration.
minx, did both of your systems say that SYSTEM was missing? Because I think this is the SYSTEM registry hive that XP is talking about. XP announcing that SYSTEM is corrupt, that I have seen before. But, missing? That’s new to me.
Anyway, Eric’s suggestion of F8 on boot & selecting Last Known Good Configuration sounds good to me. At least that should restore SYSTEM & allow XP to run.
We are sorry for the inconvenience you encountered, but this is not Comodo System Cleaner’s fault, as it runs fine, these kind of problems are a thing of the past now. As layman said above , this is the result of an incompatibility between Norton 360 and CSC. Norton 360 blocks CSC’s start-up registry keys, triggering a non responsive Windows loading screen, and in some cases Norton’s drivers cause the manifestation that you encountered.
We tried many ways of solving this problem, and the only efficient solution was removing the Norton drivers in “C: \ windows \ system32 \ drivers \ N360”. This operation must be conducted from an environment ( operating system or DOS based application ) outside Windows. After that, Windows booted in normal mode just fine, the CSC Finalize/Restore window appeared as it should.
Considering this situation, you have to choose between Comodo System Cleaner and Norton 360 as they don’t mix together.
but this is not Comodo System Cleaner's fault, as it runs fine, these kind of problems are a thing of the past now. As layman said above , this is the result of an incompatibility between Norton 360 and CSC. Norton 360 blocks CSC's start-up registry keys, triggering a non responsive Windows loading screen, and in some cases Norton's drivers cause the manifestation that you encountered.
I have run into this problem on two separate computers both running 32-bit XP, neither of which were running Norton 360. The first time it happened was probably with a version of Comodo a few months old. Most recently, it happened with 1.1.64946.38.
I have to admit that i stopped using CSC because it caused more problems than it fixed ---- on several occasions i had to do a complete OS re-install becasue of CSC and kept thinking well this version will be better and won’t do that — boy was i wrong. Until it is a ‘FINISHED PRODUCT’ i will steer clear of this one. >:(