Any word on amd vega hash rates?

[Morgon]

For those of you that have Vega hashing at a high rate can I ask what Motherboard and CPU combo you are running?

I have tried two different motherboards (TB250-BTC, Asus Z270-P) and have not managed to get more than 1350 H/s.
Both motherboards I have tried were running Kabylake CPUs (G3950, G4560).

Thinking of trying out a Skylake processor in case there is an issue with Kabylake and Vega.

Thanks

Highly doubt your mobo/CPU combo has any effect. I have one system using an ASRock H110 and G4600, and another setup with an older P8Z77 motherboard and Core i5 (on DDR3!). All my cards are running roughly 1950-70 H/s avg.

1350 sounds like your cards aren't being properly served by the driver. Make sure you have the August Blockchain driver and that you've reset your cards prior to starting your miner.

[altoholic]

Thanks. I have already applied the Aug23 blockchain drivers after running DDU. I have tried to disable the card in device manager but it would not allow me to re-enable the card again. I get a code 43 error.

For those of you that have Vega hashing at a high rate can I ask what Motherboard and CPU combo you are running?

I have tried two different motherboards (TB250-BTC, Asus Z270-P) and have not managed to get more than 1350 H/s.
Both motherboards I have tried were running Kabylake CPUs (G3950, G4560).

Thinking of trying out a Skylake processor in case there is an issue with Kabylake and Vega.

Thanks

Highly doubt your mobo/CPU combo has any effect. I have one system using an ASRock H110 and G4600, and another setup with an older P8Z77 motherboard and Core i5 (on DDR3!). All my cards are running roughly 1950-70 H/s avg.

1350 sounds like your cards aren't being properly served by the driver. Make sure you have the August Blockchain driver and that you've reset your cards prior to starting your miner.

[P00P135]

Thanks. I have already applied the Aug23 blockchain drivers after running DDU. I have tried to disable the card in device manager but it would not allow me to re-enable the card again. I get a code 43 error.

For those of you that have Vega hashing at a high rate can I ask what Motherboard and CPU combo you are running?

I have tried two different motherboards (TB250-BTC, Asus Z270-P) and have not managed to get more than 1350 H/s.
Both motherboards I have tried were running Kabylake CPUs (G3950, G4560).

Thinking of trying out a Skylake processor in case there is an issue with Kabylake and Vega.

Thanks

Highly doubt your mobo/CPU combo has any effect. I have one system using an ASRock H110 and G4600, and another setup with an older P8Z77 motherboard and Core i5 (on DDR3!). All my cards are running roughly 1950-70 H/s avg.

1350 sounds like your cards aren't being properly served by the driver. Make sure you have the August Blockchain driver and that you've reset your cards prior to starting your miner.

If you follow the instructions he gave you with devcon.exe and a batfile it might work.

[R0mi]

I'm clearly much less versed on the inner workings than you, but I always assumed it was simply an issue with initializing the driver on Windows boot vs resetting when all the subsystems are fully loaded.

Although just as a random question, is the reset still required when a system does not have an iGPU? In other words, is it an interaction with the multiple display drivers?

In my experience yes the reset is required on my MSI X370 Ryzen which does not have an internal gpu.

[altoholic]

Thanks but I have already tried the devcon tool and it did the same thing.
It claimed to have enabled it but the device manager still shows it as disabled with a yellow exclamation icon.

Only the non-blockchain drivers allow me to disable and re-enable the card.

If you follow the instructions he gave you with devcon.exe and a batfile it might work.

[jimmy_007vn]

Is it just my rig or everyone else has their AMD setting crash every time we close the Cast XMR?

[rednoW]

Is it just my rig or everyone else has their AMD setting crash every time we close the Cast XMR?

I had this issue with xmr-stak-amd in the past, screen flickers and one of my cards goes to defaults settings.
But now all is smooth both with cast-xmr or stak.
It can be non optimal clock/voltage settings or some other hardware utilities that cause memory paging / I2C errors with such postponed effect

Make sure you are closing miner with 'q' key, not just closing miner window

[billhinge]

For those of you that have Vega hashing at a high rate can I ask what Motherboard and CPU combo you are running?

I have tried two different motherboards (TB250-BTC, Asus Z270-P) and have not managed to get more than 1350 H/s.
Both motherboards I have tried were running Kabylake CPUs (G3950, G4560).

Thinking of trying out a Skylake processor in case there is an issue with Kabylake and Vega.

Thanks

gigabyte z170-ud5 skylake using bios settings here https://www.gigabyte.com/microsite/462/mining.html
64gb ram 3300Mhz
1300w gold psu
monitor plugged into onboard gpu
vega fe in x16 slot using pcie2 setting (ie not in riser)

[dragonmike]

I just had an idea...
Remember the trick we used to do to have the RX5xx working with the older drivers? I.e. Physically copying the content of the older driver's folder onto the new one, effectively tricking Windows into thinking it was using the new one?
Maybe something like this could be attempted with the Vega blockchain drivers too... I mean, if you have driver instability (devices disappearing etc) it could be worth a try...

[dragonmike]

Currently using a Z170A MSI M5 board. Guess it's back to MC to try a Z270 board.

