Topic: [Cast XMR] high speed XMR/CryptoNight miner for RX Vega GPUs (2 KHash/s) - page 74. (Read 206404 times)

Hi. I am having weird Socket Error on Cast XMR, when trying to run it on Nicehash pool (cryptonight.usa.nicehash.com:33355).
No such errors on Claymore or XMR Stak, but I have low or unstable hash rate with these, hence I want to try Cast XMR.
I am only pointing Cast XMR to the server and wallet.
I would appreciate any ideas.

Thanks. I lowered Mem_P3 to 1050 first > still crashed. Then I lowered to 1000 and it has mined for 36 hrs continuously

Thanks again!

NO, but seriously LOL!!!!!  What are you even talking about?? Cryptonight coins are the most profitable coins you can mine bar any card anywhere on this planet. If you have vegas you you have the most profitable mining cards arguably one can buy paired with the fastest miner.

6 1080Ti vs 6 Vega 64s

https://whattomine.com/coins

Compare for yourself.

I don't know why.... just so much dumb posted here all the time.

Just a quick update, been mining using cast 0.8 for 4 weeks now with no problems whatsoever. I really wanna go on for longer but I might switch to something else since monero mining has slowed down so much. It wouldn't be so bad if I could get more vegas but those cards are hard to get, almost impossible for close to msrp.

Didn't you start a whole thread about how you're mining straight to Kraken? Which uses integrated payment id.

If you click help/getting started on your pools website, it should give you examples. Generally, it's Wallet_Address.Payment_ID

I swear I found it on dev papers, but I cannot find it any more.

Anyway here is my bat. file  for ETN with 7 attempts reconnects and 8 hours restarts, you can change it to your liking.



@echo off

echo -------------------------------------------------------------------
echo Restarts the miner every 8H //you can set it to your own liking
echo -------------------------------------------------------------------
echo:

set executable=cast_xmr-vega.exe
set commandline=-S etn-jp1.nanopool.org:13333 -u etnkJyyyyyyyH5ChYSeXaJSayrzZJUBYYndkxCNsidxxxxxxxxxqcUzuAb1HkXFpcm3AzjFTZQbcdyx xxxx.Lola/[email protected] p z -ftime 1 --opencl 1 -G 0,1,2,3 --fastjobswitch  --nonicehash --reconnects 7%*
set commandline=-S etn-asia1.nanopool.org:13333 -u etnkyyyyyyChYSeXaJSayrzZJUBYYndkxCNsidxxxxxxxxxqcUzuAb1HkXFpcm3AzjFTZQbcdyxxxxx .Lola/[email protected] p z -ftime 1 --opencl 1 -G 0,1,2,3 --fastjobswitch  --nonicehash --reconnects 7%*
set commandline=-S etn-eu1.nanopool.org:13333 -u etnkJyyyyyyyyyyyyyyaJSayrzZJUBYYndkxCNsidxxxxxxxxxqcUzuAb1HkXFpcm3AzjFTZQbcdyxx xxx.Lola/[email protected] p z -ftime 1 --opencl 1 -G 0,1,2,3 --fastjobswitch  --nonicehash --reconnects 7%*


set runforseconds=28800
set restartinseconds=15
set /a counter=15
timeout 15
:start
start "cast_xmr-vega" %executable% %commandline%
echo:
echo The program is going to run for %runforseconds% seconds
timeout %runforseconds%
taskkill /f /im %executable%
cd
Mine.bat
echo:
echo Restarting the app in %restartinseconds% seconds (%counter%)
timeout %restartinseconds%
set /a counter+=1
echo:
echo:
goto start

Sorry but I cannot find it. I've read it all, and... can't see it. Dare to give us a hint?

If you have not done it already, Try to check your MB Bios if the PCI slots settings are on AUTO and switch them to Gen 1 or Gen 2 .  I had a similar problem of one Vega locking after many hours of flawless hashing. it was solved by changing from AUTO to Gen 1.

I would lower the Mem_P3 for card that goes to nirvana. BTW for Fan_Target I wouldn't use value higher than 60.

I'm having troubles with a 4 * Vega 64 rig. After 6-12 hours, cast locks up and one card will be hashing at zero. Probably temp related throttling?

What settings should I start to lower to troubleshoot? P6/P7/M3 in ntools? or the reg file for HBM?

Right now I'm using;

Reg File: 1100mhz 905mv

OverdriveNtool:
[Profile_0]
Name=Vega64
GPU_P0=852;800
GPU_P1=991;900
GPU_P2=1084;950
GPU_P3=1138;1000
GPU_P4=1200;1050
GPU_P5=1401;1100
GPU_P6=1212;950
GPU_P7=1408;905
Mem_P0=167;800
Mem_P1=500;800
Mem_P2=800;950
Mem_P3=1100;905
Fan_Min=3000
Fan_Max=4900
Fan_Target=75
Fan_Acoustic=2400
Power_Temp=85
Power_Target=0

How long have you been running it for? Stable so far?

Boo Yar
Got 1300SOC timings running on a Vega 64 BLOCKCHAIN DRIVERS

Hashing at 2218H/s.
HBM at 1225 v1.35
Core 1087 v1
Core Temp 37C
HBM Temp 42C
Stock Bios
Win 10. Aug Blockchain. Cast XMR 0.8

5 more on the memory starts to error.

Reg Mod for this, Again Vega 64 Powercolor, stock bios NOT water cooled bios.

Lowers the p7 so that at -30 hits 1087 on this card. Starts the memory at 1175 so do not even consider using if your card cant do this kind of timings already. The second upload is the bios mod for the same stock 64 bios but at 1200soc. Gives 900mv at -30% core = 980mhz, HBM starts at 1170 on that. Pulls ~2000 with HBM upped to 1190.

1300SOC - slightly lower p7 core
https://drive.google.com/file/d/1YVtLP6XUidneMNW7J_XgKsjLELriMM6x/view?usp=sharing

1200SOC - lower core speed for p5-p7 and voltage.

https://drive.google.com/file/d/1epe-KoXk5wUPn02H7D5qeWAleuLC6DHj/view?usp=sharing

Both cards EK water-cooled. 1300soc is running at 36C and the 1200soc is at 38C.

Still there is some limitation from software side. Some are still limited to 8GPU's. I have rig with 10*1070ti and tpruvot ccminer 2.2.3/4 can't run hmq1725 stable on it. While other miners/algos work well. If I run with any 8 of them - it's OK.
Also Afterburner is still not capable to show more than 8 GPU's.

Windows HAD an 8 GPU limitation, the fall creators update and subsequent AMD/Nvidia drivers fixed it. Now we do not know if any OS or Driver limit exists anymore (max ive read people being able to do is 22 GPU's using mining cards and splitters etc).

Anyone know how to fix this when you have over 4 GPU's? when you have over 4 you get this error:
https://github.com/fireice-uk/xmr-stak-amd/issues/174

I'm getting MicroHTTPD: HTTPSession Exception: read_some: End of file. On one rig after some time.
Anyone knows what it is?

Pretty sure the “myth” started as windows cannot run more than 8 Vega GPUs. Then somehow evolved into it cannot run more than 8 GPUs. It is actually not windows that is the issue anyway.

My understanding is, it is the blockchain drivers that allow only 8 Vega GPUs. Never was a windows limitation anyway.

Windows to date will allow you to run 13 total 8 of a kind +5 of the other or a combination there of.  If you want more than 13 regular cards, then you must buy P106 or P104 cards.  I have this issue running windows to get 19 cards working on the Asus B250 Mining Expert.