Antminer D3 nothing but issues, wish I would have stuck with L3+

[woogieboogie]

I finally bit the bullet and got an L3+ delivered back in July.  The thing has been running 24/7 straight with a 10% overclock and cool temps without even a hiccup ever since.
I was so pleased that I got three D3's, falling for the ROI meme of it at the time.  How do I regret just not ordering 3 more L3+'s!

Problem #1) My batch was the 19.3 GHs, labled as 19.3 GHs on the shipping box and miner itself, when booting them up I found that all three only were doing 17.5 GHs.  So I'm already jipped 5.4 Ghs.   (I'm not even beginning to think of OverClocking these toasters since already at 70c temps out of the box)

Problem #2) When contacting support,  I got the robot response of telling me to update my firmware, running for 20 minutes, then testing each individual hashboard to see which one was defective.  After replying explaining I had already updated to the newest firmware on all three, and even did their silly individual board test JUST to be by the book to ensure I'd get taken care of,  support has not replied since.

Problem #3) Even if I accept my stunted hashrates, I have to babysit the mining statuses because all three of the miners have the very common

Code:

read_temp_func: can't read all sensor's temperature, close PIC and need reboot!!!

problem, where one of the hashboards go all "x"s and I have to reboot the miner to get it working again.

Problem #3.5) Almost forgot this one, the fans are constantly revving up to 6000 RPM every 5 minutes or so, even though temps are stable,  it sounds like a jet's taking off in my basement and my wife is about to kill me.

Problem #4) X11 profitability sucks compared to Scrypt right now  

Overall I think Bitmain tried way to fast to push this mega hashing D3 out as fast as possible, and quality suffered big time.  Now I can't even sell these things to try recoup my money since they are obviously 17.5 GHs cards inside 19.3 Ghs bodies, and any buyer would think that's shady as hell.

[cioloxl]

You got a couple things wrong. The machines are the same, from the september and november batch. They were just overclocked. I got one in sept and my friend got it a couple of days ago. It's hashing at 19.3 GH/s but at higher temps. In the miner status, what does the frequency tab say?

Also, the thing about error while reading temps...I'm guessing it's just a bug. I always get it if pool 0 dies and it has to switch, but it does not affect performance in any way. The hashboard stopping thing, I only got it 2-3 times.

[cashen]

Your 3.5 issue I think tis the machine rebooting itself.
Have you tried downclocking?
What PSU are using? It is a solid 1600w PSU?

[cioloxl]

Your 3.5 issue I think tis the machine rebooting itself.
Have you tried downclocking?
What PSU are using? It is a solid 1600w PSU?

Not op, but I don't think so. Mine only does that if the pool dies somehow. We also need to know the conditions in which the machine is kept. What is the ambient temperature?

[woogieboogie]

You got a couple things wrong. The machines are the same, from the september and november batch. They were just overclocked. I got one in sept and my friend got it a couple of days ago. It's hashing at 19.3 GH/s but at higher temps. In the miner status, what does the frequency tab say?

Also, the thing about error while reading temps...I'm guessing it's just a bug. I always get it if pool 0 dies and it has to switch, but it does not affect performance in any way. The hashboard stopping thing, I only got it 2-3 times.

I wouldn't mind if they were the same and overclocked as long as they were hashing at 19.3GH while still under warranty.  The freq tab says "Default Setting" and the kernal log shows it running them at 487M, which if my math is right would be around 5750 per board?
It affects my performance when I get that temp read error, my hashrate drops to 11.6 GHs when one of the boards show errors, it's happening daily to at least one of the boards.

Your 3.5 issue I think tis the machine rebooting itself.
Have you tried downclocking?
What PSU are using? It is a solid 1600w PSU?

I figured they were rebooting, but when they ramp up, the hashrate never drops and I can keep "top" running in ssh so they don't seem to actually be rebooting.
The profits aren't great already,  I can't imagine downclocking any more especially since they are running 1.8Ghs below expected.
I'm using two Bitmain AP3++'s on 220V and one 2400w HP Server PSU with breakout board on 220V

Your 3.5 issue I think tis the machine rebooting itself.
Have you tried downclocking?
What PSU are using? It is a solid 1600w PSU?

Not op, but I don't think so. Mine only does that if the pool dies somehow. We also need to know the conditions in which the machine is kept. What is the ambient temperature?

Correct, It doesn't seem to actually reboot.  It does seem worse on Nicehash, but also does it running on antpool.       Machines are in 65F (18c) basement, humidity steady at 35% with the dehumidifier

[cioloxl]

I wouldn't mind if they were the same and overclocked as long as they were hashing at 19.3GH while still under warranty.  The freq tab says "Default Setting" and the kernal log shows it running them at 487M, which if my math is right would be around 5750 per board?
It affects my performance when I get that temp read error, my hashrate drops to 11.6 GHs when one of the boards show errors, it's happening daily to at least one of the boards.

My guess would be the temperature is pretty high. Where I keep it, the temp is around 10C. With the same frequency as yours, I don't get temps over 63 on any of the boards.

[woogieboogie]

I wouldn't mind if they were the same and overclocked as long as they were hashing at 19.3GH while still under warranty.  The freq tab says "Default Setting" and the kernal log shows it running them at 487M, which if my math is right would be around 5750 per board?
It affects my performance when I get that temp read error, my hashrate drops to 11.6 GHs when one of the boards show errors, it's happening daily to at least one of the boards.

My guess would be the temperature is pretty high. Where I keep it, the temp is around 10C. With the same frequency as yours, I don't get temps over 63 on any of the boards.

You got yours in a refrigerator? lol dang I can't imagine how I'd get the ambient temp to 50f/10c