Hi,
after switching to 11.7 I get following after mining approximately half an hour:

Miner cannot initialize for 5 minutes, need to restart miner!

����������������������������������������������������������������ͻ
�                Claymore's Dual GPU Miner - v11.7               �
�              ETH + DCR/SIA/LBC/PASC/BLAKE2S/KECCAK             �
����������������������������������������������������������������ͼ

ETH: 1 pool is specified
Main Ethereum pool is eth-eu1.nanopool.org:9999
At least 16 GB of Virtual Memory is required for multi-GPU systems
Make sure you defined GPU_MAX_ALLOC_PERCENT 100
Be careful with overclocking, use default clocks for first tests
Press "s" for current statistics, "0".."9" to turn on/off cards, "r" to reload pools, "e" or "d" to select current pool, "x" to select GPU, "z" to find best -dcri values
OpenCL initializing...

AMD ADL library not found.


Any help would be highly appreciated.
Alex

1. CVE-2017-16929 works only if you specified -mport > 0 and don't use password (-mpsw). Also it can crash miner:

From History.txt:

...
v10.2
- fixed critical issues in remote management feature (attacker could crash miner even in read-only mode).
...

That was the last known security issue and it was fixed in v10.2 and above.

Here is my opinon:
Yes my miners have "remote management" feature that allows administrators to upload files, restart miners etc. It's not a vulnerability itself. Also I know that this feature can be used by attackers, therefore by default miner uses "read-only" mode which ignores all commands except "miner_getstat1" (I mean recent versions of my miners, very old versions have no "read-only mode"). User must specify "-mport" option and positive port manually to enable potentially dangerous commands. Also I added "-mpsw" option that allows users to set a password for remote management. Also miner shows warning during startup if "read-only" mode is disabled and -mpsw is missed. Also I added necessary information to Readme file. And, of course, it's bad idea to make these ports public, they must be used in local network only, "-mport" option can expose the port to specified network interface only.
To make this feature dangerous, user must do the following:
1. Disable "read-mode", ignore miner warning.
2. Ignore "-mpsw", i.e. don't set a password, again ignore miner warning.
3. Expose the port(s) to internet.
So, in my opinion, I did everything to make this feature safe as much as possible, but some users have no idea/knowledge what they do when they change default settings.

If you're willing to share the actual address here we can investigate.  I've had no such problems myself.

Thanks for that
YOu could also send me your original bios, and will add support for it

anyone here with an rx 560 miner?
curious how it performs in claymore?
might make one since 570s or 80s are really hard to get

@bond007taz

We are very sorry for your inconvenience.

Staffs are working 24/7 to clear these stuck orders while under the heavy Ddos attack.  The attack has nothing to do with the actual transactional data. Your order will be manually confirmed in order it was received, However, please be patient with us for a bit longer.  We do expect this attack to last for a few more days.

It may show as Expired or Unpaid.  If it is showing PAID on the blockchain.info  you are GOOD TO GO!!  Just shoot us an email to info@bitmaintech.com with your ORDER ID & Payment Address and you will be contacted in the next few days.  (Also it is a late night weekend in Beijing at the moment)

The miner shipping will start as schedule on March 30th or sooner.  

Currently, the site is back up & running again just now!  

same issue here, i never got confirmation they received my payment but was up to 75 confirmations on my BTC transfer - i sent them an email - waiting to hear back.

What is the best way to contact support?

My payment is not being acknowledged by Bitmain even though I paid with BTC immediately after my order. Blockchain proves it.

I posted the details on here earlier but then removed them.

I just want to make sure that I am getting my S5!

To me it seems strange, that a board failure is SO rare on the 10,000s of units out there, yet TWO happen on the same unit simultaneously. Statistically that just isn't possible, there must be something environmental influencing the situation - whether its the fan was changed out, someone tried pushing an overclock too far etc etc. The warped plastic panels also don't appear to make sense, there is no reason why the air on those panels would get anywhere near the 105C or so to melt them.

My personal opinion is we're not getting the full story, but its not up to me to decide. PM BitmainWarranty to arrange an RMA. Be sure to link to your post describing the issues, what type and how many miners you wish to have repaired/replaced and your bitmaintech.com order number.

Is it single rail or multi rail ?

The multi rail can supply 850 watts to all connectors just not all at the same time! this is what companies do not tell you. Single rail is way better because it does supply it all at the same time I think its your PSU use single rail instead like I do with all the latest protections much better and much safer to!


I am a disabled engineer make sure if its multi-rail if you insist on using it that it can provide 25 amps on each connecter. just look at the PSU it should say it.


just looked at the PSU Specs that PSU should not have a problem unless you overclocked it. If you did what was the frequency ?


  

I agree .... which makes me think PSU.

I have a S4 B1 and S4 B2. The S4 B1 is working great but the new B2 that i got in a couple weeks ago worked great for the first few days now I cant get it to hash more than a couple hours. The box would stop hashing but it would stay on, the fans on with a blank (but lit) LCD screen.

I re-seated the SD card and it worked for about 10 hours and started doing the same thing. It works if I turn the power off and turn it back on, but only hashes for a couple hours.

I got a new SD card and flashed the image from the original SD and that worked for a few hours and then it stopped hashing.

I emailed tech support and they sent me an image that I flashed to the new SD card and the same issue.

This is frustrating! I know it works, I just dont understand why it keeps stopping.