Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 1352. (Read 6590565 times)
April 27, 2016, 03:40:19 PM
4.0 installed and working great. Only .5 MH less on the speed.
April 27, 2016, 03:38:49 PM
@ Claymore
I updated to v3.3 from a previous 3.x version and was no longer able to mine due to failing to create a big buffer. I was forced to revert to v 1.2 to resolve the issue as any other builds replicate the problem. Absolutely no changes were made to the system in question; all I did was close the previously working miner and updated the directory's contents. All environment variables have been set as well as 2 x 8 GB pagefiles and I've also removed temp files as well as the dag directory which I additionally decided to provide an alternate one on a seperate hard drive to hopefully eliminate the problem. I also tried renaming the dag files successfully created by QTminer in hopes of using them with Claymore's but that also didn't work. My other rig which is also Hawaii based surprisingly doesn't suffer from this symptom. I just gave v4.0 a try but still suffer from the same error.
Any feedback would be much appreciated!
I updated to v3.3 from a previous 3.x version and was no longer able to mine due to failing to create a big buffer. I was forced to revert to v 1.2 to resolve the issue as any other builds replicate the problem. Absolutely no changes were made to the system in question; all I did was close the previously working miner and updated the directory's contents. All environment variables have been set as well as 2 x 8 GB pagefiles and I've also removed temp files as well as the dag directory which I additionally decided to provide an alternate one on a seperate hard drive to hopefully eliminate the problem. I also tried renaming the dag files successfully created by QTminer in hopes of using them with Claymore's but that also didn't work. My other rig which is also Hawaii based surprisingly doesn't suffer from this symptom. I just gave v4.0 a try but still suffer from the same error.
Any feedback would be much appreciated!
April 27, 2016, 03:33:05 PM
Solo mining support and Linux version are planned, I'm working on it.
April 27, 2016, 03:25:24 PM
@claymore is the solo mining proxy bits in on the version 4 ?
also how does it work with no DAG i'm confused
*edit dag on the GPU** not sure what that means but you're the developer lol
also how does it work with no DAG i'm confused
*edit dag on the GPU** not sure what that means but you're the developer lol
April 27, 2016, 03:22:21 PM
It took under 10 seconds on 270x 
April 27, 2016, 03:19:19 PM
This now means that the algorithm does not require additional files, which opens the way Asic .
No asics, I just decided to solve issues with DAG files completely, I planned to do it later but after Wolf0's phrase "goddamned DAGs" I understood that I must do it right now
Now I generate DAGs directly on GPUs so no DAG files are used at all.And no slowdowns on restart?
If you have HDD, not SSD, you will see that v4.0 starts much faster. If you have slow CPU you will see the same.
So it doesnt take 10 mins on every restart to generate the dag on the gpu mem directly? You Rock!
April 27, 2016, 03:17:05 PM
This now means that the algorithm does not require additional files, which opens the way Asic .
No asics, I just decided to solve issues with DAG files completely, I planned to do it later but after Wolf0's phrase "goddamned DAGs" I understood that I must do it right now
Now I generate DAGs directly on GPUs so no DAG files are used at all.And no slowdowns on restart?
If you have HDD, not SSD, you will see that v4.0 starts much faster. If you have slow CPU you will see the same.
April 27, 2016, 03:15:10 PM
This now means that the algorithm does not require additional files, which opens the way Asic .
No asics, I just decided to solve issues with DAG files completely, I planned to do it later but after Wolf0's phrase "goddamned DAGs" I understood that I must do it right now
Now I generate DAGs directly on GPUs so no DAG files are used at all.And no slowdowns on restart?
April 27, 2016, 03:14:35 PM
Great job!
Although speed is slightly lower with 4.0 than 3.3
Although speed is slightly lower with 4.0 than 3.3
Speed is the same, but today is new epoch #47, probably you remember speed for epoch #46.
April 27, 2016, 02:57:37 PM
This now means that the algorithm does not require additional files, which opens the way Asic .
No asics, I just decided to solve issues with DAG files completely, I planned to do it later but after Wolf0's phrase "goddamned DAGs" I understood that I must do it right now
Now I generate DAGs directly on GPUs so no DAG files are used at all. April 27, 2016, 02:56:59 PM
This now means that the algorithm does not require additional files, which opens the way Asic .
Thats what i'm thinking but i cant believe it
April 27, 2016, 02:54:52 PM
powercolor R7 370 1150@1500, win 8.1, 16.1.1 crimson, claymore 3.3 = ~17mh, total of 102Mh on 6 gpu machine. Like it a lot so far.
April 27, 2016, 02:53:39 PM
mr Claymore you clever conman 
test setup 3xr9 380h operated under standards miner. Had 62 Mhs stable. After switching on your miner received 50 Mhs.
Explain what is the problem?
TKS
test setup 3xr9 380h operated under standards miner. Had 62 Mhs stable. After switching on your miner received 50 Mhs.
Explain what is the problem?
TKS
Probably lack of your knowledge, most of us boosted 5-10%
Here are my 4x380 properly set
Sapphire Nitro R9 380 2GB (Samsung memory - its 1mh faster than Elpida), core clock is stock (1040), memclock is +50(1500). -etha 1
April 27, 2016, 02:53:24 PM
This now means that the algorithm does not require additional files, which opens the way Asic .
April 27, 2016, 02:49:09 PM
v4.0:
- no DAG files anymore.
- removed "-dir" option.
- Bug fixes.
- no DAG files anymore.
- removed "-dir" option.
- Bug fixes.
What do you mean "no DAG files"?
April 27, 2016, 02:45:20 PM
Great job!
Although speed is slightly lower with 4.0 than 3.3
Although speed is slightly lower with 4.0 than 3.3
April 27, 2016, 02:28:08 PM
18 is not bad result with current DAG size
Ethereum is very memory intensive.
Run stock, and ether only mining, then with Afterburner try increasing mem speed through
1250 - > 1375 -> 1500 and check speed
Ethereum is very memory intensive.
Run stock, and ether only mining, then with Afterburner try increasing mem speed through
1250 - > 1375 -> 1500 and check speed
Stock, or moving memory/CPU clock speed does not change anything.
18.1 dual mining
17.9 solo eth mining
Changed to 4.0 no difference.
Thanks
April 27, 2016, 02:15:53 PM
v4.0:
- no DAG files anymore.
- removed "-dir" option.
- Bug fixes.
- no DAG files anymore.
- removed "-dir" option.
- Bug fixes.
April 27, 2016, 02:13:28 PM
Hi,
Running 15.12 Drivers Win 64bit. Latest 3.3 miner.
1 x SAPPHIRE HD 7950 3GB OC with Boost Vapor-X Edition
Only getting 18.1MH/s what am I doing wrong
If I put it in mode one the hash rate goes DOWN to 17.9MH/s
EthDcrMiner64.exe -ethi 16 -epool eu1.nanopool.org:9999 -ewal -epsw x -dcri 21 -dpool stratum+tcp://stratum.decredpool.org:3333 -dwal -dpsw x
Strange thing is overclocking doesn't make any difference, or can MSI afterburner not overclock these cards? if so how do I do that?
Even if I move the CPU Clock to 1100 the hash rate doesn't go up (Cant overclock from the miner program, no matter what values I put it crashes)
18 is not bad result with current DAG sizeRunning 15.12 Drivers Win 64bit. Latest 3.3 miner.
1 x SAPPHIRE HD 7950 3GB OC with Boost Vapor-X Edition
Only getting 18.1MH/s what am I doing wrong
If I put it in mode one the hash rate goes DOWN to 17.9MH/s
EthDcrMiner64.exe -ethi 16 -epool eu1.nanopool.org:9999 -ewal
Strange thing is overclocking doesn't make any difference, or can MSI afterburner not overclock these cards? if so how do I do that?
Even if I move the CPU Clock to 1100 the hash rate doesn't go up (Cant overclock from the miner program, no matter what values I put it crashes)
Ethereum is very memory intensive.
Run stock, and ether only mining, then with Afterburner try increasing mem speed through
1250 - > 1375 -> 1500 and check speed
April 27, 2016, 02:11:51 PM
I've also had problems with dual mining while eth only was stable. One rig died, other restarted. Both were weak psu and nothing more. Gave them more juice and now works like a charm on 3.2
There is easy way to test it, start dual mode with -dcri 1 and if no problems, start to increase it while mining by pressing +. Maximum consumption is reached somewhere around -dcri 80.
Wattmeter showed me 200W extra power on 4x280x rig..
Same thing with dag creation, draws more power.
Anyone sees sent hashrate on dwarf?
There is easy way to test it, start dual mode with -dcri 1 and if no problems, start to increase it while mining by pressing +. Maximum consumption is reached somewhere around -dcri 80.
Wattmeter showed me 200W extra power on 4x280x rig..
Same thing with dag creation, draws more power.
Anyone sees sent hashrate on dwarf?
I though i had a problem with the 1k watt XFX psu as well i had but i tried it with just 2 390 cards rather than the four i nonmally run and my miner still crashes in dual mode, works fine in solo eth mode.
To make sure its not a power issue, run it at -dcri 1. Risers are powered?
yup i always use powered usb riders
a 1k psu should be able to power two 390s though thier max TDP is 300watts, ill try the -dcri 1 setting though
Jump to: