Precision X + Afterburner?

Discussion in 'MSI AfterBurner Overclock Application Discussion' started by Kol12, Apr 21, 2018.

  1. Kol12

    Kol12 Member

    Messages:
    22
    Likes Received:
    0
    GPU:
    EVGA 1080 Ti FTW3
    Does anybody know whether running the two software's together can create any sort of issues? Both are reading sensor and performance data from the GPU in real time and I wonder whether that could cause issues.
     
  2. JonasBeckman

    JonasBeckman Ancient Guru

    Messages:
    14,138
    Likes Received:
    479
    GPU:
    Sapphire Vega Pulse
    Multiple monitoring software running together can conflict a bit as they attach and hook into programs though I can't really say as to how things look for the display driver or GPU being polled or queried though I don't think it's as problematic since other software can do the same while Afterburner is running.

    That said since they do much the same thing only with EVGA Precision X being exclusive to EVGA GPU's is there a point to having both running together?

    EDIT: Differs depending on software too, Afterburner and Rivatuner have a number of compatibility options as well which can aid with different programs and improve compatibility whether it's some game, some client such as Steam and it's overlay or injectors like monitoring software or something like ReShade. :)
     
  3. Kol12

    Kol12 Member

    Messages:
    22
    Likes Received:
    0
    GPU:
    EVGA 1080 Ti FTW3
    Precision X has some unique features for EVGA graphics cards like monitoring the iCX sensors and a few others. I had previously been using Precision X for overclocking my GPU and Afterburner for the OSD and screenshots, so both were running together. Precision X has always presented problems though so with this clean Windows installation I am considering shifting my overclocking and fan control/curves exclusively to Afterburner. There is nothing that I would seriously miss in Precision X but it is required for the RGB light control of the graphics card. This however is now handled by a separate program called LED Sync. As far as I know LED Sync comes as part of the Precision X installation though. I can see that I can open LED Sync independently of Precision X for RGB control. This means I should only need to open LED Sync for lighting changes and try can overclocking my card exclusively with MSI Afterburner! :)
     
  4. JonasBeckman

    JonasBeckman Ancient Guru

    Messages:
    14,138
    Likes Received:
    479
    GPU:
    Sapphire Vega Pulse
    Ah right that would be why the sensor types and support for some of these hardware parts. Of course. :)

    Interesting to hear it being bundled with this software instead of offered as a separate program for just managing the LED feature but I can see why you would want to use both in this case.
    Well if it is possible to keep EVGA Precision X to a more minimal interaction with software that should work though it is also fully possible both can work together as long as they don't try overriding more advanced functionality for the GPU.

    Conflicts during software start up as various hooks and such are initialized would mostly just lead to a crash at most or possibly not having the overlay show up so that's not too problematic, GPU clock states, fan profiles and voltage however that could require more care but you probably know that already and functionality for this usually has to be enabled before it's active so it shouldn't be a issue if Afterburner can handle this part of the GPU itself.
     

  5. Kol12

    Kol12 Member

    Messages:
    22
    Likes Received:
    0
    GPU:
    EVGA 1080 Ti FTW3
    I never experienced anything majorly obvious when running both Precision X and MSI Afterburner together but you never know what might be happening in the background. I think I recall the overclock I set in Precision X was mirrored in MSI Afterburner so maybe Afterburner has the ability to adapt to Precision X or other overclock programs.. At the end of the day these programs are all trying to poll the hardware at the same time, maybe sometimes that's ok and as you say just look out for anything obvious that might indicate a conflict.
     
  6. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    13,375
    Likes Received:
    399
    iCX sensors monitoring (but not async fans control) is supported since v4.4.0 beta 10 for some EVGA cards. Supported cards are listed here:

    https://forums.guru3d.com/threads/rtss-6-7-0-beta-1.412822/page-22#post-5436964

    Support is implemented via third-party hardware database, so third party voltage control mode must be selected in AB compatibility properties to activate it.
     
  7. Kol12

    Kol12 Member

    Messages:
    22
    Likes Received:
    0
    GPU:
    EVGA 1080 Ti FTW3
    Where are the options to monitor iCX sensors? I think there are 2-3 memory sensors and around 4 power sensors...

    Is there any possibility for conflict when multiple programs are reading/monitoring the iCX sensors or even GPU sensors in general? I don't have much choice but to run EVGA Precision X for the fan control but I much prefer MSI Afterburner's OSD. I also tend to run HWiNFO during gaming and benchmarking.
     
  8. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    13,375
    Likes Received:
    399
    If "third party" voltage control mode is selected in "General" application properties and the card is one of supported iCX models (listed in the link in the previous tab) then all 9 iCX sensors should automatically became available in the list of active monitoring graphs in "Monitoring" application properties.

    In general case - yes, multiple applications accessing hardware directly may conflict due to unsynchronized low-level access to hardware. But in modern software world developers of hardware monitoring solutions try to add common hardware access synchronization mechanisms in order to avoid such cases. And in case of NVIDIA GPUs, the days of low-level access to NVIDIA GPUs are in the past, today everyone rely on official NVAPI, which has its own internal synchronization mechanisms. So I'd say that the chances of conflict are close to zero if we're talking about multiple modern tools monitoring NVIDIA GPU.
     
    Kol12 likes this.
  9. Kol12

    Kol12 Member

    Messages:
    22
    Likes Received:
    0
    GPU:
    EVGA 1080 Ti FTW3
    I see, got it. ;)

    Thanks very much for sharing that, so very well summed up. I should do some reading on NVAPI. :)
     
    Last edited: Apr 25, 2018
  10. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    13,375
    Likes Received:
    399
    It means that hardware is accessed directly, bypassing hardware manufacturer's driver API.
     

Share This Page