"cashen" for Nvidia Inspector you can just use these commands:
NVI_0_2_200_-1000_80_83_0
that = (gpu device 0 / core + 200 / mem -1000 / powertarget 80% / temp 83)
Topic: [NemosMiner] multi algo profit switching NVIDIA/CPU miner - page 191. (Read 289464 times)
If you have Windows 7, please update PowerShell:
https://www.microsoft.com/en-us/download/details.aspx?id=50395
CCMiner may need 'MSVCR120.dll' if you don't already have it:
https://www.microsoft.com/en-gb/download/details.aspx?id=40784
CCMiner may need 'VCRUNTIME140.DLL' if you don't already have it:
https://www.microsoft.com/en-us/download/details.aspx?id=48145
running multiple cards its recommend to increase Virtual Memory 32gb-64gb is optimal
all my rigs been running for nearly a week straight i have a 1070x6 rig running 2.0.7 no issue's..
theres is something wrong with your rig.. (check risers/cables/psu)
https://www.microsoft.com/en-us/download/details.aspx?id=50395
CCMiner may need 'MSVCR120.dll' if you don't already have it:
https://www.microsoft.com/en-gb/download/details.aspx?id=40784
CCMiner may need 'VCRUNTIME140.DLL' if you don't already have it:
https://www.microsoft.com/en-us/download/details.aspx?id=48145
running multiple cards its recommend to increase Virtual Memory 32gb-64gb is optimal
all my rigs been running for nearly a week straight i have a 1070x6 rig running 2.0.7 no issue's..
theres is something wrong with your rig.. (check risers/cables/psu)
try disabling hmq1725 and re run, let me know if its just that algo or not.. what card you running? (in start.bat -Algo remove hmq1725)
Thanks, i'm using 6x GTX 1070.
After disabling hmq1725 still got an error http://preview.ibb.co/fKgjhv/Untitled.jpg
I also added the following code to the beginning of the start.bat file
Code:
SET CLOCK1=200
SET MEM1=500
SET POWTAR1=120
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
SET GPU0=-setBaseClockOffset:0,0,%CLOCK1% -setMemoryClockOffset:0,0,%MEM1% -setPowerTarget:0,%POWTAR1% -setTempTarget:0,0,83 -forcepstate:0,0
SET GPU1=-setBaseClockOffset:1,0,%CLOCK1% -setMemoryClockOffset:1,0,%MEM1% -setPowerTarget:1,%POWTAR1% -setTempTarget:1,0,83 -forcepstate:1,0
SET GPU2=-setBaseClockOffset:2,0,%CLOCK1% -setMemoryClockOffset:2,0,%MEM1% -setPowerTarget:2,%POWTAR1% -setTempTarget:2,0,83 -forcepstate:2,0
SET GPU3=-setBaseClockOffset:3,0,%CLOCK1% -setMemoryClockOffset:3,0,%MEM1% -setPowerTarget:3,%POWTAR1% -setTempTarget:3,0,83 -forcepstate:3,0
SET GPU4=-setBaseClockOffset:4,0,%CLOCK1% -setMemoryClockOffset:4,0,%MEM1% -setPowerTarget:4,%POWTAR1% -setTempTarget:4,0,83 -forcepstate:4,0
SET GPU5=-setBaseClockOffset:5,0,%CLOCK1% -setMemoryClockOffset:5,0,%MEM1% -setPowerTarget:5,%POWTAR1% -setTempTarget:5,0,83 -forcepstate:5,0
SET GPU6=-setBaseClockOffset:6,0,%CLOCK1% -setMemoryClockOffset:6,0,%MEM1% -setPowerTarget:6,%POWTAR1% -setTempTarget:6,0,83 -forcepstate:6,0
SET GPU7=-setBaseClockOffset:7,0,%CLOCK1% -setMemoryClockOffset:7,0,%MEM1% -setPowerTarget:7,%POWTAR1% -setTempTarget:7,0,83 -forcepstate:7,0
C:\CRYPTO\SOFTWARE\nvidiaInspector\nvidiaInspector.exe %GPU0% %GPU1% %GPU2% %GPU3% %GPU4% %GPU5% %GPU6% %GPU7%
SET MEM1=500
SET POWTAR1=120
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
SET GPU0=-setBaseClockOffset:0,0,%CLOCK1% -setMemoryClockOffset:0,0,%MEM1% -setPowerTarget:0,%POWTAR1% -setTempTarget:0,0,83 -forcepstate:0,0
SET GPU1=-setBaseClockOffset:1,0,%CLOCK1% -setMemoryClockOffset:1,0,%MEM1% -setPowerTarget:1,%POWTAR1% -setTempTarget:1,0,83 -forcepstate:1,0
SET GPU2=-setBaseClockOffset:2,0,%CLOCK1% -setMemoryClockOffset:2,0,%MEM1% -setPowerTarget:2,%POWTAR1% -setTempTarget:2,0,83 -forcepstate:2,0
SET GPU3=-setBaseClockOffset:3,0,%CLOCK1% -setMemoryClockOffset:3,0,%MEM1% -setPowerTarget:3,%POWTAR1% -setTempTarget:3,0,83 -forcepstate:3,0
SET GPU4=-setBaseClockOffset:4,0,%CLOCK1% -setMemoryClockOffset:4,0,%MEM1% -setPowerTarget:4,%POWTAR1% -setTempTarget:4,0,83 -forcepstate:4,0
SET GPU5=-setBaseClockOffset:5,0,%CLOCK1% -setMemoryClockOffset:5,0,%MEM1% -setPowerTarget:5,%POWTAR1% -setTempTarget:5,0,83 -forcepstate:5,0
SET GPU6=-setBaseClockOffset:6,0,%CLOCK1% -setMemoryClockOffset:6,0,%MEM1% -setPowerTarget:6,%POWTAR1% -setTempTarget:6,0,83 -forcepstate:6,0
SET GPU7=-setBaseClockOffset:7,0,%CLOCK1% -setMemoryClockOffset:7,0,%MEM1% -setPowerTarget:7,%POWTAR1% -setTempTarget:7,0,83 -forcepstate:7,0
C:\CRYPTO\SOFTWARE\nvidiaInspector\nvidiaInspector.exe %GPU0% %GPU1% %GPU2% %GPU3% %GPU4% %GPU5% %GPU6% %GPU7%
Thanks "Cashen" (nice way of controlling power target core OC mem UC for each card)
from my experience the code:
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
is for AMD cards and has nothing to do with Nvidia Cards.. (I may be wrong tho.. i'll try it with, and without, see what happens)
Best Regards
Nemo
Hi, was trying to run Nemosminer on Windows 7 x64
Continuously getting errors(please see screenshot)
Am i missing something?
Continuously getting errors(please see screenshot)
Am i missing something?
try disabling hmq1725 and re run, let me know if its just that algo or not.. what card you running? (in start.bat -Algo remove hmq1725)
Hi, was trying to run Nemosminer on Windows 7 x64
Continuously getting errors(please see screenshot)
Am i missing something?
https://preview.ibb.co/hmEO9a/Untitled.jpg
Continuously getting errors(please see screenshot)
Am i missing something?
https://preview.ibb.co/hmEO9a/Untitled.jpg
Hi,
First of all really nice project you have going on here.
I have a rig of 6 1070s, I am uses the 2.0.7 version of your program. I noticed that the alexis fork of ccminer is not downloaded/working. Is this normal?
First of all really nice project you have going on here.
I have a rig of 6 1070s, I am uses the 2.0.7 version of your program. I noticed that the alexis fork of ccminer is not downloaded/working. Is this normal?
It only downloads miners which are called. If you want to use Alexis then open the miner folder and the first Alexis. Uncomment algos you want to use. I also added c11.
If you don't want to use other miners for those algos, just open those miners and comment them out.
Thanks!
Hi,
First of all really nice project you have going on here.
I have a rig of 6 1070s, I am uses the 2.0.7 version of your program. I noticed that the alexis fork of ccminer is not downloaded/working. Is this normal?
First of all really nice project you have going on here.
I have a rig of 6 1070s, I am uses the 2.0.7 version of your program. I noticed that the alexis fork of ccminer is not downloaded/working. Is this normal?
It only downloads miners which are called. If you want to use Alexis then open the miner folder and the first Alexis. Uncomment algos you want to use. I also added c11.
If you don't want to use other miners for those algos, just open those miners and comment them out.
Hi,
First of all really nice project you have going on here.
I have a rig of 6 1070s, I am uses the 2.0.7 version of your program. I noticed that the alexis fork of ccminer is not downloaded/working. Is this normal?
First of all really nice project you have going on here.
I have a rig of 6 1070s, I am uses the 2.0.7 version of your program. I noticed that the alexis fork of ccminer is not downloaded/working. Is this normal?
One more thing.
The current API callout wasn't working for me. I had to add -b 0.0.0.0:4068 to all the miner files. Works great now with awesome miner.
The current API callout wasn't working for me. I had to add -b 0.0.0.0:4068 to all the miner files. Works great now with awesome miner.
Only equihash and I think I've heard neoscrypt? (don't have in on my list) require any memory overclock.
Also if there was a criteria for profit switching such as must be 5% more profitable that the current coin being mined over a specific time frame it could minimize the unnecessary switches.
I believe this is the reason why people hate on Zpool claiming its stealing. It isn't from my months of testing it's just situations of sub optimal switches and market value fluctuations when the longer confirmations coins are exchanged which cause those random days of regular or less profit.
Also if there was a criteria for profit switching such as must be 5% more profitable that the current coin being mined over a specific time frame it could minimize the unnecessary switches.
I believe this is the reason why people hate on Zpool claiming its stealing. It isn't from my months of testing it's just situations of sub optimal switches and market value fluctuations when the longer confirmations coins are exchanged which cause those random days of regular or less profit.
Agree. Blake2s was very big and Netko took like 2-3 days to confirm.
I'm trying to change the interval in the start.bat to 120. I don't think it works the way I want it to tho. Might make it worse.
Only equihash and I think I've heard neoscrypt? (don't have in on my list) require any memory overclock.
Also if there was a criteria for profit switching such as must be 5% more profitable that the current coin being mined over a specific time frame it could minimize the unnecessary switches.
I believe this is the reason why people hate on Zpool claiming its stealing. It isn't from my months of testing it's just situations of sub optimal switches and market value fluctuations when the longer confirmations coins are exchanged which cause those random days of regular or less profit.
Also if there was a criteria for profit switching such as must be 5% more profitable that the current coin being mined over a specific time frame it could minimize the unnecessary switches.
I believe this is the reason why people hate on Zpool claiming its stealing. It isn't from my months of testing it's just situations of sub optimal switches and market value fluctuations when the longer confirmations coins are exchanged which cause those random days of regular or less profit.
example of skein just shooting up. All 3 of my rigs switched for about 20 seconds. They should not have switched.
Which of these algos actually profit from memory speed? Wouldn't reducing mem speed gimp those too much?
I think in most of my single algo bats I have mem set to -1000.
I put it in the + for Nemo because I can't change it for each algo. I'd like to change power too, instead i have to run 1 for all.
Which of these algos actually profit from memory speed? Wouldn't reducing mem speed gimp those too much?
Nvidia Inspector also allows memory underclocking to -1000 which allows for head room on the core overclocks when set to power limits.
I haven't been able to get that done on MSI AB or I'd be using the new 2.xx versions of NEMOSMINER.
Now when mining just one algo though using the new curve feature with fixed voltage is most optimal.
I haven't been able to get that done on MSI AB or I'd be using the new 2.xx versions of NEMOSMINER.
Now when mining just one algo though using the new curve feature with fixed voltage is most optimal.
This is a snapshot of my 8 x 1080 Rig. I'm concerned it is switching too much. Anyone figure out how to get the profits to still update frequently but only switch if the most profitable has been there for say 90 seconds? this would prevent a lot of blips.
Looks to have changed 115 times since I started about 12 hours ago.
That is about 6 min average, but i'm sure 75% of those were running less than 2 minutes.
Let's say it takes about 8 seconds to switch and get to full speed. In 12 hours I spent 15 minutes offline due to switching. This is about a 2% impact.
Any thoughts?
Looks to have changed 115 times since I started about 12 hours ago.
That is about 6 min average, but i'm sure 75% of those were running less than 2 minutes.
Let's say it takes about 8 seconds to switch and get to full speed. In 12 hours I spent 15 minutes offline due to switching. This is about a 2% impact.
Any thoughts?
Great project, I'll definitely be testing it out. Will tip too - keep up the good work 
I also added the following code to the beginning of the start.bat file
Code:
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
I thought that these variables are only needed when using ethash miners.
Are you seeing any difference when using them with ccminer/ewbf?
Impressive mastery of NvidiaInspector, BTW.
How come you use it instead of AB?
I use NvidiaInspector because I feel it is faster when loading values. The command lines are cleaner I feel. I also think it "wakes" the cards up when these get pushed. Using this method I have a lot less issues of Alexis not loading all cards when started.
The var sets I include everywhere just from habit. I have had issues when not included.
I also added the following code to the beginning of the start.bat file
Code:
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
I thought that these variables are only needed when using ethash miners.
Are you seeing any difference when using them with ccminer/ewbf?
Impressive mastery of NvidiaInspector, BTW.
How come you use it instead of AB?
Jump to: