Re: [Forager] 1.8 - Multi-Pool profit switching miner (AMD/NVIDIA/CPU) 18/06/18
hi,
Just tried the latest Forager code (cloned from github), as MegaMiner seems abandoned.. there are, however, some issues.
There are a couple error messages repeated before every new interval:
Doesn't seem to cause any problems, though.
However on two out of three systems I tested, one hard crashes, and one goes into an endless error loop, something like "cannot kill process "IDLE". Unfortunately the error is not written into the log, have to catch and copy it again.
This is all on Nvidia rigs where MegaMiner has been running fine and stable for many months.
Just tried the latest Forager code (cloned from github), as MegaMiner seems abandoned.. there are, however, some issues.
There are a couple error messages repeated before every new interval:
Code:
Cannot index into a null array.
At C:\miner\Forager\Include.ps1:425 char:17
+ ... $PnpDeviceProperties = ($PnpDevices | Where-Object {$Vend ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [], RuntimeException
+ FullyQualifiedErrorId : NullArray
At C:\miner\Forager\Include.ps1:425 char:17
+ ... $PnpDeviceProperties = ($PnpDevices | Where-Object {$Vend ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [], RuntimeException
+ FullyQualifiedErrorId : NullArray
Doesn't seem to cause any problems, though.
However on two out of three systems I tested, one hard crashes, and one goes into an endless error loop, something like "cannot kill process "IDLE". Unfortunately the error is not written into the log, have to catch and copy it again.
This is all on Nvidia rigs where MegaMiner has been running fine and stable for many months.
I'll take a look. I believe the code throwing the error is redundant now
Quote
And I hope you can provide something so I can check the issue you are experiencing.
Send me the logs, even if they don't show the errors, maybe I'll discover something since I know how it should work
I will add such option, I also noticed this behavior
Send me the logs, even if they don't show the errors, maybe I'll discover something since I know how it should work
Is there a way to disable specific algos for specific pools.
reason is that when dual mining with claymore, zpool and ahash will show hi reject rates (50%) for keccak, but nicehash will be ok.
thanks.
reason is that when dual mining with claymore, zpool and ahash will show hi reject rates (50%) for keccak, but nicehash will be ok.
thanks.
I will add such option, I also noticed this behavior
Added now in latest commit
thanks... testing it now... works great. i've been able to eliminate keccak from ahash,blazepool, and zpool. keccak works fine on nicehash and zergpool.