I used the Z170A M5 for my two linux/470/570 rigs. Works flawlessly. But for VEGA was reading it's really finniky with boards. So I broke down and bought the slitghty more expensive (even more so on Amazon) Asrock H110 Pro+ board. I only need 4 of the 13 slots, but people reporting good results for Vega (even though the reviews people complain about it a lot).

Yes I have several of the M5's and they work amazing for 8 570s.

Thank you for this. It's available same day shipping for me. It'll be here this afternoon.

In the meantime I grabbed THREE different boards from MC to try them out as well.

How are you getting on with the new boards, dude?
Expecting my Onda D1800 any day now, can't wait to start inflicting myself the pain of trying to get 6 Vegas to hash...

Each of the 3 have their own problems not allowing them to work correctly. My "same day shipping" order from Amazon never arrived 

Oh man.
That's a major pain in the @ss. If the Vega's work on the Onda mobo I'll definitely let you know.
I've got all the parts for the rig except said mobo and an extension lead so I reckon I'll be ready to crack on some time next week.

You are a masochist   

The blockchain driver is really resource hungry @ 8 cards. It,s going to take ages getting anythi g done on that rig with its subpar cpu....

The Onda D1800 is six-slot.
Really hoping it'll work. Otherwise it's gonna be back to the drawing board...

[duketasos]

Hi,

I am a total noob with 4 Vega64 cards and currently running claymores_cryptonight using the nicehash pool. I don't know how to improve my hash rate and I am not sure if I can use the xmr-stak-amd with the nicehash pool. I don't know if it's trustworthy or safe to use other pools right now as I am new. I would appreciate any guidance on what to do with the rig I have. Right now I am @1690 H/s using claymores.

Is there anyway to go up from here?

Thanks!

hello mate. first read the whole topic it has many tips inside... i'm using cast-xmr and it rocks !! 2050 h/s (56's oem bios 225w each card) you can follow developer's guide. google cast-xmr and read the bitcoin talk topic.

I tried to use cast-xmr but it did not work to connect to the nicehash pool.

[/quote]

all my rigs eth with 580's and vega rigs use same mobo. bio tb250btc g4400 16gb ram (580's 8gb) , never mined at ninehash... mining at web.xmrpool with no probs.

[Quubik]

I just had an idea...
Remember the trick we used to do to have the RX5xx working with the older drivers? I.e. Physically copying the content of the older driver's folder onto the new one, effectively tricking Windows into thinking it was using the new one?
Maybe something like this could be attempted with the Vega blockchain drivers too... I mean, if you have driver instability (devices disappearing etc) it could be worth a try...

I have been testing this also out by my self but cant find detailed documentation what exactly was changed in the blockchain driver.

Possibly would want use the bare minimum from it.

[jyakulis]

For those of you that have Vega hashing at a high rate can I ask what Motherboard and CPU combo you are running?

I have tried two different motherboards (TB250-BTC, Asus Z270-P) and have not managed to get more than 1350 H/s.
Both motherboards I have tried were running Kabylake CPUs (G3950, G4560).

Thinking of trying out a Skylake processor in case there is an issue with Kabylake and Vega.

Thanks

hrm i had that problem and someone on reddit told me to disable and then enable each gpu. magically, i got 1800 h/s.

[jyakulis]

i ran my miner with hellae's guide on my 56's with no bios flash last night.

i woke up and they were running but when i went to power on the monitor it said no signal? i think it's some weird windows setting i need to manage.

[djkice]

4x vega 56 w/ 64 bios and 800mem bios

manual set 1350/1100
i also tried 1350/1050

I have an annoying issue where the cast-xmr will crash. upon reboot the drivers are back to stock voltage etc in overclock.

pretty much have to DDU.

Anyone had this issue before and figure out the cause?

i checked into the logs, it's asif the drivers are getting corrupted..

[R0mi]

4x vega 56 w/ 64 bios and 800mem bios

manual set 1350/1100
i also tried 1350/1050

I have an annoying issue where the cast-xmr will crash. upon reboot the drivers are back to stock voltage etc in overclock.

pretty much have to DDU.

Anyone had this issue before and figure out the cause?

i checked into the logs, it's asif the drivers are getting corrupted..

Can you clarify something:  are you applying  a SoftPowerPlay registry modification, or not?  I ask because like you all my Vega 56s have been flashed with the 64 bios.

If you are using a SoftPowerPlay mod, you can leave it at a stock, safe setting that at least safely reboots.  Then, after rebooting, you can use OverDriveNTool to load whatever custom saved profile you wish.  Only takes a few seconds to hit "load" and then "apply".  No need to retype all the values after each reboot.

[Xandar]

Hi guys. On what model the motherboard can work 8 Vega?
Interested in successful work experience 8 video cards.
Google translate.

[P00P135]

Is it just my rig or everyone else has their AMD setting crash every time we close the Cast XMR?

use the Q key to shutdown miner so it doesnt crash.

[Denson87]

If I try any of the 3 posted reg files on my XFX Vega56@64 Bios i get a green Screen at Windows 10 Start and cant get into Windows. Any Ideas why?

[Permonik]

Is it just my rig or everyone else has their AMD setting crash every time we close the Cast XMR?

Yes, me too.