Overclock.net › Forums › Graphics Cards › AMD/ATI › Hawaii Bios Editing ( 290 / 290X / 295X2 / 390 / 390X )
New Posts  All Forums:Forum Nav:

Hawaii Bios Editing ( 290 / 290X / 295X2 / 390 / 390X ) - Page 186

post #1851 of 3729
Quote:
Originally Posted by gupsterg View Post


Your i2cdump has both cards, both show no VDDC only offset, no VDDCI only offset but both have the -6.25mV VDDC & VDDCI offset, I reckon it's from the "memory" of IR3567B after viewing your posted VoltageObjectInfo for 1 card.

eh that explains what I just saw @ lunch time after flashing the modded bios for testing.

With the original bios I had dpm0 @ 0.968v which GPU-Z read as 0.968v! it matched.

With the modded bios I have dpm0 @ 0.962 which GPU-Z read as 0.954v, -6.25mv !

I'm wondering if the offset is being applied in the original bios at all, because gpu-z did not read -6.25mv with that bios. But with the modded bios it does read -6.25mv



How did you went about your "mod stage 1" ?

In the tutorial, in the cases where the offset is in the chip it self, you only say:
Quote:
2. Take into account the offset when doing voltage changes in powerplay table.
post #1852 of 3729
also, stage mod 3 sounds like a good thing to do and the probable cause of blackscreens. Will do smile.gif thx


1140mhz without any aditional vddc is very impressive to me. Very good card you have there!
Edited by spyshagg - 2/12/16 at 7:52am
post #1853 of 3729
Quote:
Originally Posted by gupsterg View Post

@xAcid9

Hmmm, TBH no idea why you have stuck sensor. I doubt the ROM or an option in it is cause of stuck sensor, but we have not been looking into this kind of thing.
Ok thanks, not really bothered by it since the card is stable but i need accurate information if i really want to push this card. biggrin.gif

Wut? I thought i posted this in 290s owner thread.
post #1854 of 3729
@gupsterg So the rom that you fixed for my lightning works flawlessly.
Once again thank you. thumb.gif

I have a question, in another ROM, after pasting the MC timings, I search for the text string 'gop', but it appears the ROM doesn't have it. What should I do..? redface.gif
post #1855 of 3729
Thread Starter 
@spyshagg
Quote:
I'm wondering if the offset is being applied in the original bios at all, because gpu-z did not read -6.25mv with that bios. But with the modded bios it does read -6.25mv

Software reading is inaccurate, for example even with -6.25mV on VDDCI with both my cards VDDCI in GPU-Z is 1.000V. Once offset removed it's still 1.000V but I could see differing VDDC at DPM 0 in monitoring. Also I get slightly differing readings between HWiNFO & GPU-Z.

Only way to truly know is see i2cdump & voltageobjectinfo.

Just as another bit of info I was reading buildzoid's blog and when he measured MVDDC (memory voltage) at idle it's 1.5V but under load can droop to 1.4xxV (readings taken by DMM.
Quote:
How did you went about your "mod stage 1" ?

In the tutorial, in the cases where the offset is in the chip it self, you only say:
Quote:

2. Take into account the offset when doing voltage changes in powerplay table.

Mod stage 1 I have done by editing VoltageObjectInfo, as only cracked coding this couple weeks ago.

At the time of writing tutorial in OP / quoted text from there:-

a) I was unaware of this extra dual voltage offset in memory of IR3567B (register 26)
b) it was written in the context of VDDC only offset in memory of IR3567B (register 8D)

You may have seen post on page 135. How The Stilt has got +25mV VDDC & -6.25mV VDDCI for my card is:-

Register 26 = -6.25mV VDDC & VDDCI
Register 8D = +31.25 mV VDDC
Register 8E = 0mV VDDCI

(from i2cdump in that post, register = also offset location in i2cdump)

Thus complete outcome = +25mV VDDC & -6.25mV VDDCI smile.gif .

At the moment putting a tutorial regarding VoltageObjectInfo is dangerous IMO, firstly people can remove/change:-

i) VDDCR limit (OCP) ie max VDDC settable
ii) VDDCI limit
iii) meddle with voltage offsets
iv) switching frequency of VRM
v) Load Line calibration ie VDROOP between set VID & drooped/read VDDC

So you can see from above why The Stilt didn't wish to go into revealing VoltageObjectInfo "stuff" plus NDA.

Mod stage 3 helped me with my Vapor-X and is helping with Tri-X, it will also aid desktop use not going to MAX RAM clock, etc, so defo plus in my book to do.

Yep really enjoying the Tri-X 290, done over 12hrs continuous f@h at mod stage 3 now. Tonight gonna do 390MC+RAM timings mod, then next stage will be use the latest official bios I have for that card to see if it gain anything. Finally will also try a 390 ROM with mods, as I couldn't with Vapor-X 290X. Due to the custom PCB, on every attempt just blackscreening with a 390X ROM, even if made it more "compatible".

