MSI AB / RTSS development news thread

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.

Great job as always Unwinder!

 

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).

 

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

 

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)

 

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.

 

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.

 

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...

 

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.

 

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?

 

Good job! Unwinder jump to 11:20

 

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.

 

SLI testing with AB ✔

 

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