[ANN] lolMiner-mnx, Mining MinexCoin(MNX) New version: v0.4 (July 22)

[Lolliedieb]

How can I set temp limit in this miner?

This is plainly not possible - use power target in your driver to monitor abd set temperatures.

I have the same issue trying to run a 4x 1080ti rig stock, except mine just keeps running at 0 (maybe I killed it before it crashed though), no errors, just goes from 20k sols/card to 0.
Once and a while it will run for a bit but will crash if it looses connection (not sure why it lost connection, all the other rigs on that switch are still hashing away with no problems).

I had many reports that the 0 sols appear more often when increasing OC. lolMiner utilizes and stresses card a lot and 0 sols is an indicator that the card failed in completing its task properly and the miner stops there because the complete event is never called.
Try to start at clock 0, power target 75% and 0 mem and then increase slowly mem when you see the config is stable.

deskop remote pls

demo claymore

Can you describe more in detail what feat you like to have?

[surkoff]

Try to start at clock 0, power target 75% and 0 mem and then increase slowly mem when you see the config is stable.

I tried to start in stock, e.g. 0 clock and 0 mem. Problem still here. WIN10x64

[Xaboom]

I just finish with the setup... 6x RX 570 4 GB ( 7300-7400 sol/s each card, is it ok ?) , all stable for now. Lets se what will happen in next 24 hours.

Btw my old nvidia GeForce GTX 970 10224 sol/s

RX 560 4 GB 4300 sol/s

[Ordep80]

Can you please help me with the configuration? I have 6 x rx570 8gb and they only work 3. Could someone help me? Thank you

[Xaboom]

Try this config:

--set-work-batch 7 - and if all 6 cards work fine and stable try --set-work-batch 8 etc etc. .... If works only 5 cards then try this

--set-work-batch 6


--optim STD

[Raty]

On all my 1080ti rigs this minner crashing in a minute sometimes is running 20 min but not more than 30 min. After crash miner rebooted automaticaly. Maybe BSOD. I tried to set default OC setting and set less clock and set less power and nothing help :-(

But on my 1080 rigs it is stable and it running without problem more than 24 hours.

I have everywhere installed Windows 10 Pro 64bit with last updates.

[chipah]

Just happy to report:

All cards are stock:

[Device 0] Average speed (5s): 16591.1 sol/s <-- GTX 1080, it was ~13k with v0.22
[Device 1] Average speed (5s): 10059.8 sol/s <-- RX480 4gb, was ~9.1k with optiminer

Thank you!

[john1010]

Just happy to report:

All cards are stock:

[Device 0] Average speed (5s): 16591.1 sol/s <-- GTX 1080, it was ~13k with v0.22
[Device 1] Average speed (5s): 10059.8 sol/s <-- RX480 4gb, was ~9.1k with optiminer

Thank you!

How do you get that speed in your rx 480? mine is rx 480 8gb and i only got 8k sol/s, is any special setting to achieve that hash speed? can you please share your setting, I only use the default clock and mem, I only adjusted the voltage in AB @ -55 and -10 powlim

[john1010]

I tried this v .31 on my 10gpu's but it seems that the miner only detected 8gpu, I am using sapphire nitro+ rx 570 8gb and I only got 8k sol/s is any other way to increase my hashrate? I am using default clock never configure the settings as i know that the miner is not for changing the setting.

[alarmod]

Problems with reconnecting to the pool https://mnx.4rigs.cf. An error occurs during the authorization phase - the miner exits. The program starts and stops indefinitely.

[starush]

Can you describe more in detail what feat you like to have?

I have mixed cards in my rig: 1070ti and 1050ti. You mentioned that "optim" switch is better on for 1070ti and off for 1050ti. Currently is impossible to set it differently for each card. May you include this feature in future?

[ninjam]

you can run two instances of the miner, one for 1050ti and another for 1070ti cards

[Vladeg]

New target received: 0t0000c7a408c16d5397624752b150dc00c222afeffaf2e6e6dd11e332e2aaeccerminate called after throwing an instance of '
std::bad_alloc'
 N what():  ew job received: std::bad_alloc1

Got this error. Rig 5x1080, set-work-batch is 2G or 8, both gives same result.

[john1010]

My final verdict is, this miner can only run 8gpu's as i tested it in my 10gpu rig, the miner only detect 8gpu, not worth it right now to run in 10gpu rig... I hope the dev will test or fix the miner's problem of not detecting 10gpu..

[Xaboom]

All in all... It is not profitable mining with amd cards

[Lolliedieb]

My final verdict is, this miner can only run 8gpu's as i tested it in my 10gpu rig, the miner only detect 8gpu, not worth it right now to run in 10gpu rig... I hope the dev will test or fix the miner's problem of not detecting 10gpu..

Well we had running more then 12 cards with this miner. But if this works hardly depends on drivers and OS. For example Nvidia drivers on Windows 10 does not allow more then 8 cards to work, while the drivers for Linux do. But thats not my fault then, the miner can use all OpenCL devices the drivers report - there is no hard coded limitation on this.

Problems with reconnecting to the pool https://mnx.4rigs.cf. An error occurs during the authorization phase - the miner exits. The program starts and stops indefinitely.

Can just confirm this. I am hunting this down right now.

How do you get that speed in your rx 480? mine is rx 480 8gb and i only got 8k sol/s, is any special setting to achieve that hash speed? can you please share your setting, I only use the default clock and mem, I only adjusted the voltage in AB @ -55 and -10 powlim

Current the AMDs need --work-batch as high as possible and --optim STD to max out their performance. Nvidias are much less sensitive to work batch changes. Will see where this comes from.

[Show420]

New target received: 0t0000c7a408c16d5397624752b150dc00c222afeffaf2e6e6dd11e332e2aaeccerminate called after throwing an instance of '
std::bad_alloc'
 N what():  ew job received: std::bad_alloc1

Got this error. Rig 5x1080, set-work-batch is 2G or 8, both gives same result.

I get this error too using Nvidia cards, hitting cancel on the pop up window seems to restart the miner but yes, annoying.  Have to babysit and check on it once in a while.  Sometimes it goes days without happening, sometimes it happens 3 times a day.

[ALFA-Dnepr]

You must disable the issuance of this message through the Windows registry

[dejan_p]

or you can run gpedit.msc
Computer Configuration > Administrative Templates > Windows Components > Windows Error Reporting
enable "prevent display of the user interface for critical errors"

voila problem solved
as soon as your miner crashes, it will open again  (you need to run the miner via the .bat provided with the miner)

[loewe1631]

please help me
I want to dig in my own pool. The message I get is this:
Auto GPU in platform.
Using device with id 0 (GeForce GTX 1070)
Using device with id 1 (GeForce GTX 1070)
Using device with id 2 (GeForce GTX 1070)
Using device with id 3 (GeForce GTX 1070)
Using device with id 4 (GeForce GTX 1070)
Auto selected work-batch for device 0: 32
Auto selected work-batch for device 1: 32
Auto selected work-batch for device 2: 32
Auto selected work-batch for device 3: 32
Auto selected work-batch for device 4: 32
Start Mining...
Connected to pool.coolmine.top:6666
Subscribed to stratum server
New target received: 0003333333333333400000000000000000000000000000000000000000000000
New job received: 13ae1
New job received: 13ae2
New job received: 13ae3
New job received: 13ae4
New job received: 13ae5


No hash information is available in the mine pool
Do I need to modify anything?