Hoping to add a good result to the nVida Vs AMD fanboy compo smile.gif .

@xAcid9

No worries posting question here smile.gif . Do post in owners club as well to see if another has experienced this issue and perhaps they may state how resolved. That thread gonna have more subscribers / viewers that maybe able to share something.

@rt123

No worries smile.gif , glad your happy and getting boost, thanks for feedback thumb.gif .

Any chance of some performance stats between stock vs 390MC versions? when you have time smile.gif.

You Samsung IC owners are rare plus Lightning drool.gif .

In a non UEFI ROM you won't find GOP, you'd still have to "adjust" ROM to make HD7xxx Series UEFI Patch Tool BETA fix checksum / keep to correct size of ROM.

I just did a non UEFI 390MC mod for a Sapphire forum member. Due to VRAM_Info being larger than the stock one, I removed length 47h bytes at end of ROM. (Anyone else reading this, other edits were done as per info in OP regarding 390MC mod)

Depending on size of unknown area in ROM/data/command tables I can't state to you where a non UEFI ends data wise exactly. I can only tell by viewing ROM or having tables list for ROM.

You see after all those "elements" end, it's padded out to 10000 (ie last byte of data is FFFF) by empty data. When flashed and dumped it will become length 20000 (ie last byte is 1FFFF), again padded out (ie 00 or FF in this context). If working on a dumped ROM you can just trim off 47h bytes in the context of what I did for the Sapphire member. If a size reduction occurred due to mod you can add empty bytes to correct size.

Just as added info, in UEFI ROM the module will begin at 10000 and after it's data ends it's padded out to 20000 (ie 1FFFF is last byte data wise).

I hope I make sense with my explanation redface.gif , I will add to OP if it did?
Edited by gupsterg - 2/12/16 at 12:18pm
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 #1856 of 3729
Can modify my bios so my 290 Vapor X will run at 300 mhz mem on idle instead of 150 mhz?

If you can reply and I'll upload my bios. Thank you!
post #1857 of 3729
Thread Starter 
I will add info using hawaiireader for mods in OP this weekend.

I hope this help you for now smile.gif .



Save file after modding and flash to one ROM position only on card so you have other ROM position as backup.
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 #1858 of 3729
Quote:
Originally Posted by gupsterg View Post

@Samuris Try these, I have double checked smile.gif .
Final_MLU_390MC_75_80.zip 198k .zip file
ID in MLU differs from whatever ROM you had on your card before, therefore windows will recognise and reinstallation of driver occur.
Aux Voltage = VDDCI , this voltage aids memory controller, it can help stabilise higher RAM clocks on card but do not increase excessively.
These ROMs have limit of voltages, maximum GPU VDDC 1.36875V, VDDCI 1.14375V, regardless if you manually set voltage or up offset it will not exceed limits.

I used this rom since i was'nt able to do the 390MC on the MLU myself, i succesfully edited the +75mV offset to +0mV, and lowered the 1075mhz clock to 1000 and after that i wanted to try the Stilt's memory timing from 1126-1250 all the way to 1501-1625 strap.

But i have a question, both "M75P_390MC_V1" and the original "M50P" roms use the stilt's timing on the 1126-1250 and 1251-1375 straps but for higher straps, the stilt's rom use the stock timing but not in your modded rom, what are those timing ?

post #1859 of 3729
Thread Starter 
Quote:
Originally Posted by eucalyptux View Post

your modded rom, what are those timing ?

Stock AFR 1250MHz placed in 1500 & 1625 smile.gif , these for me and many other members gives a boost.

You see my Vapor-X 290X would start artifacting at desktop/idle, if I was using Stilts timings in 1500MHz strap with RAM clock ~1440MHz IIRC. Only the stock 1250MHz (or lower strap timings) will start pulling ahead on performance vs Stilts timings after say RAM clock 1375MHz.
Quote:
Originally Posted by eucalyptux View Post


One thing I'm not aware of and you should ask @OneB1t, is if a ROM has 2 RAM IC support (like many do) is hawaiireader able to tell which supported IC is active so you are modifying timings for that?

Great to read your modding ROMs thumb.gif .
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 #1860 of 3729
@gupsterg Ok thanks, i finished my rom and going to test that for a few days smile.gif


I was talking with @Samuris via MP and we can't find the "visible AB offset" in his rom based on 290_HYNIX_MOD_V1.7, if someone know where to found this value in the hex editor
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: AMD/ATI
Overclock.net › Forums › Graphics Cards › AMD/ATI › Hawaii Bios Editing ( 290 / 290X / 295X2 / 390 / 390X )