Hi patrike,
I'm experiencing an issue mining with excavator through AM.
I'm using excavator 1.4.4a, with the "default_command_file.json" included it works well.
With AM it worked fine but not anymore, no regard how much GPU I select in benchmark or wich algorithm or wich pool I choose, I always got this
=========================== www.nicehash.com =========================
Excavator v1.4.4a_nvidia GPU Miner for NiceHash.
Copyright (C) 2018 NiceHash. All rights reserved.
Developed by
djeZo, dropky, voidstar, and agiz
with help and contributions from
zawawa, pallas, Vorksholk, bitbandi, ocminer, and Genoil.
=========================== www.nicehash.com =========================
Build time: 2018-02-16 13:11:25
Build number: 4645
Provided startup commandline:
"C:\Users\MINEUR\AppData\Local\AwesomeMinerService\UploadedSoftware\excavator\excavator.exe" -c awesome.json -p 4028
[05:05:15][0x00000fc0][info] Log started
[05:05:15][0x00000fc0][info] core | Found CUDA device: GeForce GTX 1080 Ti
[05:05:16][0x00000fc0][info] core | Found CUDA device: GeForce GTX 1080 Ti
[05:05:16][0x00000fc0][info] core | Found CUDA device: GeForce GTX 1080 Ti
[05:05:16][0x00000fc0][info] core | Found CUDA device: GeForce GTX 1080 Ti
[05:05:16][0x00000fc0][info] core | Found CUDA device: GeForce GTX 1080 Ti
[05:05:16][0x00000fc0][info] core | Found CUDA device: GeForce GTX 1080 Ti
[05:05:16][0x00000fc0][info] api | Listening on 127.0.0.1:4028
[05:05:16][0x00000fc0][info] core | Initialized!
[05:05:19][0x000007d4][warning] core | Command exec: invalid stoi argument
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
The awesome.json file generated in excavator folder look like this
[
{"time":0,"commands":[
{"id":1,"method":"subscribe","params":["nhmp.eu.nicehash.com:3200","my.btc.address"]}
]},
{"time":1,"commands":[
{"id":1,"method":"algorithm.add","params":["equihash"]}
]},
{"time":3,"commands":[
{"id":1,"method":"worker.add","params":["equihash","0"]},
{"id":1,"method":"worker.add","params":["equihash","1"]},
{"id":1,"method":"worker.add","params":["equihash","2"]},
{"id":1,"method":"worker.add","params":["equihash","3"]},
{"id":1,"method":"worker.add","params":["equihash","4"]},
{"id":1,"method":"worker.add","params":["equihash","5"]},
{"id":1,"method":"worker.add","params":["equihash","6"]},
{"id":1,"method":"worker.add","params":["equihash","7"]},
{"id":1,"method":"worker.add","params":["equihash","8"]},
{"id":1,"method":"worker.add","params":["equihash","9"]},
{"id":1,"method":"worker.add","params":["equihash","10"]},
{"id":1,"method":"worker.add","params":["equihash","11"]},
{"id":1,"method":"worker.add","params":["equihash","12"]}
]},
{"time":10,"loop":10,"commands":[
{"id":1,"method":"worker.print.speed","params":["0"]},
{"id":1,"method":"worker.print.speed","params":["1"]},
{"id":1,"method":"worker.print.speed","params":["2"]},
{"id":1,"method":"worker.print.speed","params":["3"]},
{"id":1,"method":"worker.print.speed","params":["4"]},
{"id":1,"method":"worker.print.speed","params":["5"]},
{"id":1,"method":"worker.print.speed","params":["6"]},
{"id":1,"method":"worker.print.speed","params":["7"]},
{"id":1,"method":"worker.print.speed","params":["8"]},
{"id":1,"method":"worker.print.speed","params":["9"]},
{"id":1,"method":"worker.print.speed","params":["10"]},
{"id":1,"method":"worker.print.speed","params":["11"]},
{"id":1,"method":"worker.print.speed","params":["12"]},
{"id":1,"method":"algorithm.print.speeds","params":["0"]}
]}
]
I don't understand why there's this "invalid stoi argument"
Thanks !
I'm getting this as well.. I think something broke that miner in the CUDA 9.2 upgrade...