Hey Patrik,
I think I already asked this sometime before, but couldnt show a picture and details because this happens very rare.
- One or more cards are crashed. The mining window is still open, but isnt mining anymore.
- In AM it still shows "mining", but without any informations. AM will not restart that miner.
- The "GPU" tab is empty, also the "Pools" tab.
Is it possible to setup a rule to catch this? Or maybe AM can handle this automatically? I already tried some rules, but none works. Neither a single rule, or combined rules. For example:
- The trigger "Detect Miner State -> Mining" doesnt work.
- "Detect Device Count -> 0" doesnt work.
- "Power Usage -> 0" doesnt work.
I think because there is no miner API established because of the crash, even if the mining window is still open?
I think I already asked this sometime before, but couldnt show a picture and details because this happens very rare.
- One or more cards are crashed. The mining window is still open, but isnt mining anymore.
- In AM it still shows "mining", but without any informations. AM will not restart that miner.
- The "GPU" tab is empty, also the "Pools" tab.
Is it possible to setup a rule to catch this? Or maybe AM can handle this automatically? I already tried some rules, but none works. Neither a single rule, or combined rules. For example:
- The trigger "Detect Miner State -> Mining" doesnt work.
- "Detect Device Count -> 0" doesnt work.
- "Power Usage -> 0" doesnt work.
I think because there is no miner API established because of the crash, even if the mining window is still open?
Hey Patrik,
just got that situation again with the new T-Rex version in one of my single miners. Will send you the API-report by PM.
I think I know why this can happen:
- The profit switcher switched from NBminer to T-Rex, but NBminer wasn't closed for real. It is already running in the background (but depending to the pool with 0 hashrate).
- So there are 2 miners now and AM can't show the numbers for the T-Rex.
Is it somehow possible to double check (and kill) old unneeded tasks? Tried it with a batch command when NBminer stops, but this doesn't work all the time (taskkill /F /IM nbminer.exe).
Thanks for sharing the details. I can see from the API Report the T-Rex doesn't return anything and the reason is likely that NBminer uses the API port already, preventing T-Rex from using this port.
Would it be possible for you to also send me the Remote Agent log file for the time where NBMiner was supposed to be closed? You should be able to see log messages like "Closing process" and maybe even "Killing process".
What Awesome Miner do when closing mining software is to first send a friendly request to close down. Awesome Miner will then wait for the process to terminate (a number of seconds, configurable in the Options dialog, Mining Settings section), and if the process is still running, Awesome Miner tells Windows to kill the process.
Hey Patrik,
sent you the log file by PM and some more thoughts about that problem.
This problem we are suffering a lot of. CAsi always have to restart to work well.
I have a rule for dropped cards if they have 5 cards or less, reboot, when all my rigs are 6
But it would be a good thing to incorporate something that can be launched after each change to limit memory and processes caused by the miner.
I have everything updated to the latest version of Windows both in rig and in the AM computer. The latest security update of cuda 10.1, latest driver. I even launch a VHL at the end of each mining to clean memory. But even so, the teams suffer frequent restarts, it is such, I have had to reduce the number of protocols and currencies, raise the% change so that there are fewer changes per day.
The difficulty here is that there often are so many mining software involved and often changes between them so it's not always possible to tell if it's only one our of all mining software that are the cause for the instability.
It is not a problem of NBMINER, it happens with many more miners, ttminer, trex, basically with all, some more, others less. The only weird thing I'm using are the Nvidia Creator Drivers. Because now there are two versions, the gaming version and the creator version that is for heavier processes such as photoshop, cad etc ...
But I think it has more to do with the version 1809 of windows, since since you update all the computers to this latest version, the thing is even more unstable. I can have 20 restarts per hour with 6 rigs, it's hell. I have to work with very few protocols to minimize failures. My simple conclusions
Aftherburner does not affect, I tried it without it and the same thing happened
4 or 8 gigas of ram, it does not matter, the same happens
It all started with version 1809 and its latest update. All my equipment is in that version including the one that has AM installed
The intelibreeze service is called AM, it gets to consume 100% of CPU when it did not before and when it stops mining it sometimes stays at 50% of CPU with that service and when trying to mine another currency, the miner remains frozen and it reboots. If it is true that happens more with NBMiner because now we are mining much Cuckroo31. But also with other protocols x16s x16r etc ... Sometimes it is mining well and suddenly the miner closes and can not do it right until he restarts the machine.
Something suggests that some changes of the 1809 version is affecting intelibreeze. I have more than 150 failures a day, many more, and each failure is at least 5 minutes without mining, the time of lost mining is incredible
)