 Show Posts
|
|
Pages: [1]
|
|
maximum number of GPUs this miner can support on Windows? I have the Asus B250, was planning to add 12 cards on it.
Thanks -
|
|
|
|
What is the max number of AMD cards you can utilize with WINDOWS 10 Pro?
I hear 8 and then some people say 12-13.
Thank you!
12-13. And this is not a problem of windows but problem of drivers. WIN10 64bit can utilise almost unlimited number of gpus... What is the max number of AMD cards you can utilize with WINDOWS 10 Pro?
I hear 8 and then some people say 12-13.
Thank you!
if you use win 10 64 bit and blockchain driver then max gpu only 8, if you use latest amd driver it can more than 8. I'am running with 13 gpu with win 10 64 bit amd driver 18.3.4 and 18.5.1. Thank you both of you  I wonder if someone tried pushing like 19 on ASUS b250 board. I'd be curious to see if the community can confirm more than 13 cards on a single board with AMD |
|
|
|
|
What is the max number of AMD cards you can utilize with WINDOWS 10 Pro?
I hear 8 and then some people say 12-13.
Thank you!
|
|
|
|
|
What is the maximum number of GPUs this OS can support?
|
|
|
|
Any update here, same thing just started happening to me. 4x Vega 56s. two running at 17* and the other two running normal. Any help?  I solved my problem by using an auto mouse and keyboard macro recorder. I set it to Q(quit) out of Cast XMR every 6 hours give it a 1 minute breather and restart it. Every 6 hours something happens to my Cast so rather than figure it out, I'm just restarting it right before it starts getting flaky. To be fair, this is nothing against Cast. I have a 13 card rig and I'm mixing Nvidia and AMD together. Although on older versions I never had issues WITHOUT the --ratewatch, I'm looking forward to further iterations of that command. Still love the project, hope to see more updates!  |
|
|
|
|
Hey all,
I try to build dense rigs thus most of my rigs contain 12-13 cards. My MSI Afterburner tool will only show up up to 9 or 10 GPUs. Generally speaking I use the AMD NT Tool to OC the AMD, but is there a NVIDIA only OC tool that doesn't show AMD?
Thank you
|
|
|
|
It may seems counterintuitive, but removing the ratewatchdog command resolved the problem for me.
I also had those low 60hs rate per cards showing up, but removing the "watchdog" eliminated the problem for good.
When I remove it, my hash rate drops after 1-2 hours from 18XX to 15 or 16 XX Ratewatch is crucial for me  |
|
|
|
Hi, try the option "--ratewatchdog" to monitor the hash rate and automatic restart of a dropping GPU. Or use the cast-xmr-ui for monitoring: https://github.com/anadventureisu/cast-xmr-uiBtw. are you using the Blockchain Beta or 18.3.4 driver? Regards, glph3k I'm using --ratewatchdog and Blockchain Beta From August It seems like after sometime if watchdog kicks in, the hash rate drops lower. It doesn't appear as if my graphics driver crashed, because normally it will reset all of my OC settings. Which also I tried to adjust OC settings however I'm not having much luck. In the above sample I posted, each card will start off by doing roughly 1870Hs, but after a few kernel resets I guess over the course of the day, some of the cards just become obsolete. Maybe ratewatchdog is not fully bringing the vega to it's potential. When the hashrate drops, I also notice that particular card no longer reports hashes that often. As you can tell by that small insert, GPU 1 started reporting hashes but 0 2 3 slowly fell off. So it's interesting! OC is 0 Core 905 Mem and -20% power Thank you for any advice you have. UPDATE: I was able to watch this happen today and I wanted to share the log[19:04:10] GPU2 | 48°C | Fan 4229 RPM | 1896.3 H/s
[19:04:11] GPU0 | 56°C | Fan 4634 RPM | 1863.8 H/s
[19:04:11] GPU3 Kernel Resetted.
[19:04:11] GPU3 | 54°C | Fan 4328 RPM | 86.0 H/s
[19:04:14] GPU1 | 55°C | Fan 4342 RPM | 1880.0 H/s
[19:04:16] GPU2 | 48°C | Fan 4219 RPM | 1892.3 H/s
[19:04:16] GPU0 | 56°C | Fan 4636 RPM | 1861.8 H/s
[19:04:20] GPU1 | 55°C | Fan 4352 RPM | 1883.0 H/s
[19:04:21] GPU2 | 51°C | Fan 4180 RPM | 1894.6 H/s
[19:04:22] GPU0 | 56°C | Fan 4636 RPM | 1862.8 H/s
[19:04:26] GPU1 | 55°C | Fan 4352 RPM | 1879.7 H/s
[19:04:27] GPU2 | 51°C | Fan 4178 RPM | 1894.3 H/s
[19:04:28] GPU0 | 56°C | Fan 4650 RPM | 1864.7 H/s
[19:04:31] GPU1 | 55°C | Fan 4363 RPM | 1880.7 H/s
[19:04:33] GPU2 | 51°C | Fan 4178 RPM | 1895.0 H/s
[19:04:34] GPU0 | 56°C | Fan 4632 RPM | 1865.0 H/s
[19:04:37] GPU1 | 55°C | Fan 4362 RPM | 1881.0 H/s
[19:04:39] GPU2 | 52°C | Fan 4169 RPM | 1895.3 H/s
[19:04:39] GPU0 | 56°C | Fan 4629 RPM | 1864.7 H/s
[19:04:43] GPU1 | 55°C | Fan 4373 RPM | 1881.4 H/s
[19:04:44] GPU2 | 52°C | Fan 4144 RPM | 1894.6 H/s
[19:04:45] GPU0 | 56°C | Fan 4620 RPM | 1865.0 H/s
[19:04:48] GPU1 | 55°C | Fan 4368 RPM | 1883.0 H/s
[19:04:50] GPU2 | 49°C | Fan 4274 RPM | 1893.0 H/s
[19:04:51] GPU0 | 57°C | Fan 4631 RPM | 1865.4 H/s
[19:04:54] GPU1 | 55°C | Fan 4356 RPM | 1883.0 H/s
[19:04:56] GPU2 | 49°C | Fan 4273 RPM | 1893.0 H/s
[19:04:57] GPU0 | 56°C | Fan 4630 RPM | 1865.0 H/s
[19:05:00] GPU1 | 55°C | Fan 4362 RPM | 1883.7 H/s
[19:05:01] GPU2 | 52°C | Fan 4279 RPM | 1884.7 H/s
[19:05:03] GPU0 | 56°C | Fan 4636 RPM | 1860.9 H/s
[19:05:06] GPU1 | 55°C | Fan 4363 RPM | 1871.2 H/s
[19:05:07] GPU2 | 52°C | Fan 4278 RPM | 1886.0 H/s
[19:05:08] GPU0 | 57°C | Fan 4669 RPM | 1866.7 H/s
[19:05:11] GPU1 | 55°C | Fan 4358 RPM | 1881.7 H/s
[19:05:11] GPU3 | 54°C | Fan 4301 RPM | 59.7 H/s
[19:05:13] GPU2 | 49°C | Fan 4249 RPM | 1900.7 H/s
[19:05:14] GPU0 | 56°C | Fan 4636 RPM | 1862.1 H/s
[Pool: 'cryptonightv7.usa.nicehash.com:3363' | Connected: 2018-04-19 12:02:04]
7:03:11 (100%) Online
0:00:00 ( 0%) Offline
[Job: #446 | Difficulty: 400015 | Running: 95.0 sec | Avg Job Time: 56.8 sec]
[Hash Rate Avg: 7443.7 H/s]
1852.4 H/s GPU0
1867.1 H/s GPU1
1879.9 H/s GPU2
1844.3 H/s GPU3
[Shares Found: 621 | Avg Search Time: 40.8 sec]
620 (100%) Accepted
1 ( 0%) Rejected by pool
0 ( 0%) Invalid result computation failed
0 ( 0%) Could not be submitted because of network error
0 ( 0%) Outdated because of job change
[19:05:17] GPU1 | 55°C | Fan 4336 RPM | 1882.0 H/s
[19:05:18] GPU2 | 50°C | Fan 4244 RPM | 1896.6 H/s
[19:05:20] GPU0 | 57°C | Fan 4623 RPM | 1873.5 H/s
[19:05:23] GPU1 | 55°C | Fan 4341 RPM | 1881.7 H/s
[19:05:24] GPU2 | 50°C | Fan 4216 RPM | 1894.6 H/s
[19:05:26] GPU0 | 57°C | Fan 4618 RPM | 1864.4 H/s
[19:05:28] GPU1 | 55°C | Fan 4329 RPM | 1881.0 H/s
[19:05:30] GPU2 | 52°C | Fan 4185 RPM | 1889.6 H/s
[19:05:31] GPU0 | 56°C | Fan 4605 RPM | 1866.7 H/s
[19:05:34] GPU1 | 55°C | Fan 4322 RPM | 1878.1 H/s
[19:05:35] GPU2 | 52°C | Fan 4171 RPM | 1890.6 H/s
[19:05:37] GPU0 | 55°C | Fan 4615 RPM | 1858.9 H/s
[19:05:40] GPU1 | 55°C | Fan 4317 RPM | 1881.4 H/s
[19:05:41] GPU2 | 49°C | Fan 4172 RPM | 1893.3 H/s
Now after GPU 3 was reset > it dropped to 56 hashes and it's no longer showing up like GPU 0 1 2 (3 the one which was just reset is now MIA) |
|
|
|
|
Hi anyone having issues like this with a 4x Vega 56 Build :
10:38:12] GPU1 | 56°C | Fan 4429 RPM | 1886.6 H/s
[10:38:12] GPU0 | 53°C | Fan 4319 RPM | 62.5 H/s
[10:38:17] GPU1 | 56°C | Fan 4437 RPM | 1884.0 H/s
[10:38:23] GPU1 | 56°C | Fan 4439 RPM | 1886.0 H/s
[Pool: 'cryptonightv7.usa.nicehash.com:3363' | Connected: 2018-04-19 06:14:00]
19:26:55 (100%) Online
0:00:40 ( 0%) Offline (2 Reconnects)
[Job: #168 | Difficulty: 100001 | Running: 194.0 sec | Avg Job Time: 418.1 sec]
[Hash Rate Avg: 4268.2 H/s]
816.2 H/s GPU0
1874.2 H/s GPU1
790.3 H/s GPU2
787.6 H/s GPU3
[Shares Found: 1576 | Avg Search Time: 44.4 sec]
1576 (100%) Accepted
0 ( 0%) Rejected by pool
0 ( 0%) Invalid result computation failed
0 ( 0%) Could not be submitted because of network error
0 ( 0%) Outdated because of job change
[10:38:29] GPU1 | 56°C | Fan 4428 RPM | 1885.0 H/s
[10:38:34] GPU1 | 56°C | Fan 4445 RPM | 1885.7 H/s
After some time, the hash rate just drops drastically
Thank you
|
|
|
|
|
Just want to bring this up to your attention:
--Ratewatchdog seems to sometimes cause the Hashrate one one card in a 4 Card Vega 56 rig to drop to 561- 100 hs where it normally will be abount 1.85KHs
I hope there is a way to improve upon this command or if you have tips and tricks to perhaps make this work better, please do share.
|
|
|
|
I sometimes get this error and hash down 1900 to 879
GPU Hash Rate Drop Detected.. GPU Kernel Resetted.
i use 2 x vega64
Lower your over clock - Your over clocks that worked in the past do not work on this version. I had to down clock some cards to make them fully functional with --ratewatchdog Hope this helps |
|
|
|
I tried the new version 0.92 with my 4 vegas 56 the miner freezes everytime after some hours with nicehash --algo=0 Increase your virtual ram (page file) to 60GB |
|
|
|
|
Crypto's only value is the value people put behind it. The reason why the value is so unstable is because big institutions are not contributing due to FUD. Once bitcoin is more in line with financial institutions, we will see a significant rise in BTC Value. Trading will also be more stable because "whales" won't be able to disturb the market to the extent they can presently.
The question that remains is, when will countries start regulating and adopting bitcoin so that these major companies can join board and help take BTC to the next level?
The only thing you can do now is either wait and find out (maybe it's worth it), or sell and give up.
Just my opinion ^
|
|
|
|
First off, thanks so much glph3k! I've been using your miner since the beginning, it's come a long way since then! Like many vega owners/miners, I've been waiting for the day when using the August BC drivers is no longer necessary. Seems that day is here! I'm getting full speeds on all 56/64 cards with your updated miner and the new 18.3.4 Adrenalin drivers. No more disable/enable needed! I'm also hoping to get my Vega FEs switched over soon as well, but Overdriven Tool does not support Vega FE yet on the new drivers. I will say that I did notice the same issue that RAJNIFICENT mentioned on several of my rigs. I've reduced some clocks and added some voltage, fingers crossed that that solves it. Also wanted to say I'm liking your --ratewatchdog argument. From what I've seen, it picks up the slight drops in hashrate pretty well. Vega mining is getting close to plug and play! Hi, please share your success / failures. I'm trying to reduce my overclock, however my hashrates on one rig continues to drop. If I can get rate watch to work as designed, dude my life would be complete. |
|
|
|
|
Hi,
After upgrading to 9.1 and enabling the ratewatchdog, I'm noticing some issues. For example I have 2 mixed rigs.
One rig consists of 8 1070TI, 2 vega 64, 2 RX 570 (RIG A)
Other rig consists of 8 1070TI 4 Vega 56 (RIG B)
RIG A works FLAWLESSLY with the ratewatchdog argument. I haven't dropped hashrates in over 24 hours and that's impressive considering it dropped roughly every 1000ish shares.
RIG B works somewhat. Within 5--6 hours of running the program, rate watch works as expected, but after 8-10 hours or overnight, some of the cards drop to 56 khs...
I don't know if you can make sense of this, but hope this helps improve upon the argument.
Thank you!
|
|
|
|
in regards to the myth of Windows only being able to manage 8 GPUs....that's another one debunked.  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. |
|
|
|
|
