Quote from elmor on 2021-06-04, 16:46

Quote from hadrien blanchard on 2021-06-04, 16:25

Yo , 

 1st: Very good job for this very practical tools !

 

So I have few question about settings:

 

The uP9512 give me ''only" that sort of setting.

 An no Vout command, so I can t teawk the NVVDC and some other setting.

 

Its due to a lack of uControler support ? or uControler limitation ?

 

 

thanks

Hello, on this controller you can use Voltage Offset from 0 to +150mV only. uP9512 at addr 24 = GPU, addr 25 = MSVDD, addr 26 = memory.

Quote from hadrien blanchard on 2021-06-04, 18:10

The Voltage Offset  setting show no true V increment after set it,

   and internal load balancing, still find its way to auto reduce the Vgpu set (with Xtrem tuner ) in charge.

• The output V you can monitor with your EVC its = the real NVVDC ?
• GPU V reported by GPU Z can be wrong ?
• NVVDD = GPU voltage           GPU Z GPU V sensor is on it ? or it report only the MSVDD ?
• MSVDD= secondary core voltage ?
• Both NVVDD and MSVDD must be changed with Voltage Offset ?

 

I m not subject of thermal or PWR throttling (chiller water H24 / shunt moded / and 1000W bios).

With Xtrem tuner / clasified.exe / or direct Voltage Offset with EVC.

 

Thanks for your help, I m on this problem for day's.

Quote from hadrien blanchard on 2021-06-07, 12:52

Na ? No, no help / clarification ?

 

;(

Quote from elmor on 2021-06-09, 12:09

Quote from hadrien blanchard on 2021-06-04, 18:10

The Voltage Offset  setting show no true V increment after set it,

   and internal load balancing, still find its way to auto reduce the Vgpu set (with Xtrem tuner ) in charge.

• The output V you can monitor with your EVC its = the real NVVDC ?
• GPU V reported by GPU Z can be wrong ?
• NVVDD = GPU voltage           GPU Z GPU V sensor is on it ? or it report only the MSVDD ?
• MSVDD= secondary core voltage ?
• Both NVVDD and MSVDD must be changed with Voltage Offset ?

 

I m not subject of thermal or PWR throttling (chiller water H24 / shunt moded / and 1000W bios).

With Xtrem tuner / clasified.exe / or direct Voltage Offset with EVC.

 

Thanks for your help, I m on this problem for day's.

Hello,

For faster response I suggest you join the Discord channel: https://discord.gg/PAdmwxE

• The output V you can monitor with your EVC its = the real NVVDC ?
  • Yes, it reports actual voltage as measured by the voltage regulator
• GPU V reported by GPU Z can be wrong ?
  • GPU-Z usually only reports the requested VID and not actual voltage
• NVVDD = GPU voltage           GPU Z GPU V sensor is on it ? or it report only the MSVDD ?
  • NVVDD is GPU voltage, correct. I'm not sure if MSVDD is reported by any software.
• MSVDD= secondary core voltage ?
  • Yes, I believe MS means miscellaneous.
• Both NVVDD and MSVDD must be changed with Voltage Offset ?
  • As they're using the same model of voltage regulator they are limited to the same voltage control option

Quote from hadrien blanchard on 2021-06-09, 15:06

Hi

 

 Ok thanks for all this clarification and discord link!

But I prefer to have a discuss here to leave a trace to all the people struggle to figure it out.

 

• GPU V reported by GPU Z can be wrong ?
  • GPU-Z usually only reports the requested VID and not actual voltage

                            So its mean the GPU output V read and modified by your EVC are truly applied to the GPU ? and we shouldn't t care about GPU V of GPU Z ?

 

• Both NVVDD and MSVDD must be changed with Voltage Offset ?
  • As they're using the same model of voltage regulator they are limited to the same voltage control option

                        But did MSVDD must be also modified (with EVC or classified.exe) to increase OC potential and stability ?

 

 

An other thing I don t understand, its:

      - Where came from the automatic throttling of GPU V and it related GPU MHz , even when power and thermal throttling are not hit ? And did we can have a hand to mod / off this thing ? 

 

Thanks for your help, hard to find valuable info and explanation . sharing about that in the web, sadly.

Quote from elmor on 2021-06-11, 22:18

Hello, that's fine.

•  So its mean the GPU output V read and modified by your EVC are truly applied to the GPU ? and we shouldn't t care about GPU V of GPU Z ?
  • Yes in most cases it will report a more accurate value than software. It depends on which specific controller is being used.
• MSVDD must be also modified (with EVC or classified.exe) to increase OC potential and stability ?
  • I think it can help in some cases but I have not spent much time overclocking RTX 3090. I suggest you ask this to someone else, again for example in the Discord channel.
• Where came from the automatic throttling of GPU V and it related GPU MHz , even when power and thermal throttling are not hit ? And did we can have a hand to mod / off this thing ? 
  • I'm sorry but I don't have an answer to this. I assume it's something to do with the Nvidia driver or BIOS and not related to the EVC2 device. If you can provide a screenshot of the GPU-Z sensor tab when this occurs it could help to see what's going on.

Quote from strongislandx on 2023-04-05, 03:39

Quote from hadrien blanchard on 2021-06-04, 16:25

Yo , 

 1st: Very good job for this very practical tools !

 

So I have few question about settings:

 

The uP9512 give me ''only" that sort of setting.

 An no Vout command, so I can t teawk the NVVDC and some other setting.

 

Its due to a lack of uControler support ? or uControler limitation ?

Any solution to be able to apply a fix Vgpu to the card ?

 

thanks 😉

hey thanks for starting the topic.  the 4090 gigabyte has same controller. which points did you connect the evc to.  About to order one even if it can only increase by 150mv, that nice for these cards on water