Any word on amd vega hash rates?

[GingerTiger]

Hope Windows 10 Fall Creator's Update will allow 13 Vegas on an H110 motherboard.  That is going to be sweet.

I agree I hope that this will happen, I would buy a few rigs

[Rampage89]

Does anyone have Vega 56 rig running 24/7 for weeks? I am mainly interested whether the stability can be achieved without touching for extended period. I currently run Vegas 64 with no issues. Is there any diffference?

[ingyenfrag]

Hi Guys,

I have a very strange issue :

In "Device Manager" it show my 4 cards, but in AMD Settings I have only 2 cards and when i launch OverDrivenTool it only show 4 cards, but for 2 oh thme it says "This GPU is not supported"

Can someone have seen this kind of issue? And how to solve it ?

Thx in advance

Use DDU to uninstall driver. Reinstall blockchain driver.

[ingyenfrag]

Does anyone have Vega 56 rig running 24/7 for weeks? I am mainly interested whether the stability can be achieved without touching for extended period. I currently run Vegas 64 with no issues. Is there any diffference?

I have 3 rigs. All stable, no problem.

[l1xx]

Hi Guys,

I have a very strange issue :

In "Device Manager" it show my 4 cards, but in AMD Settings I have only 2 cards and when i launch OverDrivenTool it only show 4 cards, but for 2 oh thme it says "This GPU is not supported"

Can someone have seen this kind of issue? And how to solve it ?

Thx in advance

Reinstall your drivers.

[teuflor]

anyone see a grey screen and crash when running more than 2 gpu on cast?

on a single gpu it works fine, but when i add more grey artifcats then crash,tried two separate motherboards
it only does thiswith the aug23 blockchain drivers , the ronbin hood ones dont crash but 1500 hs vs 1950

I hit a similar problem, but it was the same with XMR-Stak or Cast.  I have a MSI X370 and could not get past three GPUs without a blue screen/crash.  Changed risers, cables, Vega cards, PCIe slots, settings, on and on.

Finally solved it:  Used DDU to strip everything out.  Went directly to Microsoft's site and downloaded the fall creators update (takes a while).  That loaded the non-blockchain drivers and for the first time I could mine with 5 Vegas on that motherboard (but slow speeds).  Uninstalled the newest drivers, reinstalled blockchain drivers.  It's all good now.

hmm i tried this several times, I have a window image that alrrady contsins the fall creators update included and did this with a fresh install still the same deal, Ill try it again i guess , thanks

Have  you tried newest amd in compute mode? With rx 4xx/5xx there is no need of blockchain driver anymore.

I tried those drivers, had problems too

**update**
following Romis instructions i did a clean install, this time though i did not give the default driver time to install, I ran gpedit.msc and disabled the windows updates and driver updates in Immediatley rebooted the box.

<snip>

I think a lot of people experience crashes with multiple Vegas because they install the driver and immediately reboot.  The most important thing I found was that when you install the block chain driver, CLOSE the AMD installer at the end of the installation but don't reboot. Instead, use Regedit to go into the same directory as the SoftPowerPlay mod, and change "EnableAutoCrossfire" to "0" decimal value for every card -- e.g., folder 000, folder 001, folder 002, folder 003, folder 004.  Then reboot.  The pathway is listed at the top of every SoftPowerPlay mod that you download.  Turn off auto cross fire in the Registry values, and also in the AMD Relive settings application as well.

Second interesting thing I found was that it's best not to get too aggressive with your basic SoftPowerPlay settings.  Keep P7 in the 1401-1408/900-905 range; P3 in the 1050-1070/850-900 range (Monero settings).  Too far outside those values and SoftPowerPlay causes a blue screen/crash *on startup*.  Once you boot, however, you can use OverDriveNTool 0.2.1 to tweak the settings card by card and get stable performance.  But you can't always write those optimal values directly into the SoftPowerPlay table and get a stable reboot.  Just doesn't work, I don't know why, but that has been my experience.  I see people setting 5 or 6 cards to 1100 memory across the board -- no wonder your rig is crashing.  Not every air cooled Vega 56 can handle P3 at 1100.  Your base settings should be dialed back.  Then experiment card by card once your rig is booted.

