Have anyone tried testing different drivers in windows 10 for nvidias? Which one makes the best hashrate?
Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 632. (Read 6590565 times)
September 01, 2017, 08:51:55 AM
September 01, 2017, 08:25:32 AM
Thank you for your answer @Ursul0
Okay, understood. But could explain the fact that I get Incorrect shares from gpus with 0 memory errors ?
Is it because of tight memory straps on the modded BIOS?
Okay, understood. But could explain the fact that I get Incorrect shares from gpus with 0 memory errors ?
Is it because of tight memory straps on the modded BIOS?
September 01, 2017, 07:59:38 AM
I have some questions for anyone who can answer:
Mining Dual ETH+DCR on Windows with 8x RX 580 8GB Nitro+
- What is the acceptable amount of GPU memory errors? 0? <10? <100? <1000? etc...
- How come my GPUs give incorrect shares without having GPU memory errors?
- My incorrect / submited shares ratio is ~1% (usually a bit less). is this normal?
Mining Dual ETH+DCR on Windows with 8x RX 580 8GB Nitro+
I know that quoting myself is pretty lame but, anyone?
The errors you see would include both: those that were corrected and those that were not.
Depending on the algorithm the impact of the errors can vary.
The most error tolerant algo (among the memory intensive ones) is ethash, likely due to mostly mem read operations.
And the least tolerant to mem errors seems to be Cryptonight
September 01, 2017, 02:51:02 AM
Thank you so much for your answer @TechPark!
For personal reasons I have to be on wifi for a couple of months then on cable for next couple of months.
I have noticed that while on wifi the reject rate is higher and I can live with it. What I am trying to figure out is mainly the Incorrect shares, which are ~0.8-1% even though on most gpus I have 0 memory errors
Actually, I have gpus with 0 memory errors that produce more Incorrect shares than gpus with 100ish errors. So I am tending to believe Incorrect shares come down to tight memory straps after all
Ideally you want to have 0 errors.
On most gpus I have 0, but on some I have 100ish and I am wondering if it is a big dealWhen you ping continuously pool IP address what is the latency?
53msDid you select the closest to you pool (geographically)?
YesWhat is the value in ms for submitted share in claymore?
78msHave you tried another pool?
Are you on WiFi or cable?
I haven't tried another pool for a while now. Are you on WiFi or cable?
For personal reasons I have to be on wifi for a couple of months then on cable for next couple of months.
I have noticed that while on wifi the reject rate is higher and I can live with it. What I am trying to figure out is mainly the Incorrect shares, which are ~0.8-1% even though on most gpus I have 0 memory errors
Actually, I have gpus with 0 memory errors that produce more Incorrect shares than gpus with 100ish errors. So I am tending to believe Incorrect shares come down to tight memory straps after all
September 01, 2017, 02:33:05 AM
Hello guys, I need some help : my Claymore Miner does not show one of my GPU's temperature :
- I have 3 GPU
- but the temperature is shown for only 2 of them
Any idea ? Thanks a lot
Here's a screenshot :
- I have 3 GPU
- but the temperature is shown for only 2 of them
Any idea ? Thanks a lot
Here's a screenshot :
August 31, 2017, 11:14:52 PM
Any one else having problem with Win10 freezing?
I really like getting 117mhs again with my 4 cards but if this driver is just going to give headache after headache Im rolling back to Win7 and keeping my 105mhs.
I lowered mem from 2150 to 2100 and it ran a bit longer (previously 10 minutes before crashed windows) but its still crashing the system. Will new miner address issues with Win7 and blockchain drivers? Can anyone give advice for Win10 crashing with new drivers?
I really like getting 117mhs again with my 4 cards but if this driver is just going to give headache after headache Im rolling back to Win7 and keeping my 105mhs.
I lowered mem from 2150 to 2100 and it ran a bit longer (previously 10 minutes before crashed windows) but its still crashing the system. Will new miner address issues with Win7 and blockchain drivers? Can anyone give advice for Win10 crashing with new drivers?
I have 2 rigs with RX580: W10+Aug11 Blockchain drivers=have no issues - works flawlessly for weeks.
I do OC sanely though. Try to run it with default settings.
Hi TechPark, how many GPU's you have on each rig, miner Claymore v9.8 and setting? what motherboard?
each card hashes at 29.5-29.7 MHs
1: 6x RX580 - 9.8 - MB - ASRock B250 Gaming K4 Motherboard
2: 2x RX580 - 9.8 - MB - ASRock B250 Gaming K4 Motherboard
Same setting on both rigs:
-epool asia1.ethpool.org:3333
-ewal YYYYYYYYYYYYYYYYYY.ZZZZZZ
-epsw x
-dbg 1
-r 1
-mport XXXX
AB:
-96
1300
2075
70
So I ended up getting rid of Windows 10. Restored my PC to Win7 and installed the robinhood driver; ONLY the robinhood drivers, no crimson or anything with amd radeon's website. Im back up to 117mh/s on 4 rx 480 8gb cards using AB 4.4.0 beta 16, been running just around 24 hours with no issues. Thank you RobinHood! Windows 10 Sucks.
Not the case here.
have never had any issues with Windows 10. Managing 20+ computers and laptops.
August 31, 2017, 10:55:48 PM
Any one else having problem with Win10 freezing?
I really like getting 117mhs again with my 4 cards but if this driver is just going to give headache after headache Im rolling back to Win7 and keeping my 105mhs.
I lowered mem from 2150 to 2100 and it ran a bit longer (previously 10 minutes before crashed windows) but its still crashing the system. Will new miner address issues with Win7 and blockchain drivers? Can anyone give advice for Win10 crashing with new drivers?
I really like getting 117mhs again with my 4 cards but if this driver is just going to give headache after headache Im rolling back to Win7 and keeping my 105mhs.
I lowered mem from 2150 to 2100 and it ran a bit longer (previously 10 minutes before crashed windows) but its still crashing the system. Will new miner address issues with Win7 and blockchain drivers? Can anyone give advice for Win10 crashing with new drivers?
I have 2 rigs with RX580: W10+Aug11 Blockchain drivers=have no issues - works flawlessly for weeks.
I do OC sanely though. Try to run it with default settings.
Hi TechPark, how many GPU's you have on each rig, miner Claymore v9.8 and setting? what motherboard?
each card hashes at 29.5-29.7 MHs
1: 6x RX580 - 9.8 - MB - ASRock B250 Gaming K4 Motherboard
2: 2x RX580 - 9.8 - MB - ASRock B250 Gaming K4 Motherboard
Same setting on both rigs:
-epool asia1.ethpool.org:3333
-ewal YYYYYYYYYYYYYYYYYY.ZZZZZZ
-epsw x
-dbg 1
-r 1
-mport XXXX
AB:
-96
1300
2075
70
So I ended up getting rid of Windows 10. Restored my PC to Win7 and installed the robinhood driver; ONLY the robinhood drivers, no crimson or anything with amd radeon's website. Im back up to 117mh/s on 4 rx 480 8gb cards using AB 4.4.0 beta 16, been running just around 24 hours with no issues. Thank you RobinHood! Windows 10 Sucks.
August 31, 2017, 06:25:26 PM
I have some questions for anyone who can answer:
Mining Dual ETH+DCR on Windows with 8x RX 580 8GB Nitro+
- What is the acceptable amount of GPU memory errors? 0? <10? <100? <1000? etc...
- How come my GPUs give incorrect shares without having GPU memory errors?
- My incorrect / submited shares ratio is ~1% (usually a bit less). is this normal?
Mining Dual ETH+DCR on Windows with 8x RX 580 8GB Nitro+
I know that quoting myself is pretty lame but, anyone?
Ideally you want to have 0 errors.
When you ping continuously pool IP address what is the latency?
Did you select the closest to you pool (geographically)?
Have you tried another pool?
Are you on WiFi or cable?
What is the value in ms for submitted share in claymore?
August 31, 2017, 06:21:20 PM
Any one else having problem with Win10 freezing?
I really like getting 117mhs again with my 4 cards but if this driver is just going to give headache after headache Im rolling back to Win7 and keeping my 105mhs.
I lowered mem from 2150 to 2100 and it ran a bit longer (previously 10 minutes before crashed windows) but its still crashing the system. Will new miner address issues with Win7 and blockchain drivers? Can anyone give advice for Win10 crashing with new drivers?
I really like getting 117mhs again with my 4 cards but if this driver is just going to give headache after headache Im rolling back to Win7 and keeping my 105mhs.
I lowered mem from 2150 to 2100 and it ran a bit longer (previously 10 minutes before crashed windows) but its still crashing the system. Will new miner address issues with Win7 and blockchain drivers? Can anyone give advice for Win10 crashing with new drivers?
I have 2 rigs with RX580: W10+Aug11 Blockchain drivers=have no issues - works flawlessly for weeks.
I do OC sanely though. Try to run it with default settings.
Hi TechPark, how many GPU's you have on each rig, miner Claymore v9.8 and setting? what motherboard?
each card hashes at 29.5-29.7 MHs
1: 6x RX580 - 9.8 - MB - ASRock B250 Gaming K4 Motherboard
2: 2x RX580 - 9.8 - MB - ASRock B250 Gaming K4 Motherboard
Same setting on both rigs:
-epool asia1.ethpool.org:3333
-ewal YYYYYYYYYYYYYYYYYY.ZZZZZZ
-epsw x
-dbg 1
-r 1
-mport XXXX
AB:
-96
1300
2075
70
August 31, 2017, 06:14:30 PM
Hello I am new to trying to mine Ethereum I have the new miner and using GTX 1080 ti on windows 10 using nvidia driver 384.94 trying to mine at supernova and I am getting eth: job timeout, disconnect and Received unknown response: {jsonrpc":"2.0","result';[0x0555531 etc,,,,,
Need some help please.
Need some help please.
Anybody?
Provide more info.
Did you run default Claymore's start,bat? What is the result?
August 31, 2017, 05:19:57 PM
Does 9.9 give any boost for the blockchain drivers? are we finally going to be able to use undervolting on the Vega FE?
Vega FE can already be undervolted with the block chain drivers and claymore 9.8.
August 31, 2017, 05:04:33 PM
Does 9.9 give any boost for the blockchain drivers? are we finally going to be able to use undervolting on the Vega FE?
August 31, 2017, 04:13:58 PM
Hi Mr Claymore,
I installed latest ROCm drivers on my ubuntu 16.04.3 (latest update/dist-upgrade) with 4 RX480.
I still need the amdgpu-pro drivers (using latest) for openCL.
I tried using the ROCm OpenCL module(s) even MIOpen-OpenCL, but it fails that way:
clearly it seems the AMDGPU are not detected correctly...
I've heard that AMDGPU-Pro drivers were not good, and maybe ROCm implementation would improve performances or control (hope for ADL library?)... but currently it is not working at all.
Anyway, ROCm drivers with AMDGPU-Pro OpenCL works like a charm.
rocm-smi moreover give me new information like electric power... It will be important for my automatic optimisation...
BTW thanks for your work. Happy to mine for you 1%.
I installed latest ROCm drivers on my ubuntu 16.04.3 (latest update/dist-upgrade) with 4 RX480.
I still need the amdgpu-pro drivers (using latest) for openCL.
I tried using the ROCm OpenCL module(s) even MIOpen-OpenCL, but it fails that way:
Quote
[66B blob data]
[66B blob data]
[66B blob data]
ETH: 10 pools are specified
Main Ethereum pool is eth-eu2.nanopool.org:9999
At least 16 GB of Virtual Memory is required for multi-GPU systems
Make sure you defined GPU_MAX_ALLOC_PERCENT 100
Be careful with overclocking, use default clocks for first tests
Press "s" for current statistics, "0".."9" to turn on/off cards, "r" to reload pools, "e" or "d" to select current pool
OpenCL initializing...
AMD Cards available: 1
GPU #0: gfx803, 8192 MB available, 36 compute units
POOL/SOLO version
Cannot build OpenCL program for GPU 0
GPU #0: set -etha as 0 (ETH algo for fast cards)
No NVIDIA CUDA GPUs detected.
Total cards: 1
AMD ADL library not found.
ETHEREUM-ONLY MINING MODE ENABLED (-mode 1)
ETH: eth-proxy stratum mode
Watchdog enabled
Remote management is enabled on port 3333
[1B blob data]
ETH: Stratum - connecting to 'eth-eu2.nanopool.org' <92.222.180.118> port 9999
ETH: Stratum - Connected (eth-eu2.nanopool.org:9999)
ETH: Authorized
Setting DAG epoch #140...
Setting DAG epoch #140 for GPU0
Create GPU buffer for GPU0
GPU0, OpenCL error -48 (0) - cannot create DAG on GPU
GPU 0 failed
Setting DAG epoch #140 for GPU0
GPU0, OpenCL error -48 (0) - cannot create DAG on GPU
GPU 0 failed
[66B blob data]
[66B blob data]
ETH: 10 pools are specified
Main Ethereum pool is eth-eu2.nanopool.org:9999
At least 16 GB of Virtual Memory is required for multi-GPU systems
Make sure you defined GPU_MAX_ALLOC_PERCENT 100
Be careful with overclocking, use default clocks for first tests
Press "s" for current statistics, "0".."9" to turn on/off cards, "r" to reload pools, "e" or "d" to select current pool
OpenCL initializing...
AMD Cards available: 1
GPU #0: gfx803, 8192 MB available, 36 compute units
POOL/SOLO version
Cannot build OpenCL program for GPU 0
GPU #0: set -etha as 0 (ETH algo for fast cards)
No NVIDIA CUDA GPUs detected.
Total cards: 1
AMD ADL library not found.
ETHEREUM-ONLY MINING MODE ENABLED (-mode 1)
ETH: eth-proxy stratum mode
Watchdog enabled
Remote management is enabled on port 3333
[1B blob data]
ETH: Stratum - connecting to 'eth-eu2.nanopool.org' <92.222.180.118> port 9999
ETH: Stratum - Connected (eth-eu2.nanopool.org:9999)
ETH: Authorized
Setting DAG epoch #140...
Setting DAG epoch #140 for GPU0
Create GPU buffer for GPU0
GPU0, OpenCL error -48 (0) - cannot create DAG on GPU
GPU 0 failed
Setting DAG epoch #140 for GPU0
GPU0, OpenCL error -48 (0) - cannot create DAG on GPU
GPU 0 failed
clearly it seems the AMDGPU are not detected correctly...
I've heard that AMDGPU-Pro drivers were not good, and maybe ROCm implementation would improve performances or control (hope for ADL library?)... but currently it is not working at all.
Anyway, ROCm drivers with AMDGPU-Pro OpenCL works like a charm.
rocm-smi moreover give me new information like electric power... It will be important for my automatic optimisation...
BTW thanks for your work. Happy to mine for you 1%.
August 31, 2017, 01:54:19 PM
Finally I found a workaround for ADL undervolting bug in latest blockchain drivers, I will release new version within 24 hours.
Since AMD won't be updating the blockchain drivers, you may as well say that this is probably the last time you have to deal with this ! Happy holidays
They already updated them once i'm sure they'll update them again if needed.
they made another "blockchain" version of their drivers ? Wow, thanks, I missed this one. Will give it a try tomorrow.
It is the same driver just added support for vega
More specifically, Vega FE.
August 31, 2017, 01:35:23 PM
Finally I found a workaround for ADL undervolting bug in latest blockchain drivers, I will release new version within 24 hours.
Since AMD won't be updating the blockchain drivers, you may as well say that this is probably the last time you have to deal with this ! Happy holidays
They already updated them once i'm sure they'll update them again if needed.
they made another "blockchain" version of their drivers ? Wow, thanks, I missed this one. Will give it a try tomorrow.
It is the same driver just added support for vega
August 31, 2017, 01:11:25 PM
Finally I found a workaround for ADL undervolting bug in latest blockchain drivers, I will release new version within 24 hours.
Since AMD won't be updating the blockchain drivers, you may as well say that this is probably the last time you have to deal with this ! Happy holidays
They already updated them once i'm sure they'll update them again if needed.
they made another "blockchain" version of their drivers ? Wow, thanks, I missed this one. Will give it a try tomorrow.
August 31, 2017, 09:55:15 AM
Finally I found a workaround for ADL undervolting bug in latest blockchain drivers, I will release new version within 24 hours.
Since AMD won't be updating the blockchain drivers, you may as well say that this is probably the last time you have to deal with this ! Happy holidays
They already updated them once i'm sure they'll update them again if needed.
August 31, 2017, 09:51:13 AM
Hello I am new to trying to mine Ethereum I have the new miner and using GTX 1080 ti on windows 10 using nvidia driver 384.94 trying to mine at supernova and I am getting eth: job timeout, disconnect and Received unknown response: {jsonrpc":"2.0","result';[0x0555531 etc,,,,,
Need some help please.
Need some help please.
Anybody?
post your batch command line
August 31, 2017, 09:45:57 AM
Finally I found a workaround for ADL undervolting bug in latest blockchain drivers, I will release new version within 24 hours.
will this have the LBRY upgrade as well
August 31, 2017, 09:45:37 AM
Finally I found a workaround for ADL undervolting bug in latest blockchain drivers, I will release new version within 24 hours.
Since AMD won't be updating the blockchain drivers, you may as well say that this is probably the last time you have to deal with this ! Happy holidays
Jump to: