RTSS 6.7.0 beta 1

Discussion in 'MSI AfterBurner Overclock Application Discussion' started by Unwinder, Feb 20, 2017.

  1. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    14,941
    Likes Received:
    2,090
    Other users like @Vogon spreading the same false claims about "stupid author failing to recognise its an issue" about fan stop in different communities will follow @SweatyBumSmell if this continues. Seriously, research what is BIOS min fan speed limit, open your eyes, see that yellow dotted line displaying it on the curve on your own screenshots. You cannot go below this limit with manual fan control without altering BIOS and insulting me further and further wont help you to bypass it.
     
  2. Dan Longman

    Dan Longman Member Guru

    Messages:
    103
    Likes Received:
    39
    GPU:
    2080ti watercooled
    Gotta love people who don't understand how things are supposed to work and spread misinformation ‍♂️

    Also I finally took the time to set up my OSD using the OverlayEditor (even though it's been out for a while) in RTSS instead of using afterburner and it's so great. I like a simple text only overlay as I leave it up all the time and it's so easy and powerful to accomplish this.
    [​IMG]

    Great job as always Unwinder!
     
  3. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    14,941
    Likes Received:
    2,090
    @Vogon
    Your choice, you've got a chance as well. Screw me, no problem. And we've got one more "polite" kid with 3080 isolated from this place forever.
     
  4. ToastGrande

    ToastGrande Member

    Messages:
    12
    Likes Received:
    4
    GPU:
    RTX 2080 Ti FE
    AB v4.6.3.15840 Beta 2, Nvidia drivers 456.55. 2080ti. Tested as a AB upgrade, then as full remove/reinstall.

    As an AB upgrade from older version, the error in OC Scanner was "failed to register scanner callback!!!"

    With a remove/reinstall of AB, the error is "scan failed with code 22h"

    Loading the OC scanner [driver v456.55, NVAPI mode]
    12:28:38 Connected to MSI Afterburner control interface v2.3
    12:28:46 GPU2 : VEN_10DE&DEV_1E07&SUBSYS_12FA10DE&REV_A1&BUS_2&DEV_0&FN_0
    12:28:46 Scan failed with code 22h

    The interesting part here is that the scanning does appear to be happening as the GPU/volt display in AB is doing the characteristic brief upward/downward change in both GPU and voltage. I'm also noticing that the memory MHz is also going up/down.

    Unwinder, are there any logs I can capture to determine what's going on? The only unique piece here is that I have a pair of 2080ti's in SLI (NVbridge).
     

  5. ToastGrande

    ToastGrande Member

    Messages:
    12
    Likes Received:
    4
    GPU:
    RTX 2080 Ti FE
    And to update. Having let it alone, eventually, the OC Scanner reported:

    12:53:54 Scan succeeded, average core overclock is 118MHz, memory overclock is 200MHz
    12:53:54 Dominant limiter
    12:53:54 Voltage
    12:53:54 Results are considered unstable
    12:53:55 Overclocked curve exported to MSI Afterburner
     
  6. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    14,941
    Likes Received:
    2,090
    OC Scanner is NVIDIA’s technology, not Afterburner’s one.
     
  7. babyboom666

    babyboom666 Member

    Messages:
    29
    Likes Received:
    37
    GPU:
    GTX1080 Gaming X+
    MSI GTX1080
    AB v4.6.3.15840 Beta 2, Nvidia drivers 456.55 --> "failed to register scanner callback!!!" *
    AB v4.6.3.15840 Beta 2, Nvidia drivers 456.38 --> "failed to register scanner callback!!!" *
    AB v4.6.3.15840 Beta 2, Nvidia drivers 460.20 --> "failed to register scanner callback!!!" *
    AB v4.6.3.15840 Beta 2, Nvidia drivers 452.22 --> OK (Legacy mode) *

    AB v4.6.3.15777 Beta 1, Nvidia drivers 456.55 --> OK *
    AB v4.6.3.15777 Beta 1, Nvidia drivers 456.38 --> OK *
    AB v4.6.3.15777 Beta 1, Nvidia drivers 460.20 --> OK *
    AB v4.6.3.15777 Beta 1, Nvidia drivers 452.22 --> OK *

    *Afterburner upgrade and Afterburner full remove (clean install)
     
    Last edited: Sep 29, 2020
  8. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    14,941
    Likes Received:
    2,090
    And one more time. The last one, for search haters. New OC scanner is NVIDIA's technology, not MSI Afterburner's one. And NVIDIA clearly declared that currently it is not supported on Pascal GPUs. And I commented it A LOT of times, use search please and no need to flood this thread with it please.
     
    babyboom666 likes this.
  9. ToastGrande

    ToastGrande Member

    Messages:
    12
    Likes Received:
    4
    GPU:
    RTX 2080 Ti FE
    Unwinder, I'm assuming you must pass data from AB to OC scanner via API, including the GPU you want tested? I tried to find the API documentation, but had no luck.

    If I select card 2 in AB, OC Scanner (via NVtopps.log) seems to think it's testing GPU index 0. If I select GPU 1 in AB, the test never happens in OC Scanner.

    Is it possible AB is passing information over to OC Scanner incorrectly when there are two GPUs in the system?

    This is what was in the AB display/interface:

    Loading the OC scanner [driver v456.55, NVAPI mode]
    12:28:38 Connected to MSI Afterburner control interface v2.3
    12:28:46 GPU2 : VEN_10DE&DEV_1E07&SUBSYS_12FA10DE&REV_A1&BUS_2&DEV_0&FN_0
    12:28:46 Scan failed with code 22h

    This is from the NVtopps.log file

    [12:28:46.843 2020/09/28]ERROR! Scanner::ScannerNvapiDispatcher::fireScanStatusUpdatesRelayed scan status update!
    [12:28:48.855 2020/09/28]INFO: ScannerManager changing state to 2
    [12:28:48.855 2020/09/28]INFO: Reverting for scan
    [12:28:48.855 2020/09/28]ERROR! OC considered unstable...reverting.
    [12:28:49.014 2020/09/28]INFO: ScannerMode starting scan...
    [12:53:54.913 2020/09/28]INFO: ScannerMode scan complete, completion status 1
    [12:53:54.913 2020/09/28]INFO: Scan type 1
    [12:53:54.913 2020/09/28]INFO: Average OC 118
    [12:53:54.913 2020/09/28]INFO: Limiter 4
    [12:53:54.913 2020/09/28]INFO: Memory OC MHZ 200
    [12:53:55.694 2020/09/28]INFO: ScannerManager changing state to 0
    [12:53:55.849 2020/09/28]INFO: Applying curve successful, gpuIndex: 0, applied: 1

    Thanks in advance.
     
  10. Brama

    Brama Active Member

    Messages:
    87
    Likes Received:
    1
    GPU:
    Geforce RTX 2080ti
    With same software configuration of ToastGrande I have an identycal message. As hardware I have only one 2080ti FE with latest original BIOS.
    I noted that if I try to scan e second time, the error code 22h no more appears and the overclock routine is performed till the end.

    I noted in my system that the new NVAPI routine is quite different than the previous one:

    -more time needed. 14 minutes with old and 23 minutes with new one
    - less temp and load produced with new
    - higher overclock obtained with new
    - different main limiter detected: old routine detects power limit, new one detects voltage limits


    I know that this new code is 100% written by Nvidia, but I am sure that Unwinder has a more direct channel with Nvidia coders. :)
     
    Last edited: Sep 30, 2020

  11. ToastGrande

    ToastGrande Member

    Messages:
    12
    Likes Received:
    4
    GPU:
    RTX 2080 Ti FE
    Further update on this. If I have AB set to GPU1, clicking "scan" always returns the following in the AB window, and there is a subsequent warning in nvtopps.log. No OC Scanning occurs.

    AB window
    17:34:27 GPU1 : VEN_10DE&DEV_1E07&SUBSYS_12FA10DE&REV_A1&BUS_1&DEV_0&FN_0
    17:34:27 Failed to register scanner callback!

    NVtopps.log
    [17:34:27.309 2020/09/30]WARNING! WARNING!IpcDispatcher::handleDataMessage: Message was rejected!



    Changing AB to GPU2 and clicking "scan" returns the following, and OC scanner kicks off, but says it is for GPU index:0, and 25 minutes later finishes and the curve is applied to gpu index:0 (GPU1). I've included a grab from monitor at the same time, showing that it's running against GPU1 and not GPU2.

    17:36:27 Connected to MSI Afterburner control interface v2.3
    17:36:30 GPU2 : VEN_10DE&DEV_1E07&SUBSYS_12FA10DE&REV_A1&BUS_2&DEV_0&FN_0
    17:36:30 Start scanning, please wait a few minutes
    17:36:30 Scan failed with code 22h

    NVtopps.log
    [17:36:30.433 2020/09/30]ERROR! Scanner::ScannerNvapiDispatcher::fireScanStatusUpdatesRelayed scan status update!
    [17:36:32.438 2020/09/30]INFO: ScannerManager changing state to 2
    [17:36:32.598 2020/09/30]INFO: Applying curve successful, gpuIndex: 0, applied: 0
    [17:36:32.598 2020/09/30]INFO: Reverting for scan
    [17:36:32.598 2020/09/30]ERROR! OC considered unstable...reverting.
    [17:36:32.756 2020/09/30]INFO: Applying curve successful, gpuIndex: 0, applied: 0
    [17:36:32.930 2020/09/30]INFO: ScannerMode starting scan...


    ABCapture.JPG
     
  12. bes49magadan

    bes49magadan New Member

    Messages:
    1
    Likes Received:
    0
    GPU:
    GTX 970
    Hi. Please tell me how to display the temperature of samsung m2 ssd 970 evo plus in msi afterburner in osd. I know there is a smart plugin but it only shows the temperature of the hdd. There is another option to install HWiNFO and you drive through it. I want to do this with built-in plugins in msi afterburner. Thanks for the help and sorry for the bad english.
     
  13. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    14,941
    Likes Received:
    2,090
    Nope, the same GPU selection way is used for old and new scanner APIs, it cannot get magically broken. The only thing I can offer you until NV fixes that in future drivers is an ability to use old legacy scanner on such hardware configs. There will be config file switch in new beta forcing AB to use old legacy scanner on Pascal and Turing GPUs even on 455.xx and newer drivers.
     
  14. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    14,941
    Likes Received:
    2,090
    There is no native plugin for it included in MSI AB, and I don't plan to create one in the nearest future as I don't use M2 drives on any of my rigs. So you may use HwInfo or AIDA plugin, or update SMART plugin yourself to support M2 drive attributes there.
     
  15. erho

    erho Member

    Messages:
    27
    Likes Received:
    11
    GPU:
    Pascal
    I can see it's possible to set a constant fan speed (say 50%) for one fan while simultaneously using stock fan curve for the other fan.

    However, I haven't been able to run a custom fan curve for one fan and stock curve for the other. Is this somehow possible?
     

  16. HARDRESET

    HARDRESET Master Guru

    Messages:
    673
    Likes Received:
    261
    GPU:
    3090 RTX / 1080Ti
    Good job! Unwinder :D jump to 11:20
     
  17. Evolver

    Evolver New Member

    Messages:
    1
    Likes Received:
    1
    GPU:
    EVGA 3090 FTW3
    Yeah pretty sure he had a bug or something. I had better results with PX1 today than afterburner. Funny enough Fan Control with EVGA cards is still broken in afterburner, so weird that he got better results anyway.
     
    HARDRESET likes this.
  18. HARDRESET

    HARDRESET Master Guru

    Messages:
    673
    Likes Received:
    261
    GPU:
    3090 RTX / 1080Ti
    SLI testing with AB ✔
     
  19. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    14,941
    Likes Received:
    2,090
    The only broken thing in this context is your knowledge. Fan control for _propriertary_ fan controllers like iCX will NEVER work in MSI AB or any other software that rely on NVIDIA's official fan control implementation. No need to continue it here.
     
  20. slayer6288

    slayer6288 Active Member

    Messages:
    84
    Likes Received:
    26
    GPU:
    2080 TI
    anyone else have a fan issue with the 3090 fe and afterburner? the fan curve does not work and if I manually set the speed to say like 90% it will go down to like 75% after a few and so forth say like I set it to 80% it will go to 71% after a while it refuses to hold what I set it at
     
  21. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    14,941
    Likes Received:
    2,090

Share This Page