Overclock.net › Forums › Graphics Cards › AMD/ATI › ATI Drivers and Overclocking Software › WattTool: A simple tool that combines overclocking with VRM monitoring/tweaking for RX 400 series
New Posts  All Forums:Forum Nav:

WattTool: A simple tool that combines overclocking with VRM monitoring/tweaking for RX 400 series - Page 4

post #31 of 380
Thread Starter 
Quote:
Originally Posted by greytoad View Post

Yeah. my old voltage offset applied there too. Good work though. Any way to make it compatible with HWiNFO64? I can't run that with your tool at the same time or I start getting weird performance results. My Valley score suddenly was 25% lower. Rebooted and used built in tool with my old voltage offset and I was fine. Haven't gone back to your tool as I need mem error reporting for my current testing. I assume that was what caused the problem. If you're not aware of a problem, maybe it's just a fluke. I was running at 1450 at the time. I"m also back to 16.7.2 drivers and embd 1.1r2. embd 1.2 wont load on 16.7.2 for some reason.

Was that happening with VRM monitoring enabled or disabled?
i5 3470 + RX 480
(13 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i5-3470 Gigabyte H77-DS3H AMD Radeon RX 480 2 x 4GB Corsair Vengeance LP DDR3-1600 
Hard DriveHard DriveCoolingOS
128GB Samsung 830 SSD 240GB OCZ Trion 150 SSD Thermalright HR-02 Macho Rev. A (BW) Windows 10 Pro 
MonitorKeyboardPowerCase
Dell U2713HM generic Thermaltake Munic 430W Antec Three Hundred 
Mouse
Roccat Kone Pure Military 
  hide details  
Reply
i5 3470 + RX 480
(13 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i5-3470 Gigabyte H77-DS3H AMD Radeon RX 480 2 x 4GB Corsair Vengeance LP DDR3-1600 
Hard DriveHard DriveCoolingOS
128GB Samsung 830 SSD 240GB OCZ Trion 150 SSD Thermalright HR-02 Macho Rev. A (BW) Windows 10 Pro 
MonitorKeyboardPowerCase
Dell U2713HM generic Thermaltake Munic 430W Antec Three Hundred 
Mouse
Roccat Kone Pure Military 
  hide details  
Reply

Gear mentioned in this thread:

post #32 of 380
Multi Adapter works now as of 0.3. Great Job thumb.gif

Still if you could investigate voltage offset into the negative your tool will be perfect. biggrin.gif
post #33 of 380
Quote:
Originally Posted by BromoL View Post

Was that happening with VRM monitoring enabled or disabled?

Just performance suddenly dropped by about 25percent until I rebooted. Hasn't happened since. I'll try again. Monitoring showed no mis-reported values. I'll try it again with and without monitoring. Maybe it was a fluke or something else I was testing.
post #34 of 380
I just had the performance drop again. It happened when I changed the memory clock in wattmon with i2c on and HWiNfo64 going. I'm running the 16.8.2 driers again now. I lost maybe 50% performance in Valley. I'll reboot. There's an issue with setting memory clocks with the 16.8.2 drivers I've been testing. It could be related.

edit: reboot and it works fine. closing wattmon and HWiNFO64 and valley doesn't fix it.. Whatever is getting stuck, reboot fixes it. Most likely memory clocks are getting stuck at idle.
Edited by greytoad - 8/30/16 at 10:28am
post #35 of 380
Thread Starter 
Quote:
Originally Posted by greytoad View Post

I just had the performance drop again. It happened when I changed the memory clock in wattmon with i2c on and HWiNfo64 going. I'm running the 16.8.2 driers again now. I lost maybe 50% performance in Valley. I'll reboot. There's an issue with setting memory clocks with the 16.8.2 drivers I've been testing. It could be related.

edit: reboot and it works fine. closing wattmon and HWiNFO64 and valley doesn't fix it.. Whatever is getting stuck, reboot fixes it. Most likely memory clocks are getting stuck at idle.

I dont know what HWiNFO, GPU-Z and other tools do in order to synchronize access to the hardware. They use their own drivers and probably agreed to use a global mutex or something like that. I dont participate in anything of that. I fully understand that this is a clear disadvantage of my tool. I also dont have access to documentation of the VRM controller and i have no prior experience in doing this stuff.

I updated to version 0.4. Changes are mostly cosmetics. I disabled VRM monitoring by default. @GrimVandal (and the mining community?) will hopefully enjoy negative voltage offsets up (or down?) to -32 x 6.25 mV = -200 mV. I only tested -6.25 mV shortly to check that VOUT actually drops, which it does.

That made me smile. I am not even advertising the tool. This thread is the only place i am posting stuff.
Edited by BromoL - 8/30/16 at 11:59am
i5 3470 + RX 480
(13 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i5-3470 Gigabyte H77-DS3H AMD Radeon RX 480 2 x 4GB Corsair Vengeance LP DDR3-1600 
Hard DriveHard DriveCoolingOS
128GB Samsung 830 SSD 240GB OCZ Trion 150 SSD Thermalright HR-02 Macho Rev. A (BW) Windows 10 Pro 
MonitorKeyboardPowerCase
Dell U2713HM generic Thermaltake Munic 430W Antec Three Hundred 
Mouse
Roccat Kone Pure Military 
  hide details  
Reply
i5 3470 + RX 480
(13 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i5-3470 Gigabyte H77-DS3H AMD Radeon RX 480 2 x 4GB Corsair Vengeance LP DDR3-1600 
Hard DriveHard DriveCoolingOS
128GB Samsung 830 SSD 240GB OCZ Trion 150 SSD Thermalright HR-02 Macho Rev. A (BW) Windows 10 Pro 
MonitorKeyboardPowerCase
Dell U2713HM generic Thermaltake Munic 430W Antec Three Hundred 
Mouse
Roccat Kone Pure Military 
  hide details  
Reply
post #36 of 380
I like it. I'm going to keep using it. It's way faster reapplying my oc settings. Thanks for your hard work. A minor problem that's fixed with a reboot or simply disabling i2c monitoring isn't a big deal to me. It saves me from converting from hex. That alone might keep me from making a big mistake. Thank you.
post #37 of 380
Quote:
Originally Posted by greytoad View Post

Just performance suddenly dropped by about 25percent until I rebooted. Hasn't happened since. I'll try again. Monitoring showed no mis-reported values. I'll try it again with and without monitoring. Maybe it was a fluke or something else I was testing.

First of all which gpu are you using?

Memory overclocking for RX 470 gpus above 2000 mhz seems to have some issues.
My performance also drops by -25 to -50% if I overclock the memory above 2000.

GPU-Z shows that the card throttles down to 85 watt if you set the memory oc above 2000 memclock.
(which only really the rx 470 nitro 8GB with samsung memory can bet set to = my card)

Very strange behaviour but I assume it is driver related. mad.gif


v 0.4 superb job, awesome tool thumb.gif

You might want to up the negative voltage offset up to 48 x -6.25 (-300 total) biggrin.gif
post #38 of 380
I'm running a rx480. It works fine if I don't to i2p monitoring while doing HWiNFO64 while changing memory clocks from idle p0 state. Last time it happened I was clocking down 5 mhz. Not up. It's a pretty specific problem that can be easily avoided. Not sure if it's related to the problem people have been having getting memory clocks to stick with 16.8.2 I had that problem before doing a clean install of the driver after a ddu. I'd previously done an inplace upgrade and that's when I ran into memory scaling issues. That issue is resolved. So I don't think it's related, but who knows.
Edited by greytoad - 8/30/16 at 7:17pm
post #39 of 380
Quote:
Originally Posted by BromoL View Post

I dont know what HWiNFO, GPU-Z and other tools do in order to synchronize access to the hardware. They use their own drivers and probably agreed to use a global mutex or something like that.

m_mutex=CreateMutex(NULL, FALSE, _T("Global\\Access_ATI_I2C"));
post #40 of 380
Thread Starter 
Quote:
Originally Posted by W1zzard View Post

m_mutex=CreateMutex(NULL, FALSE, _T("Global\\Access_ATI_I2C"));

Thanks, your input is very much appreciated.
Quote:
Originally Posted by greytoad 

It works fine if I don't to i2p monitoring while doing HWiNFO64 while changing memory clocks from idle p0 state. Last time it happened I was clocking down 5 mhz. Not up.

Did you ever had success in changing clocks/voltage for p0 states? I will probably disable the edit controls for GPU/MEM P0 in the next version.
i5 3470 + RX 480
(13 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i5-3470 Gigabyte H77-DS3H AMD Radeon RX 480 2 x 4GB Corsair Vengeance LP DDR3-1600 
Hard DriveHard DriveCoolingOS
128GB Samsung 830 SSD 240GB OCZ Trion 150 SSD Thermalright HR-02 Macho Rev. A (BW) Windows 10 Pro 
MonitorKeyboardPowerCase
Dell U2713HM generic Thermaltake Munic 430W Antec Three Hundred 
Mouse
Roccat Kone Pure Military 
  hide details  
Reply
i5 3470 + RX 480
(13 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i5-3470 Gigabyte H77-DS3H AMD Radeon RX 480 2 x 4GB Corsair Vengeance LP DDR3-1600 
Hard DriveHard DriveCoolingOS
128GB Samsung 830 SSD 240GB OCZ Trion 150 SSD Thermalright HR-02 Macho Rev. A (BW) Windows 10 Pro 
MonitorKeyboardPowerCase
Dell U2713HM generic Thermaltake Munic 430W Antec Three Hundred 
Mouse
Roccat Kone Pure Military 
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home

Gear mentioned in this thread:

Overclock.net › Forums › Graphics Cards › AMD/ATI › ATI Drivers and Overclocking Software › WattTool: A simple tool that combines overclocking with VRM monitoring/tweaking for RX 400 series