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

Ok, so I have now installed the Vega 64 BIOS and I'm running:

    Core Frequency: -10%
    Memory Clock: 1105 MHz
    Power Limit: +20%

And only getting an average of 1982 H/s @ 280W power usage. Seems like low hash rate for the settings with high power usage. GPU is sitting around 68C with 3300 RPM on the fan.

Is it nessesary to do the power-play hack to the registry in order to touch the 2050 H/s realm?

Stak miner at the same speeds but I just noticed something that I haven’t noticed before.

The submission errors I get on Cast are the same I get on Stak when I mine on NanoPool

When I mine on Spacepool I have far less submission errors… But with Spacepool I don’t get what I am suppose to get (12.5ETN coins per hour)… I get a payout of roughly 7.5ETN per hour….

how do you get stats?

Been using fast job switch with the latest cast xmr release 0.8. I noticed that temps are up a bit and the average hash rate drops some due to the job changes. This latest versions, change to the kernel, mean the MEM seems to be working harder/hotter. However, I still get some outdated jobs on my 6 Vega 64 rig. Anyway I am still pulling .3 XMR every 3 days or so on the rig. I will check the rig an a couple days and see if anything changes.

Pool: 'gulf.moneroocean.stream:10128' | Connected: 2017-12-26 07:29:06]
  40:51:27 (100%) Online
  0:01:04 (  0%) Offline (3 Reconnects)

[Job: #422 | Difficulty: 335230 | Running: 50.0 sec | Avg Job Time: 320.3 sec]

[Hash Rate Avg: 11965.5 H/s]
  1997.1 H/s GPU0
  1997.4 H/s GPU1
  1996.9 H/s GPU2
  1996.5 H/s GPU3
  1980.5 H/s GPU4
  1997.2 H/s GPU5

[Shares Found: 5037 | Avg Search Time: 29.3 sec]
5021 (100%) Accepted
   0 (  0%) Rejected by pool
   0 (  0%) Invalid result computation failed
   2 (  0%) Could not be submit because of network error
  14 (  0%) Outdated because of job change

ok thnx

Up Volt a bit on cpu and bit more on mem
also
there is a whole string of other things you can check, i listed them all on my thread

it's not stable for me. went about 4 hours and crashed my whole system....

what are people lowering mem clock to fix this?

Yes I'm familiar with this and the issue I have is not Quick Edit related.

In the JSON monitoring the pool changes to "disconnected" yet I'm accessing the console over the network so it is not a network related issue. I use monerohash...gonna try supportxmr.

looks to be a tad better than STAK for me. nice job.

This miner is so worth it for me over STAK. even if the hashrates were the same, the fan noise is so much less with this miner. It was driving me absolutely crazy. I don't have a devoted room for my miners.

hmmmm could it be some kind of PCI 16x conflict, whatever that might be? I'd try using a riser connected to a PCI-E 1x slot....

In regards to what RIGED mentioned as stability the 6 Vega 56 mining rig is mining at 11500+H/s and 1200+ shares every 4 hours with 0 errors! It's been 3 days since I've found the much needed stability, it makes a hell of a difference, you can almost forget about the rig

thx for helpfull info, i will be a wise man, after reading

read the mobo manual
maybe the one PCIe port nulls the other due to bus issues
read my thread for more tips

i have an asus B250mining with 6 VEGA64
and
MSI Z270 tomahawk with 6 VEGA64

both mining ETN on Nanopool using Cast XMR at 11988h/s each SUPER STABLE burning 2620W

there is a whole flurry of tweeks and tricks  on the OS and hardware and drivers one must obey to have a boring miner just running full speed 24/7
(i bet you still have candy crush on your windows OS dont you)

for wisdom read the thread of my path to the above stated result of 1200ETN EVERY DAY

hope it helps

https://bitcointalk.org/index.php?topic=2549085.new#new

a stupid man doesnt learn from his mistakes
a smart man learns from his mistakes
a wise man learns from other peoples mistakes

I would like to clarify that I am not running risers in my system.  Two Vegas are plugged directly into the motherboard.  Therefore this is not a riser issue, nor does it have anything to do with disabling/enabling the cards using devcon.exe.   (Devcon will only detect one card out of two because Windows sees only one card).

I have followed this guide line by line...

Thanks for any help!
 

I have this exact same problem! 

To be more clear, I have 2x Vega 64 in my system - Cast Miner will sometimes crash randomly, which will cause windows to restart.  **Oddly, upon re-starting, Windows only detects 1 Vega card (not 2)**
I run a startup script (.bat file) as described in the earlier posts, and so my script automatically calls -G 0, 1 parameter in config.  Since only 1 card is detected, Cast Miner throws a user promt stating that only 1 card was detected.  As a result, my rig stalls because Cast Miner does not want to run with only 1 card.

It is very strange why Windows can sometimes boot with fewer cards detected than are actually plugged in.  What makes it even more strange is that rebooting Windows does not solve the problem, but shutting down (and rebooting) will let Windows properly detect 2 cards in the system.

In any case, the Windows detection problem likely has nothing to do with the Cast Miner itself - so i echo what Zachosan is saying above -

1)  Is there any way to run cast miner with all available video cards without having to specify -G 0, 1, ..., x (Again the reason we would like this is to let the rig come up gracefully with as many cards as detected by Windows after a reboot)
2)  Alternately, could the Developer please turn off "verbose mode" such that when Cast sees fewer cards than specified, the Cast Miner does not throw up a user prompt.  (If the cast miner sees less cards then specified, then simply indicate that fewer cards are detected, and keep running)


Anyone else who has run into this issue?

Thanks!

have you checked your raisers? You need to reinstall the drivers every time you plug a new card. This guide should help you out.

http://vega.miningguides.com/

hello! is there any way to run cast xmr miner with all available video cards? I have 5 cards so there is -G 0,1,2,3,4 parameter in config. Without -g miner uses only first card.
Sometimes system restarts and lose one or two card and miner could not launch after startup because it did not find one or two cards.

Have you tried this fix from @Morgon ? It works wonders!!

Quote from: naazz on December 15, 2017, 03:03:00 PM
But sometime it just stop mining nothing appear in the console until i hit a enter or any key and it start back.

This typically occurs when you have your Windows Command Prompt windows enabled for 'Quick Edit', and you click the mouse inside the window to focus; but this tells the Command Prompt window that you want to quick copy content.

To fix: While the miner is running, click the Command Prompt icon, go to Properties, and unselect Quick Edit. Then go back to that menu, select Defaults, and uncheck it there so future windows apply this setting.

I don't think it is a mobo issue. Will check the job # in JSON output to see if that be used to monitor freezes.

Anyone else seen this or worked around it?

Tried -S pool.supportxmr.com:5555 -u my cryptopia.address -p PC --nonicehash -G 0
Won't connect. My only guess is the disabled Windows security crap is still blocking the Cast miner.