Intel Turbo Boost Montor Problem - i5

[mrkwuzhir24]

Turbo Boost Monitor on Windows 7 Home Basic - i5 processor... first i scan for temp files etc. it worked fine. Then when i use the Registry fix of the CCLEANER, it always show this error about ACTIVE X etc. then i rescan, and same thing happens, it always show errors about it, then i restart my laptop, then the gadget INTEL TURBO BOOST MONITOR is not working anymore. Then i used my backup registry then it worked again ofcourse. This gadget of Intel is new (i think) so maybe Piriform still is not working with this issue. Thank you and God Bless everyone.

[Andavari]

You can exclude the registry key by going into CCleaner's:

Options->Exclude->Add Registry

 

Then CCleaner will never offer to remove that needed registry key again.

[blackmamba]

i have this same issue what was the registry key?? ive uninstalled and reinstalled turbo boost multiple times and cant get it to work please tell me the registry key and how to manualy re add it thanks

[gwaitsi]

I've got the same problem on an ASUS G51J and i can't restore the turbo boost. i've tried deleting the driver and monitor tool, but re-installation doesn't help.

[Nergal]

hi, please remember that not everything suggested by ccleaner's registry cleaner (or any registry cleaning/"boosting" program) should be cleaned. oft times this is because the registry entry does not properly identify itself with an installed software (a fault that could be due to bad programming on the part of the software's developer, or on purpose as is the case of many AntiMalware products). You should only remove the entries which are for software you don't have anymore. when in doubt leave the entry alone.

 

As suggested above one can right click an entry and add it to the exclude list, at which time your particular install of CCleaner will no longer suggest you remove it.

[kroozer]

And I will extend Nergal's explanation to my situation:

 

CC's reg cleaner shows unused file extensions .json .cmg, .lay

 

However, Everything search engine shows those extensions are active, so I will ignore CC's recommendation to clean them.