Bitcoin Forum
May 06, 2024, 10:03:21 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 [2]  All
  Print  
Author Topic: KNC Miner to return with 750 mg/s scrypt miner  (Read 1987 times)
Searing
Copper Member
Legendary
*
Offline Offline

Activity: 2898
Merit: 1464


Clueless!


View Profile
July 30, 2017, 02:27:35 AM
 #21

hi, I find scrypt miner on nodecrypto.com , it is refurbished one it is good price.. somebody know a better product or price of scrypt miner Huh


likely a scam site..you can mine those on www.prohashing.com for more than they are asking

so I call scam

so don't do anything with out escrow from someon YOU PICK at least

Old Style Legacy Plug & Play BBS System. Get it from www.synchro.net. Updated 1/1/2021. It also works with Windows 10 and likely 11 and allows 16 bit DOS game doors on the same Win 10 Machine in Multi-Node! Five Minute Install! Look it over it uninstalls just as fast, if you simply want to look it over. Freeware! Full BBS System! It is a frigging hoot!:)
1714989801
Hero Member
*
Offline Offline

Posts: 1714989801

View Profile Personal Message (Offline)

Ignore
1714989801
Reply with quote  #2

1714989801
Report to moderator
In order to achieve higher forum ranks, you need both activity points and merit points.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
QuintLeo
Legendary
*
Offline Offline

Activity: 1498
Merit: 1030


View Profile
July 30, 2017, 08:08:10 PM
 #22

It would be nice to see a vendor challenge Bitmain for the scrypt market

 Actually, it's more accurate to say that BitMain has challenged Innosilicon in the scrypt market - and appears to probably be winning.

 I'm not sure if the TOTAL hashrate for all Bitmain Scrypt miners has passed the TOTAL hashrate for all Innosilicon Scrypt miners yet - but it's getting close if they haven't done so.


 Miners living for years is NOT uncommon - the long-time issue was always more about "miner is no longer profitable after a year or two, shut it down" in SHA256 due the greater competition.

 I've got A2 units that were bought USED from Zoomhash (who had mined on them likely for a year or two BEFORE they sold them) and I've had for almost 2 years now, have had ZERO issues with them other than a couple of the fans dying and needing to be replaced and one PS that died early on (the original PS was a bit underrated for the 110 Mhs units).
 The actual MINERS however have been rock solid reliable despite probably being 3-4 years old now.


I'm no longer legendary just in my own mind!
Like something I said? Donations gratefully accepted. LYLnTKvLefz9izJFUvEGQEZzSkz34b3N6U (Litecoin)
1GYbjMTPdCuV7dci3iCUiaRrcNuaiQrVYY (Bitcoin)
sil2222
Full Member
***
Offline Offline

Activity: 144
Merit: 100


View Profile
July 31, 2017, 12:02:27 AM
 #23

oops Scam site is now offline. Good work
lightfoot
Legendary
*
Offline Offline

Activity: 3108
Merit: 2239


I fix broken miners. And make holes in teeth :-)


View Profile
July 31, 2017, 02:25:39 AM
 #24

The Titan was notorious for going bad due to DIES on their chip dying, not just the horrible board-level design choices they made. Arguably the lowest reliability design anyone ever produced, though it was the long-time king of efficiency for Scrypt when it DID work.

I disagree. Run Titans at 60mh per cube and they will run pretty much forever. The errors came when people ran the things at 80mh, which caused:

1) Dies to fail from too much heat. I have seen boards with burn marks on the back.

2) Power supplies running too hot. Once again have seen supplies with caps and FETs that caught fire.

3) FPGAs on the controller blowing up: This is caused partially by a crap design, part because people unplug the miners from the controller while running.

4) Removing and replacing the heat sink without new thermal compound (it's a one time use).

5) Running miners in barns, sheds, and places where either there is not enough cool air or there is literally horse crap everywhere (oh yes, I have had to clean those miners....)

6) Torquing the bolts so tightly the board tacos (this can be addressed by putting one of those rubberish thingies under the board between the front two posts).

7) PCIe power plugs burning due to crappy power supply cables or running too hot (don't use a little supply with cheap wires. Bad)

They weren't the best miners in the universe, but they weren't too bad. With the exception of 3 (and that's a biggie, using fucking optoisolators would have made everything ok) they're pretty good at 60mh, <42c on the die, under 70c on the supplies. Exceed that and things get more complex.

YMMV.
QuintLeo
Legendary
*
Offline Offline

Activity: 1498
Merit: 1030


View Profile
August 01, 2017, 03:43:43 AM
 #25

The Titan was notorious for going bad due to DIES on their chip dying, not just the horrible board-level design choices they made. Arguably the lowest reliability design anyone ever produced, though it was the long-time king of efficiency for Scrypt when it DID work.

I disagree. Run Titans at 60mh per cube and they will run pretty much forever. The errors came when people ran the things at 80mh, which caused:

1) Dies to fail from too much heat. I have seen boards with burn marks on the back.

2) Power supplies running too hot. Once again have seen supplies with caps and FETs that caught fire.

3) FPGAs on the controller blowing up: This is caused partially by a crap design, part because people unplug the miners from the controller while running.

4) Removing and replacing the heat sink without new thermal compound (it's a one time use).

5) Running miners in barns, sheds, and places where either there is not enough cool air or there is literally horse crap everywhere (oh yes, I have had to clean those miners....)

6) Torquing the bolts so tightly the board tacos (this can be addressed by putting one of those rubberish thingies under the board between the front two posts).

7) PCIe power plugs burning due to crappy power supply cables or running too hot (don't use a little supply with cheap wires. Bad)

They weren't the best miners in the universe, but they weren't too bad. With the exception of 3 (and that's a biggie, using fucking optoisolators would have made everything ok) they're pretty good at 60mh, <42c on the die, under 70c on the supplies. Exceed that and things get more complex.

YMMV.

 Per KNC's stated specs, they appear to have *supposedly* been designed to run at 80 Mhs - like the A2 was "base clock" at 1000, but if you upgraded the OEM power supply they have proven to be rock solid reliable at 1200 (the OEM power supply was only rated for 1100 watts, which is comfortable at 1000 Mhs clock but VERY marginal at 1100 and NOT ENOUGH at 1200).

 The PCI-E connectors even at the 60 Mhs level were very marginal for the power draw, though not much worse than the Spondoolies SP20 (which was NOT notorious for flames as it had power limiting in the controller).

 A LOT of the reported fails were on machines that the user had NOT done any form of "modifications" to.

 A2s are quite comfortable running in high ambient temps in "turbo mode", they have some SERIOUS airflow through the cases and lots of heatsink for the design power dissipation (though the 2 fans in the rear of the case were a waste, nice to unplug them to have around as spares though).

 Compared to the A2, the Titan was JUNK on reliability (except the A2 original power supply if you pushed it too hard), mostly due to BAD DESIGN DECISIONS that required folks to run them WAY too hard to meet their stated hashrate spec.


 This also wasn't new for KNC - at least 2 of their SHA256 miners had the same sort of issues, the Neptune might have even been WORSE on the same points.





I'm no longer legendary just in my own mind!
Like something I said? Donations gratefully accepted. LYLnTKvLefz9izJFUvEGQEZzSkz34b3N6U (Litecoin)
1GYbjMTPdCuV7dci3iCUiaRrcNuaiQrVYY (Bitcoin)
Pages: « 1 [2]  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!