Bitcoin Forum
August 17, 2018, 04:24:32 AM *
News: Latest stable version of Bitcoin Core: 0.16.2  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 [66] 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 ... 143 »
  Print  
Author Topic: [Cast XMR] high speed XMR/CryptoNight miner for RX Vega GPUs (2 KHash/s)  (Read 169089 times)
dragonmike
Hero Member
*****
Offline Offline

Activity: 742
Merit: 520


🤖UBEX.COM 🤖


View Profile
December 28, 2017, 10:42:07 AM
 #1301

So I've just flashed my 56's to 64 vbios and applied Hellae's "safe" reg file.
I've set some new frequencies in OverdriveNtool but CastXMR just keeps stopping on me after a few minutes. Does that mean I'm not giving the memory enough juice? Too much clock? Is it core related? Can anyone who's been through this help me troubleshoot the behaviour of the miner please?

...

Getting approx 1900h/s/card, total 1050w from the wall (6 GPUs).
Any suggestions welcome!

Can you elaborate on "stops" a little? Does the app crash/close, does it just stop output in the cmd shell....that kind of thing.

Reason I ask is I have similar behavior where it just stops sending out put to the Window (nope it is not the Quick Edit setting). When I try to connect to the 7777 port my moniotoring script will pick up that it is hung and then it restarts the process.
as long as your Vega are stable, Cast XMR almost never ever crashes or close -save for the Quick Edit thing, which we mentioned before-, and from personal experience my issues with the program crashing were totally gone once I found out how to stabilise the cards, meaning that I set the unmodded Vega 56 cards to 935MHz instead of 950MHz using OverdriveNTool.
Ok, so the culprit here is probably memory clock since mem voltage seems fixed anyway. So far it's been hashing all night at 1050 Mhz nicely. I'll try tweaking clocks some more today.
Well it did stop again after about 6 hours.
Restarted, leaving everything the same apart from lower core clocks. Let's see what happens. Worst case I'd have similar hashrates to what I had before the flash, but at 350W less at the wall. Which is positive I suppose.

EDIT: how can you figure out which GPU is causing trouble? Using Cast I have no visibility at all... No logs and all...


.GLOBAL DECENTRALIZED ADVERTISING EXCHANGE.

Token sale: MAY 21

                                   ▄█▄       ▄█▄         
                                  █████     █████         
                         ▄██▄      ▀█▀       ▀█▀         
                 ▄█▄     ▀██▀                             
          ▄      ▀█▀                         ▄█▄         
         ▀█▀                       ▄█▄      █████         
                         ▄██▄     █████      ▀█▀         
    ██           ▄█▄     ▀██▀      ▀█▀                   
          ▄      ▀█▀                         ▄█▄         
         ▀█▀                       ▄█▄      █████         
                         ▄██▄     █████      ▀█▀         
    ██           ▄█▄     ▀██▀      ▀█▀                   
                 ▀█▀                                     
           ▄                       ▄█▄       ▄█▄         
          ▀█▀            ▄██▄     █████     █████         
    ██           ▄█▄     ▀██▀      ▀█▀       ▀█▀         
                 ▀█▀                                     
            ▄                       ▄█▄      ▄█▄         
           ▀█▀             ▄██▄    █████    █████         
     ██             ▄█▄    ▀██▀     ▀█▀      ▀█▀         
              ▄     ▀█▀                                   
             ▀█▀                          ▄█▄             
        ██               ▄█▄    ▄██▄     █████           
                   ▄     ▀█▀    ▀██▀      ▀█▀             
                  ▀█▀                                     
             ██                    ▄██▄                   
                     ▄      ▄█▄    ▀██▀                   
                    ▀█▀     ▀█▀                           

▄█    ▄█  ▄█         ▄█████▄    ▀█▄      ▄█▀
██    ██  ██▄▄▄▄▄   ██▀   ▀██     ▀█▄  ▄█▀
██    ██  ██▀▀▀▀██  ██▀▀▀▀▀▀▀       ████   
██    ██  ██    ██  ██▄    ▄█     ▄██▀▀██▄   
▀██████▀  ▀██████▀  ▀███████▀   ▄██▀    ▀██▄
Telegram
Facebook
ANN Thread
Youtube
LinkedIn
Twitter
Medium
Reddit
Github
1534479872
Hero Member
*
Offline Offline

Posts: 1534479872

View Profile Personal Message (Offline)

Ignore
1534479872
Reply with quote  #2

1534479872
Report to moderator
1534479872
Hero Member
*
Offline Offline

Posts: 1534479872

View Profile Personal Message (Offline)

Ignore
1534479872
Reply with quote  #2

1534479872
Report to moderator
1534479872
Hero Member
*
Offline Offline

Posts: 1534479872

View Profile Personal Message (Offline)

Ignore
1534479872
Reply with quote  #2

1534479872
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1534479872
Hero Member
*
Offline Offline

Posts: 1534479872

View Profile Personal Message (Offline)

Ignore
1534479872
Reply with quote  #2

1534479872
Report to moderator
1534479872
Hero Member
*
Offline Offline

Posts: 1534479872

View Profile Personal Message (Offline)

Ignore
1534479872
Reply with quote  #2

1534479872
Report to moderator
Cyan_Antares
Jr. Member
*
Offline Offline

Activity: 126
Merit: 0


View Profile
December 28, 2017, 12:08:19 PM
 #1302

So I've just flashed my 56's to 64 vbios and applied Hellae's "safe" reg file.
I've set some new frequencies in OverdriveNtool but CastXMR just keeps stopping on me after a few minutes. Does that mean I'm not giving the memory enough juice? Too much clock? Is it core related? Can anyone who's been through this help me troubleshoot the behaviour of the miner please?

...

Getting approx 1900h/s/card, total 1050w from the wall (6 GPUs).
Any suggestions welcome!

Can you elaborate on "stops" a little? Does the app crash/close, does it just stop output in the cmd shell....that kind of thing.

Reason I ask is I have similar behavior where it just stops sending out put to the Window (nope it is not the Quick Edit setting). When I try to connect to the 7777 port my moniotoring script will pick up that it is hung and then it restarts the process.
as long as your Vega are stable, Cast XMR almost never ever crashes or close -save for the Quick Edit thing, which we mentioned before-, and from personal experience my issues with the program crashing were totally gone once I found out how to stabilise the cards, meaning that I set the unmodded Vega 56 cards to 935MHz instead of 950MHz using OverdriveNTool.
Ok, so the culprit here is probably memory clock since mem voltage seems fixed anyway. So far it's been hashing all night at 1050 Mhz nicely. I'll try tweaking clocks some more today.
Well it did stop again after about 6 hours.
Restarted, leaving everything the same apart from lower core clocks. Let's see what happens. Worst case I'd have similar hashrates to what I had before the flash, but at 350W less at the wall. Which is positive I suppose.

EDIT: how can you figure out which GPU is causing trouble? Using Cast I have no visibility at all... No logs and all...
if the clocks are somewhat overkill for the cards, it's quite hard to say. Again, that's from personal experience. But at higher than normal clocks they can work for relatively long periods of time or stop just when the program is loading the cards -when the text appears in blue color-, this means in less that 2 seconds.

Some of them lose track of their own settings and fans can stop to spin at 3000rpm and just spin at 1000rpm, temps soar to 83ºC....

A pattern I always noticed when I was having random, unexplainable hangs, is that the GPU5 always had all the leds lit, as if it was working hard and normally, while the other 5 cards only had a single led lit, as when they are in rest mode.

I learnt that going where the rig is physically placed. The OS continued to work normally so I had an internet connection to the rig, but being physically there also gave clues.

Was the GPU5 the culprit? Was it any of the others? That's the question.




Right now I am getting the following using Stock Vega 56 BIOS on "Blockchain Drivers" from AMD and it's been stable for more than 24 hours:

Average Hashrate = 1923 H/s
Fan set to = 2000 RPM
Temp = 60C (Stable)
GPU Freq = 0%
Memory Freq = 935 MHz
Power Limit % = -10
Power draw at the wall (Measured) = 150W to 165W
That's great stuff!
mehmetkorkrek
Jr. Member
*
Offline Offline

Activity: 154
Merit: 0

Energy for the 21st Century


View Profile
December 28, 2017, 12:14:57 PM
 #1303


I think the best application. I get best Hashrate with Cast XMR. I used two or three different programs before. They all have a lower hash.

I have a question. If there is a problem with the connection, the program shuts down after a while. Does this have a solution?

⚡⚡  Bittwatt  ⚡⚡   ▄▀▄▀▄▀▄▀   Energy for the 21st Century   ▄▀▄▀▄▀▄▀
GrassBite
Jr. Member
*
Offline Offline

Activity: 65
Merit: 3


View Profile
December 28, 2017, 01:31:04 PM
 #1304

Can we get support for sumokoin added?


Pretty Please?
jyakulis
Sr. Member
****
Offline Offline

Activity: 462
Merit: 250


Resident Retard


View Profile
December 28, 2017, 01:39:34 PM
 #1305

Can we get support for sumokoin added?


Pretty Please?

It already has it...

For the night is dark and full of terrors
dragonmike
Hero Member
*****
Offline Offline

Activity: 742
Merit: 520


🤖UBEX.COM 🤖


View Profile
December 28, 2017, 01:50:58 PM
 #1306

Well, stopped again after a few hours. So core clock now back up to 1408 and lowered mem clocks to 1040. Let's see how that goes. Annoying. I really thought I'd be able to run these cards closer to 1100... Now it seems I'm tweaking the other way Sad

EDIT: I suppose playing with power limit wouldn't do anything for the memory clocks anyway... so pointless playing with that.


.GLOBAL DECENTRALIZED ADVERTISING EXCHANGE.

Token sale: MAY 21

                                   ▄█▄       ▄█▄         
                                  █████     █████         
                         ▄██▄      ▀█▀       ▀█▀         
                 ▄█▄     ▀██▀                             
          ▄      ▀█▀                         ▄█▄         
         ▀█▀                       ▄█▄      █████         
                         ▄██▄     █████      ▀█▀         
    ██           ▄█▄     ▀██▀      ▀█▀                   
          ▄      ▀█▀                         ▄█▄         
         ▀█▀                       ▄█▄      █████         
                         ▄██▄     █████      ▀█▀         
    ██           ▄█▄     ▀██▀      ▀█▀                   
                 ▀█▀                                     
           ▄                       ▄█▄       ▄█▄         
          ▀█▀            ▄██▄     █████     █████         
    ██           ▄█▄     ▀██▀      ▀█▀       ▀█▀         
                 ▀█▀                                     
            ▄                       ▄█▄      ▄█▄         
           ▀█▀             ▄██▄    █████    █████         
     ██             ▄█▄    ▀██▀     ▀█▀      ▀█▀         
              ▄     ▀█▀                                   
             ▀█▀                          ▄█▄             
        ██               ▄█▄    ▄██▄     █████           
                   ▄     ▀█▀    ▀██▀      ▀█▀             
                  ▀█▀                                     
             ██                    ▄██▄                   
                     ▄      ▄█▄    ▀██▀                   
                    ▀█▀     ▀█▀                           

▄█    ▄█  ▄█         ▄█████▄    ▀█▄      ▄█▀
██    ██  ██▄▄▄▄▄   ██▀   ▀██     ▀█▄  ▄█▀
██    ██  ██▀▀▀▀██  ██▀▀▀▀▀▀▀       ████   
██    ██  ██    ██  ██▄    ▄█     ▄██▀▀██▄   
▀██████▀  ▀██████▀  ▀███████▀   ▄██▀    ▀██▄
Telegram
Facebook
ANN Thread
Youtube
LinkedIn
Twitter
Medium
Reddit
Github
bostonvex
Member
**
Offline Offline

Activity: 72
Merit: 10


View Profile
December 28, 2017, 01:56:09 PM
 #1307

Well, stopped again after a few hours. So core clock now back up to 1408 and lowered mem clocks to 1040. Let's see how that goes. Annoying. I really thought I'd be able to run these cards closer to 1100... Now it seems I'm tweaking the other way Sad

EDIT: I suppose playing with power limit wouldn't do anything for the memory clocks anyway... so pointless playing with that.

Dude, are you sure it is memclock related? I think it is a bug in cast_xmr.
dragonmike
Hero Member
*****
Offline Offline

Activity: 742
Merit: 520


🤖UBEX.COM 🤖


View Profile
December 28, 2017, 02:15:53 PM
 #1308

Well, stopped again after a few hours. So core clock now back up to 1408 and lowered mem clocks to 1040. Let's see how that goes. Annoying. I really thought I'd be able to run these cards closer to 1100... Now it seems I'm tweaking the other way Sad

EDIT: I suppose playing with power limit wouldn't do anything for the memory clocks anyway... so pointless playing with that.

Dude, are you sure it is memclock related? I think it is a bug in cast_xmr.
Well, when I was mining on unmodded 56 bios @ 925MHz memory freq the rig was mining several days without a single hickup. So I can only assume stability is memclock related. I'd be very happy to  be proven wrong!


.GLOBAL DECENTRALIZED ADVERTISING EXCHANGE.

Token sale: MAY 21

                                   ▄█▄       ▄█▄         
                                  █████     █████         
                         ▄██▄      ▀█▀       ▀█▀         
                 ▄█▄     ▀██▀                             
          ▄      ▀█▀                         ▄█▄         
         ▀█▀                       ▄█▄      █████         
                         ▄██▄     █████      ▀█▀         
    ██           ▄█▄     ▀██▀      ▀█▀                   
          ▄      ▀█▀                         ▄█▄         
         ▀█▀                       ▄█▄      █████         
                         ▄██▄     █████      ▀█▀         
    ██           ▄█▄     ▀██▀      ▀█▀                   
                 ▀█▀                                     
           ▄                       ▄█▄       ▄█▄         
          ▀█▀            ▄██▄     █████     █████         
    ██           ▄█▄     ▀██▀      ▀█▀       ▀█▀         
                 ▀█▀                                     
            ▄                       ▄█▄      ▄█▄         
           ▀█▀             ▄██▄    █████    █████         
     ██             ▄█▄    ▀██▀     ▀█▀      ▀█▀         
              ▄     ▀█▀                                   
             ▀█▀                          ▄█▄             
        ██               ▄█▄    ▄██▄     █████           
                   ▄     ▀█▀    ▀██▀      ▀█▀             
                  ▀█▀                                     
             ██                    ▄██▄                   
                     ▄      ▄█▄    ▀██▀                   
                    ▀█▀     ▀█▀                           

▄█    ▄█  ▄█         ▄█████▄    ▀█▄      ▄█▀
██    ██  ██▄▄▄▄▄   ██▀   ▀██     ▀█▄  ▄█▀
██    ██  ██▀▀▀▀██  ██▀▀▀▀▀▀▀       ████   
██    ██  ██    ██  ██▄    ▄█     ▄██▀▀██▄   
▀██████▀  ▀██████▀  ▀███████▀   ▄██▀    ▀██▄
Telegram
Facebook
ANN Thread
Youtube
LinkedIn
Twitter
Medium
Reddit
Github
bostonvex
Member
**
Offline Offline

Activity: 72
Merit: 10


View Profile
December 28, 2017, 02:46:35 PM
 #1309

Well, stopped again after a few hours. So core clock now back up to 1408 and lowered mem clocks to 1040. Let's see how that goes. Annoying. I really thought I'd be able to run these cards closer to 1100... Now it seems I'm tweaking the other way Sad

EDIT: I suppose playing with power limit wouldn't do anything for the memory clocks anyway... so pointless playing with that.

Dude, are you sure it is memclock related? I think it is a bug in cast_xmr.
Well, when I was mining on unmodded 56 bios @ 925MHz memory freq the rig was mining several days without a single hickup. So I can only assume stability is memclock related. I'd be very happy to  be proven wrong!

Fair enough. I just switched back to version 0.7 and will let you know how it goes.

What version are you on?
dragonmike
Hero Member
*****
Offline Offline

Activity: 742
Merit: 520


🤖UBEX.COM 🤖


View Profile
December 28, 2017, 02:54:38 PM
 #1310

Well, stopped again after a few hours. So core clock now back up to 1408 and lowered mem clocks to 1040. Let's see how that goes. Annoying. I really thought I'd be able to run these cards closer to 1100... Now it seems I'm tweaking the other way Sad

EDIT: I suppose playing with power limit wouldn't do anything for the memory clocks anyway... so pointless playing with that.

Dude, are you sure it is memclock related? I think it is a bug in cast_xmr.
Well, when I was mining on unmodded 56 bios @ 925MHz memory freq the rig was mining several days without a single hickup. So I can only assume stability is memclock related. I'd be very happy to  be proven wrong!

Fair enough. I just switched back to version 0.7 and will let you know how it goes.

What version are you on?
I'm on the latest, aka v0.8.
Not sure if it makes any difference in stability... How does the intensity affect hashrate? I've set it to the max (I think that's 9), but no idea if lowering it would allow clocking mem higher (or prevent the miner from stopping)?


.GLOBAL DECENTRALIZED ADVERTISING EXCHANGE.

Token sale: MAY 21

                                   ▄█▄       ▄█▄         
                                  █████     █████         
                         ▄██▄      ▀█▀       ▀█▀         
                 ▄█▄     ▀██▀                             
          ▄      ▀█▀                         ▄█▄         
         ▀█▀                       ▄█▄      █████         
                         ▄██▄     █████      ▀█▀         
    ██           ▄█▄     ▀██▀      ▀█▀                   
          ▄      ▀█▀                         ▄█▄         
         ▀█▀                       ▄█▄      █████         
                         ▄██▄     █████      ▀█▀         
    ██           ▄█▄     ▀██▀      ▀█▀                   
                 ▀█▀                                     
           ▄                       ▄█▄       ▄█▄         
          ▀█▀            ▄██▄     █████     █████         
    ██           ▄█▄     ▀██▀      ▀█▀       ▀█▀         
                 ▀█▀                                     
            ▄                       ▄█▄      ▄█▄         
           ▀█▀             ▄██▄    █████    █████         
     ██             ▄█▄    ▀██▀     ▀█▀      ▀█▀         
              ▄     ▀█▀                                   
             ▀█▀                          ▄█▄             
        ██               ▄█▄    ▄██▄     █████           
                   ▄     ▀█▀    ▀██▀      ▀█▀             
                  ▀█▀                                     
             ██                    ▄██▄                   
                     ▄      ▄█▄    ▀██▀                   
                    ▀█▀     ▀█▀                           

