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 89

post #881 of 1773
Thread Starter 
Quote:
Originally Posted by AndreDVJ View Post

I updated the UEFI GOP with the tool mentioned on the OP but my motherboard still resets CSM to enabled. I believe I did everything to qualify to pure UEFI booting (Windows 10 Pro x64, SSD running a single GPT partition, GOP module with the videocard BIOS, latest motherboard UEFI).

I ran some tests yesterday.

Case 1

If a ROM is non UEFI from factory and we add UEFI/GOP manually or via GOPupd tool, mobo will not post in "pure UEFI" mode (ie Compatibility Support Module = OFF , Secure Boot = ON, Fast Boot = ON). This is due to a signature in the Legacy section, which the UEFI section in ROM will authenticate and it is failing the check.

Case 2

If a ROM is UEFI from factory and we update version of UEFI/GOP in it manually or using GOPupd tool, mobo will post when in "pure UEFI" mode (ie Compatibility Support Module = OFF , Secure Boot = ON, Fast Boot = ON). As the signature in Legacy section is correct to have UEFI, the UEFI can authenticate it.

Case 3

If you modify any factory UEFI ROM or updated factory UEFI ROM manually or using GOPupd and then modify GPU clock, etc mobo will not post when in "pure UEFI" mode (ie Compatibility Support Module = OFF , Secure Boot = ON, Fast Boot = ON). This is due to a signature in the Legacy section, which the UEFI section in ROM will authenticate and it is failing the check as we modified the Legacy section. The Legacy section is where we do all mods like GPU clock, etc.

Other info

In OP heading:-

My Fury Tri-X, Fury X, Nano & Radeon Pro Duo VDDC/MVDDC offset ROM packs and finding offset in rom

The stock ROMs for Fury Tri-X STD/OC , Fury X , Nano and Radeon Pro Duo are factory UEFI ROMs. Only the modded ones in those ROM packs will not work in "pure UEFI" mode.

Signature info

For a while Hawaii bios mod was not possible as OS driver used to ref a signature in ROM. See this post by The Stilt, link.

The OS driver at x point stopped referencing this signature, this signature also is in Fiji bios.

This signature is ref'd by the UEFI/GOP module, which becomes active when we boot mobo in "pure UEFI" mode. If the stock Legacy section has been modified and signature not been updated it will fail authentication. This is what my current testing is inferring, this not only occurs on Fiji but also on Hawaii.
Edited by gupsterg - 6/20/16 at 9:42am
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 #882 of 1773
Quote:
Originally Posted by gupsterg View Post

I ran some tests yesterday.

Case 1

If a ROM is non UEFI from factory and we add UEFI/GOP manually or via GOPupd tool, mobo will not post in "pure UEFI" mode (ie Compatibility Support Module = OFF , Secure Boot = ON, Fast Boot = ON). This is due to a signature in the Legacy section, which the UEFI section in ROM will authenticate and it is failing the check.

Case 2

If a ROM is UEFI from factory and we update version of UEFI/GOP in it manually or using GOPupd tool, mobo will post when in "pure UEFI" mode (ie Compatibility Support Module = OFF , Secure Boot = ON, Fast Boot = ON). As the signature in Legacy section is correct to have UEFI, the UEFI can authenticate it.

Case 3

If you modify any factory UEFI ROM or updated factory UEFI ROM manually or using GOPupd and then modify GPU clock, etc mobo will not post when in "pure UEFI" mode (ie Compatibility Support Module = OFF , Secure Boot = ON, Fast Boot = ON). This is due to a signature in the Legacy section, which the UEFI section in ROM will authenticate and it is failing the check as we modified the Legacy section. The Legacy section is where we do all mods like GPU clock, etc.

Other info

In OP heading:-

My Fury Tri-X, Fury X, Nano & Radeon Pro Duo VDDC/MVDDC offset ROM packs and finding offset in rom

The stock ROMs for Fury Tri-X STD/OC , Fury X , Nano and Radeon Pro Duo are factory UEFI ROMs. Only the modded ones in those ROM packs will not work in "pure UEFI" mode.

Signature info

For a while Hawaii bios mod was not possible as OS driver used to ref a signature in ROM. See this post by The Stilt, link.

