WinMiner v1.126a - auto switch windows app for multi miner optimization

[BitBustah]

(1)   Make sure you are using version 1.61 (the update should happen automatically when clicking the “Start” button. Look at the top left corner of the WinMiner window to see the version number)
(2)   Go to Settings and on the “General” tab - check the “enable debug log” option
(3)   Go to the “Benchmark results” tab – and press “clear” to remove the previous limited benchmark results
(4)   Exit WinMiner by clicking right click on the WinMiner icon in the tray and choosing “Exit”
(5)   Run WinMiner, wait for Benchmarking to complete, and send us the logs (Help > Send Error Report)

Update OK. Using correct version. Benchmarking now, will send you logs. Thanks!

Log files sent. Thanks.

[TeamWinMiner]

I am trying to set the password after the mail validation, but i keep getting the message "weak" and cannot procede. I'm using a random psw generator that includes all kind of characters but after trying at least 10 different 20-long char psw i gave up, not sure what to do, can you help?

same here, weak password each time

Thanks for letting us know.
We are looking into the password reported by several of you – will update shortly on fix.

You need to add more miners and newer ones.
Dual Claymore 9.7 is faster on 1060/1070 than 9.5 that is downloaded
Xmr-stack-cpu is faster than Claymore.
With Dual Claymore the one of the most important things to add is -dcri setting - 1080/1080ti are much more profitable with high values. The best would be automatic changing in realtime to get maximum profit. Or at least 3-5 user entered values from which app will choose the most profitable at the moment.

Receiving this errors in log:
11.07.2017   10:01:29.725         INFO   >>>>> LOG START >>>>>
11.07.2017   10:01:29.756      SharedMemory   INFO   Creating shared memory file
11.07.2017   10:01:29.911      SharedMemory   ERROR   Error while creating memory file: Heкoтopыe или ccылки нa cвoйcтвa нeльзя пpeoбpaзoвaть.
11.07.2017   10:01:30.929      SharedMemory   ERROR   Trying to access non-existing map file
11.07.2017   10:01:31.915      SharedMemory   ERROR   Trying to access non-existing map file
11.07.2017   10:01:32.915      SharedMemory   ERROR   Trying to access non-existing map file

Thanks for the feedback and tips.
(1)   Miners –
   - Claymore 9.7 is still undergoing tests by the team and will be updated as soon as we are finished with that.
   - Xmr-stack-cpu – being added to the list for testing right now. Thanks!
   - Dcri settings – during optimization/benchmarking different dcri values are being tested automatically (0, 30, 70 and 100) to make sure profit is maximized.
(2)   Errors – its indeed a bug and we are working to fix. Please note that it does not influence the proper operation of WinMiner.

Hey,
"Reporting (on WinMiner website)" means you will get some confidential info to your server? Do you have some restrictions?

No need to worry
No confidential info is being looked at or sent – it is just the software operation logs and the email address.
You are also welcome to look at the Terms of Service for the restrictions.

[BitBustah]

This project looks very promising. As a developer myself I can see that a lot of work went into this application and website. I hope the little problems will be figured out so we can all enjoy it

[TeamWinMiner]

This project looks very promising. As a developer myself I can see that a lot of work went into this application and website. I hope the little problems will be figured out so we can all enjoy it

Thank you!
A true appreciation from a fellow developer is as high as it can get!

[BitBustah]

Let me know when the error on those benchmarks has been found. Can't wait to start mining.

[abudfv2008]

   - Dcri settings – during optimization/benchmarking different dcri values are being tested automatically (0, 30, 70 and 100) to make sure profit is maximized.

0 30 70 100 is not enough. These works for 1060/1070, usually somewhere around 35-50-60. But for 1080/1080ti 200+ ... 400+ is more profitable nowadays (LBRY usually ~480-500 on 1080Ti)
And as for AMD cards and GTX1060 dcri should be changed very presicely. E.g. right now on 1xFuri Eth+DCR dcri30=2.40 dcri36 =2.69$, dcri40 = 2.59 dcri50=2.30
First to implement realtime optimizing of dcri setting will get many users.

[TeamWinMiner]

Let me know when the error on those benchmarks has been found. Can't wait to start mining.

Latest fixes (v1.62a):
(1)   We believe we traced down and fixed the password strength error.
(2)   We believe we also traced down and fixed the benchmarking error – it seems to be related to non-English OS languages.

Please check and let us know if we can put these behind us

[BitBustah]

Let me know when the error on those benchmarks has been found. Can't wait to start mining.

Latest fixes (v1.62a):
(1)   We believe we traced down and fixed the password strength error.
(2)   We believe we also traced down and fixed the benchmarking error – it seems to be related to non-English OS languages.

Please check and let us know if we can put these behind us

Benchmark still not working I think. I'm using the Asus Tweak II tool to monitoring my GPU.. Seems like it's not getting "stressed"..
Sending another log/bug when done benchmarking.

[TeamWinMiner]

   - Dcri settings – during optimization/benchmarking different dcri values are being tested automatically (0, 30, 70 and 100) to make sure profit is maximized.

0 30 70 100 is not enough. These works for 1060/1070, usually somewhere around 35-50-60. But for 1080/1080ti 200+ ... 400+ is more profitable nowadays (LBRY usually ~480-500 on 1080Ti)
And as for AMD cards and GTX1060 dcri should be changed very presicely. E.g. right now on 1xFuri Eth+DCR dcri30=2.40 dcri36 =2.69$, dcri40 = 2.59 dcri50=2.30
First to implement realtime optimizing of dcri setting will get many users.

