CAUSE:
We have narrowed this phenomenon down to either Windows Explorer maxing out the CPU constantly, or that Windows is falsely reporting the CPU's state to RamBooster. 

SOLUTION:
To get RamBooster to ignore this erroneous information and Optimize when your available RAM gets below the Alarm Level, in Preferences, set "Run ONLY if CPU-usage is below this"  to -0- (zero).