Jump to content
AIDA64 Discussion Forum

Recommended Posts

Hi!

I've been using AIDA64 for a some years now and I've put a lot of work in my panel - I really appreciate the support you put into AIDA64!

One thing I'd like to add to my panel is the reason for the current limit for the GPU. GPU-Z, EVGA Precision X and MSI Afterburner all have indicators to report the cause for throttling as "Power limit", "Voltage limit", "Temperature limit" or "No Load Limit". I guess these values are available through the nvidia API. I guess the best would be to 4 different sensor values for each of those, each of them being 0 or 1. 

I'd then be able to add a kind of "LED indicator" for each of those states to my panel: 

IMG_0072.thumb.PNG.08bfaa7f2952fea38656b200fc040a63.PNG

 

Is that something you'd consider to add to AIDA64?

Share this post


Link to post
Share on other sites

We will look into it after the rollout of the next AIDA64 stable update, which is due next week ;)

Share this post


Link to post
Share on other sites

We haven't yet found a way to detect those states.  We'll also need to find out how to integrate them in the existing AIDA64 hardware monitoring module framework, since that one doesn't support yes/no states properly yet. Please give us a bit more time on this ;)

Share this post


Link to post
Share on other sites

Thanks for this status report! Very much appreciated. 

I thought that these values are published in the NVAPI but then you'd have certainly found it yet. Maybe you can contact the guys from GPU-Z, RivaTuner/Afterburner. They show this value, among others. 

For how to integrate it: Either make a single value which could assume discreet values like 0=No limit, 1=Power Limit, 2=Temperature Limit, 3=Voltage limit. That would be fine for me, because I'd use this to create a color indicator (making a big bar which is mostly hidden behind a texture so that you can only see the bar's color through a small hole that makes it look like a small bulb. Then I use the values to change the color of this bar to reflect the different states). 

Of course, you could also create 4 separate simple 0/1 values, but that seems like overkill to me. 

Share this post


Link to post
Share on other sites
On ‎2017‎. ‎05‎. ‎05‎. at 8:41 PM, Grestorn said:

Thanks for this status report! Very much appreciated. 

I thought that these values are published in the NVAPI but then you'd have certainly found it yet. Maybe you can contact the guys from GPU-Z, RivaTuner/Afterburner. They show this value, among others. 

For how to integrate it: Either make a single value which could assume discreet values like 0=No limit, 1=Power Limit, 2=Temperature Limit, 3=Voltage limit. That would be fine for me, because I'd use this to create a color indicator (making a big bar which is mostly hidden behind a texture so that you can only see the bar's color through a small hole that makes it look like a small bulb. Then I use the values to change the color of this bar to reflect the different states). 

Of course, you could also create 4 separate simple 0/1 values, but that seems like overkill to me. 

The problem with the single value is that to my understanding the throttling cause is not reported as an "either", but as a bit field combo, so there's a possible state of power limit + voltage limit in the same time, or even power limit + temperature limit + voltage limit.  So reporting that would either need discreet values -- which would blow up the number of sensor items considerably --, or would require us to report the values as a string (text form).  The latter solution would however make it impossible for you to put indicator LEDs on your panel...

Share this post


Link to post
Share on other sites

Hm, when I look at the graphs of MSI Afterburner, it seems that the bits are actually mutual exclusive. And GPU-Z also displays it as a single state. So it seems even though it's technically represented as a bit field, there's only one bit that can be set at one time (which also would make sense logically). 

I'd just go for a single value with one discreet value for each state. A string wouldn't help me, as you said yourself.

Share this post


Link to post
Share on other sites

We've added the Performance Cap Reason information to the Display / GPU page in the latest beta version of AIDA64 Extreme available at:

https://www.aida64.com/downloads/latesta64xebeta

After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

It can indeed have multiple reasons combined as a bit mask, so it's not trivial how to add that to the existing LCD and SensorPanel modules.  We'll think about it :)

Share this post


Link to post
Share on other sites

Yes, way to go... !!

Can't wait to get this in the Panel. 

In theory, separate indicator values would work well. For a simple "LED" indicator, I'd make create bar elements for each value on to of each other. 0 would make them very small (i.e. invisible) while 1 would make it big enough, so that only one color becomes visible.