Thank you very much for the feedback and pointers.
(1) LBRY – currently not supported. We have added to the wish list though
(2) More dcri values - will add more values to the optimization. Naturally, the more values we add the lengthier the benchmarking process will be. This is especially true due to dag size (e.g. optimization for ETH +DCR is not the same as optimization for UBQ+DCR).
(3) Real time dcri optimization – we currently do that for a limited number of values. Including all possible values would make bencmarking run forever... . Nevertheless, point taken, we will think of a creative way to address this.

Thanks again!

[zorvalth]

Ok, in the setting i chosed all coins and in the job decisions i see this:


There is now ETH, ZCASH, ZCL...

Why it doesnt consider them? And I'm pretty sure in the testing it tested ZCL and showed 3+ usd per day and when i restarted the app(1 min later) its ZEN on its place with 2.53 usd/day

p.s. I figured it out, it shows the best coin from every algo. btw when on DUAL and choosed BGN it cant show everything:

[BitBustah]

Did you find anything from the bug/log I submitted?

[TeamWinMiner]

Did you find anything from the bug/log I submitted?

Sure!
We did another update (the one that also updated Claymore 9.7).
It is important that you clear the benchmark (otherwise it will wait up to 24h before attempting the hardware benchmark again, currency benchmark happens continuously).
Settings > Benchmark results > Clear > Save

Let us know if problem solved.

[inkubux]

The balance is not reported in the application but is displayed correctly in the website

http://imgur.com/a/5cm0l

[abudfv2008]

   - Dcri settings – during optimization/benchmarking different dcri values are being tested automatically (0, 30, 70 and 100) to make sure profit is maximized.

0 30 70 100 is not enough. These works for 1060/1070, usually somewhere around 35-50-60. But for 1080/1080ti 200+ ... 400+ is more profitable nowadays (LBRY usually ~480-500 on 1080Ti)
And as for AMD cards and GTX1060 dcri should be changed very presicely. E.g. right now on 1xFuri Eth+DCR dcri30=2.40 dcri36 =2.69$, dcri40 = 2.59 dcri50=2.30
First to implement realtime optimizing of dcri setting will get many users.

Thank you very much for the feedback and pointers.
(1) LBRY – currently not supported. We have added to the wish list though
(2) More dcri values - will add more values to the optimization. Naturally, the more values we add the lengthier the benchmarking process will be. This is especially true due to dag size (e.g. optimization for ETH +DCR is not the same as optimization for UBQ+DCR).
(3) Real time dcri optimization – we currently do that for a limited number of values. Including all possible values would make bencmarking run forever... . Nevertheless, point taken, we will think of a creative way to address this.

Thanks again!

1. Sia. Pascal, kessak, nist5 etc also should be added to maximize profit. Without them you won't beat modded versions of NHM.
2.  Benchmark can be done in one attempt if you would be able to change dcri in real time. Anyway manual input for some algo is ok.
3. I think that with dual mining 3 settings are just the points to start closer to the optimum. After start real time optimizing should take place.

[inkubux]

The balance is not reported in the application but is displayed correctly in the website

http://imgur.com/a/5cm0l

When I switch to US dollars it is fine

[gilad215]

I have Windows with Hebrew Language, now i can finally run the benchmark but the winminer doesnt detect the hashrates, its just stuck on benchmarking, even though its mining ok.

i have found the problem: the claymores miner doesnt know the command rig2 because my username is 1070 rig2 (with a space), so it doesnt write the log

[inkubux]

Are you planning on adding more withdraw options ?

Litecoin would be awesome. It's fast and transaction fees are low.

[BitBustah]

Did you find anything from the bug/log I submitted?

Sure!
We did another update (the one that also updated Claymore 9.7).
It is important that you clear the benchmark (otherwise it will wait up to 24h before attempting the hardware benchmark again, currency benchmark happens continuously).
Settings > Benchmark results > Clear > Save

Let us know if problem solved.

Still not fixed.. Only 2 algos pass the benchmark, others stay at 0... Resulting in mining at 2.84 dollars or so... I'm getting more at NiceHash. I've lost a lot of time today, I'm going to continue on NiceHash. I'll try again in a few weeks.. Sorry.

[3xcalibur]

Hi guys ! Forgive me for formatting errors as this is my first ever post on Bitcoin Forum.

I quickly tried this program which looks wonderful.

In terms of giving feedback, I noticed that equihash mining was giving me over $4 usd in income, and the claymore's miner under $3, however the miner was defaulting to claymore's which wasn't the most profitable.
I'll try and send a bug report in the program and maybe that will assist in solving it ?

Anyways once this issue is solved I will most likely try it for far longer !

Thank you for all the time and effort you've put in so far guys.

edit... it seems that, for now, the problem has resolved and the most profitable coin is mining ! wow, that was fast.
anyways i'll keep an eye on it for u guys and let u know if anything else happens.

by the way i checked out the site, and the payout option of paying out virtually at any time seems wonderful to me, thank you once more. i'm continuing with this miner for now.

p.s i couldn't be sure of all the coins as i'm a little new, but the algorithms grs and dgb don't seem to be activating properly, even when those two alone are selected.

[preda]

wow compliments for the program i am actually twsting it!!! ill let you know guys but compliments to the development!!