After windows Fall update my ETH mining speeds dropped off dramatically.
I upgraded to 10.3 and tried to reinstall the 17.2.1 AMD drivers. Still no help on speed.
Any suggestions?
Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 479. (Read 6590718 times)
January 13, 2018, 08:01:36 PM
January 13, 2018, 08:00:07 PM
Hi Claymore,
I've received a few reports from users running Awesome Miner to monitor Claymore Ethereum miner about issues with larger number of GPU's. In some systems when you have a large number of GPU's, you get a timeout on the Claymore monitoring API - it simply doesn't respond within a reasonable time. If the user is starting the mining process with a few GPU's less, then it works fine again. So when you go above a certain number of GPUs, the monitoring API isn't working even if the mining itself is running fine.
Is this a know issue? Are there any workarounds?
Thanks!
I've received a few reports from users running Awesome Miner to monitor Claymore Ethereum miner about issues with larger number of GPU's. In some systems when you have a large number of GPU's, you get a timeout on the Claymore monitoring API - it simply doesn't respond within a reasonable time. If the user is starting the mining process with a few GPU's less, then it works fine again. So when you go above a certain number of GPUs, the monitoring API isn't working even if the mining itself is running fine.
Is this a know issue? Are there any workarounds?
Thanks!
Please send me some logs so I can check the reason.
I have the same problem with eth manager too, all rigs up to 6 cards work perfect, all ( 6 rigs ) with 12 cards timeout constantly and reconnect after 10sec to 10 min for couple of secconds before it timeouts again
January 13, 2018, 07:31:54 PM
A question for you guys.
I have a GTX 1080 TI,
Claymore version i downloaded: Claymore's Dual Ethereum+Decred_Siacoin_Lbry_Pascal AMD+NVIDIA GPU Miner v10.3 - Catalyst 15.12-17.x - CUDA 8.0_7.5_6.5
I have gforce experience nvidia driver: 390.65
CUDA 8.0 With the latest patch cuda_8.0.61.2_windows
Operating system is Win10 x64.
The problem I'm having, is that after setting up the Claymore start.bat file to:
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
EthDcrMiner64.exe -epool eu1.ethermine.org:4444 -ewal. -epsw x
After I try to run it I get this:
Any insight ? Should I downgrade my Nvidia driver from 390.65 Lower and it would solve the problem ? ;<
Halp...
I have a GTX 1080 TI,
Claymore version i downloaded: Claymore's Dual Ethereum+Decred_Siacoin_Lbry_Pascal AMD+NVIDIA GPU Miner v10.3 - Catalyst 15.12-17.x - CUDA 8.0_7.5_6.5
I have gforce experience nvidia driver: 390.65
CUDA 8.0 With the latest patch cuda_8.0.61.2_windows
Operating system is Win10 x64.
The problem I'm having, is that after setting up the Claymore start.bat file to:
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
EthDcrMiner64.exe -epool eu1.ethermine.org:4444 -ewal
After I try to run it I get this:
Any insight ? Should I downgrade my Nvidia driver from 390.65 Lower and it would solve the problem ? ;<
Halp...
its a driver issue, probably replacing the driver might solve it. check if you can do clock adjustments in MSI after burner. the miner don't detect your GPU card properly.
January 13, 2018, 05:38:51 PM
A question for you guys.
I have a GTX 1080 TI,
Claymore version i downloaded: Claymore's Dual Ethereum+Decred_Siacoin_Lbry_Pascal AMD+NVIDIA GPU Miner v10.3 - Catalyst 15.12-17.x - CUDA 8.0_7.5_6.5
I have gforce experience nvidia driver: 390.65
CUDA 8.0 With the latest patch cuda_8.0.61.2_windows
Operating system is Win10 x64.
The problem I'm having, is that after setting up the Claymore start.bat file to:
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
EthDcrMiner64.exe -epool eu1.ethermine.org:4444 -ewal. -epsw x
After I try to run it I get this:
https://ibb.co/cKtCWm
Any insight ? Should I downgrade my Nvidia driver from 390.65 Lower and it would solve the problem ? ;<
Halp...
I have a GTX 1080 TI,
Claymore version i downloaded: Claymore's Dual Ethereum+Decred_Siacoin_Lbry_Pascal AMD+NVIDIA GPU Miner v10.3 - Catalyst 15.12-17.x - CUDA 8.0_7.5_6.5
I have gforce experience nvidia driver: 390.65
CUDA 8.0 With the latest patch cuda_8.0.61.2_windows
Operating system is Win10 x64.
The problem I'm having, is that after setting up the Claymore start.bat file to:
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
EthDcrMiner64.exe -epool eu1.ethermine.org:4444 -ewal
After I try to run it I get this:
https://ibb.co/cKtCWm
Any insight ? Should I downgrade my Nvidia driver from 390.65 Lower and it would solve the problem ? ;<
Halp...
January 13, 2018, 04:14:13 PM
Hi Claymore, thanks for your 10.3. I'm using ethos and they haven't updated yet. Is there anyway to update it myself or could you please announce that the linux version is now available so that they can update it in their OS?
Thanks!
Thanks!
January 13, 2018, 03:57:07 PM
PCIE bus number is not showing in Claymore miner though release notes state that this feature has been added in 10.3
Claymore 10.3 , Blockchain drivers ,Windows 10 FCU (1709) Mining ETH only
Claymore 10.3 , Blockchain drivers ,Windows 10 FCU (1709) Mining ETH only
Check this: https://bitcointalksearch.org/topic/m.27584620
If it does not help, PM the log file.
January 13, 2018, 03:49:20 PM
Is there a way to configure it to mining for two wallets?
January 13, 2018, 03:08:30 PM
It should show up when you hit the 's' key.
January 13, 2018, 03:06:16 PM
PCIE bus number is not showing in Claymore miner though release notes state that this feature has been added in 10.3
Claymore 10.3 , Blockchain drivers ,Windows 10 FCU (1709) Mining ETH only
Claymore 10.3 , Blockchain drivers ,Windows 10 FCU (1709) Mining ETH only
January 13, 2018, 12:18:56 PM
Does voltage control work with v10 in blockchain drivers or any of the 17.10.x drivers?
I'm using voltage control mvddc and cvddc since v10 with Blockchain drivers Aug 23... now I'm using v10.3 and everything is perfect.
what version of windows do you have?
, mine got slammed with fall creation 1609.
Cant change voltage with Afterburner 4.4 beta 16 either
I'm in nicehash 1.8.6 which uses claymore 10.3, but cant control with claymore 9.7 on Nicehash 1.8.0 either
My windows is 10 with fall creation installed.
I'm not using Afterburner, just claymore and mining direct to ethermine pool.
Follow my claymore config, just to you see how I setup each card:
Code:
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
EthDcrMiner64.exe -epool us1.ethermine.org:4444 -ewal YourWallet -epsw x -mode 0 -esm 0 -asm 1 -r 0 -allpools 1 -ftime 10 -tstop 85 -tt 65 -fanmin 45 -fanmax 100 -cclock 1250,1150,1150,1150,1150,1150,1150,1150 -mclock 2250,2150,2150,2150,2150,2150,2150,2150 -cvddc 900,850,850,850,850,850,850,850 -mvddc 900,850,850,850,850,850,850,850 -ttdcr 80
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
EthDcrMiner64.exe -epool us1.ethermine.org:4444 -ewal YourWallet -epsw x -mode 0 -esm 0 -asm 1 -r 0 -allpools 1 -ftime 10 -tstop 85 -tt 65 -fanmin 45 -fanmax 100 -cclock 1250,1150,1150,1150,1150,1150,1150,1150 -mclock 2250,2150,2150,2150,2150,2150,2150,2150 -cvddc 900,850,850,850,850,850,850,850 -mvddc 900,850,850,850,850,850,850,850 -ttdcr 80
January 13, 2018, 12:10:04 PM
Does voltage control work with v10 in blockchain drivers or any of the 17.10.x drivers?
I'm using voltage control mvddc and cvddc since v10 with Blockchain drivers Aug 23... now I'm using v10.3 and everything is perfect.
what version of windows do you have?
, mine got slammed with fall creation 1609.
Cant change voltage with Afterburner 4.4 beta 16 either
I'm in nicehash 1.8.6 which uses claymore 10.3, but cant control with claymore 9.7 on Nicehash 1.8.0 either
January 13, 2018, 11:44:25 AM
Does voltage control work with v10 in blockchain drivers or any of the 17.10.x drivers?
I'm using voltage control mvddc and cvddc since v10 with Blockchain drivers Aug 23... now I'm using v10.3 and everything is perfect.
January 13, 2018, 11:41:10 AM
hello..i tried to mine ethereum i get 60.9 mhs wit 2 rx580 armor...but whn i start dual mining wit eth+dcr the eth hashpower decreaes to 55mhs..
can anybody suggest a good dcri setup so tht my etg hashpower s not effected...
can anybody suggest a good dcri setup so tht my etg hashpower s not effected...
Try the option -dcri 24, this was the best config for my RX 580 armor dual mining (ETH+DCR).
To test use the +/- keys of your keyboard to adjust the dcri option.
January 13, 2018, 11:29:23 AM
Hello,
how can i stop claymore disconnecting me from pascal nanopool when to many shares rejected? i use dual miner eth+pasc.
how can i stop claymore disconnecting me from pascal nanopool when to many shares rejected? i use dual miner eth+pasc.
Adjust your overclock to eliminate bad shares
January 13, 2018, 11:23:10 AM
Hi guys,
i have i noob question.
Whats the usd/per h can gtx1070 asus performance?
i have i noob question.
Whats the usd/per h can gtx1070 asus performance?
Try this eth calculator, I put 30 mh/s that is an average speed for this kind of card:
https://www.cryptocompare.com/mining/calculator/eth?HashingPower=30&HashingUnit=MH%2Fs&PowerConsumption=110&CostPerkWh=0.6&MiningPoolFee=1
Mining ETH, today is almost US$ 3.00 per day or US$ 0.125 per hour.
January 13, 2018, 10:19:19 AM
Hi guys,
i have i noob question.
Whats the usd/per h can gtx1070 asus performance?
i have i noob question.
Whats the usd/per h can gtx1070 asus performance?
January 13, 2018, 09:57:39 AM
Does voltage control work with v10 in blockchain drivers or any of the 17.10.x drivers?
January 13, 2018, 07:47:15 AM
Hi Claymore,
I've received a few reports from users running Awesome Miner to monitor Claymore Ethereum miner about issues with larger number of GPU's. In some systems when you have a large number of GPU's, you get a timeout on the Claymore monitoring API - it simply doesn't respond within a reasonable time. If the user is starting the mining process with a few GPU's less, then it works fine again. So when you go above a certain number of GPUs, the monitoring API isn't working even if the mining itself is running fine.
Is this a know issue? Are there any workarounds?
Thanks!
I've received a few reports from users running Awesome Miner to monitor Claymore Ethereum miner about issues with larger number of GPU's. In some systems when you have a large number of GPU's, you get a timeout on the Claymore monitoring API - it simply doesn't respond within a reasonable time. If the user is starting the mining process with a few GPU's less, then it works fine again. So when you go above a certain number of GPUs, the monitoring API isn't working even if the mining itself is running fine.
Is this a know issue? Are there any workarounds?
Thanks!
Please send me some logs so I can check the reason.
January 13, 2018, 07:13:44 AM
Hi Claymore,
I've received a few reports from users running Awesome Miner to monitor Claymore Ethereum miner about issues with larger number of GPU's. In some systems when you have a large number of GPU's, you get a timeout on the Claymore monitoring API - it simply doesn't respond within a reasonable time. If the user is starting the mining process with a few GPU's less, then it works fine again. So when you go above a certain number of GPUs, the monitoring API isn't working even if the mining itself is running fine.
Is this a know issue? Are there any workarounds?
Thanks!
I've received a few reports from users running Awesome Miner to monitor Claymore Ethereum miner about issues with larger number of GPU's. In some systems when you have a large number of GPU's, you get a timeout on the Claymore monitoring API - it simply doesn't respond within a reasonable time. If the user is starting the mining process with a few GPU's less, then it works fine again. So when you go above a certain number of GPUs, the monitoring API isn't working even if the mining itself is running fine.
Is this a know issue? Are there any workarounds?
Thanks!
January 13, 2018, 07:06:48 AM
Hi, I'm new to mine
and I have no knowledge of how to start ...
I already have my gpu to mine but I do not know where to start, someone could help me please.
Thank you
and I have no knowledge of how to start ...
I already have my gpu to mine but I do not know where to start, someone could help me please.
Thank you
Hi, I'm new to coding and computing and I want to write a miner
and I have no knowledge of how to start ...
I already have my PC for coding but I do not know where to start, someone could help me please.
Thank you
Jump to: