Sorry to resurrect an old thread, but just putting this here for my own benefit as I'd completely forgotten what my CC would do in OPP5, before finding it scrawled on a piece of paper on a shelf.
I found on my system that on finding an error, it'd proceed to clock down until it was back at the starting number pretty reliably.
Also, I'm not sure how much the CPU stress test stresses NEON code. My GHz pandora's pretty stable at 1.2GHz@OPP4 most of the time, but on running DraStic I have to clock down to 1.1GHz otherwise I get pretty repeatable glitches.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.