Menu Close

Chackiwinja

Forum Replies Created

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • in reply to: Old benchmark back #541
    Chackiwinja
    Participant

    Okay, I understand. But would it be possible to use two benchmarks only for the EOS screenshot?

    in reply to: 1.3.7 #532
    Chackiwinja
    Participant

    Can you use both the “old” speed detect and Core Temp’s speed detect? The “old” speed detect reads the FSB change while Core Temp reads the total speed of the CPU.

    As an example:
    My CPU normally runs at 3400 MHz (34×100) and I was able to bypass Core Temp by lowering my multiplier and raising my clock speed (33×103) = 3391 MHz. Since there is no FSB change detect, my MOSS said software overclock 0.00% while it actually is ~3%. It does show that a different multiplier and core speed is used in the logfile, but it will be harder for us to detect it as we then would need to check all logfiles.

    Standard clock: http://i.imgur.com/L7JUR.jpg
    Modified clock: http://i.imgur.com/GxCf1.jpg

    So if we can have both detection methods logged, we can catch both the software overclockers and the turbo modus overclockers. E.g. Software Overclock and Core Overclock or similar.

    in reply to: 1.3.7 #531
    Chackiwinja
    Participant

    The extra logfile information is a great addition. The Net info will be really useful when comparing to the WAC logs.

Viewing 3 posts - 1 through 3 (of 3 total)