Overclock.net › Forums › Graphics Cards › AMD/ATI › Fiji Bios Editing ( Fury / Fury X / Nano / Radeon Pro Duo )
New Posts  All Forums:Forum Nav:

Fiji Bios Editing ( Fury / Fury X / Nano / Radeon Pro Duo ) - Page 126

post #1251 of 1773
Quote:
Originally Posted by gupsterg View Post

Use HWiNFO smile.gif .
In Nano PowerPlay VRM temp limit is lower than Fury/X, view data table below (soon to be added to OP smile.gif ).





Above table needs some tweaking for Fury Strix. IR3567B is dual output with 6+2 phases, now as there are 10 GPU phases and 2 HBM phases some doubling is going on. I would assume the HBM is sitting on the 2 phases of output loop 2 due to a few reasons. So if it's 5 phases out of the 6 doubled to make 10 the IR3567B OCP for loop 1 would kick in at 310A.

I have now got OCP/VR_Hot/OTP/OVP/UVP tuning capabilities via bios mod biggrin.gif .
In the context of HBM, I have 3 smile.gif and maybe more tongue.gif to support my view.

My results on HBM OC+Tmod , then jearly410 data and finally StenioMoreira.

HWiNFO says that VRM VDD temp is below ambient, not sure if this a delta temperature... GPU VR VDDC Temp is in the mid 60's. The clocks were jumping around in the Geekbench4 compute, however I was able to run GPUPI at the same settings without any clock fluctuations. On thing I noticed is that Geekbench takes around 40/50watts of gpu core power, however gpupi goes above 100W and the clock is stable. Unigine heaven also runs fine and takes up to 250W gpu core power and everything is fine... I'm kinda puzzled... :|

(I even ran gpupi at 1145MHz with a small voltage bump ( stayed at around 1.21/22 under load+fans at 50%) no problems at all)
post #1252 of 1773
Thread Starter 
VRM temps are not delta of temperature in HWiNFO, if you are getting below ambient temperature reading on a VRM then either HWiNFO has an issue on the Strix or the sensor is malfunctioning IMO.

Post a screen shot of your HWiNFO sensors window and perhaps another Strix owner will share theirs.
The Stilt Machine
(14 items)
 
XPS - i5 4690K
(12 items)
 
XPS - Q6600
(8 items)
 
CPUMotherboardGraphicsRAM
Ryzen 7 1700 Asus Crosshair VI Hero Sapphire Fury X@1145/545 G.Skill Trident Z 2x 8GB 3200MHz C14 
Hard DriveCoolingCoolingCooling
Samsung Evo 840 ThermalRight Archon IB-E X2 + 2x TY143 ThermalRight TY-143 2x front case intake Arctic Cooling F12 + 2x F9 as rear case exhaust 
OSMonitorKeyboardPower
Win 7 Pro x64 / Win 10 Pro x64 Asus MG279Q Cherry MX-Board 3.0 Cooler Master V850 
CaseMouse
SilverStone TJ06 Logitech G700S 
CPUMotherboardGraphicsRAM
i5 4690K@4.9GHz 1.255V Asus Maximus VII Ranger Sapphire Fury X@1145/545 HyperX Savage 2x8GB 2400MHz C11 
Hard DriveCoolingOSMonitor
Samsung Evo 840 TR Archon SB-E X2 Win 7 Pro x64 / Win 10 x64 Asus MG279Q 
KeyboardPowerCaseMouse
Cherry MX-Board 3.0 Cooler Master V850 SilverStone TJ06 Logitech G700S 
CPUMotherboardGraphicsRAM
Intel Q6600 G0 Asus P5K Premium Black Pearl Sapphire Toxic HD5850 Corsair Dominator 4GB 
Hard DriveCoolingOSPower
Crucial MX 100 256GB TR TRUE Rev.A Win 7 Pro x64 Cooler Master V650 
  hide details  
Reply
The Stilt Machine
(14 items)
 
XPS - i5 4690K
(12 items)
 
XPS - Q6600
(8 items)
 
CPUMotherboardGraphicsRAM
Ryzen 7 1700 Asus Crosshair VI Hero Sapphire Fury X@1145/545 G.Skill Trident Z 2x 8GB 3200MHz C14 
Hard DriveCoolingCoolingCooling
Samsung Evo 840 ThermalRight Archon IB-E X2 + 2x TY143 ThermalRight TY-143 2x front case intake Arctic Cooling F12 + 2x F9 as rear case exhaust 
OSMonitorKeyboardPower
Win 7 Pro x64 / Win 10 Pro x64 Asus MG279Q Cherry MX-Board 3.0 Cooler Master V850 
CaseMouse
SilverStone TJ06 Logitech G700S 
CPUMotherboardGraphicsRAM
i5 4690K@4.9GHz 1.255V Asus Maximus VII Ranger Sapphire Fury X@1145/545 HyperX Savage 2x8GB 2400MHz C11 
Hard DriveCoolingOSMonitor
Samsung Evo 840 TR Archon SB-E X2 Win 7 Pro x64 / Win 10 x64 Asus MG279Q 
KeyboardPowerCaseMouse
Cherry MX-Board 3.0 Cooler Master V850 SilverStone TJ06 Logitech G700S 
CPUMotherboardGraphicsRAM
Intel Q6600 G0 Asus P5K Premium Black Pearl Sapphire Toxic HD5850 Corsair Dominator 4GB 
Hard DriveCoolingOSPower
Crucial MX 100 256GB TR TRUE Rev.A Win 7 Pro x64 Cooler Master V650 
  hide details  
Reply
post #1253 of 1773
Update on things I should have probably mentioned on my previous posts and that is that anything higher than (12 hex) would cause my card to shutoff, clearly power limitations at 72V+ core(8d 00 12) While the shutoffs came much sooner when my bios had power limits of 450TD/ 450A/450W . Once I tried 499/499/499 instead, stability increased and time before shutdown tripled, yet it would still shut down. Temps of the VRM would have to be kept very low, in order to make use of anything over 72v/(12hex)
post #1254 of 1773
Quote:
Originally Posted by gupsterg View Post

Use HWiNFO smile.gif .
In Nano PowerPlay VRM temp limit is lower than Fury/X, view data table below (soon to be added to OP smile.gif ).





Above table needs some tweaking for Fury Strix. IR3567B is dual output with 6+2 phases, now as there are 10 GPU phases and 2 HBM phases some doubling is going on. I would assume the HBM is sitting on the 2 phases of output loop 2 due to a few reasons. So if it's 5 phases out of the 6 doubled to make 10 the IR3567B OCP for loop 1 would kick in at 310A.

I have now got OCP/VR_Hot/OTP/OVP/UVP tuning capabilities via bios mod biggrin.gif .
In the context of HBM, I have 3 smile.gif and maybe more tongue.gif to support my view.

My results on HBM OC+Tmod , then jearly410 data and finally StenioMoreira.

Fascinating stuff this! Is there any way to mod the Nano bios to stop it throttling back at 98 degrees on the VR VDDC and VDD temps? Maybe push it up a bit safely? Im only touching 78 degrees on the core when it throttles because of the VRMs frown.gif
post #1255 of 1773
Thread Starter 
Yeah, defo interesting data, been after cracking it for a while smile.gif.

Yes, I can increase the VR_VDDC temp limit in PowerPlay using hex editor.

I'm still learning about "things" so can not say to you how it would effect output capability of VRM due to increased temps. As temp increases VRM can output less. Nano only has 4 phases Vs 6 on Fury/X ref PCB.

As long as you are willing to accept risk then I'm willing to do the mod smile.gif .

The VRM power figures we see in HWiNFO are definitely wrong frown.gif . The OCP limit data we see now clearly shows this wink.gif . The Stilt had stated this when I was discussing in PM about negative scaling, I didn't wanna think it was so but it is redface.gif . The Stilt did not give info on table/how to translate registers, due to NDA. I worked on registers and then a member from another forum verified it and explained some bits smile.gif .

Mumak stated in PM what we see in HWiNFO is what the driver is showing to it, so not HWiNFO issue.

Only way to truly know what power card is using is via equipment. HWiNFO data in this context is just useful to compare say delta change in power reading between say stock vs an oc. Still unsure how accurate this would be.
Edited by gupsterg - 9/28/16 at 1:24am
The Stilt Machine
(14 items)
 
XPS - i5 4690K
(12 items)
 
XPS - Q6600
(8 items)
 
CPUMotherboardGraphicsRAM
Ryzen 7 1700 Asus Crosshair VI Hero Sapphire Fury X@1145/545 G.Skill Trident Z 2x 8GB 3200MHz C14 
Hard DriveCoolingCoolingCooling
Samsung Evo 840 ThermalRight Archon IB-E X2 + 2x TY143 ThermalRight TY-143 2x front case intake Arctic Cooling F12 + 2x F9 as rear case exhaust 
OSMonitorKeyboardPower
Win 7 Pro x64 / Win 10 Pro x64 Asus MG279Q Cherry MX-Board 3.0 Cooler Master V850 
CaseMouse
SilverStone TJ06 Logitech G700S 
CPUMotherboardGraphicsRAM
i5 4690K@4.9GHz 1.255V Asus Maximus VII Ranger Sapphire Fury X@1145/545 HyperX Savage 2x8GB 2400MHz C11 
Hard DriveCoolingOSMonitor
Samsung Evo 840 TR Archon SB-E X2 Win 7 Pro x64 / Win 10 x64 Asus MG279Q 
KeyboardPowerCaseMouse
Cherry MX-Board 3.0 Cooler Master V850 SilverStone TJ06 Logitech G700S 
CPUMotherboardGraphicsRAM
Intel Q6600 G0 Asus P5K Premium Black Pearl Sapphire Toxic HD5850 Corsair Dominator 4GB 
Hard DriveCoolingOSPower
Crucial MX 100 256GB TR TRUE Rev.A Win 7 Pro x64 Cooler Master V650 
  hide details  
Reply
The Stilt Machine
(14 items)
 
XPS - i5 4690K
(12 items)
 
XPS - Q6600
(8 items)
 
CPUMotherboardGraphicsRAM
Ryzen 7 1700 Asus Crosshair VI Hero Sapphire Fury X@1145/545 G.Skill Trident Z 2x 8GB 3200MHz C14 
Hard DriveCoolingCoolingCooling
Samsung Evo 840 ThermalRight Archon IB-E X2 + 2x TY143 ThermalRight TY-143 2x front case intake Arctic Cooling F12 + 2x F9 as rear case exhaust 
OSMonitorKeyboardPower
Win 7 Pro x64 / Win 10 Pro x64 Asus MG279Q Cherry MX-Board 3.0 Cooler Master V850 
CaseMouse
SilverStone TJ06 Logitech G700S 
CPUMotherboardGraphicsRAM
i5 4690K@4.9GHz 1.255V Asus Maximus VII Ranger Sapphire Fury X@1145/545 HyperX Savage 2x8GB 2400MHz C11 
Hard DriveCoolingOSMonitor
Samsung Evo 840 TR Archon SB-E X2 Win 7 Pro x64 / Win 10 x64 Asus MG279Q 
KeyboardPowerCaseMouse
Cherry MX-Board 3.0 Cooler Master V850 SilverStone TJ06 Logitech G700S 
CPUMotherboardGraphicsRAM
Intel Q6600 G0 Asus P5K Premium Black Pearl Sapphire Toxic HD5850 Corsair Dominator 4GB 
Hard DriveCoolingOSPower
Crucial MX 100 256GB TR TRUE Rev.A Win 7 Pro x64 Cooler Master V650 
  hide details  
Reply
post #1256 of 1773
Hey guys. I've recently just bought a Fury X and was playing around with overclocking it within means of it being a brand new card and I just wanted to share that I have managed my clocks to 1105/523 with a voltage increase of just 24mv with Sapphire Trixx and I think that its working out great. I'm able to play Fallout 4 with pretty few significant drops in frames and the temp of the GPU is topping out at around 36* celsius. This is a great little card. I guess if I would ask a question it would be, is there any more true performance for gaming to be had past this point for the Fury X? I'm completely satisfied with the current performance that I'm seeing, I'm just curious. smile.gif
post #1257 of 1773
Quote:
Originally Posted by gupsterg View Post

Yeah, defo interesting data, been after cracking it for a while smile.gif.

Yes, I can increase the VR_VDDC temp limit in PowerPlay using hex editor.

I'm still learning about "things" so can not say to you how it would effect output capability of VRM due to increased temps. As temp increases VRM can output less. Nano only has 4 phases Vs 6 on Fury/X ref PCB.

As long as you are willing to accept risk then I'm willing to do the mod smile.gif .

The VRM power figures we see in HWiNFO are definitely wrong frown.gif . The OCP limit data we see now clearly shows this wink.gif . The Stilt had stated this when I was discussing in PM about negative scaling, I didn't wanna think it was so but it is redface.gif . The Stilt did not give info on table/how to translate registers, due to NDA. I worked on registers and then a member from another forum verified it and explained some bits smile.gif .

Mumak stated in PM what we see in HWiNFO is what the driver is showing to it, so not HWiNFO issue.

Only way to truly know what power card is using is via equipment. HWiNFO data in this context is just useful to compare say delta change in power reading between say stock vs an oc. Still unsure how accurate this would be.

Very interesting posts Gupsterg.

Thanks for the shares.

REP +1
post #1258 of 1773
Quote:
Originally Posted by gupsterg View Post

VRM temps are not delta of temperature in HWiNFO, if you are getting below ambient temperature reading on a VRM then either HWiNFO has an issue on the Strix or the sensor is malfunctioning IMO.

Post a screen shot of your HWiNFO sensors window and perhaps another Strix owner will share theirs.

I would appreciate if someone could stress a strix to compare VRM temps, mine are below ambient at idle. This screen was taken after 30mins of 1080p unigine heaven extreme @1050MHz 150% Power Target on stock vcore. The card is unlocked to 4096 shaders.

post #1259 of 1773
Quote:
Originally Posted by gupsterg View Post

Yeah, defo interesting data, been after cracking it for a while smile.gif.

Yes, I can increase the VR_VDDC temp limit in PowerPlay using hex editor.

I'm still learning about "things" so can not say to you how it would effect output capability of VRM due to increased temps. As temp increases VRM can output less. Nano only has 4 phases Vs 6 on Fury/X ref PCB.

As long as you are willing to accept risk then I'm willing to do the mod smile.gif .

The VRM power figures we see in HWiNFO are definitely wrong frown.gif . The OCP limit data we see now clearly shows this wink.gif . The Stilt had stated this when I was discussing in PM about negative scaling, I didn't wanna think it was so but it is redface.gif . The Stilt did not give info on table/how to translate registers, due to NDA. I worked on registers and then a member from another forum verified it and explained some bits smile.gif .

Mumak stated in PM what we see in HWiNFO is what the driver is showing to it, so not HWiNFO issue.

Only way to truly know what power card is using is via equipment. HWiNFO data in this context is just useful to compare say delta change in power reading between say stock vs an oc. Still unsure how accurate this would be.

Absolutely - Would bumping the temp limt up to 110 degrees on the VRMs be safe for the Nano you reckon? Of course I accept any and all risk when flashing my card with these modded bioses, you're doing me a favour! haha biggrin.gif
post #1260 of 1773
Hi can someone help me how to undervolt Fury to -125mv or -150mv thx in advance
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: AMD/ATI
Overclock.net › Forums › Graphics Cards › AMD/ATI › Fiji Bios Editing ( Fury / Fury X / Nano / Radeon Pro Duo )