▄█    ▄█  ▄█         ▄█████▄    ▀█▄      ▄█▀
██    ██  ██▄▄▄▄▄   ██▀   ▀██     ▀█▄  ▄█▀
██    ██  ██▀▀▀▀██  ██▀▀▀▀▀▀▀       ████   
██    ██  ██    ██  ██▄    ▄█     ▄██▀▀██▄   
▀██████▀  ▀██████▀  ▀███████▀   ▄██▀    ▀██▄
Telegram
Facebook
ANN Thread
Youtube
LinkedIn
Twitter
Medium
Reddit
Github
h311m4n
Sr. Member
****
Offline Offline

Activity: 423
Merit: 252



View Profile
December 28, 2017, 02:58:17 PM
 #1311

Well, stopped again after a few hours. So core clock now back up to 1408 and lowered mem clocks to 1040. Let's see how that goes. Annoying. I really thought I'd be able to run these cards closer to 1100... Now it seems I'm tweaking the other way Sad

EDIT: I suppose playing with power limit wouldn't do anything for the memory clocks anyway... so pointless playing with that.

Dude, are you sure it is memclock related? I think it is a bug in cast_xmr.
Well, when I was mining on unmodded 56 bios @ 925MHz memory freq the rig was mining several days without a single hickup. So I can only assume stability is memclock related. I'd be very happy to  be proven wrong!

In my experience, stability issues are almost always related to memory frequencies being too high. Some cards are just worse than others. I have some RX470s that hash non stop at 2050Mhz while others have to be dropped to 1900, otherwise my miners end up crashing. Once they have been all fine tuned, they will mine for days on end. The same goes for Vegas. For polaris this could be troubleshooted with the number of memory errors in hwmonitor.

Just remember that what counts is not to have the fastest hashrate, but to have a stable rig.

▄                        ███▄▄█████████▄            ▄███████████████      █████████
████████████▄  ▀█████████████████████████▄  ▀██████████████ ▀█████████ ███████
███████ ▄  ▀██████ ██████████████ ███▄  ▀███ ██████████████ █▀▀▀ ███████
███████▀██████
████▀▀███
█▀
| - Digital marketplace
- Community based coin
- High ROI masternode
- POS   [ LIGHTPAPER ]

.████████████████████████.
██████████████████████████
███████████  █  ██████████
████████         ▀████████
█████████▌  ███▄   ███████
█████████  ▐████   ███████
████████▌        ▄████████
████████   ████   ▀███████
█████▌    ▐███▀    ███████
███████▄        ▄▄████████
████████  █  ████████████
█████████████████████████
.███████████████████████.
.████████████████████████.
██████████████████████████
██████████████▀     ▀█████
███ ▀████████▌        ███
███    ▀████▀        ▄████
███                 ▐████
████                ▐█████
██████              ██████
███████           ▄███████
██████▀         ▄█████████
████▄▄      ▄▄████████████
██████████████████████████
.████████████████████████.
.███████████████████████.
█████████████████████████
████████▀▀▀███▀▀▀████████
█████▀ ▄▄▀▀▀▀▀▀▀▄▄ ▀█████
████                 ███
███▌    ▄▄     ▄▄    ▐███
███    ████   ████    ██
██▌     ▀▀     ▀▀     ▐██
██▄   ▀▄▄▄     ▄▄▄▀   ▄██
████▄    ███████    ▄████
█████████████████████████
█████████████████████████
.███████████████████████.
bostonvex
Member
**
Offline Offline

Activity: 72
Merit: 10


View Profile
December 28, 2017, 03:00:42 PM
 #1312

Well, stopped again after a few hours. So core clock now back up to 1408 and lowered mem clocks to 1040. Let's see how that goes. Annoying. I really thought I'd be able to run these cards closer to 1100... Now it seems I'm tweaking the other way Sad

EDIT: I suppose playing with power limit wouldn't do anything for the memory clocks anyway... so pointless playing with that.

Dude, are you sure it is memclock related? I think it is a bug in cast_xmr.
Well, when I was mining on unmodded 56 bios @ 925MHz memory freq the rig was mining several days without a single hickup. So I can only assume stability is memclock related. I'd be very happy to  be proven wrong!

Fair enough. I just switched back to version 0.7 and will let you know how it goes.

What version are you on?
I'm on the latest, aka v0.8.
Not sure if it makes any difference in stability... How does the intensity affect hashrate? I've set it to the max (I think that's 9), but no idea if lowering it would allow clocking mem higher (or prevent the miner from stopping)?

I've used -I 9 on version 0.6 and up and never had an issue until recently. Only that changed on my end was upgrading to v0.8 and swapping out my mobo. "only thing" = swapping out mobo...big change I know but I have the exact same mobo before and no issues till v0.8. I'm not pressing the cards hard either, running 920MHz memclock.

Are you using JJs modified monitoring script? If you are, then next time it hangs, browse to 127.0.0.1:7777 and try to refresh the page...only after you do that will JJs pick up that the process is hung and restart it.
dragonmike
Hero Member
*****
Offline Offline

Activity: 742
Merit: 520


🤖UBEX.COM 🤖


