A4 Dominator Configuration

I have started this topic to discuss Innosilicon A4 Dominator configuration on Prohashing. Thanks for your input!

I used to have a few A4s on here but sold them.. Anything specific you need to know I will do my best..

The answer to the A4 is to make sure you have a Batch 3 A4 and are running 2.0.3 of the software.

Works great.

4/30/17 9:35 pm EST: I have been running the A4's at 1200 Mhz. I still am seeing a situation where one of the 4 cores drops out and starts shares start getting rejected. I think this may be a power issue on ProHashing. I reset the cards to run at 1000 Mhz to see if this resolves the issue. Side note the other A4's I have pointed to another pool have been hashing fine all day, with minimal rejected shares.

5/1/2017 7:14 am EST: 2 A4's running on PH overnight, one set to 1000Mhz is hashing fine, the one set to 1100Mhz has dropped one core with an 18% reject rate. One A4 running on a different pool is set at 1200Mhz and has a low reject rate on all cores. All are set at 820mV.

jinxorbit wrote:4/30/17 9:35 pm EST: I have been running the A4's at 1200 Mhz. I still am seeing a situation where one of the 4 cores drops out and starts shares start getting rejected. I think this may be a power issue on ProHashing. I reset the cards to run at 1000 Mhz to see if this resolves the issue. Side note the other A4's I have pointed to another pool have been hashing fine all day, with minimal rejected shares.

Does this only happen on the same core, every time? Or, is there no way to tell which core it is?

It seems to random which cores drop out with high reject rates. I currently think that the miners difficulty of 8192 might be the issue...

5/1/17 9:13 am EST: moving all A4 back to PH with device difficulty set to 8. So far device reject rates are low. All cores are running fine for about the past hour or so.

[Archived image unavailable: http://johnorben.com/wp-content/uploads/2017/05/A4_ProHashing_20170501.jpg]
Current config as of 5/1/2017 11:00 am EST;
this configuration has been running stable for several hours.
Device reject .76% to 2.37%.

jinxorbit wrote:[Archived image unavailable: http://johnorben.com/wp-content/uploads/2017/05/A4_ProHashing_20170501.jpg]
Current config as of 5/1/2017 11:00 am EST;
this configuration has been running stable for several hours.
Device reject .76% to 2.37%.

You're still running the 2.0.2 software. I suggest you move to 2.0.3 -- It has several fixes beyond the Nicehash Xnonce support and greatly improved the performance of mine.

Edit:

Well I just checked mine out
23days 20h 19m 06s Runtime
15.01% Device Reject
2.66% Pool Reject
0.05% Pool Stale