On 23rd August you posted elsewhere
I get this error in the event viewer three or more times a day.
{Registry Hive Recovered} Registry hive (file): '\??\C:\Windows\System32\SMI\Store\Machine\SCHEMA.DAT' was corrupted and it has been recovered. Some data might have been lost.
Now you say
To: Hazelnut
CCleaner is not on my Start Up list. At the end of a session I double click the icon on my desk top and run it. Just the Cleaner, for routine cleaning of the junk I pick up on the internet. I was really just asking if SCHEMA.DAT was one of the files the cleaner was overwriting and that is why it kept needing to be recovered. I don't know what exact files the cleaner overwrites. I will stop running it for a while and see if the error continues.
CCleaner is absolutely not guilty of corrupting your registry "three or more times a day" unless you are running CCleaner at the end of a session "three or more times a day".
We just do not know how many sessions are in a day.
You really do not have to run CCleaner every session.
If you do not run CCleaner for a month it still will not drown in junk files.
Just stop running CCleaner and if the errors continue you will have proof that CCleaner is innocent.
In the other forum Hazel linked to you have said that after you "turned the computer on 8/24/2012 6:10:45 AM"
Information 8/24/2012 6:24:20 AM Service Control Manager 7036 None
(The Windows Modules Installer service entered the stopped state.)
Information 8/24/2012 6:24:20 AM Service Control Manager 7040 None
(The start type of the Windows Modules Installer service was changed from auto start to demand start.)
Error 8/24/2012 6:24:19 AM Kernel-General 5 None
({Registry Hive Recovered} Registry hive (file): '\??\C:\Windows\System32\SMI\Store\Machine\SCHEMA.DAT was corrupted and it has been recovered. Some data might have been lost.)
Information 8/24/2012 6:24:19 AM Service Control Manager 7040 None
(The start type of the Windows Modules Installer service was changed from demand start to auto start.)
You also said a similar sequence at around 7:03:50
It seems obvious to me that the problem commenced when SOMETHING chose to switch W.M.I. service to auto start,
and as a result the registry hive was found to be corrupt, and a recovery ATTEMPT was made at 6:24:19
(I said ATTEMPT because in my experience what Windows promises is not always fulfilled)
and one second later the W.M.I. service was STOPPED.
During the same session, without any CCleaner involvement,
an identical sequence of cause and event occurred from 7:03:50 AM to 7:03:51 AM.
CCleaner is totally innocent of this second sequence,
My conclusion is that you either have something else happening between 6:24:20 AM and 7:03:50 AM that corrupted your registry,
OR ALTERNATIVELY Windows FAILED to correct your registry when it so attempted at 6:24:19 AM;
it only said it was recovered because it did not realize that Windows was broken and might need to be re-installed.
It may well be that something is wrong with your Windows update system / scheduling