Topic: XMR-stak-JK 2.10.7 Compiled with no devfee (Updated: 2019-8-18) - page 10. (Read 28564 times)

there is none.

to disable individual devices you should read this thread;  it already explains how to modify the settings and comment out the necessary lines and disable/change different devices in the nvidia.txt, cpu.txt and amd.txt....


What would be better is you should check readme.md, compile.md, etc on the official github:
https://github.com/fireice-uk/xmr-stak     Just scroll down;  there's links there to each subject.  It goes into great detail.

I didn't write the program, I just compiled the source with no devfee.

How to configure the display of statistics in the window of the miner (as in ccminer)?
how to disable support for mining on the CPU?

yes, this one is current, i am unaware of any algo changes coming up soon.

Thanks, I will try. Tell me more, does this miner support Cryptonight v7 ?

There is no batch file.

You run the app for the first time, answer the questions, and it generates .txt files with the configurations and starts mining right away.

When you go to run it thereafter, you simply launch the .exe to mine.


You can reference the docs or this thread for how to trim and modify each video card's properties/intensities; as well as how to create separate configurations for use with different pools/algos.


But;  if you wish to have the app auto-run at startup (especially in windows 10);  it should be run as administrator;  its folder should be in the root of C for example;  do not use a .lnk to launch it from the startup folder;  you must make a simple batch and the batch file should look something like this (modify it for your config; and this should be one of the only reasons you should need a batch file for xmr-stak):
Be sure this batch file is set to run as administrator.

this miner supports Cryptonight v7 ?
please give the file a start.bat for GTX 1070.
I tormented myself half a day, I can not start it at all. I do not understand what to write there.

This card is on my main desktop so not a dedicated mining rig, but I'm doing about 740H/s on average with an Elpida powersaver ROM, core at 1200, mem at 1900 and no change to power limit.

Calling 1080Ti users of this build:

I just got back from servicing a few of my friend's miners;  as well as disassembling and re-pasting cards to be resold...

At the end of my night;  I loaded xmr-stak 2.4.4 and it would crash when it loads the threads for the nvidia cards....    one card, both cards, either card... same result on the 1080 Ti's.


Here's a big rub:
I updated the video driver.  Clean DDE and install clean via the latest available download.    Same results.
Tried my build of 2.4.2.   Same results.
Tried modifying bfactor/bsleep.  Same results.


Here's the twist:
I was given a 1080 from him as a thanks for all the work today....    brought it home;  works like a champ (not Ti...).  We did not test XMR-stak on the 1080 machines, because they have all been dismantled, cleaned, and re-pasted and re-boxed to re-sell and invest the return in crypto during this low....   so;  in my own eyes, to this day I have seen it work with every card I can throw at it except:  1080Ti, and GTX 2xx series....



So has anyone here had success with their 1080 Ti's?
If so:
What OS, Video driver version, and make/model of card do you have?


FYI; this is a driver crash, leading to a cuda error because the driver crashed.    As mentioned above, changing bfactor/bsleep/threads changed nothing.   Mining other algos (xevan, skien, neoscrypt, etc) works fine.

Thanks.    Hopefully this will help me figure out whats really wrong.  

Update of my result, seems that it increased from 614 - 630/645H Thanks for the help.. Oh by the way what is the hashrate of your card? I am using Sapphire RX 580 8GB and MSI Gaming X 570 4Gb..

Here's the screenshot:

I will copy this settings on the AMD config txt? Or only the intensity, worksize and memchunk? sorry totally nood using this miner, since when i was started mining I only using claymore eth base and phoenix miner.

Each card entry in your amd.txt file should look something like this:

{ "index" : 0, "intensity" : 800, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 2, "mem_chunk" : 2, "comp_mode" : false },
{ "index" : 0, "intensity" : 800, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 2, "mem_chunk" : 2, "comp_mode" : false },

With only the index number incrementing by 1 for each card. This gives 2 threads (why the lines are duplicated) with intensity of 800, etc. So, for example, the 2nd card would have entries like so:

{ "index" : 1, "intensity" : 800, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 2, "mem_chunk" : 2, "comp_mode" : false },
{ "index" : 1, "intensity" : 800, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 2, "mem_chunk" : 2, "comp_mode" : false },

Etc. up to the 12th card, which will have index of 11.

I got that same error too and tried installing visual ++c and nothing fix by doing that, I dunno why, I ask my friends about the error and they told me that I must uninstall and install the visual ++c but again, nothing happened.. I discovered that it will need to add more virtual memory to fix that error, I recently setting up the VM with 35K but after I add some VM to 55K and the error fixed.. This miner needs more Virtual memory to run smoothly.. Hope it helps.

I'm using 12 rx 570 nitro+ 8gb per rig and I only got 615H per card, is this hashrate power is okay or there is a way to increase it, I'm using the latest version of xmr-stak I hope somebody here put some help..

Thanks

Do you have a link to this stripped-down version of Windows 10, I'd like to give it a go and see what happens.

Yep, I thank the dev for releasing the source as well.

I'll be gone for the weekend; hopefully I can pick this back up next week when I'm less busy....

I don't fundamentally begrudge the dev fee for the Claymore miner it's just the way it does it that results in a greater loss of mining than just the fee alone (time spent changing servers adds a significant loss).
Maybe longer periods between collecting dev fee and a lower dev fee (he must be loaded by now) would help.

Honesly i am not yet try this software. It is seem nice software for mining with no fee. But i still choose claymore with dev fee, because i think dev fee is important for developing the software. Anyway thank for sharing new mining software, and i waiting news for it's speed mining.

You seem close and thank you for that. I think it's a refreshment to this thread as there wasn't any posts since June 26th or so.

yeah.  for now, ive been focused on work... and every attempt so far at compiling 2.4.5 so far has failed.

I want to wipe the laptop Ive been using to compile, and try reinstalling everything fresh again and see where I can get.

I already have the doctored source to compile that removes all the devfee addresses and sets the devfee factor to zero.  I think the only thing I need to change is the build pull number (there's a giithub reference variable its compiled with that's linked to version,  I haven't changed that yet, but it really doesn't matter int he grand scope of things).

I did compile XTL stak at the same time I did 2.4.4... but it seems to not be a version people are after and Ill be ignoring it from now on.

JaredKaragen, great work. Should I assume that you abandoned 2.4.5 or there isn't progress?