Any plans for a Z11 firmware in the future?

Efudd I sent a PM with support ID and logs, maybe you can help me figure this out.

Anyone else experiencing major differences between reported hashrate in miner status and reported hashrate on pool sites.  I've been seeing 10-12k differences at least 2 or 3 times a day on my Z9 for a while now and this comes out to more like a 20% dev fee than a 1% dev fee.  I installed the firmware on two of my z9 mini's and I frequently see hashrates 1-4K below what is reported in the miner status.
I've attached some screenshots.




**Update:  I'm trying 2.1c firmware on the Z9 now after reading some recent posts, but I already have 2.1c on the Z9 mini where I'm noticing up to 20% dependencies.***
**Update2: Nevermind I definitely had 2.1c firmware on Z9 already, it just doesn't list it at the top of the page in System Summary it just says 2.1**

I asked about this in a PM, but got no response.  Is the option still available to be a paid user?  I would rather pay a lump sum and avoid the dev fee and possible bugs making it larger than the 3.67%.  People have 1% in mind because at one point in this post or in the firmware notes it did say 1%.  I don't know when that changed, but somewhere in some description you definitely listed 1% as the dev fee.

Get ready to be sad panda's.  Thanks to this: https://money.cnn.com/2018/06/14/news/economy/trump-china-tariffs/index.html
you can expect to pay 25-30% duty on all cryptocurrency miners and a ton of other stuff coming from China.  I ordered 3 z9 mini's at an end price with shipping of @ $2500.  I had to fork over a COD check to UPS for $744 to cover the duties they paid before they would release the 3 miners to me.

Sorry to be the bearer of bad news, but your card probably died.  I can pretty much guarantee if you post test them one at a time there will be a no post card in the bunch.  I've lost 2 already in a similar fashion by pushing over clocks too hard, it's why I buy all EVGA cards, their warranty and RMA process is the best in the bizz.  Just no questions asked replacements every time.

Is there a way to set the intensity on a per card basis rather than setting it for all cards?  I love the intensity addition, but the reason I wanted it is to set the intensity lower on one of my cards so I can still use my computer and stream video without buffering while keeping the other cards running at full speed.

I couldn't find anything in the help about about it, but is there switch to set a GPU usage percentage with EWBF?  I have two 1070's in my personal rig with 3 monitors.  I watch a lot of streaming video online and when the miner is running I get a lot of skipping and stuttering.  It would be nice to be able to set 5% or so aside for my general computer usage rather than killing mining on a whole card just so I can watch netflix.

Upgrade to windows 10 anniversary edition.

For anybody having random crash problems with "Thread exited with code: 46, Thread exited with code: 77, and Thread exited with code 30 errors" this tip from EWBF has indirectly solved my problem.  Add "--eexit 1" to your miner command switches and edit your existing batch file to make them a simple restart script as exampled below.  If the miner crashes it will shut down forcing it to go back to the beginning of the batch and restart the miner.

Thanks EWBF!

:restart
miner --server us1-zcash.flypool.org --port 3333 --user address.phoop --eexit 1 --pass x --cuda_devices 0
goto :restart

Have you upgraded to windows 10 anniversary edition?  I was not getting the speeds others were out of my 1060 and 1070, after upgrading to anniversary edition I was on par with everyone else.

Just got the same glitch, restarting the script worked fine.
Some time ago I had kind of the same problem with Claymore and my AMD's.
hint to EWBF: Setting the (-r 240) "restart by user" switch to every 4 hours solved my problem.
[/quote]

Thanks for the restart by user hint, didn't even know it existed till I saw your post.  I've set it up on all my miners as a just in case measure.  I believe I have found a solution for Thread exited with code: 46 , Thread exited with code: 77 , and Thread exited with code 30 .  After hours of tinkering and sifting through logs in EVGA precision X I noticed a correlation between power % and this error.  Every time it would happen on my 1060 and 1070 rigs they would be within 4% of 100%.  One of the times I even saw GPU voltage at 0.000% the line before the miner crashed.  I've found on both my rigs that were having this problem, setting the power % to 94% has stopped the problem and allowed me to returned to an overclocked (rather than under clocked) configuration.  My 1060 is now getting me a consistent 280-300 sol/sec with these overclocked settings on an MSI 1060 3GT OC 3GB.

I tried much solver so hard and still nadda.  I did find a work around but it isn't really an acceptable one in my opinion.  If I under clock the graphics cards both memory and GPU the miner doesn't crash.  I'd say that I have two failing cards, but they work fine for gaming and hours of valley benchmark without crashes or artifact with massive overclocking.

-Both Rigs are Win10 Pro x64
-Drivers 376.66
-GPU's 2x 1070 EVGA ACX 2.0 Superclocked in 1070 rig and 1x MSI GTX 1060 3GT OC (B01KUCL25Y) in 1060 rig.
-1070 rig is a gigabyte z97x-ud3h-cf motherboard and 1060 rig is an optiplex 390 desktop with PS replaced.
-1070 rig has I5-4460 and optiplex 390 1060 rig has an I5-2500s
-1070 rig has a PC power & cooling 950W Silencer MK-II PS and Optiplex has Thermaltake SP-650
-No risers.
-The 1070's all have two 8 pin connectors coming from the power supply (no adapters) and the 1060 has one 6 pin power cable direct from the power supply
-miner --server us1-zcash.flypool.org --port 3333 --user address.phoop --solver 1 --pass x --cuda_devices 0 1 2 Note: I've tried using all solvers 0-3 per ewbf's suggestion and I've also tried running the cards individually by using cuda_devices selection with the same results.
I start the miners from an account with administrator privileges, but I don't right click and run as admin.  If I run it from an admin command prompt I do get the same problem though.  I assume if it was admin related it wouldn't work at all, not work for 5-10 minutes then stop working.
The benchmarks will run on whatever you have set as your primary display.  I have one display connected to each video card so to make benchmark run off other gpu I just have to set the other monitor as my primary display.  No SLI mode is not on with hardware or software bridge.  No I have not tested the cards one by one in main GPU slot.  I have this case http://www.antec.com/product.php?id=705069&lan=nz so adding/removing cards can be a bit of a pain.

Getting the same thing on two different rigs with 1060's and 1070's, I've tried 1.0 and 2.0 it doesn't seem to make a difference which one I'm running.  I'd also like to add that this doesn't happen right away, the miner works fine for 5-10 minutes first before this happens. The cards run valley benchmark just fine for hours but I removed all overclocking anyway to eliminate possibilities per EWBF's suggestion.  Any other ideas would be much appreciated, having two rigs down is a big waste of resources.

For me this was not true, it was the crimson 15.12 drivers causing the miner to crash.  I'd tried every troubleshooting trick in the readme to no avail and even asked in these forums, nothing worked.  If your miner is crashing or If you are having stability issues update to the latest relive drivers from AMD.

I was really confused on this one because I have two identical Optiplex 390 machines, both running windows 10 pro, both with newest A11 bios, both with onboard video enabled too, both with 8 gb of ram, and both with R9 fury's in them.  One has been running flawless for almost a month and the other wouldn't run at all.  I'm sure I used the 15.12 drivers on the machine that was working when I set it up, but that was in the earlier days of claymore (9.0) and I must have left the automatic driver update option checked.  Some change made between 9.0 and 9.2 causes issues with the 15.12 drivers on certain rigs.

Just to be thorough I removed the newest drivers on the optiplex that has been working and installed the 15.12 drivers and zecminer64 would crash right after card detection every time.  Updated to newest drivers with clean install option and it's working again.

Thanks for the quick reply.  I have removed these from my windows environmental variables and added them to my batch file.  Still crashing on start as before.


I have moved all my commands to the config file as suggested and I'm still getting an error with the -ethi 4 command switch.  The console reports "UNKNOWN OPTION -ethi" in red, then on the next line "UNKNOWN OPTION 4" also in red.

Any other suggestions would be much appreciated.

Thanks,

I've tried all the above steps to no avail, right after video card detection (which it is detecting properly) I get zecminer64.exe has stopped working
It wasn't suggested in your troubleshooting but I did install AMD opencl 3.0 as I had that resolve issues on another one of my rigs.  This computer is a I5-2500s with 8GB and an R9 Fury.  I have put the environmental variables in the System->Advanced System Settings->Environmental variables, if this isn't where they were supposed to go please provide directions on where to put them.  I have manually set page file in windows to 18GB to exceed the 16GB minimum you listed.  When I try to use the -ethi 4 command it tells me it's not recognized.  As you can see from my batch file below I put in a 60 second timer before the script is run.  Any help you could provide would be much appreciated.

Here is my current batch file (minus my zwal)
TIMEOUT /T 60 /NOBREAK
ZecMiner64.exe -zpool us1-zcash.flypool.org:3333 -dbg 1 -zwal hiddentoprotecttheinnocent -zpsw x -i 8 -di 0

Here is a copy of the most recent log
20:08:43:735   26f4   args: -zpool us1-zcash.flypool.org:3333 -dbg 1 -zwal hiddentoprotecttheinnocent -zpsw x -i 8 -di 0
20:08:43:740   26f4   
20:08:43:744   26f4   ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
20:08:43:749   26f4   º            Claymore's ZCash AMD GPU Miner v9.2 Beta            º
20:08:43:749   26f4   ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ
20:08:43:749   26f4   
20:08:43:966   26f4   ZEC: 1 pool is specified
20:08:43:971   26f4   Main ZCash pool is us1-zcash.flypool.org:3333
20:08:44:228   26f4   OpenCL platform: AMD Accelerated Parallel Processing
20:08:44:232   26f4   OpenCL platform: AMD Accelerated Parallel Processing
20:08:44:232   26f4   OpenCL initializing...

20:08:44:232   26f4   AMD Cards available: 1
20:08:44:248   26f4   GPU #0: Fiji, 4096 MB available, 56 compute units
20:08:44:248   26f4   POOL version
20:08:44:248   26f4   b321
20:08:44:264   26f4   Platform: Windows

I tried the 0.8b on my gtx 580 rig and it detects the card unlike before where it would just say no supported card detected, now it does 0 sol/s.   Just letting you know if this release was intended to work with Cuda 2.0 devices it ain't working with 5 series cards.

Thanks,

On both my Nvidia 1060 rigs the below has started happening on a daily basis and all mining stops.  To get it started again I have to close the app and re-open it.  Is there a command switch like with Claymore that will make the miner restart in the event of a crash?  Any idea why this is happening?  Both rigs are I5 4th generation on windows 10 64-bit running 375.95 nvidia drivers.

Thanks,