Topic: [Cast XMR] high speed XMR/CryptoNight miner for RX Vega GPUs (2 KHash/s) - page 85. (Read 206404 times)
January 05, 2018, 12:51:50 PM
this is so good miner, ty sir! got the most high hash than other miner. and cooler GPU, i like it
January 05, 2018, 09:13:22 AM
I've noticed that when Windows blocks CastXMR from accessing a GPU because of aggressive overclocking, the software doesn't handle it very gracefully. The affected GPU stops reporting its hashrate every five seconds, and after a few minutes the software hangs entirely and multiple ^C are needed to terminate the run, assuming that the system doesn't freeze entirely and need a warm reset.
A useful feature would be for CastXMR to recognize that if it is accessing a list of GPUs, each of them should report results periodically, and if one of them goes missing for, say, twice the running average time between results, then it should be considered dead, and a clean restart of CastXMR should be initiated.
Or better yet, if CastXMR could perform a disable/enable of the problem card and then reinitialize it individually, so that none of the other cards had to be bothered.
With a Mining Expert 19-slot motherboard running a pile of aggressively overclocked Vegas, you're more likely to wedge one of the cards than usual, and being able to recover gracefully from that situation would substantially improve the average hashrate.
A useful feature would be for CastXMR to recognize that if it is accessing a list of GPUs, each of them should report results periodically, and if one of them goes missing for, say, twice the running average time between results, then it should be considered dead, and a clean restart of CastXMR should be initiated.
Or better yet, if CastXMR could perform a disable/enable of the problem card and then reinitialize it individually, so that none of the other cards had to be bothered.
With a Mining Expert 19-slot motherboard running a pile of aggressively overclocked Vegas, you're more likely to wedge one of the cards than usual, and being able to recover gracefully from that situation would substantially improve the average hashrate.
It's not really a problem with CAST-XMR now is it. That is you choosing to overdrive the card and then demand that that the tool fix it for you. Maybe you should spend more time accepting a stable hash rate per card and live with it. Its really a driver issue anyway and you are taking risks when overclocking that you will put the system into an unrecoverable state.
I personally don't need a feature in CAST that disables the cards and I don't think that would be helpful for people who have configured their systems correctly. I reboot once a week for windows updates, other than that I don't really look at the rigs.
If you need these bandaid scripts to monitor your hash rate cause it drops or your cards hang you have other problems that are not associated with the miner. I would rather the dev spend time improving the miner efficiency rather than adding some lame monitoring function that is completely unnecessary.
Oh and by the way I use Wattman. YIKES!
Really? Unbelieveble!
I'm using cast_xmr_vega with 6x VEGA56. Everyday and very often I need to restart miner or PC. VEGA's are not modded.
Everything I do before running the miner is run devcon.exe for cli enable/disable GPU's and then Overdriven tool with overclock settings.
Very often is output paused... until S is pressed and after is all messages displayed with OUTDATED result.
I never had a ban from poolserver but last 2 days 3 times! Sometimes freezing after Difficulty changed message.
When I press Q displayed 'quitting..' and nothing happend.
Right click top of command window > properties > options tab > uncheck quick edit mode
January 05, 2018, 09:03:07 AM
I've noticed that when Windows blocks CastXMR from accessing a GPU because of aggressive overclocking, the software doesn't handle it very gracefully. The affected GPU stops reporting its hashrate every five seconds, and after a few minutes the software hangs entirely and multiple ^C are needed to terminate the run, assuming that the system doesn't freeze entirely and need a warm reset.
A useful feature would be for CastXMR to recognize that if it is accessing a list of GPUs, each of them should report results periodically, and if one of them goes missing for, say, twice the running average time between results, then it should be considered dead, and a clean restart of CastXMR should be initiated.
Or better yet, if CastXMR could perform a disable/enable of the problem card and then reinitialize it individually, so that none of the other cards had to be bothered.
With a Mining Expert 19-slot motherboard running a pile of aggressively overclocked Vegas, you're more likely to wedge one of the cards than usual, and being able to recover gracefully from that situation would substantially improve the average hashrate.
A useful feature would be for CastXMR to recognize that if it is accessing a list of GPUs, each of them should report results periodically, and if one of them goes missing for, say, twice the running average time between results, then it should be considered dead, and a clean restart of CastXMR should be initiated.
Or better yet, if CastXMR could perform a disable/enable of the problem card and then reinitialize it individually, so that none of the other cards had to be bothered.
With a Mining Expert 19-slot motherboard running a pile of aggressively overclocked Vegas, you're more likely to wedge one of the cards than usual, and being able to recover gracefully from that situation would substantially improve the average hashrate.
It's not really a problem with CAST-XMR now is it. That is you choosing to overdrive the card and then demand that that the tool fix it for you. Maybe you should spend more time accepting a stable hash rate per card and live with it. Its really a driver issue anyway and you are taking risks when overclocking that you will put the system into an unrecoverable state.
I personally don't need a feature in CAST that disables the cards and I don't think that would be helpful for people who have configured their systems correctly. I reboot once a week for windows updates, other than that I don't really look at the rigs.
If you need these bandaid scripts to monitor your hash rate cause it drops or your cards hang you have other problems that are not associated with the miner. I would rather the dev spend time improving the miner efficiency rather than adding some lame monitoring function that is completely unnecessary.
Oh and by the way I use Wattman. YIKES!
Really? Unbelieveble!
I'm using cast_xmr_vega with 6x VEGA56. Everyday and very often I need to restart miner or PC. VEGA's are not modded.
Everything I do before running the miner is run devcon.exe for cli enable/disable GPU's and then Overdriven tool with overclock settings.
Very often is output paused... until S is pressed and after is all messages displayed with OUTDATED result.
I never had a ban from poolserver but last 2 days 3 times! Sometimes freezing after Difficulty changed message.
When I press Q displayed 'quitting..' and nothing happend.
I think what they are saying is cast works for most people, I find it the best miner for xmr, etn etc and it will run stable for days or even a week or so at full hash (2050 per vega fe) and I just restart periodically when checking pool hash rate if I need to. If you are having these problems it points to your system.
Why should everyone else suffer additional code bloat with periodic checks that risks slowing things down to suit one individual? better option is to address the issues on your rig
January 05, 2018, 08:12:16 AM
I've noticed that when Windows blocks CastXMR from accessing a GPU because of aggressive overclocking, the software doesn't handle it very gracefully. The affected GPU stops reporting its hashrate every five seconds, and after a few minutes the software hangs entirely and multiple ^C are needed to terminate the run, assuming that the system doesn't freeze entirely and need a warm reset.
A useful feature would be for CastXMR to recognize that if it is accessing a list of GPUs, each of them should report results periodically, and if one of them goes missing for, say, twice the running average time between results, then it should be considered dead, and a clean restart of CastXMR should be initiated.
Or better yet, if CastXMR could perform a disable/enable of the problem card and then reinitialize it individually, so that none of the other cards had to be bothered.
With a Mining Expert 19-slot motherboard running a pile of aggressively overclocked Vegas, you're more likely to wedge one of the cards than usual, and being able to recover gracefully from that situation would substantially improve the average hashrate.
A useful feature would be for CastXMR to recognize that if it is accessing a list of GPUs, each of them should report results periodically, and if one of them goes missing for, say, twice the running average time between results, then it should be considered dead, and a clean restart of CastXMR should be initiated.
Or better yet, if CastXMR could perform a disable/enable of the problem card and then reinitialize it individually, so that none of the other cards had to be bothered.
With a Mining Expert 19-slot motherboard running a pile of aggressively overclocked Vegas, you're more likely to wedge one of the cards than usual, and being able to recover gracefully from that situation would substantially improve the average hashrate.
It's not really a problem with CAST-XMR now is it. That is you choosing to overdrive the card and then demand that that the tool fix it for you. Maybe you should spend more time accepting a stable hash rate per card and live with it. Its really a driver issue anyway and you are taking risks when overclocking that you will put the system into an unrecoverable state.
I personally don't need a feature in CAST that disables the cards and I don't think that would be helpful for people who have configured their systems correctly. I reboot once a week for windows updates, other than that I don't really look at the rigs.
If you need these bandaid scripts to monitor your hash rate cause it drops or your cards hang you have other problems that are not associated with the miner. I would rather the dev spend time improving the miner efficiency rather than adding some lame monitoring function that is completely unnecessary.
Oh and by the way I use Wattman. YIKES!
Really? Unbelieveble!
I'm using cast_xmr_vega with 6x VEGA56. Everyday and very often I need to restart miner or PC. VEGA's are not modded.
Everything I do before running the miner is run devcon.exe for cli enable/disable GPU's and then Overdriven tool with overclock settings.
Very often is output paused... until S is pressed and after is all messages displayed with OUTDATED result.
I never had a ban from poolserver but last 2 days 3 times! Sometimes freezing after Difficulty changed message. https://ibb.co/n9Ra4w
When I press Q displayed 'quitting..' and nothing happend.
January 05, 2018, 07:51:00 AM
Too much errors with cast_xmr_vega.exe on 6x VEGA56.
Very often freezing, or stoped/paused and after pressing 'S' is ouput report showed with outdated result....
Very often freezing, or stoped/paused and after pressing 'S' is ouput report showed with outdated result....
January 05, 2018, 02:22:28 AM
Can I post here a Feature request?
Would be nice if you could define Fallback Pools.
So in Example if the Main Pool have an disconnect, that the miner switch to the next prioritized pool.
I got some issues that nicehash europ server have sometimes some downtimes...
Thanks!
Would be nice if you could define Fallback Pools.
So in Example if the Main Pool have an disconnect, that the miner switch to the next prioritized pool.
I got some issues that nicehash europ server have sometimes some downtimes...
Thanks!
January 04, 2018, 09:14:46 PM
I wonder what I am doing wrong. Optimized version of stak-amd is getting around 5670 hashes (3 vega 64s @ around 215 watts per card).
CAST_XMR ist at around 5680 hashes [Hash Rate Avg: 5685.2 H/s]. That makes a difference of about 10 hashes on avg.
Any settings you can recommend so I can get more out of my vega 64s?
CAST_XMR ist at around 5680 hashes [Hash Rate Avg: 5685.2 H/s]. That makes a difference of about 10 hashes on avg.
Any settings you can recommend so I can get more out of my vega 64s?
Did you read through this thread?
Also - standard response -
I encourage you to read through the following threads/guides:
Vega thread https://bitcointalksearch.org/topic/any-word-on-amd-vega-hash-rates-2002025
Cast thread https://bitcointalksearch.org/topic/cast-xmr-high-speed-xmrcryptonight-miner-for-rx-vega-gpus-2-khashs-2256917
vega.miningguides.com
January 04, 2018, 08:25:07 PM
I wonder what I am doing wrong. Optimized version of stak-amd is getting around 5670 hashes (3 vega 64s @ around 215 watts per card).
CAST_XMR ist at around 5680 hashes [Hash Rate Avg: 5685.2 H/s]. That makes a difference of about 10 hashes on avg.
Any settings you can recommend so I can get more out of my vega 64s?
CAST_XMR ist at around 5680 hashes [Hash Rate Avg: 5685.2 H/s]. That makes a difference of about 10 hashes on avg.
Any settings you can recommend so I can get more out of my vega 64s?
January 04, 2018, 03:51:35 AM
hi
i have just a dummy plug,no screen but he is not on the gpu 3?
will try without
edit:
like that:
-G 0,1,2,3,4
become
-G 0,1,2,3 and -G 4
thanks
edit 2:no compute driver,i m with the blockchain august 23
i have just a dummy plug,no screen but he is not on the gpu 3?
will try without
edit:
like that:
-G 0,1,2,3,4
become
-G 0,1,2,3 and -G 4
thanks
edit 2:no compute driver,i m with the blockchain august 23
January 03, 2018, 06:36:08 PM
hi
same problem with 0.81 :gpu3 hangs and crash the rig.
0.70 vers start at 4200 h for my 5 rx570 and all the card drop and get a 3400 hahsrate :/
same problem with 0.81 :gpu3 hangs and crash the rig.
0.70 vers start at 4200 h for my 5 rx570 and all the card drop and get a 3400 hahsrate :/
Are you using one of the GPUs for display? If you are, cast doesn't play well in that situation, especially if you're using the forcecompute parameter.
To get it to work in .81, try launching two bat files. One for the single GPU you're using for graphics without the forcecompute parameter and one for the rest of the GPUs with forcecompute on.
That worked for me anyway. Hope it helps you too.
January 03, 2018, 02:35:59 PM
hi
same problem with 0.81 :gpu3 hangs and crash the rig.
0.70 vers start at 4200 h for my 5 rx570 and all the card drop and get a 3400 hahsrate :/
same problem with 0.81 :gpu3 hangs and crash the rig.
0.70 vers start at 4200 h for my 5 rx570 and all the card drop and get a 3400 hahsrate :/
January 03, 2018, 12:03:01 PM
Very good soft, It could be very interesting to have logs HRate and temperature exploitable remotely, or at least in a text file (with a log rotate like).
Thanks again.
Version 0.7 added an HTTP listener that returns a JSON-formatted report. Thanks again.
It can be activated with --remoteaccess, and is available on port 7777
thanks again
January 03, 2018, 10:10:42 AM
Very good soft, It could be very interesting to have logs HRate and temperature exploitable remotely, or at least in a text file (with a log rotate like).
Thanks again.
Version 0.7 added an HTTP listener that returns a JSON-formatted report. Thanks again.
It can be activated with --remoteaccess, and is available on port 7777
January 03, 2018, 10:05:01 AM
Very good soft, It could be very interesting to have logs HRate and temperature exploitable remotely, or at least in a text file (with a log rotate like).
Thanks again.
Thanks again.
January 03, 2018, 09:28:55 AM
Just wanted to say thanks to the cast-xmr team, great job on the miner!
I just started mining with Sapphire PULSE RX 570 - 4 GB, Modded bios, GPU 1350 Mem 1950 running under 100W, i get ~890h/s on Monero with cast-xmr miner.
The best i could do with sgminer and xmr-stak was around 800-820 h/s
can you share your AB settingsI just started mining with Sapphire PULSE RX 570 - 4 GB, Modded bios, GPU 1350 Mem 1950 running under 100W, i get ~890h/s on Monero with cast-xmr miner.
The best i could do with sgminer and xmr-stak was around 800-820 h/s
CV
CC
MC
what is your memory ?
thanks before
Here you go:
Memory ELPIDA, 4G
CPU Clock: 1350
CPU Voltage: 900mv
MEM Clock: 1950
Mem Voltage: 1000mv
Running at 60 C
hope this helps
may i know where to put CPU Voltage
my power still run 120-130W
my card RX 570 4G Elpida Memory
Im not sure you can play with voltages in MSI Afterburner.
I use a software called OverdriveNTool version 0.2.3, i believe i posted the link to it before but i suggest you follow the steps on https://mining.help/
Its a great guide on how to use this software to undervolt and overclock your card
regards
January 03, 2018, 08:56:39 AM
Just wanted to say thanks to the cast-xmr team, great job on the miner!
I just started mining with Sapphire PULSE RX 570 - 4 GB, Modded bios, GPU 1350 Mem 1950 running under 100W, i get ~890h/s on Monero with cast-xmr miner.
The best i could do with sgminer and xmr-stak was around 800-820 h/s
can you share your AB settingsI just started mining with Sapphire PULSE RX 570 - 4 GB, Modded bios, GPU 1350 Mem 1950 running under 100W, i get ~890h/s on Monero with cast-xmr miner.
The best i could do with sgminer and xmr-stak was around 800-820 h/s
CV
CC
MC
what is your memory ?
thanks before
Here you go:
Memory ELPIDA, 4G
CPU Clock: 1350
CPU Voltage: 900mv
MEM Clock: 1950
Mem Voltage: 1000mv
Running at 60 C
hope this helps
may i know where to put CPU Voltage
https://image.prntscr.com/image/TPvVdoRHRD_A9XftQkyWhQ.png
my power still run 120-130W
my card RX 570 4G Elpida Memory
Im not sure you can play with voltages in MSI Afterburner.
I use a software called OverdriveNTool version 0.2.3, i believe i posted the link to it before but i suggest you follow the steps on https://mining.help/
Its a great guide on how to use this software to undervolt and overclock your card
January 03, 2018, 08:06:32 AM
some parameter to lower the power to a gpu? I have 4 rx 480 and G 1,2,3 work fine but G 0 hangs less than a minute
I ran into the same issue with using 5 rx 580s. The fourth GPU always hangs. Try the previous version of cast and report back (version 7).
Where do I find version 7?
Just change the URL of the download link to a 070.
http://www.gandalph3000.com/download/cast_xmr-vega-win64_070.zip
hi
i have the same thing on my rig of 5x 570 ,gpu3 hashrate drop to 860--->> 180h and crash the rig
i try everything,change pci EX,risers,voltage...even motherboard :/
no problem with sgminer 750 hash,neither stack amd 760 hash.
i'm trying vers 0.70.
January 03, 2018, 05:14:02 AM
Just wanted to say thanks to the cast-xmr team, great job on the miner!
I just started mining with Sapphire PULSE RX 570 - 4 GB, Modded bios, GPU 1350 Mem 1950 running under 100W, i get ~890h/s on Monero with cast-xmr miner.
The best i could do with sgminer and xmr-stak was around 800-820 h/s
can you share your AB settingsI just started mining with Sapphire PULSE RX 570 - 4 GB, Modded bios, GPU 1350 Mem 1950 running under 100W, i get ~890h/s on Monero with cast-xmr miner.
The best i could do with sgminer and xmr-stak was around 800-820 h/s
CV
CC
MC
what is your memory ?
thanks before
Here you go:
Memory ELPIDA, 4G
CPU Clock: 1350
CPU Voltage: 900mv
MEM Clock: 1950
Mem Voltage: 1000mv
Running at 60 C
hope this helps
may i know where to put CPU Voltage
my power still run 120-130W
my card RX 570 4G Elpida Memory
January 03, 2018, 01:25:18 AM
Hi All,
I've been working on a simple GUI wrapper around the miner to monitor it in a more user-friendly way and to restart the miner automatically if the hashrate drops below a specified amount. I'm sure there's lots of bugs (very little validation in the GUI), but it might be useful for some of you.
https://github.com/anadventureisu/cast-xmr-ui
https://i.imgur.com/wpSvkSL.png
I've been working on a simple GUI wrapper around the miner to monitor it in a more user-friendly way and to restart the miner automatically if the hashrate drops below a specified amount. I'm sure there's lots of bugs (very little validation in the GUI), but it might be useful for some of you.
https://github.com/anadventureisu/cast-xmr-ui
https://i.imgur.com/wpSvkSL.png
Where can I put a LIKE on your post?
January 02, 2018, 11:52:58 PM
Hi All,
I've been working on a simple GUI wrapper around the miner to monitor it in a more user-friendly way and to restart the miner automatically if the hashrate drops below a specified amount. I'm sure there's lots of bugs (very little validation in the GUI), but it might be useful for some of you.
https://github.com/anadventureisu/cast-xmr-ui
I've been working on a simple GUI wrapper around the miner to monitor it in a more user-friendly way and to restart the miner automatically if the hashrate drops below a specified amount. I'm sure there's lots of bugs (very little validation in the GUI), but it might be useful for some of you.
https://github.com/anadventureisu/cast-xmr-ui
Looks good!
Jump to: