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 172

post #1711 of 3620
Quote:
Originally Posted by Enzarch View Post

Yes, these are blackscreens when under load. There isnt a large group of us with this particular problem; where is will blackscreen above a certain voltage threshold, and this problem is greatly exacerbated when running higher refresh rates.
Quote:
Originally Posted by gupsterg View Post



I would assume under load blackscreen would be:-

a) lack of VDDC
b) perhaps RAM / MC just can't cope, so "silicon lottery", perhaps try lower RAM clock
c) upping VDDCI (aka Aux Voltage may help, kizwan has solved his similar issue that way).

If it's still occurring, I'm sorry but got no more ideas redface.gif , perhaps using a differing ROM will help or ask tech support of your card if they have an updated ROM. I have done this twice on 2 Sapphire cards I own/owned. I wasn't having blackscreen but just wanted a newer version of ROM if they had one smile.gif .
I bet you are using Displayport and more than 60Hz refresh rate.
Black-outs(temporary blackscreens) are very usual with these cards. I even experience this on my card.
If you want to get rid of this, you need to lower the volts(and thus lower the cloks) or select 60Hz refresh rate if you are using displayport.
These blackouts are caused by corruprion of digital signal aka....displayport caused by high core volts.
Dont ask me why, I have no idea redface.gif


If anyone knows how to fix it, it would be super cool. I have 144Hz monitor for a reason.....and not that I will use it @60Hz biggrin.gif
post #1712 of 3620
Quote:
Originally Posted by gupsterg View Post

I would assume under load blackscreen would be:-

a) lack of VDDC
b) perhaps RAM / MC just can't cope, so "silicon lottery", perhaps try lower RAM clock
c) upping VDDCI (aka Aux Voltage may help, kizwan has solved his similar issue that way).

If it's still occurring, I'm sorry but got no more ideas redface.gif , perhaps using a differing ROM will help or ask tech support of your card if they have an updated ROM. I have done this twice on 2 Sapphire cards I own/owned. I wasn't having blackscreen but just wanted a newer version of ROM if they had one smile.gif .
Quote:
Originally Posted by fat4l View Post


I bet you are using Displayport and more than 60Hz refresh rate.
Black-outs(temporary blackscreens) are very usual with these cards. I even experience this on my card.
If you want to get rid of this, you need to lower the volts(and thus lower the cloks) or select 60Hz refresh rate if you are using displayport.
These blackouts are caused by corruprion of digital signal aka....displayport caused by high core volts.
Dont ask me why, I have no idea redface.gif


If anyone knows how to fix it, it would be super cool. I have 144Hz monitor for a reason.....and not that I will use it @60Hz biggrin.gif

Sorry, I should have been more thorough in my information

I have been trying to solve this for quite a long time: Purchased Oct. 2013

I have tried dozens of ROMS (if not near 100), none of which have made any impact

VDDCI up or down makes zero difference, this is exclusively a "too much" VDDC equals black-out, which recovers once voltage comes back down

The only thing that ever made a difference (other than changing refresh rate) was changes in early drivers (13.12 era) but these were not very consistent. Once, way back in the day I was able to complete Firestrike @ 1235/1500

A bit more info for those smarter than I, When BS occurs, the scene is still being rendered as normal, you just cant see it; This is evidenced by GPU loads and voltages as well as benchmark scores being unaffected by the black-outs.

This is not just over Displayport, this will happen regardless of DP, DVI, or HDMI. and they show this behavior independent of each other (This can be shown by mirroring display outs, the black-outs per display are unrelated to each other.

DVI can behave a bit differently to the others, by being more stubborn to recover and sometimes corrupting until reboot.

This isnt the biggest problem, particularly now we have other ways to improve performance that aren't just brute force, with you guys awesome guides and so damn much testing and trial and error, I have been able to settle my 290 @ 1080/1350 on a 390x vBIOS with tighter timings and hand made DPM table netting me just under 13000 FS graphics score. But we dont modify, hack, solder, and tweak, just to settle thumb.gif
post #1713 of 3620
Quote:
Originally Posted by fat4l View Post


I bet you are using Displayport and more than 60Hz refresh rate.
Black-outs(temporary blackscreens) are very usual with these cards. I even experience this on my card.
If you want to get rid of this, you need to lower the volts(and thus lower the cloks) or select 60Hz refresh rate if you are using displayport.
These blackouts are caused by corruprion of digital signal aka....displayport caused by high core volts.
Dont ask me why, I have no idea redface.gif


If anyone knows how to fix it, it would be super cool. I have 144Hz monitor for a reason.....and not that I will use it @60Hz biggrin.gif

one of my two cards is now having blackouts with either displayport, hdmi and DVI, all at 60hz.

7 months ago it didn't had this problem (when it was my main card, but now is the secondary on crossfire).

The overclock is not degrading, but this problem is.
post #1714 of 3620
Thread Starter 
Only my experience of DP with high Hz smile.gif , I've had no issues in the same way as you guys.

I have never had a new monitor which I had to swap out due to QA issues upon delivery, 3rd time I was lucky smile.gif . I have a Eizo FG2421, I bought mine early 2015. I had read info about the "lottery" with this screen, just thought it would be sorted as I'd bought so long after launch.

Next I've had 3 differing Hawaii cards since early 2015, Sapphire Tri-X 290 (STD) ref PCB , Asus DCUII 290X (STD) custom PCB and currently Vapor-X 290X (STD) custom PCB.

Only time any of them blackscreen'd has been:-

a) lack of VDDC for clocks set
b) pushed memory too far, on occasions if I added a little more VDDC all was well, other times not; thus thought reached the limit.

