Topic: Bitmain looks like they're releasing a 15GH/s DASH miner called the AntMiner D3 - page 111. (Read 299686 times)

I have my 5x D3 running at 17Ghz now, 4 of them are at speed out of the box, one was at 19ghz, i downclocked it to 17ghz. They are all 19,3Ghz. Will try your settings at 18ghz if they are stable at 17ghz tomorrow.

18,008 ghz

stable so far
Elapsed   
2d4h17m3

Fan set auto, running 47xx RPM. Highest Chip Temp : 79deg, was 92deg Celcius

Thanks for the tip -- I'll give this a shot.

-Tim

What's the hashrate after downclocking?

I'm having xxx's on half of my miners, I have to restart them almost every day. After reboot they run ok for a day or so. Even if I drop the temp to 60C (fan speed at 80%) I'm still getting errors. So I'm just monitoring them and if I see xxx's I just reboot them.

u got a bad controller, u can swap the working unit controller to this... check if that resolve your issue.

yes, they OC it
and its fucking hot. even in AC and proper ventilation.
in couple of hours, too many XXXXXX and one board losing its mind.

what i did, down-clocked to 500Mhz. Now running fine, temp down almost 8 deg C

This is good place to start: https://bitmainhelp.zendesk.com/hc/en-us/articles/220872007-Possible-problems-for-Antminer-Troubleshooting-for-S7-S9

See if any of the errors you have are in the list.

I just received four D3s from Bitmain in the Nov 1-15 batch (the 19.3 GH/s version). One of the four miners set up just fine, just like my September batch miners. I am having some of the same chip temp issues that other posters are having with this 19.3 GH/s miner, but at least it is mining.

The other three miners I received in this batch are giving me the following error, and I cannot seem to resolve it:

"Hardware Version:   Socket connect failed: Connection refused"

I realize that miners will display this as they start up, sometimes for many minutes. But once configuration is complete and I click "Save & Apply," this message usually goes away and the miner connects to my pool as we would expect. This is not happening with the three of my four miners in the Nov 1-15 batch. These miners display the "Socket Connection Failed" message, and when I toggle with the settings in the miner browser to troubleshoot it, I'll get a browser "can't reach this page" error once I try to save and apply the settings (as if the miners disconnected themselves from the internet -- they are no longer discoverable on the network). A few moments later, the miners will spin up again (as if they restarted on their own) and I'll be able to reach their IP address in a web browser like normal, but they have the same "Socket Connection Failed" error message, and the same issues I had before (e.g., the browser saying "can't reach this page" once I try to save changes to settings) persist. This repeats over and over, and the miner never connects.

Does anyone have any idea what this might be, and what I might be able to do to troubleshoot it? I've opened a ticket on Bitmain's support site, but they are taking days to respond, so I figured I would check here to see if anyone here has experienced and resolved this on their own.

Here are the things I've tried:
1. Swapping ethernet cables
2. I've tested the miners on two different internet connections -- the internet connection that all my miners are on, and my back-up internet connection
3. Flashing firmware
4. Using the "reset" function
5. The tactic suggested in this thread (https://enforum.bitmain.com/bbs/topics/3876) that someone used to resolve a similar issue with the S9

Thanks in advance for any suggestions!

-Tim

I think these 19Gh/s units are just overclocked to the tits. I'm gonna down clock mine. Seems to be causing a lot of issues for a lot of folks.

2nd miner running less then 1 hour already has Xes

https://imgur.com/a/74Xfp

Antpool has launched dash recently and they have 0% fee.  But i heard they kept transaction rewards for themselves.

Update, i got 2 more miners setup today, they are also at default frequency setting, but are only hashing at 17ghz frequency at 487 the first are hashing at 19ghz with frequency at 537, both can't be default? All temps are below 70C, i sat fanspeed at 85%

She is running at low 60's across all chips im at 100% and it's in a very cool enviroment, so i am lost

That being said, she is sitting back at 19 for over 4 hours now !

Hahah thank you, keeping my eye on interesting coins that look to be developing and BOOM ! switching to getting paid out in them , only way i can see this ever paying itself off.

I'm seeing a lot of people having issues with the D3's. It's starting to make me worry about the ones I have coming in next week. Should I be worried? Mine will probably only run at 72-76 Fahrenheit. 

taking some gambles for bigger gains, I like it!

Got my first D3 running for 24 hours now, It has already failed 3 times with 2 different hash boards showing XXX in ASCI status, gone after a reboot, update to latest firmware did not help. Is this D3 just fubar from the start? Temps are all normal.

Sounds like Heat Hombre. These D3's are hot runnin bastards and they DON'T like running over 70c. Reset it and run your fans at 100%. I honestly think they are way hotter than S9's. A misfiring hash board, HW errors and xxxx's id very symptomatic of 70 plus c in the chips.

I am in the UK mate- the top hashboard is loosing its performance and throwing X instead of O its dropping to around 13Ghz. from 19.3