OCCT Reporting False Error?

[hans030390]

I've been overclocking my recently purchased FX-6100 (got it for $100 along with an asus M5A97 for $80!), and I noticed something odd when testing it with OCCT. I was running the OCCT test, not Linpack, with a large data set. It ran without errors for 9 hours at 4.1GHz (only using multipliers, 1.37V on load), but when I pressed the OFF button, it said it had stopped because of an error.

This has happened to me twice at different speeds/voltages. Usually if there is an error, it will stop running and report it. This time and one other time before, however, it says there was an error when stopped instead of giving its usual stopped by user message.

I'm guessing this is probably just a bug, but I wanted to see what everyone else though.

 

[Tetedeiench3]

Hello,

yes, this has been identified, and should be fixed in the most recent beta (where almost everything concerning that was rebuilt to avoid bugs such as the one you are reporting).

You can safely ignore this error.

You can get the latest beta at : http://www.ocbase.com/download.php?fileext=beta

Just a warning, it is an early stage beta, and may contains other bugs. The current GPU:3D DX10 still needs quite some work (i'm not happy with the error detection rate right now). The CPU part should be fine.