Hello,

some solution for "ethermine pool EU SSL certification validation failed" problem? e.g. switch to accept any SSL cert from mining pool?
We switched back to non-SSL connection on port 4444, but that's not an ideal solution.

Regards,
Stanislav

That's cool. :-) I tried to upgrade NV drivers over VNC, but Win always ended up with BSOD+reboot plus corrupted cuda dlls.

I ended up with NBMiner + MSI Afterburner (oldschool like 2017  ) - no drivers reinstall - hashrate almost the same, but working. The reason behind that is windows not updated since install (Windows 10 Version 1703, 10.0.15063).

It would be nice to have simple password security on API passed through commandline option or config, so no one can stalk on local network.

Thx.

I tied all other old versions 5.8b, 5.6... all the same issue (also after windows restart).

I upgraded from old 5.2c miner (due to DAG size) to 5.8c and now miner even doesn't start ... any suggestions?

We use 388.71 drivers (also on other working machines).

2021.11.01:11:28:39.771: main Phoenix Miner 5.8c Windows/msvc - Release build
2021.11.01:11:28:39.771: main Cmd line:
2021.11.01:11:28:39.771: main config.txt: -nvidia -nvKernel 3 -mode 1 -gbase 0 -gser 1 -logfile debug.log -tt 62 -tstop 75 -tstart 60 -fanmin 50 -fanmax 100 -cclock +50 -mclock +450 -powlim -20 -straps 1
2021.11.01:11:28:40.307: main CUDA version: 9.0, CUDA runtime: 8.0
2021.11.01:11:28:40.314: main Available GPUs for mining:
2021.11.01:11:28:40.314: main GPU0: GeForce GTX 1070 (pcie 1), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
2021.11.01:11:28:40.314: main GPU1: GeForce GTX 1070 (pcie 2), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
2021.11.01:11:28:40.314: main GPU2: GeForce GTX 1070 (pcie 3), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
2021.11.01:11:28:40.314: main GPU3: GeForce GTX 1070 (pcie 4), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
2021.11.01:11:28:40.314: main GPU4: GeForce GTX 1070 (pcie 5), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
2021.11.01:11:28:40.314: main GPU5: GeForce GTX 1070 (pcie 6), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
2021.11.01:11:28:40.314: main GPU6: GeForce GTX 1070 (pcie , CUDA cap. 6.1, 8 GB VRAM, 15 CUs
2021.11.01:11:28:40.314: main GPU7: GeForce GTX 1070 (pcie 9), CUDA cap. 6.1, 8 GB VRAM, 15 CUs

<--- exit without any info

Regards,
Stannicek

Hello guys,

anyone knows how to edit VBIOS to disable SAPPHIRE NITRO GLOW "disco"  lighting (and not to use Sapphire Trixx)?

Regards

I tried to switch to old version miner v9.8 and it is stable when network problem happened, so it is related only to v10.0 miner and AMD blockchain drivers. I didn't tried other non-blockchain AMD drivers.

@Claymore
Can you please clarify, what is being done with cards, when restoring work after network outage?

It's not PSU i guess. It is 100% reproducible just by pulling out ethernet cable from lan socket. It crashes immediately during restore of the work(when reconnected to pool). Rigs are running days without crash, but when cable pulled off or some problem happened on network, it goes to hard reboot.

Hello,

does someone facing hard reboot (without any info .. just like on/off on PSU) with Claymore v10.0 on windows when mining (in dual mode) and connection to both pools get lost?

Regards

Hello.

With GTX 1070 I got strange errors after some time (very random) :

08:02:50:826   d98   parse packet: 247
08:02:50:826   d98   ETH: job is the same
08:02:50:826   d98   new buf size: 0
08:02:55:248   14ec   GPU 4, GpuMiner cu_k01 failed 4, unspecified launch failure
08:02:55:248   14ec   GPU 4, GpuMiner kx failed 1
08:02:55:248   14ec   Set global fail flag, failed GPU4
08:02:55:248   14ec   GPU 4 failed
08:02:55:248   1b40   GPU 4, GpuMiner cu_k01 failed 4, unspecified launch failure
08:02:55:248   1b40   GPU 4, GpuMiner kx failed 1
08:02:55:248   1b40   Set global fail flag, failed GPU4
08:02:55:248   1b40   GPU 4 failed
08:02:55:264   d70   GPU 7, GpuMiner cu_k01 failed 4, unspecified launch failure
08:02:55:264   d70   GPU 7, GpuMiner kx failed 1
08:02:55:264   d70   Set global fail flag, failed GPU7
08:02:55:264   dbc   GPU 6, GpuMiner cu_k01 failed 4, unspecified launch failure
08:02:55:264   dbc   GPU 6, GpuMiner kx failed 1
08:02:55:264   dbc   Set global fail flag, failed GPU6
08:02:55:264   d70   GPU 7 failed
08:02:55:264   dbc   GPU 6 failed
08:02:55:264   17c4   GPU 6, GpuMiner cu_k01 failed 4, unspecified launch failure
08:02:55:264   17c4   GPU 6, GpuMiner kx failed 1
08:02:55:264   11a4   GPU 7, GpuMiner cu_k01 failed 4, unspecified launch failure
08:02:55:264   17c4   Set global fail flag, failed GPU6
08:02:55:264   17c4   GPU 6 failed
08:02:55:264   11a4   GPU 7, GpuMiner kx failed 1
08:02:55:264   11a4   Set global fail flag, failed GPU7
08:02:55:264   11a4   GPU 7 failed
08:02:55:295   1b20   GPU 2, GpuMiner cu_k01 failed 4, unspecified launch failure
08:02:55:295   1b20   GPU 2, GpuMiner kx failed 1
08:02:55:295   1b20   Set global fail flag, failed GPU2
08:02:55:295   1b20   GPU 2 failed
08:02:55:295   1b24   GPU 2, GpuMiner cu_k01 failed 4, unspecified launch failure
08:02:55:295   1b24   GPU 2, GpuMiner kx failed 1
08:02:55:295   1b24   Set global fail flag, failed GPU2
08:02:55:295   1b24   GPU 2 failed
08:02:55:311   1124   GPU 3, GpuMiner cu_k01 failed 4, unspecified launch failure
08:02:55:311   1124   GPU 3, GpuMiner kx failed 1
08:02:55:311   1124   Set global fail flag, failed GPU3
08:02:55:311   1124   GPU 3 failed
08:02:55:311   1b28   GPU 3, GpuMiner cu_k01 failed 4, unspecified launch failure
08:02:55:311   1b28   GPU 3, GpuMiner kx failed 1
08:02:55:311   1b28   Set global fail flag, failed GPU3
08:02:55:311   1b28   GPU 3 failed
08:02:55:311   17e4   GPU 0, GpuMiner cu_k01 failed 4, unspecified launch failure
08:02:55:311   17e4   GPU 0, GpuMiner kx failed 1
08:02:55:326   17e4   Set global fail flag, failed GPU0
08:02:55:326   17e4   GPU 0 failed
08:02:55:326   1b38   GPU 0, GpuMiner cu_k01 failed 4, unspecified launch failure
08:02:55:326   1b38   GPU 0, GpuMiner kx failed 1
08:02:55:326   1b38   Set global fail flag, failed GPU0
08:02:55:326   1b38   GPU 0 failed
08:02:55:326   12bc   GPU 5, GpuMiner cu_k01 failed 4, unspecified launch failure
08:02:55:326   12bc   GPU 5, GpuMiner kx failed 1
08:02:55:326   12bc   Set global fail flag, failed GPU5
08:02:55:326   12bc   GPU 5 failed
08:02:55:326   17b0   GPU 5, GpuMiner cu_k01 failed 4, unspecified launch failure
08:02:55:326   17b0   GPU 5, GpuMiner kx failed 1
08:02:55:326   17b0   Set global fail flag, failed GPU5
08:02:55:326   17b0   GPU 5 failed
08:02:55:342   17e0   GPU 1, GpuMiner cu_k01 failed 4, unspecified launch failure
08:02:55:342   17e0   GPU 1, GpuMiner kx failed 1
08:02:55:342   17e0   Set global fail flag, failed GPU1
08:02:55:342   17e0   GPU 1 failed
08:02:55:342   ab8   GPU 1, GpuMiner cu_k01 failed 4, unspecified launch failure
08:02:55:342   ab8   GPU 1, GpuMiner kx failed 1
08:02:55:342   ab8   Set global fail flag, failed GPU1
08:02:55:342   ab8   GPU 1 failed


Strange is, that all GPU fails at once. I'm using Nvidia 384.94 drivers.

Any suggestions?

Yes, it's okay. This is with all 8 cards connected. "Idle" means everything ready for miner start. :-)

Just to share my experience with Blockchain drivers, electricity, etc.

Pre-Previous state  :

8x Sapphire RX580 Nitro+ Special Edition (blue one) - Samsung mem - flashed silent bios (1750 strip -> 2000 strip) - nothing special
17.7.1 - drivers
-cclock 1150;-mclock 2200;-cvddc 840;-mvddc 840;
power drain - ~1170W measured on wall (idle system 150W)
running ROCK stable more than two weeks
~212 MHs

Previous state :

8x Sapphire RX580 Nitro+ Special Edition (blue one) - Samsung mem - flashed silent bios (1750 strip -> 2000 strip) - nothing special
Aug23 blockchain drivers
-cclock 1150;-mclock 2200;-cvddc 875;-mvddc 875;
power drain - ~1270+/-20W measured on wall (idle system 150W)
miner sometimes restart + lot of GPU memory errors
~237MHs


Current state :

8x Sapphire RX580 Nitro+ Special Edition (blue one) - Samsung mem + Uber-mix v 3.1 straps flashed silent bios
Aug23 blockchain drivers 
-cclock 1150;-mclock 2125;-cvddc 880;-mvddc 880;
power drain - ~1380W+/-20W measured on wall (idle system 150W)
miner without restarts - minimum GPU memory errors
~ 245MHs

Still digging around to lower electricity drainage..

Hello,

i'm new to this and i'm looking for good bios for SAPPHIRE NITRO+ RX580 8GB Special Edition (blue one) with Samsung memory (vram K4G80325FB) & dual bios. I just copied 1:1750 to 1:2000 within OC bios image and I got 26.5-26.9 MHs (cclock 1150/mclock 2200/ cvddc&mvddc 840) with 17.7.1 amd drivers (this one I'm using because beta blockchain drivers doesn't allow undervolting by AB/claymore) - temp around 50C and running pretty stable. I get 29Mhs with beta blockchain.

Is there anyting to tweak? :-)

Thank you