Msi afterburner will allow you gain much more control over the gpus so that you can undervolt and change fan speeds as well create custom fan profiles.

24 mh is a bit slow, you should be able to get atleast 25 mh per card or more depending if you over clock.  But from what I read is that can change a bit depending the type of ram the card contains and some other things.  try adding this into the miner bat for starters, --cl-global-work 16384  --cl-local-work 256

Thanks for the info! that parameter got me 25mh.
Was there a new DAG just a few days ago?  I remember getting 28-29 not too long ago, or maybe my memory is just bad.
Any recommended core/memory clocks?  I have an R9 Reference card (still going strong) and I believe it's "Hawaii"

I'm having issues getting ethminer to work on Windows 7 with GTX 1080 card. I'm using version 1.1.3 It crashes with CUDA error in func 'ethash_cuda_miner::search' at line 303: unknown error. In open cl it crashes with  clEnqueueMapBuffer(-5). Both crash right after the DAG loads before mining starts. the windows nvidia driver crashes and the screen flashes when either of these happen. Any help would be greatly appreciated.

Still occasionally getting a hang when starting the miner and generating dags even though you can restart it any it seems to work fine.

The problem is when the dag changes when the miner is working it causes the client to hang sometimes for some reason.

1.0.8 runs fine on my machines. I'm not sure what it is. It seems 1.1.3 randomly locks up too while the whole system seems fine. Not sure what's causing it. The epoch change or the miner just having stability issues.

This happens to me, only with AMD under windows (Nvidia under linux works fine)  with both, version 1.0.8 and 1.1.2
both versions freezes when a new dag is generated.
just close the miner, started it again and it works, but it's downtime until i find out.

Curious bit here... I overclock my memory on my cards. I wonder if the stability issues and the random hangs when generating the DAG files relate to it becoming corrupt while entering memory and being in memory.

The cards hash fine, but I could see a large chunk of memory becoming corrupted possible causing this to happen. Perhaps some sort of error checking to prevent this from happening? I'm sure I'm not the only one that OCs memory.

for the  "-L sequential"  on version ethminer-opencl-0.9.41 it s not recognize

overclock the memory does it really increase performance?

i tryied on r9 380 asus, xfx, sapphire, they don't have same stock memory speed

but i see no difference when increasing memory speed, and 1500mhz is not stable of some of them
so i put them all at 1400 (asus default is 1375, even with 1375 make no difference)

i have only 2gigas's
asus 380's are the fastest  20.8mh for the best one (20.1 for the worst)    best setting --cl-global-work 8192 --cl-local-work 128

sapphire the best 19.3mh ,the worst one 17.6    best setting   --cl-global-work 16384 --cl-local-work 64

xfx did not test yet but it s less than 19mh   current setting --cl-global-work 16384 --cl-local-work 64

for the gpu clock speed asus run at 1010 (default 970), all the other at 1033 (default 1000)

I've got some rigs running at Win8 with 14.4 whql drivers. Miner 1.0.8 is working just fine (-S -G --farm-recheck 400). However, miner 1.1.3 does not accept/reject any shares.. it just shows [A0+0:R0:F0] all the time. It does show mining speed (pretty similar to 1.0.8 ) in the mining window.. Just not accepting shares.  

These rigs have 5x R9 280X each

Or simply copy opencl files from 14.4 into miner directory