This way you could also use a "sliding" indicator, showing the throttling reason over time (similar to GPU-Z's display) by placing a 'graph' element for each value on top of each other. 0 being all the way down and 1 all the to the top. 

Share this post


Link to post
Share on other sites
1 hour ago, Grestorn said:

Yes, way to go... !!

Can't wait to get this in the Panel. 

In theory, separate indicator values would work well. For a simple "LED" indicator, I'd make create bar elements for each value on to of each other. 0 would make them very small (i.e. invisible) while 1 would make it big enough, so that only one color becomes visible.

This way you could also use a "sliding" indicator, showing the throttling reason over time (similar to GPU-Z's display) by placing a 'graph' element for each value on top of each other. 0 being all the way down and 1 all the to the top. 

We don't really want to implement separate indicators.  It would involve adding 48 new sensor items (6 reasons multiplied by 8 GPUs).  We're thinking more in the line of simply returning the reason bit mask as it is passed by ForceWare.  It would work like: a value of 1 means Power Limit, 2 means Temperature Limit, 4 means Reliability Voltage, 16 means Utilization, etc.  A value of 3 would mean Power Limit + Temperature Limit occuring in the same time, and a value of 7 would mean Power Limit + Temperature Limit + Reliability Voltage occuring in the same time.  I'm not sure however how you could define a proper LED colour assignment to make it useful for your purposes.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

  • Similar Content

    • By Charlie
      Hello, I got a NVIDIA Gt 710 card graphic card so when I do the GPGPU benchmark test, it shows in the Single-Precision  around 311.7 GFLOPS, But if you see the GPU specifications in the main window it says 366.0 GFLOPS @ 953 Mhz while running the GPGPU benchmark test.  
      I'm confused with that result,  anyone can tell me why is that ? Thanks.

    • By Mikanoshi
      GTX 1080 and 970 are installed, but second GPU is not visible in Display > GPU:

      I need these values to be available in Sensor Panel:
      GPU2's core frequency, memory freq, core utilization, video utilization, memory utilization and, if possible, fan % (currently it's RPM only)
      dumps.zip
    • By Fiery
      Ever wondered how big the new nVIDIA Pascal GPU family would turn out to be? Here's the whole list of Pascal SKUs, with their respective PCI device IDs. Enjoy!
      Note: The list contains a few Maxwell IDs as well, in order to clarify the difference between GMxxx-A and GMxxx-B PCI device regions.
      Note #2: GM200-B may have been a second iteration, an optimized variant of the original GM200, but never reached the market. Could have been a plan B in case Pascal slips to late 2016 or 2017.
      [...]
      15F0 Graphics Device [GP100GL-A]
      15F1 Graphics Device [GP100GL-A]
      [...]
      1725 Graphics Device [GP100-B]
      172E Graphics Device [GP100-B]
      [...]
      1B6F Graphics Device [GP102-B]
      [...]
      1B80 GeForce GTX 1080 [GP104-A]
      [...]
      1C02 Graphics Device [GP106-A]
      [...]
      1CC2 Graphics Device [GP107-B]
      [...]
      1D01 Graphics Device [GP108-A]
      [...]
       
      Click for the full list of PCI IDs here.
    • By Travis
      ​I have a NVIDIA GeForce GT 520 video card that I've been having nightmarish crash problems with. It's the same problem that thousands of other users are having with the message: "Display Driver NVIDIA Kernel Mode Driver Version xxx.xx (the version number is irrelevant because it changes with every update but nothing ever improves) Stopped Responding And Has Successfully Recovered".  NVIDIA Support, while never giving a definitive fix for this problem, does have a number of troubleshooting suggestions (which thus far have gone nowhere) but one was to obtain AIDA64 Extreme and run a diagnostic on the VRAM in my video card to see if it's good or if it fails. Thus far I have not been able to determine exactly how to do that with AIDA64 and was wondering if someone could give me some guidance here?  I need to run it on the VRAM only and not some other component.  Also, are they referring to a "stress test" as an actual diagnostic, or is there some true diagnostic that will analyze the VRAM and let me know if it has a problem, kind of like MemTest would do for your computer's RAM.  Another suggestion they had was to test the Power Supply Unit (PSU); I think that's a bit of a "red herring" but I'm willing to try; is there a diagnostic test for that in AIDA64 as well?  Thanks and standing by...
×
×
  • Create New...