View Profile
December 28, 2017, 04:09:02 PM
 #1313

Not using any monitoring script for now. Just trying to make it work reliably, basically.

Failing mobo is like the thing you don't want to happen because it's the one variable you tend to always rule out when you have issues. On my two rigs of RX570's I've got some GPUs chugging at 1950MHz mem speed, while other keep crashing at 1850 and lower -h values (in Claymore). I can't think there's anything wrong with the GPUs, so it's gotta be risers... or the damn mobo.

Let's see how the Vega rig behaves...


.GLOBAL DECENTRALIZED ADVERTISING EXCHANGE.

Token sale: MAY 21

                                   ▄█▄       ▄█▄         
                                  █████     █████         
                         ▄██▄      ▀█▀       ▀█▀         
                 ▄█▄     ▀██▀                             
          ▄      ▀█▀                         ▄█▄         
         ▀█▀                       ▄█▄      █████         
                         ▄██▄     █████      ▀█▀         
    ██           ▄█▄     ▀██▀      ▀█▀                   
          ▄      ▀█▀                         ▄█▄         
         ▀█▀                       ▄█▄      █████         
                         ▄██▄     █████      ▀█▀         
    ██           ▄█▄     ▀██▀      ▀█▀                   
                 ▀█▀                                     
           ▄                       ▄█▄       ▄█▄         
          ▀█▀            ▄██▄     █████     █████         
    ██           ▄█▄     ▀██▀      ▀█▀       ▀█▀         
                 ▀█▀                                     
            ▄                       ▄█▄      ▄█▄         
           ▀█▀             ▄██▄    █████    █████         
     ██             ▄█▄    ▀██▀     ▀█▀      ▀█▀         
              ▄     ▀█▀                                   
             ▀█▀                          ▄█▄             
        ██               ▄█▄    ▄██▄     █████           
                   ▄     ▀█▀    ▀██▀      ▀█▀             
                  ▀█▀                                     
             ██                    ▄██▄                   
                     ▄      ▄█▄    ▀██▀                   
                    ▀█▀     ▀█▀                           

▄█    ▄█  ▄█         ▄█████▄    ▀█▄      ▄█▀
██    ██  ██▄▄▄▄▄   ██▀   ▀██     ▀█▄  ▄█▀
██    ██  ██▀▀▀▀██  ██▀▀▀▀▀▀▀       ████   
██    ██  ██    ██  ██▄    ▄█     ▄██▀▀██▄   
▀██████▀  ▀██████▀  ▀███████▀   ▄██▀    ▀██▄
Telegram
Facebook
ANN Thread
Youtube
LinkedIn
Twitter
Medium
Reddit
Github
kggcel
Newbie
*
Offline Offline

Activity: 3
Merit: 0


View Profile
December 28, 2017, 05:55:00 PM
 #1314

weird... I'm getting only 1.2KH/s with a Vega 64. All drivers are set.

Could it be due to different mining pool?

I'm using dark-mine.su
pyr8
Newbie
*
Offline Offline

Activity: 14
Merit: 0


View Profile
December 28, 2017, 06:02:03 PM
 #1315

I see here that many people claim to get 1950 Hs with memory speed of 945 or so. I'm wondering what i'm doing wrong - i'm also getting 1950, but with memory at 1100 (and gpu at 1407). If i set memory to 945, hash rate goes down to ~1700-1750!?

I'm using Vega 56 cards, with 64 bios and registry files for HBM1100. And of course, blockchain drivers and latest version of Cast XMR.

P.S. i have 6 cards, tried with single one and same result. I'm also using only 2GB of RAM, not sure could that be an issue (but i doubt, as all calculations are done inside GPUs).

thanks



One you upgrade to the 64 BIOS, you have to use 64 settings. 1950 H/s @ 935/945 is for 56 un-moded cards!

Try these settings (for your appropriate card and BIOS type) NOTE that it's a starting point, your results may vary slightly:

Vega 64 Hash Rates

1900 Hash/s with 200 watts power consumption

    Core Frequency: -10%
    Memory Clock: 1025 MHz
    Power Limit: -23%

2000 Hash/s with 250 watts power consumption

    Core Frequency: -10%
    Memory Clock: 1095 MHz
    Power Limit: 0

2050 Hash/s with 280 watts power consumption

    Core Frequency: -10%
    Memory Clock: 1105 MHz
    Power Limit: +20%

Vega 56 Hash Rates

1900 Hash/s with 150 watts power consumption

    Core Frequency: -10%
    Memory Clock: 945 MHz
    Power Limit: -22%

2000 Hash/s with 200 watts power consumption

    Core Frequency: -10%
    Memory Clock: 965 MHz
    Power Limit: 0

2050 Hash/s with 225 watts power consumption

    Core Frequency: -10%
    Memory Clock: 990 MHz
    Power Limit: +12%


