excavator by NiceHash - multi-algorithm NVIDIA GPU miner [1.5.6a]

[cveks]

nicehash is ripping you all guys .

Nobody hacked them, they simply decided to steal all bitcoins from their miners and hashing power buyers.


They steal hash power from miners, and they steal profit from hash power buyers.

They are classic scam company.

You believe them that they gave you this miner for free?

Only free cheese is in the mousetrap.

[Kaan3000]

nicehash is ripping you all guys .

Nobody hacked them, they simply decided to steal all bitcoins from their miners and hashing power buyers.


They steal hash power from miners, and they steal profit from hash power buyers.

They are classic scam company.

You believe them that they gave you this miner for free?

Only free cheese is in the mousetrap.

You don't have to mine to nicehash. The miner is not only for free but also faster than what is otherwise available in the market; closed or open source...

I lost some money on nicehash, wasted my hashrate too. But this miner is good

[dropky]

I was just doing a restart on one of my rigs with nicehash 2.0.1.10 on it.

When it restarted it came up saying - we don't allow bots here type in the number below ?

I had the miner set to start when windows started by putting a link to it in the startup folder.
I had it setup like this so if the computer restarts or there is a power outage and it comes on again it would start mining by iself.
Is there any way around this if I am out or at work otherwise I have to be there to type in the number

Did you enable "Autostart mining" under Configure -> Mining?

Yes I have on all of them. Thats why I was surprised as I have rebooted np before..
I also rebooted the rig remotely with teamviewer, would that affect it ?
 I've upgraded to 2.0.1.11 now.

Teamviewer shouldn't affect anything, bot prevention should only pop up at new install, but I might be mistaken (I'll check).. Do you still have the problem with NHM 2.0.1.11? Does it happen every time?

[dropky]

Hello. Is there a config option for excavator to exit on pool error or when the pool is offline?

No, if the pool is offline excavator will repeatedly try to reconnect. You could always write your own script that monitors excavator via its API.

[stevej]

I upgraded to 2.0.1.11 yesterday.

Since then I have noticed that excavator is mining ok, then all of a sudden I see red lines and it restarts.
Its mining equihash with 8 x nvidia GTX 1060 3gb
It hasn't been doing this with earlier versions, it would go for days.
Once I saw this tonight I went to the log files to see what the errors are, the lines below keep coming up and it looks like its just before it restarts.
The errors below are in the log files at where it looks like it restarts.

{"name":"NHM","hostname":"Miner04","pid":2864,"level":30,"msg":"[JSONTypedParse<T>] Unable to parse response as JSON SyntaxError: Unexpected token P in JSON at position 40","time":"2018-02-27T04:41:27.920Z","v":0}
{"name":"NHM","hostname":"Miner04","pid":2864,"level":30,"msg":"[API] method: undefined error: TypeError: Cannot read property 'method' of null","time":"2018-02-27T04:41:27.920Z","v":0}

[stevej]

I was just doing a restart on one of my rigs with nicehash 2.0.1.10 on it.

When it restarted it came up saying - we don't allow bots here type in the number below ?

I had the miner set to start when windows started by putting a link to it in the startup folder.
I had it setup like this so if the computer restarts or there is a power outage and it comes on again it would start mining by iself.
Is there any way around this if I am out or at work otherwise I have to be there to type in the number

Did you enable "Autostart mining" under Configure -> Mining?

Yes I have on all of them. Thats why I was surprised as I have rebooted np before..
I also rebooted the rig remotely with teamviewer, would that affect it ?
 I've upgraded to 2.0.1.11 now.

Teamviewer shouldn't affect anything, bot prevention should only pop up at new install, but I might be mistaken (I'll check).. Do you still have the problem with NHM 2.0.1.11? Does it happen every time?

It definatley wasn't a new install, I was just rebooting.
I'll try a reboot with 2.0.1.11 and see what happens.

[dropky]

It definatley wasn't a new install, I was just rebooting.
I'll try a reboot with 2.0.1.11 and see what happens.

I checked with the NHM team, bot prevention pops up if it's a new install or if there were any changes in the system or config files.

[dropky]

I have a rig with several different cards.  Will I be able to benchmark with the excavator so I don't have to manually configure parameters for every card and algo?


Thanks