The OS driver at x point stopped referencing this signature, this signature also is in Fiji bios.

This signature is ref'd by the UEFI/GOP module, which becomes active when we boot mobo in "pure UEFI" mode. If the stock Legacy section has been modified and signature not been updated it will fail authentication. This is what my current testing is inferring, this not only occurs on Fiji but also on Hawaii.

That was exactly my problem using edited BIOS
post #883 of 1773
Thread Starter 
+rep on confirmation, smile.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 #884 of 1773
Quote:
Originally Posted by AndreDVJ View Post

Well I opened the ticket with Sapphire, though about SKU, there are only two possible for the Tri-X card. 11247-00-40G and 11247-01-40G. Both are the very same card, but the latter comes with that factory overclock which I'd be ashamed of (+40Mhz).

I updated the UEFI GOP with the tool mentioned on the OP but my motherboard still resets CSM to enabled. I believe I did everything to qualify to pure UEFI booting (Windows 10 Pro x64, SSD running a single GPT partition, GOP module with the videocard BIOS, latest motherboard UEFI).

My SKU# is 11247-00-4G, but they kept asking me to confirm my part number ( 299-1E329-000SA) as they acted like they've never seen that part number before.

Anyway Sapphire is acting all cloak and dagger on these BIOS' as make you ask for them instead of just posting them on their website for anyone to download. This is why I'm not so eager to publish them as I don't want to get caught up in their game.

Personally I don't see why these can't be publically published instead of making you go through their red tape of asking for them. Took me two weeks of hounding them before they finally e-mailed the files. No download, strictly e-mail. This is why I say they must be tailored to specific SKU's / Part Numbers. Still...

Oh, and word of advice... don't piss them off by hounding them... they'll make you wait. And it is best to put in a ticket as opposed to e-mailing them. The ticket will get answered quicker, even though they may eventually ask you to e-mail the same info you put in the ticket. Go figure wth.gif
post #885 of 1773
Thread Starter 
Quote:
Originally Posted by sygnus21 View Post

This is why I say they must be tailored to specific SKU's / Part Numbers. Still...

The difference between Sapphire Fury Tri-X STD & OC SKU bios is default GPU clock + FanRPMMax and then the signature/checksum.

I used own a Vapor-X 290X STD and one point, view the label for a OC vs STD.





The PCB used was the same.

I had a STD flashed to OC for a while wink.gif .

The difference between OC vs STD ROM was pretty much only on parameters relating to OC clocks.

So IMO the ROM you gained from Sapphire support is not very much tailored to your SKU/PN/SERIAL tongue.gif .

Glad they've sorted your issue smile.gif , thanks for share wink.gif .
Edited by gupsterg - 6/20/16 at 11:42pm
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 #886 of 1773
Quote:
Originally Posted by sygnus21 View Post

My SKU# is 11247-00-4G, but they kept asking me to confirm my part number ( 299-1E329-000SA) as they acted like they've never seen that part number before.

Anyway Sapphire is acting all cloak and dagger on these BIOS' as make you ask for them instead of just posting them on their website for anyone to download. This is why I'm not so eager to publish them as I don't want to get caught up in their game.

Personally I don't see why these can't be publically published instead of making you go through their red tape of asking for them. Took me two weeks of hounding them before they finally e-mailed the files. No download, strictly e-mail. This is why I say they must be tailored to specific SKU's / Part Numbers. Still...

Oh, and word of advice... don't piss them off by hounding them... they'll make you wait. And it is best to put in a ticket as opposed to e-mailing them. The ticket will get answered quicker, even though they may eventually ask you to e-mail the same info you put in the ticket. Go figure wth.gif

My P/N is 299-1E329-100SA. Googling your specific part number, it belongs to you only. Probably a typo printed in the label.

Is If I flash original BIOS that came with my card, and turn on CSM, the mobo won't even post. The label clearly states UEFI in my box, so that alone would warrant a RMA because the GOP is faulty if they refuses to support me. I am pretty sure they want to avoid all that trouble.

