pc crash after ccleaner registry malwarebytes'

After I had removed an old Free-version of Malwarebytes' Anti-Malware with a tool that they send me and installed the Pro-version, when I first activated the Registry cleaning tool of CCleaner my PC crashed, which has never happened before. Could anyone explain why this happened?

Since the incident, I made adjustments in the Settings, allowing for exclusions of Malwarebytes' but I haven't activated the registry cleaning tool since.

Hermes35

Type gebeurtenis: Fout

Bron van gebeurtenis: Ci

Categorie van gebeurtenis: CI-service

Gebeurtenis-ID: 4126

Datum: 23-6-2011

Tijd: 9:46:45

Gebruiker: n.v.t.

Computer: D-EB84F6B9BE9E4

Beschrijving:

Bezig met het opschonen van beschadigde metagegevens van de inhoudsindex op c:\system volume information\catalog.wci. De index wordt automatisch hersteld doordat alle documenten opnieuw worden gefilterd.

Zie Help en ondersteuning op http://go.microsoft.com/fwlink/events.asp'>http://go.microsoft.com/fwlink/events.asp'>http://go.microsoft.com/fwlink/events.asp'>http://go.microsoft.com/fwlink/events.asp voor meer informatie.

Type gebeurtenis: Fout

Bron van gebeurtenis: Ci

Categorie van gebeurtenis: CI-service

Gebeurtenis-ID: 4124

Datum: 23-6-2011

Tijd: 9:46:45

Gebruiker: n.v.t.

Computer: D-EB84F6B9BE9E4

Beschrijving:

De inhoudsindex op c:\system volume information\catalog.wci is beschadigd. Stop de Indexing-service (cisvc) en start deze opnieuw.

Type gebeurtenis: Waarschuwing

Bron van gebeurtenis: Ci

Categorie van gebeurtenis: CI-service

Gebeurtenis-ID: 4132

Datum: 23-6-2011

Tijd: 9:46:45

Gebruiker: n.v.t.

Computer: D-EB84F6B9BE9E4

Beschrijving:

Tijdens het herstellen van de catalogus c:\system volume information\catalog.wci zijn in het PropertyStore-object 1 inconsistentie(s) gevonden.

Zie Help en ondersteuning op http://go.microsoft.com/fwlink/events.asp voor meer informatie.

Type gebeurtenis: Fout

Bron van gebeurtenis: System Error

Categorie van gebeurtenis: (102)

Gebeurtenis-ID: 1003

Datum: 23-6-2011

Tijd: 9:40:27

Gebruiker: n.v.t.

Computer: D-EB84F6B9BE9E4

Beschrijving:

Foutcode; 00000006, parameter1: 00000000, parameter2: 00000000, parameter3: 00000000, parameter4: 00000000.

Zie Help en ondersteuning op http://go.microsoft.com/fwlink/events.asp voor meer informatie.

Gegevens:

0000: 53 79 73 74 65 6d 20 45 System E

0008: 72 72 6f 72 20 20 45 72 rror Er

0010: 72 6f 72 20 63 6f 64 65 ror code

0018: 20 30 30 30 30 30 30 30 0000000

0020: 36 20 20 50 61 72 61 6d 6 Param

0028: 65 74 65 72 73 20 30 30 eters 00

0030: 30 30 30 30 30 30 2c 20 000000,

0038: 30 30 30 30 30 30 30 30 00000000

0040: 2c 20 30 30 30 30 30 30 , 000000

0048: 30 30 2c 20 30 30 30 30 00, 0000

0050: 30 30 30 30 0000

Zie Help en ondersteuning op http://go.microsoft.com/fwlink/events.asp voor meer informatie.

Perhaps the Pro version of Malwarebytes is fighting to the death any infringement of its registry keys.

Perhaps CCleaner has seen keys that were left behind by the previous version are are linked to nothing,

but are still under Pro version protection.

This is ambiguous

"when I first activated the Registry cleaning tool"

Do you mean you clicked the Registry button on the left,

or the "Scan Issues",

or the "Fix Selected Issues" and if so what issues were selected.

You need to provide more information:

* Windows operating system version, i.e.; Windows XP, Vista, 7.

* CCleaner version.

I use Windows XP, SP3, and have the latest version of CCleaner.

Just returned home and found the above responses plus a P.M. timed 11.23 advising

It happened indeed after I hit the regsitry cleaning tool on the left, the PC crashed before I could select anything to remove.

For the benefit of all I am responding here. It states on :-

http://www.malwarebytes.org/products/malwarebytes_pro#features

Malwarebytes Anti-Malware PRO monitors every process and stops malicious processes before they even start.

This confirms what I suspected before.

Malwarebytes Anti-Malware PRO runs in real-time to defend against anything happening,

unlike the non-PRO which tells you what looks dodgy when you run on demand.

Obviously they take the responsibility seriously and have hysterics when they see a non-white-listed process looking at something sacred to themselves.

They saw CCleaner coming as soon as you launched the EXE,

and when you hit the Registry button it "got its retaliation in first" before there could be a presentation of an analysis.

You have a watch-dog that will take the leg off the postman when he turns into your street ! !

I suggest you contact malwarebytes support or their user forum about how to tame its reactions.

CCleaner could be white-listed by themselves, or they should tell you how to do it for yourself.

My experience of Comodo C.I.S. protection is that some applications are automatically white-listed,

and the rest are similarly allowed to escape punishment if the user :-

Authorises specific activities, and it obeys the constraints.

E.G. If you authorise what you should not trust, such as a screen saver,

then if it is secretly a key-logger Comodo will not allow it to monitor your keyboard and to phone home,

unless you allow it to both monitor keyboard and to initiate use of the Internet.

Thanks for the reaction, I'll let them know.

Hermes 35