I have the same problem as DaveyJones. v3.0 not working for me.When i run it through CMD it prompts the parameters and does nothing at all. No errors, no works, nothing.Win7 x64, R9 380x, Crimson 15.12 (Crimson 16.1)

I have the same problem as DaveyJones. v3.0 not working for me.When i run it through CMD it prompts the parameters and does nothing at all. No errors, no works, nothing.Win7 x64, R9 380x, Crimson 15.12 (Crimson 16.1)

Bumping ... started with the 2.0 version

Sorry, I have no idea why you see it. I think it must be something related to some software on your system. You can try it on clean Windows to check if it is true.

Please read Readme and FAQ in the first post of this thread before asking any questions, probably the answer is already there.

I have the same problem as DaveyJones. v3.0 not working for me.When i run it through CMD it prompts the parameters and does nothing at all. No errors, no works, nothing.Win7 x64, R9 380x, Crimson 15.12 (Crimson 16.1)

Bumping ... started with the 2.0 version

Sorry, I have no idea why you see it. I think it must be something related to some software on your system. You can try it on clean Windows to check if it is true.

Why should it be a software issue when everything till 1.2 ran fine? Must be a change that came into your miner between 1.2 and 2.0

I have the same problem as DaveyJones. v3.0 not working for me.When i run it through CMD it prompts the parameters and does nothing at all. No errors, no works, nothing.Win7 x64, R9 380x, Crimson 15.12 (Crimson 16.1)

Bumping ... started with the 2.0 version

Sorry, I have no idea why you see it. I think it must be something related to some software on your system. You can try it on clean Windows to check if it is true.

Why should it be a software issue when everything till 1.2 ran fine? Must be a change that came into your miner between 1.2 and 2.0

I use third-party EXE packer to protect miner from disassembling and changes, perhaps it can cause such thing but I cannot remove it because I have some experience about how my miners can be used if they don't have this protection. Anyway, it works for >99% systems. So your system must have something special.

Please read Readme and FAQ in the first post of this thread before asking any questions, probably the answer is already there.

@Claymore <-- seems to get your attention Any idea, v3 seems to crash after a while on 6x nano. v2 works perfectly (same settings, nothing changed)Also, speed remains the same. No improvement, in some cases even less..As i said before, all my other rigs with older cards are doing A LOT better. So kudos on that!

No ideas about crashes, for Fury there are not any improvements, though on my Nano I don't see any slowdown, same speed exactly.

Been having the issue with the miner that crashes on a few rigs of mine now.

I'm absolutely certain, Trixx seems to be the only utility which allows you to do so without any hassle anyway. A wide variety of algorithms benefit from setting the memory to 150 Mhz [600 Mhz effective] such as Quark & Qubit which rely on latency rather than throughput. This sets your memory bus to a strap with tighter timings which will ultimately lower power consumption and heat and also allows for more overclocking headroom. To prove my point, I managed to yield 23 MH/s for Quark, a similar figure for Qubit and 37 MH/s Ethereum & 620 MH/s for Decred in dual mining mode on a 390x without rejected shares.

Has anyone tried Stilit's bios or any other modded bios for that matter on Ethereum?

Seriously why so complicated, its simple... Install drivers that allow underclock (13.x) then put open cl dll's from the 15.12 drivers in the folder with the miner, the miner will use the 15.12 dll files for opencl and any over/underclocking will be controlled by the installed drivers. No restarting changing settings or generally screwing around, simple and clean.

I'm absolutely certain, Trixx seems to be the only utility which allows you to do so without any hassle anyway. A wide variety of algorithms benefit from setting the memory to 150 Mhz [600 Mhz effective] such as Quark & Qubit which rely on latency rather than throughput. This sets your memory bus to a strap with tighter timings which will ultimately lower power consumption and heat and also allows for more overclocking headroom. To prove my point, I managed to yield 23 MH/s for Quark, a similar figure for Qubit and 37 MH/s Ethereum & 620 MH/s for Decred in dual mining mode on a 390x without rejected shares.

Has anyone tried Stilit's bios or any other modded bios for that matter on Ethereum?

Seriously why so complicated, its simple... Install drivers that allow underclock (13.x) then put open cl dll's from the 15.12 drivers in the folder with the miner, the miner will use the 15.12 dll files for opencl and any over/underclocking will be controlled by the installed drivers. No restarting changing settings or generally screwing around, simple and clean.

I use Sapphire Trixx to downclock my memory to 150 Mhz which also increases hashrate due to tighter timings.

Using 15.7.1 and Trixx? Are You sure it's underclocked? Checked in Trixx card info or GPU-Z?

I'm absolutely certain, Trixx seems to be the only utility which allows you to do so without any hassle anyway. A wide variety of algorithms benefit from setting the memory to 150 Mhz [600 Mhz effective] such as Quark & Qubit which rely on latency rather than throughput. This sets your memory bus to a strap with tighter timings which will ultimately lower power consumption and heat and also allows for more overclocking headroom. To prove my point, I managed to yield 23 MH/s for Quark, a similar figure for Qubit and 37 MH/s Ethereum & 620 MH/s for Decred in dual mining mode on a 390x without rejected shares.

Has anyone tried Stilit's bios or any other modded bios for that matter on Ethereum?

15.12 Trixx and Win7 x64 I can only overclock, but not downclock. Trixx accepts downclock, pretends that it's done, but if I check in card info or GPU-Z clocks are default values.

My point is. It works with every driver, no need to copy files. It all works out of the box. (tested on 6 different kind of cards and 4 different chips) ;-)

In my experience AB does not work well with rigs using different cards ie 7950, 7870 etc. Also using dlls is a handy way to get past certain issue with drivers and more than 4 gpu in windows, ie when using 6 gpu driver mod not all drivers are supported. At any rate it is good for community to know there are a few different options.

@Claymore, since the v3.0 I got 3 hangs on my rigs. Some of the gpu crashes, then the miner is trying to restart itself but it stops on the text logo where it says"Claymore dual.... v3.0" Can you make an option if gpu crashes to reboot the whole windows? That way It wont take an hour for the pool to notifies me. Right now i got a better hashrate with your miner but its pointless because i lost 3-4 working hours on some rigs. Got lucky it didnt happen at night...

- reduced delays at shares sending, it must improve speed on pools a bit.

It is not a major update, just found some additional delays in v3.0 so I uplodaded an update. No other changes.

PS. I see dwarfpool has "Sent hashrate" column. How to make it work? I tried eth-proxy + ethminer but it is still empty. If someone can point me how to make it work for Stratum I will add it to my miner.

Please read Readme and FAQ in the first post of this thread before asking any questions, probably the answer is already there.

v3.1: I see dwarfpool has "Sent hashrate" column. How to make it work? I tried eth-proxy + ethminer but it is still empty. If someone can point me how to make it work for Stratum I will add it to my miner.