They replied to my ticket in three hours, asking to send an e-mail providing P/N and SKU #. Let's see how my ticket goes.
My rig
(17 items)
 
  
CPUMotherboardGraphicsRAM
Core i7 6700K Gigabyte GA-Z170X-Gaming 5 Sapphire Radeon R9 Fury Tri-X G.Skill Trident Z DDR4 3200Mhz 
Hard DriveHard DriveHard DriveCooling
Samsung SSD 850 PRO Corsair Neutron GTX SSD NVMe Samsung SSD 950 PRO Corsair Hydro H100i GTX 
OSMonitorKeyboardPower
Windows 10 Pro x64 BenQ XL2420T SteelSeries 6Gv2 Thermaltake Thoughpower Grand 850W 
CaseMouseMouse PadAudio
Cooler Master CM690 III Windowed Razer DeathAdder Chroma SteelSeries QCK+ Fnatic Asphalt Edition Asus Xonar DGX 
Other
TP-LINK Archer T9E 
  hide details  
Reply
My rig
(17 items)
 
  
CPUMotherboardGraphicsRAM
Core i7 6700K Gigabyte GA-Z170X-Gaming 5 Sapphire Radeon R9 Fury Tri-X G.Skill Trident Z DDR4 3200Mhz 
Hard DriveHard DriveHard DriveCooling
Samsung SSD 850 PRO Corsair Neutron GTX SSD NVMe Samsung SSD 950 PRO Corsair Hydro H100i GTX 
OSMonitorKeyboardPower
Windows 10 Pro x64 BenQ XL2420T SteelSeries 6Gv2 Thermaltake Thoughpower Grand 850W 
CaseMouseMouse PadAudio
Cooler Master CM690 III Windowed Razer DeathAdder Chroma SteelSeries QCK+ Fnatic Asphalt Edition Asus Xonar DGX 
Other
TP-LINK Archer T9E 
  hide details  
Reply
post #887 of 1773
Quote:
Originally Posted by AndreDVJ View Post

My P/N is 299-1E329-100SA. Googling your specific part number, it belongs to you only. Probably a typo printed in the label.

Is If I flash original BIOS that came with my card, and turn on CSM, the mobo won't even post. The label clearly states UEFI in my box, so that alone would warrant a RMA because the GOP is faulty if they refuses to support me. I am pretty sure they want to avoid all that trouble.

They replied to my ticket in three hours, asking to send an e-mail providing P/N and SKU #. Let's see how my ticket goes.

First, just because you couldn't find something on Google doesn't mean it's true or not. It simple means Google couldn't find your query.

That said. double checking the card's physical label, plus my old RMA with a previous card says this IS a correct part number. My guess is it's probably an production early batch since I bought into the card early... something I truly regret, but that's another story for another time. However that doesn't negate the part numbers stamped on the two different cards I got (my original, and the RMA replacement).

As sent to Sapphire, this is the label off the box, which is the same info on the card's label....



Here's the card (bottom card)....



post #888 of 1773
I honestly don't think so and I believe Sapphire messed up with your card

The earliest production cards (July 2015) have been clocked as 1040Mhz. They put a lame OC label and gone for it.

I bought mine at November, from a store that had it stuck for months while I still was at Australia (Aussies hate AMD cards it seemed there, at least in Sydney).



I don't regret a single bit. It became an air cooled "Fury X" smile.gif

My rig
(17 items)
 
  
CPUMotherboardGraphicsRAM
Core i7 6700K Gigabyte GA-Z170X-Gaming 5 Sapphire Radeon R9 Fury Tri-X G.Skill Trident Z DDR4 3200Mhz 
Hard DriveHard DriveHard DriveCooling
Samsung SSD 850 PRO Corsair Neutron GTX SSD NVMe Samsung SSD 950 PRO Corsair Hydro H100i GTX 
OSMonitorKeyboardPower
Windows 10 Pro x64 BenQ XL2420T SteelSeries 6Gv2 Thermaltake Thoughpower Grand 850W 
CaseMouseMouse PadAudio
Cooler Master CM690 III Windowed Razer DeathAdder Chroma SteelSeries QCK+ Fnatic Asphalt Edition Asus Xonar DGX 
Other
TP-LINK Archer T9E 
  hide details  