If I was in your position @Enzarch I would have RMA'd card after all that you've done, I'm guessing this occurrence has occurred after warranty expired?

Bios modding has been all pretty much performance related, no one has looked into what may be "display output" related AFAIK. But I'm pretty certain all those sections are gonna be pretty much the same between ROMs. This is going by when several times I've done ROM compares from say beginning of data tables to end of command tables. Command tables from what I've seen are the same, it's the data tables that change and TBH its PowerPlay, VRAM_Info and VoltageObjectInfo from what I've noted.

If do see anything or read fix will be sure to post.

I know on the Sapphire forum they have this mantra of suggesting it's PSU related and guide people to go 750W + for even 1x 290/X (I usually rolleyes.gif @ this suggestion). I know I've run f@h for about 24-48hrs continuous at times in my Q6600 rig and gamed many hours without issue. CPU/GPU OC'd and powered by the 650W and no issues.

I've added 390 MC mod to OP, The Stilt highlighted better for higher RAM clocks when originally posted info, perhaps may help, but don't know.

We've all been tightening RAM timings for performance, perhaps loosening them may aid? again don't know, just a suggestion floating in my mind.
Edited by gupsterg - 2/6/16 at 10:08am
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 #1715 of 3620
Woah my mind is blown. The blackouts i get when i overclock really high but don't get high temps or artifacts... Yeah display clock signal coruption makes sense. Maybe when i run high clocks i should just run 60hz over my dvi instead of lightboost 120hz like I'm used to... Or just do vga?

Cuz that's actually what i see, the display gets weird for a microsecond and then goes black. Everything is still going, hell when I've done this in a csgo game and I'd still be in teamspeak talking to my friends while having a black screen that won't come back.
post #1716 of 3620
Quote:
Originally Posted by gupsterg View Post


If I was in your position @Enzarch I would have RMA'd card after all that you've done, I'm guessing this occurrence has occurred after warranty expired?

Bios modding has been all pretty much performance related, no one has looked into what may be "display output" related AFAIK. But I'm pretty certain all those sections are gonna be pretty much the same between ROMs. This is going by when several times I've done ROM compares from say beginning of data tables to end of command tables. Command tables from what I've seen are the same, it's the data tables that change and TBH its PowerPlay, VRAM_Info and VoltageObjectInfo from what I've noted.

If do see anything or read fix will be sure to post.

I know on the Sapphire forum they have this mantra of suggesting it's PSU related and guide people to go 750W + for even 1x 290/X (I usually rolleyes.gif @ this suggestion). I know I've run f@h for about 24-48hrs continuous at times in my Q6600 rig and gamed many hours without issue. CPU/GPU OC'd and powered by the 650W and no issues.

I've added 390 MC mod to OP, The Stilt highlighted better for higher RAM clocks when originally posted info, perhaps may help, but don't know.

We've all been tightening RAM timings for performance, perhaps loosening them may aid? again don't know, just a suggestion floating in my mind.

Card runs perfectly at stock voltages, plus it seemed AMD were fixing this in drivers at the time, so an RMA wasnt thought about.

Yes please, if you find anything of use it would be appreciated.

