Author

Topic: Miners stopps and goes to 0Mh (Read 440 times)

newbie
Activity: 17
Merit: 0
December 13, 2017, 08:19:56 AM
#17
After a few reboots I was able to flash the bad card in windows pc  Cheesy

Low mhs was because of to hard intensity on dualminer
newbie
Activity: 17
Merit: 0
December 03, 2017, 12:40:25 PM
#16
See if a different Bios is detected for any of the cards when you change the Bios switch to the side you didn't change. If they are all the same, put the Bios switch on the side closest to the I/O ports and try flashing the original Bios from the cards with only the 1750 MHz straps copied higher. After you flash the Bios try running them with a 1150 MHz core clock and 2000 MHz memory clock.

I might found the sinner! one of the cards in other bios mode makes the whole system crash at bootup. The other four shows this as their second bios

4 cards: 8gb · ellesmere rx 570 113-2e366du-s4l samsung · polaris10
1 card:  8gb · ellesmere rx 570 113-2e366au-x4z samsung · polaris10

Im assuming that means they are all samsung memory, but how to flash a broken bios that doesnt even alow the rig to boot? Both bios position wont boot

The other 4 are now running at your suggested bios mod and clock, seems fine for now  Wink

Am I losing hashrate since im running ethos and not windows with amd blockchain drivers?
hero member
Activity: 1036
Merit: 606
December 03, 2017, 04:46:25 AM
#15
See if a different Bios is detected for any of the cards when you change the Bios switch to the side you didn't change. If they are all the same, put the Bios switch on the side closest to the I/O ports and try flashing the original Bios from the cards with only the 1750 MHz straps copied higher. After you flash the Bios try running them with a 1150 MHz core clock and 2000 MHz memory clock.
newbie
Activity: 17
Merit: 0
December 02, 2017, 06:24:15 PM
#14
Oh thanks  Smiley

how do i check the memory type now? will backuping the "wrong" bios now show the cards correct memory producer?
Since all the cards main bios is now the same as the first card

Judging on what you tell me i believe 2 of my cards have samsung memory since they still work fine with this bios mod and the others to be some other brand. Shouldn't have trusted the it's the same manufacturer it has to be the same memory gut feeling  Embarrassed

Edit: This is bios name in ethos 8gb · ellesmere rx 570 113-2e366au-x4z samsung · polaris10
hero member
Activity: 1036
Merit: 606
December 02, 2017, 06:04:56 PM
#13
The 1500 MHz timing straps are too aggressive for some cards which is why I use the Polaris Bios Editor v1.6.2 'one click patch'. That adjusts the 1750 MHz and up straps only. PBE v1.6.3 and up adjusts the straps from 1500 MHz and up. Most cards have more than one memory type with a different set of straps for each labeled 1: for the first set and 2: for the second set. When copying the straps manually, you need to copy the straps from each set and not mix them up with the timings on the other set. PBE identifies the memory type and applies the correct straps automatically with the 'one click timing patch'.

Flip the Bios switch to the side closest to the I/O poerts and only flash that Bios. Before flashing a Bios to a card, you need to make sure it has the same memory type as card the Bios came from. Even cards from the same brand and model will often have different memory types as manufacturers use what ever memory is available from different vendors when they are manufacturing cards. I would flash the original Bios back to each card and then in ethos you can check what memory type is listed for each card. Once you have confirmed the cards are all the same, try flashing a Bios with only the 1750 MHz and up timings adjusted. Either manually from the original Bios or with PBE v1.62.
newbie
Activity: 17
Merit: 0
December 02, 2017, 05:26:20 PM
#12
At first I used polaris bios editor and copied 1500 straps to the above ones, then i used the one click timing as suggested in a post above.
Does it matter which bios i flash on the cards? i notice some of them have the switch in the other direction, all show as same bios in dashboard

Should also mention that i backup bios from one card and then used the modified version of that on all the cards, is that bad?
hero member
Activity: 1036
Merit: 606
December 02, 2017, 04:38:54 PM
#11
1340 MHz core and 2150 MHz memory clock is way too much for a RX 570. Try setting 1200 Mhz for the core clock and 2000 MHz for the memory.

I dont really see how that would help as they crash on stock speeds but i will give it a go

So now they just crash instantly compared to original clocks. Have I messed up my cards or just my bios? Roll Eyes

Have checked risers they are all good unless my bios messup destroyd them

What Bios mod have you done with the cards that are crashing?
newbie
Activity: 17
Merit: 0
December 02, 2017, 04:27:36 PM
#10
1340 MHz core and 2150 MHz memory clock is way too much for a RX 570. Try setting 1200 Mhz for the core clock and 2000 MHz for the memory.

I dont really see how that would help as they crash on stock speeds but i will give it a go

So now they just crash instantly compared to original clocks. Have I messed up my cards or just my bios? Roll Eyes

Have checked risers they are all good unless my bios messup destroyd them
hero member
Activity: 1036
Merit: 606
December 02, 2017, 04:04:38 PM
#9
The stock core clock is set for gaming and is too high for mining Ethash, which is a memory intensive algorithm. Also switch the riser with another card that's working to see if anything changes.
newbie
Activity: 17
Merit: 0
December 02, 2017, 03:57:20 PM
#8
1340 MHz core and 2150 MHz memory clock is way too much for a RX 570. Try setting 1200 Mhz for the core clock and 2000 MHz for the memory.

I dont really see how that would help as they crash on stock speeds but i will give it a go
hero member
Activity: 1036
Merit: 606
December 01, 2017, 07:16:13 PM
#7
1340 MHz core and 2150 MHz memory clock is way too much for a RX 570. Try setting 1200 Mhz for the core clock and 2000 MHz for the memory.
newbie
Activity: 17
Merit: 0
December 01, 2017, 07:12:05 PM
#6
Reflashed all the cards with one click timing, but they are still crashing at stock speed  Huh even tried downloading a bios, same result
Have i broken them?
newbie
Activity: 17
Merit: 0
December 01, 2017, 08:25:53 AM
#5
Thanks for fast reply's Smiley

After 16 hours runtime one of the 3 with moded bios on stock speed crashed. I have only copied 1500 straps to higher so I will try other bios mod, still think it's weird that four of them is still going with the bios mod, two at speeds of core 1340 and mem 2150

Edit: I messed up  Embarrassed
sr. member
Activity: 784
Merit: 282
November 30, 2017, 08:28:30 PM
#4
I use to experience this all the time when I was starting out. As the previous posters mentioned, it could be a bad bios mod, but to be specific, you may be pushing your cards overclock or undervolt settings too much.

The fact that it initially works means you did the bios mod process correctly, the problem lies in your settings. Try and reduce the coreclock/memclock slowly maybe with -5 increments. If that doesn't work and considering that you undervolted it, try adding more power/voltage slowly in +2 increments.
hero member
Activity: 1036
Merit: 606
November 30, 2017, 07:57:42 PM
#3
Most likely a bad Bios mod. I suggest using the PBE v1.6.2 'one click timing patch' bundled performance timings on the original Bios. They work great for most of my cards and 90% of the time are better than just copying the lower frequency straps.

https://github.com/jaschaknack/PolarisBiosEditor

I have a Sapphire Nitro+ RX 570 4 GB card that gets 28.4 MH/s + 740 MH/s DCR dual mining with a 2020 MHz memory overclock.
sr. member
Activity: 1008
Merit: 297
Grow with community
November 30, 2017, 07:36:59 PM
#2
Sorry if this is wrong place. I couldn't find any gpu subforum under altcoins Huh
Can't delete this post so hoping i mod will fix my mistake  Embarrassed

I have a rig of 5 rx 570 nitro+ 8Gb cards that i have bios moded with polaris editor. 2 of them are stable at a hashrate of 23.3Mh while the other 3 sometimes run on 21Mh, jumps in voltage and eventually crash to 0Mh, it can take 30min to several hours.
core 1340 mem 2150
Running them on stock clocks is 20.5Mh and seems to be working fine (going on 3rd hour)

On my nvidia rig mem clock was king gaining 5mh overclock, but on the amd rig mem clock gain only 0.5Mh while core clock gains 2.3Mh

Bios mod, lower voltages and clocks they said... leaving me confused as that only lowers my hashrate on amd cards  Huh
my good old r9 290 4Gb did 31Mh (core +100 mem +450-500) not that long ago, my 1070's does 31Mh now.

Im using Ethos on my rigs

What in the heck am i doing wrong with these amd cards? Sad


you might missed or messed up with modding Bios, have you followed exactly the procedure and suggested straps? there were also the one touch feature on those modding apps and might be useful to you.

https://bitcointalk.org/index.php?topic=1882656.new#new

https://bitcointalksearch.org/topic/guidetutorialxmrethhow-to-mod-bios-rx470570480580-vega-mining-1954245



newbie
Activity: 17
Merit: 0
November 30, 2017, 06:00:42 PM
#1
Sorry if this is wrong place. I couldn't find any gpu subforum under altcoins Huh
Can't delete this post so hoping i mod will fix my mistake  Embarrassed

I have a rig of 5 rx 570 nitro+ 8Gb cards that i have bios moded with polaris editor. 2 of them are stable at a hashrate of 23.3Mh while the other 3 sometimes run on 21Mh, jumps in voltage and eventually crash to 0Mh, it can take 30min to several hours.
core 1340 mem 2150
Running them on stock clocks is 20.5Mh and seems to be working fine (going on 3rd hour)

On my nvidia rig mem clock was king gaining 5mh overclock, but on the amd rig mem clock gain only 0.5Mh while core clock gains 2.3Mh

Bios mod, lower voltages and clocks they said... leaving me confused as that only lowers my hashrate on amd cards  Huh
my good old r9 290 4Gb did 31Mh (core +100 mem +450-500) not that long ago, my 1070's does 31Mh now.

Im using Ethos on my rigs

What in the heck am i doing wrong with these amd cards? Sad



Jump to: