[Cast XMR] high speed XMR/CryptoNight miner for RX Vega GPUs (2 KHash/s)

[carlo_0000]

Hi guys.

I have a problem with my vegas.

I have a MSI z370 PC PRO motherboard and 2 vegas plugged in.
With only one vega connected i hace no problems at all. works fine.
But when am trying to connect the second, and start mining with the second i got a crash when i start cast xmr.
When i am using a only one vega AMD settings shows normal, if 2 vegas are connected, HBCC memory option in amd display settings just disapear.

1st vega is connected to PCI-E x16
2nd vega is connected to PCI-E x4

iI have more PCI-E slots, but they are mini PCI, and i need a riser in order to use them.
I have tryied to change in BIOS settings enable minngng, but am still having the same crash when 2nd vega start mining.
Do you think if I buy a riser and connect the second vega to a mini PCI, can solve the problem?.

rest of my specs are:
i5 8600K
SSD 250
16 gb ram
2x vegas 56

Thanks all!!

you forgot to disable  crossfire

[Cyan_Antares]

Hi guys.

I have a problem with my vegas.

I have a MSI z370 PC PRO motherboard and 2 vegas plugged in.
With only one vega connected i hace no problems at all. works fine.
But when am trying to connect the second, and start mining with the second i got a crash when i start cast xmr.
When i am using a only one vega AMD settings shows normal, if 2 vegas are connected, HBCC memory option in amd display settings just disapear.

1st vega is connected to PCI-E x16
2nd vega is connected to PCI-E x4

iI have more PCI-E slots, but they are mini PCI, and i need a riser in order to use them.
I have tryied to change in BIOS settings enable minngng, but am still having the same crash when 2nd vega start mining.
Do you think if I buy a riser and connect the second vega to a mini PCI, can solve the problem?.

rest of my specs are:
i5 8600K
SSD 250
16 gb ram
2x vegas 56

Thanks all!!

yes, disable crossfire. This excellent guide has some tips to achieve that.

http://vega.miningguides.com/

[Apneal]

New --forcecompute switch does not work for Vega yet?

[dragonmike]

New --forcecompute switch does not work for Vega yet?

According to AMD, all of the features that benefit compute workloads are already enabled by default in Vega's architecture, so the switch isn't necessary. It's basically for other RX GPUs.

[dragonmike]

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?

Edit: up until it stops, the miner reports 0 errors, if that's of any help...

Edit2: increased the hbm voltage a notch and it seems to be mining for now... Current overdriventool file looks like this:
[Profile_0]
Name=Vega64
GPU_P0=852;900
GPU_P1=991;900
GPU_P2=1084;900
GPU_P3=1138;900
GPU_P4=1150;900
GPU_P5=1202;900
GPU_P6=1212;900
GPU_P7=1376;905
Mem_P0=167;900
Mem_P1=500;900
Mem_P2=800;900
Mem_P3=1050;915
Fan_Min=3600
Fan_Max=4900
Fan_Target=75
Fan_Acoustic=2400
Power_Temp=85
Power_Target=0

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

[zythros]

A ping monitor would be nice if it'd be simple to implement like Claymore's miner, as of right now I use claymore's to first check the pools accepted share ping as of right now I'm at 150 ping on xmrpool but I'm still getting 5% late invalid shares.

 It was 10% late shares with a 250 ping on Nanopool that would of end up costing me a lot of money. I've used the command promt ping prompt but that wasn't accurate enough and it doesn't allow me to ping the port only the address for example I pinged nanopool's US.west server closest to me and average ping came back to me as 110 but when I mine it's 200-250

Is anyone else getting a high amount of late shares with a similiar ping? I know my ping is high it's 100 ms default was just wondering if this is normal for me?

[bostonvex]

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.

[dragonmike]

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.

Basically yes, it hangs. Stops sending output and doesn't mine anymore.
It's most certainly overclock/undervolt related, just trying to figure out which, and troubleshoot efficiently.

[bostonvex]

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.

Basically yes, it hangs. Stops sending output and doesn't mine anymore.
It's most certainly overclock/undervolt related, just trying to figure out which, and troubleshoot efficiently.

Gotcha. I have same behavior with stock bios, stock reg. Started when I upgraded to 0.8.1. You seem confident that it is OC/uV. Thanks for clarifying and let me know what you find. I'm going to downgrade to 0.7 and see if it fixes the issue on my end. Oh yes, and ofcourse I swapped out mobos.

[dragonmike]

Does the memory voltage in OverdriveNtool actually even do anything? I see hbm voltage @ 1.356V in HWinfo64. Mem clock 1050, SoC clock 1200.
HMB temps are fine between 50-55C.


Set GPU clocks now @ 1408 (P7), just under 0.9V (905mV set for P7)

I do seem to suddenly get the infamous sudden hashrate drop however. Hmmm...

[Cyan_Antares]

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.

[pyr8]

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

[dragonmike]

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.

[vladaepro]

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.

[vladaepro]

For all who may be interested, i can share my 'hardware' rig monitor, which monitor both rig presence (local ping) and pool hash rate, and perform hard reset if any of two stuck. It's based on cheap ESP8266 (NodeMCU) controller which do all the work without any additional hardware - just need to connect wires from mobo (reset, power led and gnd).

Here's how very simple web interface looks like


https://www.dropbox.com/s/tj46hxv0sdzcpeg/rigsmonitor.png?dl=0

[dragonmike]

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...

[Cyan_Antares]

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]

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?

[GrassBite]

Can we get support for sumokoin added?

Pretty Please?

[jyakulis]

Can we get support for sumokoin added?

Pretty Please?

It already has it...