Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 313. (Read 6590565 times)
March 17, 2018, 12:22:49 AM
Hi. With Claymore 11.5 i often recieve "socket was closed by pool". This is miner problem or my interner connection issue?
March 17, 2018, 12:15:49 AM
I made more money with the last version (11.4), this new version is sucking big time.
March 16, 2018, 11:47:03 PM
Those of you on Windows 10 getting random shutdowns do this:
Right click start. bat file - properties - options - uncheck QuickEdit Mode - apply - ok
What happens is a window like control panel, Windows defender or task manager comes up and the console freezes. Then the window goes away Claymore resumes and uh oh! Looks like our GPUs failed. But they didnt. Fall creator update did this not Claymore.
While you're in there increase the font size and make it bold.
Right click start. bat file - properties - options - uncheck QuickEdit Mode - apply - ok
What happens is a window like control panel, Windows defender or task manager comes up and the console freezes. Then the window goes away Claymore resumes and uh oh! Looks like our GPUs failed. But they didnt. Fall creator update did this not Claymore.
While you're in there increase the font size and make it bold.
March 16, 2018, 10:32:13 PM
I have Noticed that to with CLaymore miner 11.4 nvidia rig getting random claymore shutdown about every 4 hours and share rejection about 2%
March 16, 2018, 09:08:56 PM
@claymore, what this means?
2 x GTX 1070.
It happens only on nvidia gpus and all gpus at once. This is in your latest version 11.5v. The computer keeps restarting because of that. It does not restart straight away, time to happen it is random.
Code:
GPU 0, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
13:45:41:406 1bd0 GPU 0, GpuMiner kx failed 1
13:45:41:406 1bd0 Set global fail flag, failed GPU0
13:45:41:407 1bd0 GPU 0 failed
13:45:41:409 1bc4 GPU 0, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
13:45:41:410 1bc4 GPU 0, GpuMiner kx failed 1
13:45:41:411 1bc4 Set global fail flag, failed GPU0
13:45:41:412 1bc4 GPU 0 failed
13:45:41:452 1bcc GPU 1, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
13:45:41:453 1bcc GPU 1, GpuMiner kx failed 1
13:45:41:454 1bcc Set global fail flag, failed GPU1
13:45:41:455 1be0 GPU 1, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
13:45:41:456 1bcc GPU 1 failed
13:45:41:458 1be0 GPU 1, GpuMiner kx failed 1
13:45:41:459 1be0 Set global fail flag, failed GPU1
13:45:41:460 1be0 GPU 1 failed
2 x GTX 1070.
It happens only on nvidia gpus and all gpus at once. This is in your latest version 11.5v. The computer keeps restarting because of that. It does not restart straight away, time to happen it is random.
Same thing happening with me, only on nvidia GPU's ... 2x nVidia Titan V ... 11.2 working fine , as soon as i switched to 11.5 i started to get random resboots every 30-55 minutes , same errors ...
Code:
00:41:07:523 17b0 ETH: 03/16/18-00:41:07 - New job from us1.ethermine.org:4444
00:41:07:523 17b0 target: 0x0000000112e0be82 (diff: 4000MH), epoch 175(2.37GB)
00:41:07:523 17b0 ETH - Total Speed: 163.743 Mh/s, Total Shares: 119, Rejected: 0, Time: 00:54
00:41:07:523 17b0 ETH: GPU0 81.841 Mh/s, GPU1 81.902 Mh/s
00:41:07:523 17b0 PASC - Total Speed: 1637.427 Mh/s, Total Shares: 72, Rejected: 2
00:41:07:523 17b0 PASC: GPU0 818.405 Mh/s, GPU1 819.022 Mh/s
00:41:07:648 2464 GPU 1, GpuMiner cu_k03 failed 77, an illegal memory access was encountered
00:41:07:648 2464 GPU 1, GpuMiner kx failed 1
00:41:07:648 2464 Set global fail flag, failed GPU1
00:41:07:648 2464 GPU 1 failed
00:41:07:663 10e0 GPU 1, GpuMiner cu_k03 failed 77, an illegal memory access was encountered
00:41:07:663 10e0 GPU 1, GpuMiner kx failed 1
00:41:07:663 10e0 Set global fail flag, failed GPU1
00:41:07:663 10e0 GPU 1 failed
00:41:07:741 1ec0 GPU 0, GpuMiner cu_k03 failed 77, an illegal memory access was encountered
00:41:07:741 1ec0 GPU 0, GpuMiner kx failed 1
00:41:07:741 1ec0 Set global fail flag, failed GPU0
00:41:07:741 1ec0 GPU 0 failed
00:41:07:741 1ad4 GPU 0, GpuMiner cu_k03 failed 77, an illegal memory access was encountered
00:41:07:741 1ad4 GPU 0, GpuMiner kx failed 1
00:41:07:741 1ad4 Set global fail flag, failed GPU0
00:41:07:741 1ad4 GPU 0 failed
March 16, 2018, 07:30:57 PM
Same here, it worked good at the begging and then it started to fluctuate (3 rigs on 11.5 oldknrl rest on 11.4)
Click in "effective current hashrate" to remove it and you will get better resolution for the other two. Try closing gpuz or hwmonitor.
March 16, 2018, 07:26:19 PM
Can someone please help or advise
Claymore doesn't show does not GPU temperature and fan status so I can't use fan and temrature related controls. Commands like -tt, -ttdcr, -ttli, -tstop, -tstart, -fanmax, -fanmin
RX 580 pulse 8 GB GPUs
Driver version 23.20.782.0
Driver date 20/10/2017
Radeon-Software-Crimson-Relive-Edition-17.10.2
MotherBoard B250 MINING EXPERT
Windows 10 ent edition x64
I am able to control fan and temprature via MSI afterburner
Claymore doesn't show does not GPU temperature and fan status so I can't use fan and temrature related controls. Commands like -tt, -ttdcr, -ttli, -tstop, -tstart, -fanmax, -fanmin
RX 580 pulse 8 GB GPUs
Driver version 23.20.782.0
Driver date 20/10/2017
Radeon-Software-Crimson-Relive-Edition-17.10.2
MotherBoard B250 MINING EXPERT
Windows 10 ent edition x64
I am able to control fan and temprature via MSI afterburner
UPDATE
Updated to radeon version 18.2.1, using Compute mode now. Good thing that hashrate gone up by 2 Mh/s each card.
temperature and fan stats started showing fine until rig crashed.
and now after the reboot same issue - can't see fan and temperature stats. seems like some sort of bug in claymore.
Can someone advise if they have seen the problem?
Has someone seen the issue? Is there some setting in driver?
March 16, 2018, 05:11:56 PM
Hi all,
11.4 works good for me (thanks Claymore!): slightly higher hashrate, but as of today I've been having these recurrent drops in my reported hashrate, like every 50 minutes. It's really a pattern, so I wonder if anybody else has been having these and what the cause could be...
image of the drops:https://ibb.co/eCr7Sx
11.4 works good for me (thanks Claymore!): slightly higher hashrate, but as of today I've been having these recurrent drops in my reported hashrate, like every 50 minutes. It's really a pattern, so I wonder if anybody else has been having these and what the cause could be...
image of the drops:https://ibb.co/eCr7Sx
Probably has gpu locking and claymore restarts in 10 minutes, this generates the gap.
March 16, 2018, 04:31:09 PM
Same here, it worked good at the begging and then it started to fluctuate (3 rigs on 11.5 oldknrl rest on 11.4)
March 16, 2018, 03:51:52 PM
Hi all,
11.4 works good for me (thanks Claymore!): slightly higher hashrate, but as of today I've been having these recurrent drops in my reported hashrate, like every 50 minutes. It's really a pattern, so I wonder if anybody else has been having these and what the cause could be...
image of the drops:https://ibb.co/eCr7Sx
11.4 works good for me (thanks Claymore!): slightly higher hashrate, but as of today I've been having these recurrent drops in my reported hashrate, like every 50 minutes. It's really a pattern, so I wonder if anybody else has been having these and what the cause could be...
image of the drops:https://ibb.co/eCr7Sx
March 16, 2018, 03:51:20 PM
11.5 with -oldkernels 1 gives me less and fluctating reported hashrate.... 11.4 works perfect for me but i am getting 3-6% stale shares and someone mentioned 0-2% stale shares with 11.5
March 16, 2018, 03:25:59 PM
AMD cards that are BIOS modded definitely use oldkernels
AMD cards that are overclocked right on the edge might need oldkernels
Go ahead and try new kernels. With everything the same as before. If theres any instability or increase in rejected/incorrect do not bother underclocking just go straight to oldkernels.
The main difference between the two I've found is you don't get the fluctuating hash rate with the newer ones. So if you can get away using them do it.
That's my story and I am sticking to it.
AMD cards that are overclocked right on the edge might need oldkernels
Go ahead and try new kernels. With everything the same as before. If theres any instability or increase in rejected/incorrect do not bother underclocking just go straight to oldkernels.
The main difference between the two I've found is you don't get the fluctuating hash rate with the newer ones. So if you can get away using them do it.
That's my story and I am sticking to it.
March 16, 2018, 03:14:38 PM
So in which case should we use -oldkrernels 1 ?
Is there any advantega of using 11.5 instead of 11.4?
Should i use the old kernels with RX580 Nitro + 8GB cards?
Thanks
Is there any advantega of using 11.5 instead of 11.4?
Should i use the old kernels with RX580 Nitro + 8GB cards?
Thanks
March 16, 2018, 02:18:04 PM
Still getting stale shares on ethermine. It's worse during the day which makes me think its their server
Also I'm getting 1% incorrect shares. Does not seem to go down with lowering clocks.
Still some fluctuation in speed too. Bios nodded rx580s using oldkernels on windows. Each card will drop 3% to 5% randomly for a short period of time.
Edit: stale shares correlates to when the rig current effective hashrate drops. It is only 63mhs. So this makes sense. Pings are 40 to 60 ms. I bet if I add some horsepower the stales disappear.
Also I'm getting 1% incorrect shares. Does not seem to go down with lowering clocks.
Still some fluctuation in speed too. Bios nodded rx580s using oldkernels on windows. Each card will drop 3% to 5% randomly for a short period of time.
Edit: stale shares correlates to when the rig current effective hashrate drops. It is only 63mhs. So this makes sense. Pings are 40 to 60 ms. I bet if I add some horsepower the stales disappear.
March 16, 2018, 02:15:08 PM
This script can help to users who wants to use versions of Claymore which will be less then version where this new feature will be implemented.
Yes a very smart way of doing it!
For those who don't understand you can run different coins AND different versions of claymore.
March 16, 2018, 02:04:59 PM
I have 4 rigs that have MSI RX 570 Armor cards and 4 with other brand cards, when i upgrade claymore to 11.4 from 11 at least 3 of the cards on each of the MSI card rigs fail.
1 x MSI rig is using 6 x RX570 4GB = Cards stop mining 11.4 on linux, 1500 straps bios
3 x MSI rigs are 18 x RX570 8GB = Cards stop mining with 11.4 on linux, standard bios
4 x Rigs with mix of RX570 Nitro+, Gigabyte RX570, RX570 Pulse on 11.4 on linux = mining fine with not a single card stopping.
Very odd that its just the MSI Armor cards, only one else seeing this?
Is everyone getting the same hashrate increase with 11.5 using the oldkernals?
Thanks
1 x MSI rig is using 6 x RX570 4GB = Cards stop mining 11.4 on linux, 1500 straps bios
3 x MSI rigs are 18 x RX570 8GB = Cards stop mining with 11.4 on linux, standard bios
4 x Rigs with mix of RX570 Nitro+, Gigabyte RX570, RX570 Pulse on 11.4 on linux = mining fine with not a single card stopping.
Very odd that its just the MSI Armor cards, only one else seeing this?
Is everyone getting the same hashrate increase with 11.5 using the oldkernals?
Thanks
If your bios is stock you shouldn't have to use oldkernels. Try it both ways and let us know.
March 16, 2018, 01:55:10 PM
Can I set the epools.txt (dpools.txt) files as an option in command line or in config.txt file? Because switching to another coin I need different alternative pools.
You can do it in bat file like I do it.
Quote
I have the following file structure for Claymore:
...
Of course something should be changed and you do not need something, but it can help you how it can be done.
...
Of course something should be changed and you do not need something, but it can help you how it can be done.
This script can help to users who wants to use versions of Claymore which will be less then version where this new feature will be implemented.
March 16, 2018, 01:36:32 PM
Hi, since a few days ago when the claymore is connected the word unsecure appears in the ip of the pool, in the following way:
ETH: Stratum - connecting to 'us1.ethermine.org' <18.219.59.155> port 4444 (unsecure)
Is there a problem? I did not have that before, how can I solve it? Thank you.
ETH: Stratum - connecting to 'us1.ethermine.org' <18.219.59.155> port 4444 (unsecure)
Is there a problem? I did not have that before, how can I solve it? Thank you.
No Not at all, if you want a pool connection that is more secure then use the SSL with port 5555
Hey man Im getting this error, any ideas?
Faulting application name: EthDcrMiner64.exe, version: 0.0.0.0, time stamp: 0x5aa91985
Faulting module name: igdrclneo64.dll, version: 0.0.0.0, time stamp: 0x5a96b19b
Exception code: 0xc0000005
Fault offset: 0x0000000000030819
Faulting process id: 0x704
Faulting application start time: 0x01d3bd2dcce86dee
Faulting application path: C:\Users\Max\Downloads\Claymore's Dual Ethereum+Decred_Siacoin_Lbry_Pascal_Blake2s_Keccak AMD+NVIDIA GPU Miner v11.5\EthDcrMiner64.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_250db833a1cd577e\igdrclneo64.dll
Report Id: f06b3f20-a28a-4664-8cce-8a58b561b034
Faulting package full name:
Faulting package-relative application ID:
Faulting application name: EthDcrMiner64.exe, version: 0.0.0.0, time stamp: 0x5aa91985
Faulting module name: igdrclneo64.dll, version: 0.0.0.0, time stamp: 0x5a96b19b
Exception code: 0xc0000005
Fault offset: 0x0000000000030819
Faulting process id: 0x704
Faulting application start time: 0x01d3bd2dcce86dee
Faulting application path: C:\Users\Max\Downloads\Claymore's Dual Ethereum+Decred_Siacoin_Lbry_Pascal_Blake2s_Keccak AMD+NVIDIA GPU Miner v11.5\EthDcrMiner64.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_250db833a1cd577e\igdrclneo64.dll
Report Id: f06b3f20-a28a-4664-8cce-8a58b561b034
Faulting package full name:
Faulting package-relative application ID:
could you post your .bat file?
I figured out the issue, was very strange one.
I'm using the ASrock motherboard BTC-H110+, it comes with onboard graphics,
Intel graphics, for some reason disabling and unistalling this fixed the issue.
It could be some kind bug, where its interfere with ATI drivers, not sure but definitly needs some investigation..
March 16, 2018, 01:34:43 PM
Hi, since a few days ago when the claymore is connected the word unsecure appears in the ip of the pool, in the following way:
ETH: Stratum - connecting to 'us1.ethermine.org' <18.219.59.155> port 4444 (unsecure)
Is there a problem? I did not have that before, how can I solve it? Thank you.
ETH: Stratum - connecting to 'us1.ethermine.org' <18.219.59.155> port 4444 (unsecure)
Is there a problem? I did not have that before, how can I solve it? Thank you.
use ssl: prefix and change port to say 5555...
Also I'm still having app crashes on my less stable workers (during init stage, I'd guess about one out of 5 restarts on unstable machines) also on mixed polaris & vega
ssl://
March 16, 2018, 01:34:02 PM
Would anyone mind sharing a good SoftPP table and Overdriventool settings for Vega 64?
My 6x Vega 56 @ 64 rig is a bit flaky. I managed to get it hashing Cryptonight coins relatively stably but with comparatively high voltages on some fudged SoftPP table and clocks by me... But whatever I try with ETH is not hashing for more than 2 minutes before it goes boom.
EDIT: oh and also, does v11.4 require Vegas to be on the Aug23 blockchain driver to achieve max speed or would the latest Adrenalin work?
My 6x Vega 56 @ 64 rig is a bit flaky. I managed to get it hashing Cryptonight coins relatively stably but with comparatively high voltages on some fudged SoftPP table and clocks by me... But whatever I try with ETH is not hashing for more than 2 minutes before it goes boom.
EDIT: oh and also, does v11.4 require Vegas to be on the Aug23 blockchain driver to achieve max speed or would the latest Adrenalin work?
Jump to: