Search content
Sort by
Showing 14 of 14 results by rufo28
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v11.7 (Windows/Linux)
Any idea what's going on here?
All of the sudden, my miner doesn't work anymore...
https://i.imgur.com/Pu2Nafe.jpg
All of the sudden, my miner doesn't work anymore...
https://i.imgur.com/Pu2Nafe.jpg
Just now , first time to see rejected share in my rig since the beginning i used claymore..
I've got 2 rejected shares now..
FYI, did not touch or configured anything..
It is a weird day!
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v11.7 (Windows/Linux)
What does this mean in the log:the lines in bold
00:47:50:494 860 ETH: 03/13/18-00:47:50 - New job from us1.ethermine.org:4444
00:47:50:494 860 target: 0x0000000112e0be82 (diff: 4000MH), epoch 174(2.36GB)
00:47:50:494 860 gpu #0 dt 0.13 (0%, good)
00:47:50:494 860 gpu #1 dt 0.13 (0%, good)
00:47:50:494 860 ETH: 03/13/18-00:47:50 - New job from us1.ethermine.org:4444
00:47:50:494 860 target: 0x0000000112e0be82 (diff: 4000MH), epoch 174(2.36GB)
00:47:50:494 860 gpu #0 dt 0.13 (0%, good)
00:47:50:494 860 gpu #1 dt 0.13 (0%, good)
Anyone answer this question?
I'm also wondering what is this mean?
It's for debug purposes, don't pay any attention to it.
Thanks @Claymore for the feedback! cheers!
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v11.3 (Windows/Linux)
What does this mean in the log:the lines in bold
00:47:50:494 860 ETH: 03/13/18-00:47:50 - New job from us1.ethermine.org:4444
00:47:50:494 860 target: 0x0000000112e0be82 (diff: 4000MH), epoch 174(2.36GB)
00:47:50:494 860 gpu #0 dt 0.13 (0%, good)
00:47:50:494 860 gpu #1 dt 0.13 (0%, good)
00:47:50:494 860 ETH: 03/13/18-00:47:50 - New job from us1.ethermine.org:4444
00:47:50:494 860 target: 0x0000000112e0be82 (diff: 4000MH), epoch 174(2.36GB)
00:47:50:494 860 gpu #0 dt 0.13 (0%, good)
00:47:50:494 860 gpu #1 dt 0.13 (0%, good)
Anyone answer this question?
I'm also wondering what is this mean?
Re: [ANN] [1080 | 1080TI] ETHlargement - The Hashrate Hardener
49.55 mh is no great at all 
53-55mh is achievable with this tool.
53-55mh is achievable with this tool. yes, got 54-55 MH/s here!Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v11.7 (Windows/Linux)
Dear Claymore,
thanks for the updated version, but i have error for NVML cannot detect temperature as well as CUDA error.
If it worked before try lower clocks to see if that is the reason.thanks for the updated version, but i have error for NVML cannot detect temperature as well as CUDA error.
From your log:
Code:
22:25:30:396 294c gpu 9 nvidia memclock set ok (6355MHz, previous value was 5505MHz)
So may be set a bit lower overclock than +850? That's what I mean.
@claymore:
Thanks, so far no downtime for 11.7.. and the oc config are working in my 12 GPUs.
@Claymore: Thanks for the clarification, i will try again 11.7 when i get home and configured less overclock in the script to the GPUs.
I will let you know what will be the result.
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v11.7 (Windows/Linux)
@claymore
can you maybe fix miner for gpu temp monitor
when i use MS remote desktop, and run miner .. only 1 gpu show temp
when i run minier via teamviver, show all gpu temp and fan %, or i run local .. via keyboard and monitor
but, teamviver is not free, and from time to time block conncection and you must wait for another.
And MS remote desktop is builed in, free and working great
can you maybe fix miner for gpu temp monitor
when i use MS remote desktop, and run miner .. only 1 gpu show temp
when i run minier via teamviver, show all gpu temp and fan %, or i run local .. via keyboard and monitor
but, teamviver is not free, and from time to time block conncection and you must wait for another.
And MS remote desktop is builed in, free and working great
It is not related to the miner, the reason is in Windows and AMD drivers.
@dadoremix : Kindly try chrome remote desktop, it's free as well.
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v11.7 (Windows/Linux)
Dear Claymore,
thanks for the updated version, but i have error for NVML cannot detect temperature as well as CUDA error.
If it worked before try lower clocks to see if that is the reason.thanks for the updated version, but i have error for NVML cannot detect temperature as well as CUDA error.
From your log:
Code:
22:25:30:396 294c gpu 9 nvidia memclock set ok (6355MHz, previous value was 5505MHz)
So may be set a bit lower overclock than +850? That's what I mean.
@Claymore: Thanks for the clarification, i will try again 11.7 when i get home and configured less overclock in the script to the GPUs.
I will let you know what will be the result.
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v11.7 (Windows/Linux)
Dear Claymore,
thanks for the updated version, but i have error for NVML cannot detect temperature as well as CUDA error.
thanks for the updated version, but i have error for NVML cannot detect temperature as well as CUDA error.
If it worked before try lower clocks to see if that is the reason.
@Claymore : do you mean under clocking my GPU's?
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v11.7 (Windows/Linux)
v11.7:
- added temperature management and overclock support for recent Nvidia cards in Windows: "-tt", "-powlim", "-cclock", "-mclock", "-tt", "-fanmax", "-fanmin" options are supported for Nvidia too.
- now "y" key also disables CrossFire.
- added "-y" option.
- fixed issue with miner restart that was required sometimes to apply overclock settings for AMD cards.
- fixed issue with rejected shares when "-esm 3" option is used.
- Linux version: fixed issue with remote management.
- some changes in watchdog routines to improve ability to restart miner after various OpenCL fails.
- a few minor bug fixes and improvements.
PS. For Nvidia "-cclock" and "-mclock" options also support delta mode, for example, "-mclock +400", see readme for details.
- added temperature management and overclock support for recent Nvidia cards in Windows: "-tt", "-powlim", "-cclock", "-mclock", "-tt", "-fanmax", "-fanmin" options are supported for Nvidia too.
- now "y" key also disables CrossFire.
- added "-y" option.
- fixed issue with miner restart that was required sometimes to apply overclock settings for AMD cards.
- fixed issue with rejected shares when "-esm 3" option is used.
- Linux version: fixed issue with remote management.
- some changes in watchdog routines to improve ability to restart miner after various OpenCL fails.
- a few minor bug fixes and improvements.
PS. For Nvidia "-cclock" and "-mclock" options also support delta mode, for example, "-mclock +400", see readme for details.
Dear Claymore,
thanks for the updated version, but i have error for NVML cannot detect temperature as well as CUDA error.
Below the sample result logs:
=========================================================================
22:25:30:131 294c gpu 8 nvidia powlim set ok (85%, previous value was 100%)
22:25:30:177 294c gpu 8 nvidia setcoreclock set ok (1733MHz, previous value was 1683MHz)
22:25:30:271 294c gpu 8 nvidia memclock set ok (6355MHz, previous value was 5505MHz)
22:25:30:302 294c gpu 9 nvidia powlim set ok (85%, previous value was 100%)
22:25:30:349 294c gpu 9 nvidia setcoreclock set ok (1632MHz, previous value was 1582MHz)
22:25:30:396 294c gpu 9 nvidia memclock set ok (6355MHz, previous value was 5505MHz)
22:25:30:412 294c gpu 10 nvidia powlim set ok (70%, previous value was 100%)
22:25:30:459 294c gpu 10 nvidia setcoreclock set ok (1763MHz, previous value was 1733MHz)
22:25:30:506 294c gpu 10 nvidia memclock set ok (5555MHz, previous value was 5005MHz)
22:25:47:018 294c CUDA error 9 #102 - 46
22:25:47:097 294c CUDA error 9 #102a - 46
22:25:47:097 294c CUDA error 9 #103 - 46
22:25:47:097 294c CUDA error 9 #105 - 46
22:25:47:097 294c CUDA error 10 #102 - 46
22:25:47:112 294c CUDA error 10 #102a - 46
22:25:47:128 294c CUDA error 10 #103 - 46
22:25:47:128 294c CUDA error 10 #105 - 46
22:25:47:300 2988 NVML: cannot get current temperature, error 999 (an internal driver error occurred)
22:25:47:315 2988 NVML: cannot get fan speed, error 999 (an internal driver error occurred)
22:25:47:519 2988 NVML: cannot get current temperature, error 999 (an internal driver error occurred)
22:25:47:519 2988 NVML: cannot get fan speed, error 999 (an internal driver error occurred)
22:25:47:644 2988 NVML: cannot get current temperature, error 999 (an internal driver error occurred)
22:25:47:644 2988 NVML: cannot get fan speed, error 999 (an internal driver error occurred)
22:25:47:753 2988 NVML: cannot get current temperature, error 999 (an internal driver error occurred)
22:25:47:753 2988 NVML: cannot get fan speed, error 999 (an internal driver error occurred)
22:25:47:878 2988 NVML: cannot get current temperature, error 999 (an internal driver error occurred)
22:25:47:878 2988 NVML: cannot get fan speed, error 999 (an internal driver error occurred)
22:25:47:987 2988 NVML: cannot get current temperature, error 999 (an internal driver error occurred)
best regards,
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v11.6 (Windows/Linux)
Hello Gents,
I would like to share my issue using claymore (new or old) versions.
My RIG consists of 3 AMD and 7 Nvidia (2x1080 and 5x1080Ti).
When i ran it for mining only Ethereum, there's a "Cuda error 11 - cannot write buffer for DAG".
I already put VM max to 16000MB , but still it will show this error.
Experiment 1 : I separate running my bat file for the 3 AMD ( -platform 1 , all are working and running ), then ran the 7 Nvidia bat file (-platform 2, 2-3 cards has this error)
Experiment 2 : I ran in one bat file (-platform 3) all AMD and Nvidia Cards, results still the same 2-3 cards has the error.
Experiment 3 : I ran in one bat file (-platform 3 , -di 01234567), AMD and Nvidia ( excluding 2 cards - either AMD or Nvidia) it works fine and continuously running..
So , is there any limitation for the claymore miner in number of cards in RIG?
Thanks and much appreciated if you can clear this up..
I would like to share my issue using claymore (new or old) versions.
My RIG consists of 3 AMD and 7 Nvidia (2x1080 and 5x1080Ti).
When i ran it for mining only Ethereum, there's a "Cuda error 11 - cannot write buffer for DAG".
I already put VM max to 16000MB , but still it will show this error.
Experiment 1 : I separate running my bat file for the 3 AMD ( -platform 1 , all are working and running ), then ran the 7 Nvidia bat file (-platform 2, 2-3 cards has this error)
Experiment 2 : I ran in one bat file (-platform 3) all AMD and Nvidia Cards, results still the same 2-3 cards has the error.
Experiment 3 : I ran in one bat file (-platform 3 , -di 01234567), AMD and Nvidia ( excluding 2 cards - either AMD or Nvidia) it works fine and continuously running..
So , is there any limitation for the claymore miner in number of cards in RIG?
Thanks and much appreciated if you can clear this up..
Try VM 32000
Thanks for the response, i will try and check..
Will inform you..
@AzzAz , Many thanks for your suggestion... currently after changing it to 32000 it run successfully for few minutes now.
I will observed further...
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v11.6 (Windows/Linux)
Hello Gents,
I would like to share my issue using claymore (new or old) versions.
My RIG consists of 3 AMD and 7 Nvidia (2x1080 and 5x1080Ti).
When i ran it for mining only Ethereum, there's a "Cuda error 11 - cannot write buffer for DAG".
I already put VM max to 16000MB , but still it will show this error.
Experiment 1 : I separate running my bat file for the 3 AMD ( -platform 1 , all are working and running ), then ran the 7 Nvidia bat file (-platform 2, 2-3 cards has this error)
Experiment 2 : I ran in one bat file (-platform 3) all AMD and Nvidia Cards, results still the same 2-3 cards has the error.
Experiment 3 : I ran in one bat file (-platform 3 , -di 01234567), AMD and Nvidia ( excluding 2 cards - either AMD or Nvidia) it works fine and continuously running..
So , is there any limitation for the claymore miner in number of cards in RIG?
Thanks and much appreciated if you can clear this up..
I would like to share my issue using claymore (new or old) versions.
My RIG consists of 3 AMD and 7 Nvidia (2x1080 and 5x1080Ti).
When i ran it for mining only Ethereum, there's a "Cuda error 11 - cannot write buffer for DAG".
I already put VM max to 16000MB , but still it will show this error.
Experiment 1 : I separate running my bat file for the 3 AMD ( -platform 1 , all are working and running ), then ran the 7 Nvidia bat file (-platform 2, 2-3 cards has this error)
Experiment 2 : I ran in one bat file (-platform 3) all AMD and Nvidia Cards, results still the same 2-3 cards has the error.
Experiment 3 : I ran in one bat file (-platform 3 , -di 01234567), AMD and Nvidia ( excluding 2 cards - either AMD or Nvidia) it works fine and continuously running..
So , is there any limitation for the claymore miner in number of cards in RIG?
Thanks and much appreciated if you can clear this up..
Try VM 32000
Thanks for the response, i will try and check..
Will inform you..
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v11.6 (Windows/Linux)
Hello Gents,
I would like to share my issue using claymore (new or old) versions.
My RIG consists of 3 AMD and 7 Nvidia (2x1080 and 5x1080Ti).
When i ran it for mining only Ethereum, there's a "Cuda error 11 - cannot write buffer for DAG".
I already put VM max to 16000MB , but still it will show this error.
Experiment 1 : I separate running my bat file for the 3 AMD ( -platform 1 , all are working and running ), then ran the 7 Nvidia bat file (-platform 2, 2-3 cards has this error)
Experiment 2 : I ran in one bat file (-platform 3) all AMD and Nvidia Cards, results still the same 2-3 cards has the error.
Experiment 3 : I ran in one bat file (-platform 3 , -di 01234567), AMD and Nvidia ( excluding 2 cards - either AMD or Nvidia) it works fine and continuously running..
So , is there any limitation for the claymore miner in number of cards in RIG?
Thanks and much appreciated if you can clear this up..
I would like to share my issue using claymore (new or old) versions.
My RIG consists of 3 AMD and 7 Nvidia (2x1080 and 5x1080Ti).
When i ran it for mining only Ethereum, there's a "Cuda error 11 - cannot write buffer for DAG".
I already put VM max to 16000MB , but still it will show this error.
Experiment 1 : I separate running my bat file for the 3 AMD ( -platform 1 , all are working and running ), then ran the 7 Nvidia bat file (-platform 2, 2-3 cards has this error)
Experiment 2 : I ran in one bat file (-platform 3) all AMD and Nvidia Cards, results still the same 2-3 cards has the error.
Experiment 3 : I ran in one bat file (-platform 3 , -di 01234567), AMD and Nvidia ( excluding 2 cards - either AMD or Nvidia) it works fine and continuously running..
So , is there any limitation for the claymore miner in number of cards in RIG?
Thanks and much appreciated if you can clear this up..
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v11.5 (Windows/Linux)
Do you mine running HwInfo 24/7 can affect hashrate/valid shares and overall work of the miner?
Yes, it can affect overall stability of a system
I have just recently started running HWinfo 24/7 and have not had any problems - so far - but that said it is best not to have anything else running when mining as it could affect the overall stability.
Yes, I've had the same with hwinfo. I installed and ran it and lost 5-10% hashrate. Turned it off, and back to normal.
How about speccy app running 24/7, does it degrades hashrate?