Hm, sounds strange to me, as i though vega64 bios is used only because of better undervolting and overclocking possibilities. Instead in relative percentages, do you know exact frequencies of GPU at those settings? I'm most interested in lower power consumption (150W) and getting about 1900 Hash/s is just fine to me. Even if cards doesn't complaint about 1100mhz, i believe they will be more relaxed on 945MHz.

And just to be clear, you didn't even change registry for voltage adjusting, just using installed drivers/cards with factory settings?

Btw, is there any explanation of intensity argument, and how to find the best one for the card (except trying all 10)?


Right now I am getting the following using Stock Vega 56 BIOS on "Blockchain Drivers" from AMD and it's been stable for more than 24 hours:

Average Hashrate = 1923 H/s
Fan set to = 2000 RPM
Temp = 60C (Stable)
GPU Freq = 0%
Memory Freq = 935 MHz
Power Limit % = -10
Power draw at the wall (Measured) = 150W to 165W

That sounds quite nice - mine fans are about 3000-3500 in order to keep HBM temp around 60-62C. But i'm using 6 gpu which of course increase total heat and cards are harder to cool - how much cards you have?
However, i'll give it a try (stock bios, unmodified registry).

Thanks.

My HBM is hovering around 63/65C...do you know what the safe maximum is for these temperatures. I read that HBM will usually run hotter than GPU temps as well, but I'm not sure what a safe maximum is?!
pyr8
Newbie
*
Offline Offline

Activity: 14
Merit: 0


View Profile
December 28, 2017, 06:10:15 PM
 #1316

I see here that many people claim to get 1950 Hs with memory speed of 945 or so. I'm wondering what i'm doing wrong - i'm also getting 1950, but with memory at 1100 (and gpu at 1407). If i set memory to 945, hash rate goes down to ~1700-1750!?

I'm using Vega 56 cards, with 64 bios and registry files for HBM1100. And of course, blockchain drivers and latest version of Cast XMR.

P.S. i have 6 cards, tried with single one and same result. I'm also using only 2GB of RAM, not sure could that be an issue (but i doubt, as all calculations are done inside GPUs).

thanks



One you upgrade to the 64 BIOS, you have to use 64 settings. 1950 H/s @ 935/945 is for 56 un-moded cards!

Try these settings (for your appropriate card and BIOS type) NOTE that it's a starting point, your results may vary slightly:

Vega 64 Hash Rates

1900 Hash/s with 200 watts power consumption

    Core Frequency: -10%
    Memory Clock: 1025 MHz
    Power Limit: -23%

2000 Hash/s with 250 watts power consumption

    Core Frequency: -10%
    Memory Clock: 1095 MHz
    Power Limit: 0

2050 Hash/s with 280 watts power consumption

    Core Frequency: -10%
    Memory Clock: 1105 MHz
    Power Limit: +20%

Vega 56 Hash Rates

1900 Hash/s with 150 watts power consumption

    Core Frequency: -10%
    Memory Clock: 945 MHz
    Power Limit: -22%

2000 Hash/s with 200 watts power consumption

    Core Frequency: -10%
    Memory Clock: 965 MHz
    Power Limit: 0

2050 Hash/s with 225 watts power consumption

    Core Frequency: -10%
    Memory Clock: 990 MHz
    Power Limit: +12%


Hm, sounds strange to me, as i though vega64 bios is used only because of better undervolting and overclocking possibilities. Instead in relative percentages, do you know exact frequencies of GPU at those settings? I'm most interested in lower power consumption (150W) and getting about 1900 Hash/s is just fine to me. Even if cards doesn't complaint about 1100mhz, i believe they will be more relaxed on 945MHz.

And just to be clear, you didn't even change registry for voltage adjusting, just using installed drivers/cards with factory settings?

Btw, is there any explanation of intensity argument, and how to find the best one for the card (except trying all 10)?


Right now I am getting the following using Stock Vega 56 BIOS on "Blockchain Drivers" from AMD and it's been stable for more than 24 hours:

Average Hashrate = 1923 H/s
Fan set to = 2000 RPM
Temp = 60C (Stable)
GPU Freq = 0%
Memory Freq = 935 MHz
Power Limit % = -10
Power draw at the wall (Measured) = 150W to 165W

That sounds quite nice - mine fans are about 3000-3500 in order to keep HBM temp around 60-62C. But i'm using 6 gpu which of course increase total heat and cards are harder to cool - how much cards you have?
However, i'll give it a try (stock bios, unmodified registry).

Thanks.

My HBM is hovering around 63/65C...do you know what the safe maximum is for these temperatures. I read that HBM will usually run hotter than GPU temps as well, but I'm not sure what a safe maximum is?!

I answered my own question:  https://www.reddit.com/r/Amd/comments/72f101/vega_56_safe_hbm_temps/
bostonvex
Member
**
Offline Offline

Activity: 72
Merit: 10


View Profile
December 28, 2017, 06:19:10 PM
 #1317

weird... I'm getting only 1.2KH/s with a Vega 64. All drivers are set.

Could it be due to different mining pool?

I'm using dark-mine.su

What are you're settings? Are you using OverdriveNtool? Sounds like a HBM issue. Did you disable and enable the devices with devcon.exe? check this page http://vega.miningguides.com/
bostonvex
Member
**
Offline Offline

Activity: 72
Merit: 10


View Profile
December 28, 2017, 06:22:57 PM
 #1318

Not using any monitoring script for now. Just trying to make it work reliably, basically.

Failing mobo is like the thing you don't want to happen because it's the one variable you tend to always rule out when you have issues. On my two rigs of RX570's I've got some GPUs chugging at 1950MHz mem speed, while other keep crashing at 1850 and lower -h values (in Claymore). I can't think there's anything wrong with the GPUs, so it's gotta be risers... or the damn mobo.

Let's see how the Vega rig behaves...

No issues so far with version 0.7 and it has been 4 hours.
vladaepro
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
December 28, 2017, 06:23:31 PM
 #1319

I see here that many people claim to get 1950 Hs with memory speed of 945 or so. I'm wondering what i'm doing wrong - i'm also getting 1950, but with memory at 1100 (and gpu at 1407). If i set memory to 945, hash rate goes down to ~1700-1750!?

I'm using Vega 56 cards, with 64 bios and registry files for HBM1100. And of course, blockchain drivers and latest version of Cast XMR.

P.S. i have 6 cards, tried with single one and same result. I'm also using only 2GB of RAM, not sure could that be an issue (but i doubt, as all calculations are done inside GPUs).

thanks



One you upgrade to the 64 BIOS, you have to use 64 settings. 1950 H/s @ 935/945 is for 56 un-moded cards!

Try these settings (for your appropriate card and BIOS type) NOTE that it's a starting point, your results may vary slightly:

Vega 64 Hash Rates

1900 Hash/s with 200 watts power consumption

    Core Frequency: -10%
    Memory Clock: 1025 MHz
    Power Limit: -23%

2000 Hash/s with 250 watts power consumption

    Core Frequency: -10%
    Memory Clock: 1095 MHz
    Power Limit: 0

2050 Hash/s with 280 watts power consumption

    Core Frequency: -10%
    Memory Clock: 1105 MHz
    Power Limit: +20%

Vega 56 Hash Rates

1900 Hash/s with 150 watts power consumption

    Core Frequency: -10%
    Memory Clock: 945 MHz
    Power Limit: -22%

2000 Hash/s with 200 watts power consumption

    Core Frequency: -10%
    Memory Clock: 965 MHz
    Power Limit: 0

2050 Hash/s with 225 watts power consumption

    Core Frequency: -10%
    Memory Clock: 990 MHz
    Power Limit: +12%


Hm, sounds strange to me, as i though vega64 bios is used only because of better undervolting and overclocking possibilities. Instead in relative percentages, do you know exact frequencies of GPU at those settings? I'm most interested in lower power consumption (150W) and getting about 1900 Hash/s is just fine to me. Even if cards doesn't complaint about 1100mhz, i believe they will be more relaxed on 945MHz.

And just to be clear, you didn't even change registry for voltage adjusting, just using installed drivers/cards with factory settings?

Btw, is there any explanation of intensity argument, and how to find the best one for the card (except trying all 10)?


Right now I am getting the following using Stock Vega 56 BIOS on "Blockchain Drivers" from AMD and it's been stable for more than 24 hours:

Average Hashrate = 1923 H/s
Fan set to = 2000 RPM
Temp = 60C (Stable)
GPU Freq = 0%
Memory Freq = 935 MHz
Power Limit % = -10
Power draw at the wall (Measured) = 150W to 165W

That sounds quite nice - mine fans are about 3000-3500 in order to keep HBM temp around 60-62C. But i'm using 6 gpu which of course increase total heat and cards are harder to cool - how much cards you have?
However, i'll give it a try (stock bios, unmodified registry).

Thanks.

My HBM is hovering around 63/65C...do you know what the safe maximum is for these temperatures. I read that HBM will usually run hotter than GPU temps as well, but I'm not sure what a safe maximum is?!

I think (but can't claim) that it slows down automatically somewhere about 70C, so you shouldn't be able to burn it out. But if you want to avoid slowdowns keep it under 65.
Crypto_Future
Member
**
Offline Offline

Activity: 72
Merit: 10


View Profile
December 28, 2017, 06:33:26 PM
 #1320

Really AMAZED at 470 performance.

One question is it better to have tight timmings or higher VRAM mhz for this miner?
Pages: « 1 ... 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 [66] 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 ... 143 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!