What do you mean by manually configure parameters? Which parameters (algorithm parameters or OC settings)? Excavator is already tuned for the most Pascal cards (check here - https://github.com/nicehash/excavator/tree/master/nvidia, under each algorithm you can see the cards algorithm is optimized for). If you want to optimize OC settings, that's up to you. 

[stevej]

It definatley wasn't a new install, I was just rebooting.
I'll try a reboot with 2.0.1.11 and see what happens.

I checked with the NHM team, bot prevention pops up if it's a new install or if there were any changes in the system or config files.

`

Ok, windows rebooted to update, it came up after that.

I keep disabling Windows Update and stopping the service but the bloody thing keeps turning itself on again

[dropky]

I upgraded to 2.0.1.11 yesterday.

Since then I have noticed that excavator is mining ok, then all of a sudden I see red lines and it restarts.
Its mining equihash with 8 x nvidia GTX 1060 3gb
It hasn't been doing this with earlier versions, it would go for days.
Once I saw this tonight I went to the log files to see what the errors are, the lines below keep coming up and it looks like its just before it restarts.
The errors below are in the log files at where it looks like it restarts.

{"name":"NHM","hostname":"Miner04","pid":2864,"level":30,"msg":"[JSONTypedParse<T>] Unable to parse response as JSON SyntaxError: Unexpected token P in JSON at position 40","time":"2018-02-27T04:41:27.920Z","v":0}
{"name":"NHM","hostname":"Miner04","pid":2864,"level":30,"msg":"[API] method: undefined error: TypeError: Cannot read property 'method' of null","time":"2018-02-27T04:41:27.920Z","v":0}

Please check excavator log file. To enable excavator file logging change "ExcavatorExtraStartupParameters": "", to "ExcavatorExtraStartupParameters": "-f 0" in General.json config file, restart NHM, wait for the crash, then search for the excavator logs here: C:\Users\user_name\AppData\Roaming\nhm2\bin\excavator_server\archived_logs or in the same directory that excavator is.

[Newton90]

hello.how can i change intensity in this miner?

because if i add for nist5 for example this:

{"time":5,"commands":[
      {"id":1,"method":"device.set.intensity","params":["0","22"]}
      
   ]},

to default_command_file nothing is happen.thanks.

[dropky]

hello.how can i change intensity in this miner?

because if i add for nist5 for example this:

{"time":5,"commands":[
      {"id":1,"method":"device.set.intensity","params":["0","22"]}
      
   ]},

to default_command_file nothing is happen.thanks.

Intensity method is not supported. You can change the intensity for nist5 with algorithm parameters - https://github.com/nicehash/excavator/tree/master/nvidia#-nist5.

Like this: {"id":1,"method":"worker.add","params":["alg_id", "device_id","intensity"]}

[akuci]

It's almost 150 sols behind (on 6 cards total) DSTM on Equihash, so it would be nice if the developers can look into ways to improve Equihash, as it's most of the time the most profitable algo to mine.
On 2 RIGS you have one card free, on 4, you have 2 cards woth of hash for free on DSTM.

[dropky]

It's almost 150 sols behind (on 6 cards total) DSTM on Equihash, so it would be nice if the developers can look into ways to improve Equihash, as it's most of the time the most profitable algo to mine.
On 2 RIGS you have one card free, on 4, you have 2 cards woth of hash for free on DSTM.

We're working on improvements for Equihash..

[dropky]

Hello! I have an issue with unstable (floating) hashrate on DaggerHashimoto algo. In my PC with GTX 1070 Excavator shows iron stable 30 MH/s, it never changes. But on my rig with 6x GTX 1070 Ti hashrate fluctuates between ~150 MH/s and 180 MH/s, and it can hash on 150 for quite a long time (hours) before it goes up to 180, holds it there a bit, and then hashrate goes down again. Is there a way to make it more stable?

Unfortunately no. There are two things that need to be taken into consideration here. First, when mining daggerhashimoto occasionally new DAG has to be built, when that happens the hashrate will decrease for a bit since the miner isn't really mining at that exact moment. The second thing is the precision of the reported speed. You should call worker.reset 10 seconds after worker.add to get more accurate results (worker.reset purpose is to reset time interval measurement and achieve more accurate speeds). Also keep in mind that slight speed variation is completely normal, even expected. If you check the average pool speed over couple of hours, there shouldn't be any noticeable/big floating.

[Amstellodamois]

Is there a limit in the number of cards? Can I run it on my 12 card rig?

[dropky]

Is there a limit in the number of cards? Can I run it on my 12 card rig?

There are no limits imposed by excavator. I am aware of examples where people have gotten in the range of 12-18 GPU devices working correctly. So yes, it should work just fine on your rig with 12 cards.

[Amstellodamois]

Thanks

[proteus7]

If I have a mixed rig with 6 similar cards (1080ti) and 1 different card (Tesla), how can I get Excavator to disable it, so that it can be used elsewhere? Trying to disable card 0 specifically.
There doesn't seem to be a command line option for this...

[dropky]

If I have a mixed rig with 6 similar cards (1080ti) and 1 different card (Tesla), how can I get Excavator to disable it, so that it can be used elsewhere? Trying to disable card 0 specifically.
There doesn't seem to be a command line option for this...

How are you running excavator? If you're using config file, just don't assign any workers for the specific card.