PSU much like everything else, has no effect (yes, fully tested with other PSU's)

Memory settings have no effect.

But now that I am thinking about it again, other than those ancient drivers, there is one thing that seems to have a small, but consistent effect on raising the voltage threshold before black-outs, I forgot, as it's something I do when CPU overclocking anyway: Raising "System Agent Voltage" a bit more than usual seems to allow just a bit more VDDC..... I sure hope this gives some insight

As much as I hate to see others with this problem, I sure am glad you guys are coming out of the woodwork
post #1717 of 3620
Quote:
Originally Posted by navjack27 View Post

Woah my mind is blown. The blackouts i get when i overclock really high but don't get high temps or artifacts... Yeah display clock signal coruption makes sense. Maybe when i run high clocks i should just run 60hz over my dvi instead of lightboost 120hz like I'm used to... Or just do vga?

Cuz that's actually what i see, the display gets weird for a microsecond and then goes black. Everything is still going, hell when I've done this in a csgo game and I'd still be in teamspeak talking to my friends while having a black screen that won't come back.

my tests demonstrate the blackouts are due to voltage only.

1000mhz 1.34v = blackout
1200mhz 1.34v = blackout

1000mhz 1.2v= ok
1200mhz 1.3v = ok
post #1718 of 3620
Quote:
Originally Posted by spyshagg View Post

my tests demonstrate the blackouts are due to voltage only.

1000mhz 1.34v = blackout
1200mhz 1.34v = blackout

1000mhz 1.2v= ok
1200mhz 1.3v = ok
yep thats right,
high voltage = blackout

Why? Digital signal corruption.
Buy why ? ..no idea.... redface.gif
post #1719 of 3620
Thread Starter 
@The Stilt

Right fixed my VoltageObjectInfo smile.gif .
Code:
7C 00 03 01 01 03 1A 00 08 96 60 00 00 00 00 00
6D 00 DF 00 8D 00 00 00 26 00 00 00 FF 00 01 07
0C 00 0A 00 00 00 00 00 00 00 04 07 0C 00 0E 00
00 00 00 00 00 00 02 00 24 00 00 04 00 00 00 80
10 00 00 00 00 00 1E 05 00 00 10 00 46 05 00 80
00 00 DC 05 00 80 10 00 0E 06 06 03 22 00 0C 96
A6 00 00 00 00 00 D4 00 A2 00 D5 00 A2 00 D6 00
A2 00 D7 00 A2 00 D3 00 40 00 FF 00

Now i2cdump is:-
Code:
28 14 25 03 15 1F 7C 42 67 6A 11 66 66 44 FF FF 
A2 22 80 10 2A FF FF 00 00 00 55 55 50 00 00 00 
00 00 3C 78 20 20 00 80 06 21 9C 2D 37 9C 5C 26 
85 07 FC 7F 79 05 05 10 81 A0 60 00 00 66 00 00 
A8 90 00 00 00 00 00 00 14 14 00 40 80 60 A0 FF 
FF 00 30 88 54 0D 88 12 02 02 66 00 50 25 00 4A 
30 03 0E 60 C4 9C 24 88 80 00 00 00 00 DF 06 FF 
FF 20 00 00 00 00 00 00 00 00 00 00 15 15 00 00 
00 00 00 00 00 00 00 00 88 88 01 C2 44 00 00 1F 
00 05 43 5E 70 01 70 70 5E AA 7B 6D 03 02 1C 1D 
00 00 00 00 00 00 01 01 08 55 20 9A 88 00 00 08 
01 00 00 00 FF 00 23 DF 00 00 74 70 AD 15 00 00 
00 00 FF 77 A3 00 00 00 00 00 00 04 01 44 00 00 
00 00 AD 50 0C 00 10 00 3F 00 00 00 23 C0 F0 00 
00 00 00 10 01 03 01 88 00 00 00 00 00 00 00 00 
00 00 00 00 00 33 00 00 00 00 00 00 00 00 00 00

Like I said earlier in thread before 3 state VDDCI mod I'd get 1.000V VDDCI thus never thought I had a offset present for it. After the 3 state VDDCI mod I just thought GPU-Z was misreading voltages as it would show 0.844v for 0.850v and 1.000v for 1.000v.

Now it's showing 0.852v for 0.850v and 1.000v is still 1.000v.

So seems to me due to the inaccuracy in software voltage monitoring, it was not very clear I had a -6.25mV offset set for VDDC / VDDCI present in MTP of my IR3567B. So many thanks for pointing it out smile.gif .

I'm just so surprised there were 2 sets of offsets in there, really surprises me why an AIB would set them this way, what's the point in one offset setting -6.25mV VDDC & VDDCI and another setting +31.25mv VDDC only.

There isn't anything else loopy with by IR3567B setup? cheers.
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 #1720 of 3620
First order of business: Thanks for such an incredible thread, and incredible detective and tinkering work. This is a truly impressive feat! The willingness to make this available, and work with those of us who couldn't possibly unravel this stuff ourselves is a credit to this place and the folks involved.

Second, my apologies for a very nooby question. I've read just about this entire thread (many parts a few times), and every single section of the 1st post more than once, including many of the linked for further discussion areas. I've also read the entire HawaiiReader thread (linked on the github page).

Short version: Can I use Hawaii Reader to change the idle memory clocks to something higher-- and where do I make those inputs? I'm a bit confused on this point, and it's likely down to my own understanding (or lack thereof). I'm trying to fix idle* horizontal flickering/tearing/artifacting

Longer version: My card (R9 290 Windforce 3X OC, rev 1) works fine in Windows with latest stock roms. No blackscreens, no flicker, idle and gaming. My problem is a little more esoteric: When I boot into OS X* (Xeon 5650 + X58 + El Capitan/Clover) directly via DisplayPort, which is my primary monitor, I get pretty horrendous horizontal tearing/artifacts at the desktop. We're talking every 1-3 seconds, usually. Sometimes it will stop for a few seconds. It is exacerbated by moving the mouse or dragging a window. Now, the interesting part is that at full load (Heaven Benchmark, for instance), the tearing stops entirely-- even if I put Heaven into windowed mode and do other tasks (email, browsing, moving around the desktop. From this noob's perspective this would indicate that the issue is one of the following: 1) GPU/mem idle clocks too low, 2)gpu/mem idle voltage too low at low DPM states, or 3)something in the jumping from idle states to higher DPM states is causing the issue.