You can save some time by taking one SoftPowerPlay Registry mod and copying that as several files -- RegMod001, RegMod002, RegMod003, RegMod004, RegMod005 -- edit each of those files for one particular card, e.g., edit the "000," "001," "002," so you don't have to manually do this each and every time.

thanks for sharing your experience! I have some problems with my 3rd rig. 6 x Vega on a Z170 Pro Gaming Board. in Windows is all ok, after installing my Blockchain driver -> Reboot. Everything ok. Use the reg keys for softplaytable -> cant boot into windows.

i will try to disable crossfire in front of using the softplay table reg

but i have only "Enable"crossFireAutoLink" in the reg keys, did you mean thad one?

[l1xx]

anyone see a grey screen and crash when running more than 2 gpu on cast?

on a single gpu it works fine, but when i add more grey artifcats then crash,tried two separate motherboards
it only does thiswith the aug23 blockchain drivers , the ronbin hood ones dont crash but 1500 hs vs 1950

I hit a similar problem, but it was the same with XMR-Stak or Cast.  I have a MSI X370 and could not get past three GPUs without a blue screen/crash.  Changed risers, cables, Vega cards, PCIe slots, settings, on and on.

Finally solved it:  Used DDU to strip everything out.  Went directly to Microsoft's site and downloaded the fall creators update (takes a while).  That loaded the non-blockchain drivers and for the first time I could mine with 5 Vegas on that motherboard (but slow speeds).  Uninstalled the newest drivers, reinstalled blockchain drivers.  It's all good now.

hmm i tried this several times, I have a window image that alrrady contsins the fall creators update included and did this with a fresh install still the same deal, Ill try it again i guess , thanks

Have  you tried newest amd in compute mode? With rx 4xx/5xx there is no need of blockchain driver anymore.

I tried those drivers, had problems too

**update**
following Romis instructions i did a clean install, this time though i did not give the default driver time to install, I ran gpedit.msc and disabled the windows updates and driver updates in Immediatley rebooted the box.

<snip>

I think a lot of people experience crashes with multiple Vegas because they install the driver and immediately reboot.  The most important thing I found was that when you install the block chain driver, CLOSE the AMD installer at the end of the installation but don't reboot. Instead, use Regedit to go into the same directory as the SoftPowerPlay mod, and change "EnableAutoCrossfire" to "0" decimal value for every card -- e.g., folder 000, folder 001, folder 002, folder 003, folder 004.  Then reboot.  The pathway is listed at the top of every SoftPowerPlay mod that you download.  Turn off auto cross fire in the Registry values, and also in the AMD Relive settings application as well.

Second interesting thing I found was that it's best not to get too aggressive with your basic SoftPowerPlay settings.  Keep P7 in the 1401-1408/900-905 range; P3 in the 1050-1070/850-900 range (Monero settings).  Too far outside those values and SoftPowerPlay causes a blue screen/crash *on startup*.  Once you boot, however, you can use OverDriveNTool 0.2.1 to tweak the settings card by card and get stable performance.  But you can't always write those optimal values directly into the SoftPowerPlay table and get a stable reboot.  Just doesn't work, I don't know why, but that has been my experience.  I see people setting 5 or 6 cards to 1100 memory across the board -- no wonder your rig is crashing.  Not every air cooled Vega 56 can handle P3 at 1100.  Your base settings should be dialed back.  Then experiment card by card once your rig is booted.

You can save some time by taking one SoftPowerPlay Registry mod and copying that as several files -- RegMod001, RegMod002, RegMod003, RegMod004, RegMod005 -- edit each of those files for one particular card, e.g., edit the "000," "001," "002," so you don't have to manually do this each and every time.

thanks for sharing your experience! I have some problems with my 3rd rig. 6 x Vega on a Z170 Pro Gaming Board. in Windows is all ok, after installing my Blockchain driver -> Reboot. Everything ok. Use the reg keys for softplaytable -> cant boot into windows.

i will try to disable crossfire in front of using the softplay table reg

but i have only "Enable"crossFireAutoLink" in the reg keys, did you mean thad one?

apply the reg files one by one and reboot after each one. This way you will identify the card that is not accepting the settings. Make sure you do restore points before each apply, so you can easily revert it.
After you identify a problematic card - disconnect it, and continue with the rest untill you know which work with the mod and which not. After that - try a different mod, usually with lower memory settings.

[dragonmike]

Ok so I'm about to get a 6x Vega56 build done on that Onda D1800 board.
I'm a little unsure about all the stuff I'm reading above. What are these mods you keep referring to? I thought oc/voltage settings could be done within the Claymore miner directly? Also, I was under the impression there was no need for BIOS mods on Vegas (esp. 56's) if you intend to mine Crypronight?

I might be misguided... Please help me clear the confusion!

[teuflor]

Ok so I'm about to get a 6x Vega56 build done on that Onda D1800 board.
I'm a little unsure about all the stuff I'm reading above. What are these mods you keep referring to? I thought oc/voltage settings could be done within the Claymore miner directly? Also, I was under the impression there was no need for BIOS mods on Vegas (esp. 56's) if you intend to mine Crypronight?

I might be misguided... Please help me clear the confusion!

just read the last 20-30 pages here, and all your questions will be answered!

[Ledipaa]

Ok so I'm about to get a 6x Vega56 build done on that Onda D1800 board.
I'm a little unsure about all the stuff I'm reading above. What are these mods you keep referring to? I thought oc/voltage settings could be done within the Claymore miner directly? Also, I was under the impression there was no need for BIOS mods on Vegas (esp. 56's) if you intend to mine Crypronight?

I might be misguided... Please help me clear the confusion!

https://www.reddit.com/r/MoneroMining/comments/74hjqn/monero_and_vega_the_definitive_guide/

All you need, just a little registry mods in order to take full advantage of your vegas.

Dont mind the RAM size and HBCC mem part. 4GB ram is enough and HBCC has nothing to do with mining, just disable and enable your cards from device manager after every reboot.

[dragonmike]

Ok so I'm about to get a 6x Vega56 build done on that Onda D1800 board.
I'm a little unsure about all the stuff I'm reading above. What are these mods you keep referring to? I thought oc/voltage settings could be done within the Claymore miner directly? Also, I was under the impression there was no need for BIOS mods on Vegas (esp. 56's) if you intend to mine Crypronight?

I might be misguided... Please help me clear the confusion!

https://www.reddit.com/r/MoneroMining/comments/74hjqn/monero_and_vega_the_definitive_guide/

All you need, just a little registry mods in order to take full advantage of your vegas.

Dont mind the RAM size and HBCC mem part. 4GB ram is enough and HBCC has nothing to do with mining, just disable and enable your cards from device manager after every reboot.

Much appreciated - that's exactly what I needed. I shall dig into this thread with great appetite and hopefully digest and assimilate it accordingly!

[R0mi]

thanks for sharing your experience! I have some problems with my 3rd rig. 6 x Vega on a Z170 Pro Gaming Board. in Windows is all ok, after installing my Blockchain driver -> Reboot. Everything ok. Use the reg keys for softplaytable -> cant boot into windows.

i will try to disable crossfire in front of using the softplay table reg

but i have only "Enable"crossFireAutoLink" in the reg keys, did you mean thad one?

Yes, that one.  Set "EnableCrossFireAutoLink" to "0" after installing the drivers but before rebooting.  You have to close out of the AMD installer and not reboot; go into RegEdit.

But I don't think that is your problem.  Try a different SoftPowerPlay table -- find one that let's you reboot. 

[soothaa]

I'm about to tear my hair out. I have been fighting with these damn VEGAs all weekend!

After nearly a dozen hours I have a single Vega card working in my board.

Fresh install of Fall Creative Update
Aug 23rd Blockchain Drivers
XMR CAST 0.6

HBM: 990MHz

Mining XMR at 1,400h/s

Does anyone have any ideas why I'm so low?

[ingyenfrag]

I'm about to tear my hair out. I have been fighting with these damn VEGAs all weekend!

After nearly a dozen hours I have a single Vega card working in my board.

Fresh install of Fall Creative Update
Aug 23rd Blockchain Drivers
XMR CAST 0.6

HBM: 990MHz

Mining XMR at 1,400h/s

Does anyone have any ideas why I'm so low?

In device manager disable and enable cards one by one.

[dallase]

I'm about to tear my hair out. I have been fighting with these damn VEGAs all weekend!

After nearly a dozen hours I have a single Vega card working in my board.

Fresh install of Fall Creative Update
Aug 23rd Blockchain Drivers
XMR CAST 0.6

HBM: 990MHz

Mining XMR at 1,400h/s

Does anyone have any ideas why I'm so low?

It sounds like your devcon is not resetting the driver.  Are you running as admin?

Maybe it was just coincidence, but I had a 1300 hash rate at one point until I upped virtual memory to 32GB.

[Morgon]

Maybe it was just coincidence, but I had a 1300 hash rate at one point until I upped virtual memory to 32GB.

This is possible. Current community understanding is that you should have 16GB Virtual Memory for each Vega. I made the mistake of getting 32GB of physical RAM, and I'm only using 10% (more if I have other programs running like HWinfo64) - never more than 8GB so far.

[Tao1123]

Hello all,

I am building my first mining Rig with the below components.

6x Sapphire RX Vega 56 air cooled
Asrock Fatal1ty B250 Gaming K4 motherboard
Intel Celeron G3930 Kaby Lake Dual-Core 2.9 GHz LGA 1151 Processor
2x G.SKILL NT Series 4GB DDR4 SDRAM 2133 Ram
1x EVGA 600w Bronze PSU for motherboard, cpu, and risers
2x HP DPS-1200w with Breakout Board for the cards
6x UBIT PCIE risers
Windows 10 Pro 64-bit

For simplicity sake lets number the pcie slots on the motherboard 1-6 right to left starting with the one closest to the CPU, slot 2 and 5 are full size PCI slots the rest are PCIE extension slots.  Same thing with the GPUs, 1-6 right to left, each one is meant to be plugged in to the corresponding PCIE slot on the motherboard. I assembled everything except I left the PCIE risers unplugged from the Motherboard for now and loaded windows onto the HDD.  Once that was done I plugged in all the cards and loaded AMD driver 17.30.15.  It recognized 4 of the cards after restart but 2 of them were getting code 43. 

At this point I realized I had forget to set my Motherboard Bios so I followed this guide: https://blockoperations.com/gpu-miner-bios-settings-asrock-b250-gaming-k4-motherboard/ Afterwards I was getting 1 card.  I decided to start over and try to load each driver individually. 

Card 1 worked intermittently in PCIE slot 1 I was able to reload the driver on to it.  When placed into slot 2 the first fullsize slot it worked everytime with no problem.  Thinking it may be a power issue to explain the intermittent connectivity I swapped PSU and still nothing, then tried cables, still same issue.  I resigned myself to the intermittent connectivity and moved on to card 2.  Card 2 slot 2 no issues at all I tried it in PCI slot 1, 2, and 3 and it worked in all of them.  Card 3 was not recognized in any slot except slot 2 and when it was I attempted to load the driver and the screen would intermittently go in and out.  I would get a white noise screen from time to time as well.  Loading the driver failed multiple times and gave me error 1803.  I followed several steps to rectify that issue and finally had a successful load albeit with the screen still intermittently going in and out. 

At this point I figured I would try to run with just the 3 cards.  Card 1 in slot 1, card 2 in slot 3, and card 3 in slot 2.  On boot the rig would power up then powerdown after a few seconds, it did this twice and the third time it finally booted.  When i was finally in windows only card 2 and 3 were showing activity lights and the machine only recognized the 2.  Device manager showed 3 hidden cards claiming they were not connected. 

At this point I was informed that Driver 17.30.xx was corrupt on the Vegas and I needed to turn off quick boot and sleep mode.  I also made it so windows update will not download hardware drivers.  So I turned them off and plugged in all 6 cards.  I then rebooted in safe mode and ran DDU.  Once done I restarted and leaving all cards plugged in I ran AMd driver 17.8.2 as I was told that was a stable build.  The motherboard continued to reboot several times on start up before it booted fully.  With all cards in it would start to boot then the screen would go black.  Additionally 3 cards would show activity lights.  I let it sit with a black screen for 30 minutes before I manually shut it down and tried again.  I did this several times sometimes it would get to the windows 10 welcome screen then go black, sometimes it wouldn't.  At this point I unplugged 3 cards from the Motherboard and reset the motherboard bios back to default.  It would still start to run then stop on power up.  After resetting the bios it was only recognizing 1 card and Nicehash Miner was not recognizing a single GPU. 

At this point I stopped in frustration.  I am probably going to start over entirely.  First run DDU on all cards.  Then wipe the HDD and reinstall windows.  I will adjust windows before ever putting a GPU in.  Then update drivers on each GPU 1 by 1 only ever having 1 gpu in at a time.  I am at a complete loss as to what I am doing wrong or what is not working.  Any help at all will be appreciated.

[soothaa]

I'm about to tear my hair out. I have been fighting with these damn VEGAs all weekend!

After nearly a dozen hours I have a single Vega card working in my board.

Fresh install of Fall Creative Update
Aug 23rd Blockchain Drivers
XMR CAST 0.6

HBM: 990MHz

Mining XMR at 1,400h/s

Does anyone have any ideas why I'm so low?

In device manager disable and enable cards one by one.

Tried that repeatedly..

Maybe it was just coincidence, but I had a 1300 hash rate at one point until I upped virtual memory to 32GB.

This is possible. Current community understanding is that you should have 16GB Virtual Memory for each Vega. I made the mistake of getting 32GB of physical RAM, and I'm only using 10% (more if I have other programs running like HWinfo64) - never more than 8GB so far.

So I just ran out and grabbing 16GB of physical RAM (up from 4GB) and now I'm getting 1 running steady at 2000+. Holy cow 16 per VEGA? I think I set like 40 at the moment for 2 but I'll check. Now I'm on trying to get the second one to work..

[Morgon]

Holy cow 16 per VEGA? I think I set like 40 at the moment for 2 but I'll check. Now I'm on trying to get the second one to work..

On a dedicated mining rig, that's easily done with a 128GB M.2 chip, like my favorite  <$60 ADATA.

It's only 118GB usable, but after Windows itself, and setting my VirtMem to 80GB (adding a 5th GPU this week), I still have 7 GB left. You'd have to be a little creative (stripping out Windows components) to get enough for 6, I suppose, but I'm sure it could be done. Of course, the 256GB is only $90 (and traditional SSDs are $80, but I really love the compact 'package' by using M.2).

[soothaa]

Holy cow 16 per VEGA? I think I set like 40 at the moment for 2 but I'll check. Now I'm on trying to get the second one to work..

On a dedicated mining rig, that's easily done with a 128GB M.2 chip, like my favorite  <$60 ADATA.

It's only 118GB usable, but after Windows itself, and setting my VirtMem to 80GB (adding a 5th GPU this week), I still have 7 GB left. You'd have to be a little creative (stripping out Windows components) to get enough for 6, I suppose, but I'm sure it could be done. Of course, the 256GB is only $90 (and traditional SSDs are $80, but I really love the compact 'package' by using M.2).

Hasn't fixed my problem sadly.

Have the Virtual Memory set to 48GB with 3 Vegas. Set my threads to:

   { "index" : 0, "intensity" : 2016, "worksize" : 8, "affine_to_cpu" : false },
   { "index" : 0, "intensity" : 1700, "worksize" : 8, "affine_to_cpu" : false },
   { "index" : 1, "intensity" : 2016, "worksize" : 8, "affine_to_cpu" : false },
   { "index" : 1, "intensity" : 1700, "worksize" : 8, "affine_to_cpu" : false },
   { "index" : 2, "intensity" : 2016, "worksize" : 8, "affine_to_cpu" : false },
   { "index" : 2, "intensity" : 1700, "worksize" : 8, "affine_to_cpu" : false }

And am getting "cl out of host memory" errors.