Old benchmark back

What is Moss ? Forums Old benchmark back

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #293
    Chackiwinja
    Participant

    Like I announced previously here http://nohope.eu/forum/?mingleforumaction=viewtopic&t=3, Core Temp does not read the FSB/BCLK change, but only the total frequency – which I was able to demonstrate.

    Now a new problem has came up: in the core temp settings, you can disable the real time capture, thus giving you the possibility to overclock. This was demonstrated by an ESL user here:
    http://en.twitch.tv/tdream30/b/361414773

    So I’m afraid that we have to either quit using Core Temp due to this error, or find a way to make sure that all users always have the “real temp” benchmark active. This was also the problem with BlackBox, you could easily disable it in the menu.

    Anyway, we urgently need the old benchmark back, and then we need to find a solution to check this. Maybe CPU-Z is an alternative? From what I know there is no option to freeze it

    #539
    ADM_nohope
    Keymaster

    I cant do 2 benchmarks each screens , but I will investigate securing coretemp andusing a new tool , btw coretemp uses cpuz driver but it’s not a free tools

    #541
    Chackiwinja
    Participant

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

    #544
    ADM_nohope
    Keymaster

    look like there is a problem with core temp monitoring disabled too … working on it

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.

Play Cool , Play Hard but Play Fair