Bitcoin Forum

I've been mining for a couple days already i have about 10 D3s running at the moment and i can't cerrainly say how often it happens because i haven't been monitoring them long enough but they'll go into fault mode (red led blinking) if i check the status 1 or 2 hasboards will show xxxxxx after a while will come back to the normal status if anyone is mining right now are youe miners doing the same?

bump

That could be also a fault PSU, try to switch PSU's from a working one to that one and try it again.

I know thats what the troubleshooting says but i have 14 and they all do the same lol

Mine just arreived and it's also doing the same... damnit!!

Gonna open a support ticket

They all doing it i guess is the way they work and we need a firware update

Perhaps not enough power, that is the sound of it, maybe. You need the log files to see where the issue is. Before coming here, check those because that will tell you what the deal is and you will probably not even need advice after that because it is very straight forward

Already switched PSU, and still the same, and it's only happening on one (in my case), and the PSU i switched is working perfectly on another rig

ok, i think i got the solution, i had same issue, i had my miners connected to internet through powerline (internet over power) but after i connected them directly to router and since then they run nonstop without issues....
 Try to put your miners to run directly to router, and check if they ll get same XXXXX issue again, im pretty sure the powerline adaptors cause this issue

Can't think of a router with that many ports

Mine is connected to a switch directly, which in turn is connected to the router, directly as well.

2 D3's, one with the issue, another without, I can only think it's hardware now

same here, 2 of the D3's have the same issue, after a couple of time they both
shows the xxx xxx
go down with frequenz will help for now, will see if it is more stable with lower Frequenz

This may or not make sense, I underclocked to 456M was still having HW Errors, then I switched the blade to the empty controller connector, and so far 10 minutes without errors (i was having them after 2m , mostly 5)

Thanks tomi_maroni for the underclock idea.

Try it and see if it works for you

EDIT: After I pressed post, here comes the error... FML

same here, underclocked to 438, and always Errors on both of them

I had same issues with you guys, if you are using powerline to connect to router, this is the issue, powerline use the electricity cables and it somehow mess with miner's elecricity, try to either connect the miners directly to router with ethernet, unless you have many miners then use hub or something, try to avoid powerline adaptors

At what temperature is yours running?

is your voltage is stable? no electricity spike or something ? try use some stabilizer maybe ?

now testing with freq 425, both 9hours stable,
Chain#    ASIC#    Frequency    MH/S(RT)    HW    Temp(PCB)    Temp(Chip)
1               60               425         4965.46      0         53             68
1               60               425         4991.61      0         51             65
1               60               425         5035.19      0         52             65

original and new apw3++ PSU from Bitmain

yeah it seems they probably clocked it too high

If you have 14 and they're all doiing the same, must be something with your setup.  Did you figure it out?

I have 7 L3+ and they all doing alright i don't think there is nothing wrong with my setup there's gotta be something wrong with the miners

I lost a hash board a couple times on one of my L3+'s and 2 of my D3s
In my case I just reboot and it comes back.

I'm also using a powerline network adapter.

I'm having the same issue and all of my friends as well. Reboot helps but this should not be happening at all. Wrote to Bitmain. This is the response from them:

Dear XXXXXX,

Please try reloading the firmware:

https://s3.cn-north-1.amazonaws.com.cn/shop-bitmain/download/Antminer-D3-201709131713-0M.tar.gz

Run the miner for 20 minutes after loading.

If it still does not work please test each hash board separately to determine which one is defective.

To test each hash board separately: keep the PSU connectors and controller cable on one of the hash boards connected and disconnect the cables from the other two hash boards. With the miner running you can see the status of the connected hash board.

Here is more detail: http://support.bitmain.com/hc/en-us/articles/226142788-Testing-hash-board-one-by-one

On the miner status screen defective chips are displayed as "xxx", "---" or " ASIC≠72

Once you know which part is defective please create a Repair ticket and ship the part back to us according to these instructions: https://shop.bitmain.com/workOrderGuide.htm

http://support.bitmain.com/hc/en-us/articles/222648028-How-to-disassemble-miners

Please pack the hash boards carefully. If the PINs are lost due to shipping damage it will void the warranty. Here is a video demonstrating how to pack the boards: https://youtu.be/Z0LdykALhxI

Please let us know if you have additional questions or concerns.

Best regards,
Barbara
Bitmain


I haven't upgraded the firmware yet, waiting if the problem will come back.

I have the same problem. I have 4 Antminer D3. 1 is working for 5 days without problems. The other D3 have every 1-2 days hashboad fails xxxxxxxxx.
Can someone help me??

same here :(

This will fix the problem:
1. Flash to lastest firmware
2. Set the fan speed to 100%
3. Set the frequency to 419

The above settings work for me and made the miner stable

any solution to this?

Read the post above yours !!

WRote a small script in php to check your D3's and reboot them automatically in case an hashboard has errors

https://gist.github.com/tperalta82/6e11253cd4b9cf9c5c6fa15bbf046d4f

put this in a linux server as a cronjob, change the $hosts array, to add your hosts.

There are 3 different methods to call reboot on the miner, personally, the wget one is better for me, because it runs everywhere (embedded devices)
Had an issue with curl, seems to fail to authetnicate on some weird cases
and ssh lib is not present everywhere.

Read the code first, understand it, redistribute it, improve it, do whatever you want with it.

P.S.: it works for me

Does this affect hash rate?

Can others confirm it's working?

I also got this but only for two times in one month. When it happened I noticed that my priority 1 mining pool’s server went from alive to dead. A reboot solved the issue (miner resumed mining on priority 2 server and when server 1 came back alive, it switched to that fine with no problems). I think it may be to do with the firmware not coping with a server going down and switching to priority 2 server.

The first time it happened I was on the default firmware for the mid-Sept batch (17.5GH) and the second just happened yesterday and I am on the 20th Nov 2017 firmware (latest version at time of posting).

what brand switch are they connected to? if its anything with link in the name id change that out pronto