Reply
My rig
(17 items)
 
  
CPUMotherboardGraphicsRAM
Core i7 6700K Gigabyte GA-Z170X-Gaming 5 Sapphire Radeon R9 Fury Tri-X G.Skill Trident Z DDR4 3200Mhz 
Hard DriveHard DriveHard DriveCooling
Samsung SSD 850 PRO Corsair Neutron GTX SSD NVMe Samsung SSD 950 PRO Corsair Hydro H100i GTX 
OSMonitorKeyboardPower
Windows 10 Pro x64 BenQ XL2420T SteelSeries 6Gv2 Thermaltake Thoughpower Grand 850W 
CaseMouseMouse PadAudio
Cooler Master CM690 III Windowed Razer DeathAdder Chroma SteelSeries QCK+ Fnatic Asphalt Edition Asus Xonar DGX 
Other
TP-LINK Archer T9E 
  hide details  
Reply
post #889 of 1773
That's fine. All I know is that's the number on the card... and the one Sapphire accepted.

Peace coolsmiley.png
Edited by sygnus21 - 6/21/16 at 12:15pm
post #890 of 1773
Althon replied to my e-mail with "new" BIOS'es. Unsurprisingly they sent me the OC version (1040Mhz) of them.
Code:
299-1E329-100SA/299-1E329-300SA: E1040/M500 OC clock:
Default BIOS: 329P05HU.O5C
Unlock power BIOS: 329P05HU.Q5D

Name: 329P05HU.O5C
   CRC-32: c6fde47b
   MD4: 928dc5ab018b580e96da09d2a6936927
   MD5: 566a8d5e50be4a3684c21bd0ab706a57
   SHA-1: e32f386c6587cb0e749f95e6287797ed6276da5b

Name: 329P05HU.Q5D
   CRC-32: 6df2b417
   MD4: ddce35f15a563018a786db5b15b88cbc
   MD5: 3d9505849dd806501cf8d6de3ed0a6f5
   SHA-1: fd8cb8487ba394fdb644aa58bc6a3d710bc6b1e7


Well these ones are the same I found here a while ago. They have version 1.59 of GOP module.
Code:
Dump Gop Driver Info:
    Machine type code      X64
    Size Of Gop Image      97312 (95 KB)
    GOP Driver Name: AMD GOP X64 Release Driver Rev.1.59.0.0.0.Jun 29 2015.13:03:19
    GOP AMD_Build          202
    GOP AMD_CL             1165960

No complains about, because I can disable CSM and see my mobo reset back to enable. I honestly believe it's a Gigabyte bug.

With 1.58 my mobo won't even post. Originally my Fury card comes with that version.
My rig
(17 items)
 
  
CPUMotherboardGraphicsRAM
Core i7 6700K Gigabyte GA-Z170X-Gaming 5 Sapphire Radeon R9 Fury Tri-X G.Skill Trident Z DDR4 3200Mhz 
Hard DriveHard DriveHard DriveCooling
Samsung SSD 850 PRO Corsair Neutron GTX SSD NVMe Samsung SSD 950 PRO Corsair Hydro H100i GTX 
OSMonitorKeyboardPower
Windows 10 Pro x64 BenQ XL2420T SteelSeries 6Gv2 Thermaltake Thoughpower Grand 850W 
CaseMouseMouse PadAudio
Cooler Master CM690 III Windowed Razer DeathAdder Chroma SteelSeries QCK+ Fnatic Asphalt Edition Asus Xonar DGX 
Other
TP-LINK Archer T9E 
  hide details  
Reply
My rig
(17 items)
 
  
CPUMotherboardGraphicsRAM
Core i7 6700K Gigabyte GA-Z170X-Gaming 5 Sapphire Radeon R9 Fury Tri-X G.Skill Trident Z DDR4 3200Mhz 
Hard DriveHard DriveHard DriveCooling
Samsung SSD 850 PRO Corsair Neutron GTX SSD NVMe Samsung SSD 950 PRO Corsair Hydro H100i GTX 
OSMonitorKeyboardPower
Windows 10 Pro x64 BenQ XL2420T SteelSeries 6Gv2 Thermaltake Thoughpower Grand 850W 
CaseMouseMouse PadAudio
Cooler Master CM690 III Windowed Razer DeathAdder Chroma SteelSeries QCK+ Fnatic Asphalt Edition Asus Xonar DGX 
Other
TP-LINK Archer T9E 
  hide details  
Reply
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 )