Even more interesting is that if I run my OS X system with dual monitors-- the artifacts/tearing/horizontal lines never appear! From what I've read, AMD has set up the R9 200/300 GPUs in a way that when multiple monitors are plugged in the lowest DPM state is never fully reached (either the clocks or the voltages don't hit DPM 0 values).

I'm guessing that for whatever reason, my GPU is OK, since it works just fine in Windows. But something about the combination of DisplayPort + OS X (which has far less efficient drivers!) pushes the system just over the edge towards artifacts.

I'm also afraid to raise voltages too high, because I have a low ASIC quality card (~69%), that takes high volts on the stock rom. Hawaii reader shows DPM 0 set to 993mv, but MSi AB and GPUz show idle VDDC at 1.080 volts! So that looks like an offset of +15mv. DPM 7 as reported by AIDA64 is 1.250 volts, but MSI AB/GPUz report around 1.203 volts under load (GPUZ render test).

Finally, and I don't know if this is pertinent, but is it normal that when I check DPM voltages via AIDA64 that they don't progress from lower to higher as I go up the states? They go up, then drop in the middle, then go back up at the top? See:

DPM0: GPUClock = 300 MHz, VID = 0.99300 V
DPM1: GPUClock = 483 MHz, VID = 1.20600 V
DPM2: GPUClock = 727 MHz, VID = 1.18100 V
DPM3: GPUClock = 924 MHz, VID = 1.16800 V
DPM4: GPUClock = 968 MHz, VID = 1.20000 V
DPM5: GPUClock = 1004 MHz, VID = 1.23100 V
DPM6: GPUClock = 1031 MHz, VID = 1.25000 V
DPM7: GPUClock = 1040 MHz, VID = 1.25000 V

In any case, if anyone can help me with the very basic question (can I use HR to change idle gpu/mem clocks?), I'd be thrilled. I know you are all very busy.
My System
(19 items)
 
  
CPUMotherboardGraphicsGraphics
Xeon X5650 GA-X58-UD3R Windforce R9 290 XFX 5770 Single Slot 
RAMHard DriveHard DriveHard Drive
PNY 1866 DIMM G.Skill Sniper 60 SSD MX100 256 GB Toshiba 7200 
Hard DriveHard DriveCoolingOS
Seagate 3 TB Samsung 1 TB 212+ OS X El Capitan 
OSMonitorPowerCase
Windows 10 Professional 27" Apple Cinema Display Corsair RM850x Antec Three Hundred Two 
  hide details  
Reply
My System
(19 items)
 
  
CPUMotherboardGraphicsGraphics
Xeon X5650 GA-X58-UD3R Windforce R9 290 XFX 5770 Single Slot 
RAMHard DriveHard DriveHard Drive
PNY 1866 DIMM G.Skill Sniper 60 SSD MX100 256 GB Toshiba 7200 
Hard DriveHard DriveCoolingOS
Seagate 3 TB Samsung 1 TB 212+ OS X El Capitan 
OSMonitorPowerCase
Windows 10 Professional 27" Apple Cinema Display Corsair RM850x Antec Three Hundred Two 
  hide details  
Reply
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 )