for a couple of version I have been experiencing a very recurring failure, and almost always happens in the 1080ti rigs. When you change from AL-GO and you go to another currency, the miner mine, I see it in the console but in the AM screen it indicates "Miner offline", but it is working. At the end, the offline mining rule is applied to me, reboot rig and then it works.
It's been happening since the OC was implemented with administrator permissions. It is rare that the miner is mining, but the panel figured as offline, without time, temperature, hash or anything, but in the console you see the miner working. It's clear how the program does not read it, it detects offline, and reboot. It is very uncomfortable.
I see this on one of my mixed 1070/1080 rigs too and very, very rarely on my 1080 Ti rig. So I think its not an issue of 1080 Ti's, but of the used mining software and/or the combination which one will be exited first and which one will be opened right after. Iam sure its T-Rex and/or CryptoDredge, never realized that with different miners.
I deactivated the restart in the Offline-Rule, I only get a message when it happens. Just started logging again and will try to catch that case.
dethating that rule is a patch. Because without a real rig it fails and is offline and you do not detect it, and you are in bed 8 hours, because it is 8 hours of lack of mining.
Also, without these data, they are not reflected in the statistics of the rig. So it's just a patch until stability is again because I guess something Patrike could do to control this problem.
Do you also mainly see this for T-Rex (and possibly CryptoDredge) or is it for all mining software? Based on your other post it sounds like it was mainly for T-Rex, but please confirm if this is the only software you run into these problems.
1) If this is an issue with the API of the mining software, please generate an API report for the miner next time you see the issue (toolbar Tools -> API Report). If the API doesn't respond, Awesome Miner might indicate "Mining" but you don't see any other details. The API Report would be able to confirm if this is the case.
2) (I don't think this second point is relevant in your case, but I leave it here as general information). If you also experience that Awesome Miner considers the miner to have crashed completely while it's still running, please also consider the following:
The Remote Agent log file will indicate the Process ID (PID) when it launches mining software. It will look something like this in the log file "Mining Engine Process started, PID: 11524". If you run into this problem where Awesome Miner doesn't think the mining software is running anymore - could you please compare the PID of the process in the Remote Agent log file with what the Windows Task Manager indicates for the mining software? When all is working fine, they should of course be the same, as Awesome Miner monitors the process with this PID. If no process with this PID is found, Awesome Miner considers it a mining software crash.
I already have the fault. I have tried to ignore it by adding more time to the OFFLINE rule that is by default to leave more margin.
In the screenshots you will see that all the miners have been reset when changing to x16rt but rig3 and rig5 both of 1080ti have failed me. One shows even temperature data but not mine, and the other has remained directly on Offline without doing anything until it has been restarted. After restart it works without problems. Not only does it happen with Trex, it also happens with other miners like cryptodredge, nor do I use a wide variety of miners.
The problem persists even having increased the Offline rule to 6 minutes, time to spare. But the rig ends up restarting.
I attached captures with link to not fill the forum of images and I paste the report of RIG 3, which came to work but badly, and restarted, the RIG5 did not arrive or start the miner. Then it restarts and works as if nothing. This took about two or three weeks, coincides with the administrator changes in the native OC and also coincides with the fact that I use Aftherburner for the fan curve.
I leave the api of RIG 3 that if it worked but badly and re-re-established the same
https://www.dropbox.com/s/ys5rztu2k480w5g/1.png?dl=0https://www.dropbox.com/s/95jpe8wusodbg8i/2.png?dl=0After 5 minutes later he has made another change and he has also failed, this is the catch belonging to RIG5 that also the api below is just that image. Look how is OFFLINE in AM, no data, but down in console is undermining or so it seems.
https://www.dropbox.com/s/reedfrb4r344jub/3.png?dl=0Api for RIG5. Belonging to the previous catch
Version: 6.5.2
API command: /api/v1/status
<?xml version="1.0" encoding="utf-16"?>
<StatusUpdate xmlns:xsd="
http://www.w3.org/2001/XMLSchema" xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance">
<MinerId>26</MinerId>
<Privileged>false</Privileged>
<ResponseTime>0</ResponseTime>
<CoinStatusList />
<ProcessStatus>
<Arguments> -i 21 --no-watchdog -a x16rt -o stratum+tcp://eu.blockmasters.co:3696 -u 3NhW4ZakVjn3FFgbzxG81MwSYzSBEhrKso.rig5 -p c=BTC --api-bind-http 0.0.0.0:4028</Arguments>
<Pid>5080</Pid>
<StartedUtc>2019-06-05T14:04:37.5845064Z</StartedUtc>
<InstanceId>1</InstanceId>
<MainWindowHandle>131784</MainWindowHandle>
</ProcessStatus>
<SystemStatus>
<OperatingSystem>Microsoft Windows 10 Pro 64-bit</OperatingSystem>
<MachineName>DESKTOP-I67T6BB</MachineName>
<IsAdminProcess>false</IsAdminProcess>
<IsService>false</IsService>
<WindowsUptimeSeconds>602</WindowsUptimeSeconds>
<IdleTimeMs>589531</IdleTimeMs>
<DotNetVersion>4.7.1</DotNetVersion>
<CpuStatusList>
<CpuStatus>
<Name>Intel Pentium G4400</Name>
<CoreCount>2</CoreCount>
<ThreadPerCore>1</ThreadPerCore>
<CoreClockList>
<SensorValues>
<Value>-1</Value>
<Max>-1</Max>
</SensorValues>
<SensorValues>
<Value>-1</Value>
<Max>-1</Max>
</SensorValues>
</CoreClockList>
<Temperature>
<Value>-1</Value>
<Max>-1</Max>
</Temperature>
<CoreTempList>
<SensorValues>
<Value>-1</Value>
<Max>-1</Max>
</SensorValues>
<SensorValues>
<Value>-1</Value>
<Max>-1</Max>
</SensorValues>
</CoreTempList>
<Load>
<Value>30.769229888916016</Value>
<Max>100</Max>
</Load>
<CoreLoadList>
<SensorValues>
<Value>27.218936920166016</Value>
<Max>100</Max>
</SensorValues>
<SensorValues>
<Value>34.319526672363281</Value>
<Max>100</Max>
</SensorValues>
</CoreLoadList>
<PackagePower>
<Value>-1</Value>
<Max>-1</Max>
</PackagePower>
<CorePower>
<Value>-1</Value>
<Max>-1</Max>
</CorePower>
</CpuStatus>
</CpuStatusList>
<GpuStatusList>
<GpuStatus>
<Name>GeForce GTX 1080 Ti</Name>
<SubvendorName>Gigabyte</SubvendorName>
<IsNvidia>true</IsNvidia>
<PciBusId>1</PciBusId>
<VendorDeviceId>0</VendorDeviceId>
<GlobalDeviceId>0</GlobalDeviceId>
<Power>
<Value>200.69324252820957</Value>
<Max>212</Max>
</Power>
<Voltage>
<Value>0.793</Value>
<Max>0.812</Max>
</Voltage>
<CoreClock>
<Value>1582</Value>
<Max>1620</Max>
</CoreClock>
<MemoryClock>
<Value>5200</Value>
<Max>5200</Max>
</MemoryClock>
<Temperature>
<Value>64</Value>
<Max>65</Max>
</Temperature>
<Load>
<Value>100</Value>
<Max>100</Max>
</Load>
<FanRpm>
<Value>3096</Value>
<Max>3149</Max>
</FanRpm>
<FanPercent>
<Value>81</Value>
<Max>82</Max>
</FanPercent>
</GpuStatus>
<GpuStatus>
<Name>GeForce GTX 1080 Ti</Name>
<SubvendorName>MSI</SubvendorName>
<IsNvidia>true</IsNvidia>
<PciBusId>3</PciBusId>
<VendorDeviceId>1</VendorDeviceId>
<GlobalDeviceId>1</GlobalDeviceId>
<Power>
<Value>225.74179722791007</Value>
<Max>235</Max>
</Power>
<Voltage>
<Value>0.825</Value>
<Max>0.843</Max>
</Voltage>
<CoreClock>
<Value>1708</Value>
<Max>1746</Max>
</CoreClock>
<MemoryClock>
<Value>5200</Value>
<Max>5200</Max>
</MemoryClock>
<Temperature>
<Value>73</Value>
<Max>73</Max>
</Temperature>
<Load>
<Value>99</Value>
<Max>100</Max>
</Load>
<FanRpm>
<Value>2396</Value>
<Max>2450</Max>
</FanRpm>
<FanPercent>
<Value>92</Value>
<Max>92</Max>
</FanPercent>
</GpuStatus>
<GpuStatus>
<Name>GeForce GTX 1080 Ti</Name>
<SubvendorName>Gigabyte</SubvendorName>
<IsNvidia>true</IsNvidia>
<PciBusId>6</PciBusId>
<VendorDeviceId>2</VendorDeviceId>
<GlobalDeviceId>2</GlobalDeviceId>
<Power>
<Value>198.74162292956834</Value>
<Max>210</Max>
</Power>
<Voltage>
<Value>0.812</Value>
<Max>0.825</Max>
</Voltage>
<CoreClock>
<Value>1556</Value>
<Max>1582</Max>
</CoreClock>
<MemoryClock>
<Value>5200</Value>
<Max>5200</Max>
</MemoryClock>
<Temperature>
<Value>71</Value>
<Max>71</Max>
</Temperature>
<Load>
<Value>100</Value>
<Max>100</Max>
</Load>
<FanRpm>
<Value>3440</Value>
<Max>3451</Max>
</FanRpm>
<FanPercent>
<Value>90</Value>
<Max>90</Max>
</FanPercent>
</GpuStatus>
<GpuStatus>
<Name>GeForce GTX 1080 Ti</Name>
<SubvendorName>NVIDIA</SubvendorName>
<IsNvidia>true</IsNvidia>
<PciBusId>7</PciBusId>
<VendorDeviceId>3</VendorDeviceId>
<GlobalDeviceId>3</GlobalDeviceId>
<Power>
<Value>199.47619501371184</Value>
<Max>216</Max>
</Power>
<Voltage>
<Value>0.781</Value>
<Max>0.825</Max>
</Voltage>
<CoreClock>
<Value>1607</Value>
<Max>1708</Max>
</CoreClock>
<MemoryClock>
<Value>5400</Value>
<Max>5400</Max>
</MemoryClock>
<Temperature>
<Value>74</Value>
<Max>74</Max>
</Temperature>
<Load>
<Value>100</Value>
<Max>100</Max>
</Load>
<FanRpm>
<Value>1570</Value>
<Max>1920</Max>
</FanRpm>
<FanPercent>
<Value>93</Value>
<Max>93</Max>
</FanPercent>
</GpuStatus>
<GpuStatus>
<Name>GeForce GTX 1080 Ti</Name>
<SubvendorName>MSI</SubvendorName>
<IsNvidia>true</IsNvidia>
<PciBusId>8</PciBusId>
<VendorDeviceId>4</VendorDeviceId>
<GlobalDeviceId>4</GlobalDeviceId>
<Power>
<Value>225.69252474635243</Value>
<Max>234</Max>
</Power>
<Voltage>
<Value>0.862</Value>
<Max>0.875</Max>
</Voltage>
<CoreClock>
<Value>1733</Value>
<Max>1759</Max>
</CoreClock>
<MemoryClock>
<Value>5200</Value>
<Max>5200</Max>
</MemoryClock>
<Temperature>
<Value>68</Value>
<Max>69</Max>
</Temperature>
<Load>
<Value>99</Value>
<Max>100</Max>
</Load>
<FanRpm>
<Value>2263</Value>
<Max>2304</Max>
</FanRpm>
<FanPercent>
<Value>86</Value>
<Max>87</Max>
</FanPercent>
</GpuStatus>
<GpuStatus>
<Name>GeForce GTX 1080 Ti</Name>
<SubvendorName>MSI</SubvendorName>
<IsNvidia>true</IsNvidia>
<PciBusId>9</PciBusId>
<VendorDeviceId>5</VendorDeviceId>
<GlobalDeviceId>5</GlobalDeviceId>
<Power>
<Value>222.89175980859869</Value>
<Max>238</Max>
</Power>
<Voltage>
<Value>0.85</Value>
<Max>0.862</Max>
</Voltage>
<CoreClock>
<Value>1733</Value>
<Max>1759</Max>
</CoreClock>
<MemoryClock>
<Value>5200</Value>
<Max>5200</Max>
</MemoryClock>
<Temperature>
<Value>64</Value>
<Max>64</Max>
</Temperature>
<Load>
<Value>99</Value>
<Max>100</Max>
</Load>
<FanRpm>
<Value>1899</Value>
<Max>2012</Max>
</FanRpm>
<FanPercent>
<Value>80</Value>
<Max>81</Max>
</FanPercent>
</GpuStatus>
</GpuStatusList>
<MemoryStatus>
<Used>2544947200</Used>
<Available>6011482112</Available>
</MemoryStatus>
<DriveStatusList>
<DriveStatus>
<Name>Local Disk (C:\)</Name>
<Available>12238794752</Available>
<Total>63376977920</Total>
</DriveStatus>
<DriveStatus>
<Name>cache (E:\)</Name>
<Available>437055524864</Available>
<Total>500105736192</Total>
</DriveStatus>
</DriveStatusList>
<NvidiaDriverVersion>419.67</NvidiaDriverVersion>
<MacAddress>309C23614AD8</MacAddress>
<IsLinux>false</IsLinux>
</SystemStatus>
<AccessDenied>false</AccessDenied>
</StatusUpdate>
<?xml version="1.0" encoding="utf-16"?>
<ManagedMiner xmlns:xsd="
http://www.w3.org/2001/XMLSchema" xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance">
<ID>26</ID>
<Type>Managed</Type>
<Description>Rig5</Description>
<Enabled>true</Enabled>
<EngineType>BtMiner</EngineType>
<EngineSubType>Disabled</EngineSubType>
<RemoteProxyHostId>0</RemoteProxyHostId>
<LastKnownAlgorithm>CuckaToo31</LastKnownAlgorithm>
<StatusQueryInterval>5</StatusQueryInterval>
<SortOrder>4</SortOrder>
<GroupID>0</GroupID>
<UserNotes />
<HighlightColor>None</HighlightColor>
<TagList />
<RunningWorker>
<PoolId>0</PoolId>
</RunningWorker>
<RunningWorkerList />
<UseWorkerSuffix>true</UseWorkerSuffix>
<WorkerSuffix>rig5</WorkerSuffix>
<SshPort>22</SshPort>
<UseCustomSshCredentials>false</UseCustomSshCredentials>
<ProfitProfileType>Single</ProfitProfileType>
<ProfitProfileId>17</ProfitProfileId>
<DeviceNameList />
<MacAddress>309C23614AD8</MacAddress>
<HasUpgradedCustomWorker>true</HasUpgradedCustomWorker>
<HostId>11</HostId>
<PoolType>Group</PoolType>
<PoolId>0</PoolId>
<DeviceProfileId>0</DeviceProfileId>
<EnvironmentVars>GPU_FORCE_64BIT_PTR 0
GPU_MAX_HEAP_SIZE 100
GPU_USE_SYNC_OBJECTS 1
GPU_MAX_ALLOC_PERCENT 100
GPU_SINGLE_ALLOC_PERCENT 100
</EnvironmentVars>
<CommandLineParams />
<UseBatchCommands>false</UseBatchCommands>
<BatchCommands />
<UseBatchCommandsBeforeStop>false</UseBatchCommandsBeforeStop>
<BatchCommandsBeforeStop />
<UseBatchCommandsAfterStop>true</UseBatchCommandsAfterStop>
<BatchCommandsAfterStop>"Coins/day: " + Math.Round(miningHelper.GetCoinsPerDay(), 4)</BatchCommandsAfterStop>
<ProfitCommandLineParams />
<ProfitUseCustomExecutable>false</ProfitUseCustomExecutable>
<ProfitCustomExecutable />
<ProfitCustomBatchCommands />
<SettingValues>
<StringPair>
<Key>api-listen</Key>
<Value>true</Value>
</StringPair>
<StringPair>
<Key>api-allow</Key>
<Value>W:127.0.0.1/32</Value>
</StringPair>
<StringPair>
<Key>api-network</Key>
<Value>false</Value>
</StringPair>
<StringPair>
<Key>expiry</Key>
<Value>120</Value>
</StringPair>
<StringPair>
<Key>log</Key>
<Value>5</Value>
</StringPair>
<StringPair>
<Key>queue</Key>
<Value>1</Value>
</StringPair>
<StringPair>
<Key>scan-time</Key>
<Value>60</Value>
</StringPair>
<StringPair>
<Key>temp-hysteresis</Key>
<Value>3</Value>
</StringPair>
</SettingValues>
<WindowMode>ConsoleFormat</WindowMode>
<ProcessPriority>Normal</ProcessPriority>
<ProcessAffinity />
<CleanBinFiles>true</CleanBinFiles>
<UseOverrideConfig>false</UseOverrideConfig>
<UseOverrideExcavatorConfig>false</UseOverrideExcavatorConfig>
<UseOverrideSrbMinerConfig>false</UseOverrideSrbMinerConfig>
<MinerConfigFileSettings />
<InstanceId>0</InstanceId>
<Autostart>true</Autostart>
<AutostartDelay>0</AutostartDelay>
<EngineSettings>
<AutoDownload>true</AutoDownload>
<Type>BtMiner</Type>
<Algorithm>CuckaToo31</Algorithm>
<SubType>Disabled</SubType>
<UseCustomExecutable>false</UseCustomExecutable>
<CustomExecutable />
</EngineSettings>
<StartedUtc>2019-06-04T14:50:24.7028997Z</StartedUtc>
<LimitedPoolPrioritizeList />
<LimitedVirtualPoolList />
<IsProfitMiner>true</IsProfitMiner>
<PoolProfitList>
<int>712</int>
<int>744</int>
<int>571</int>
<int>390</int>
<int>188</int>
<int>770</int>
<int>864</int>
<int>759</int>
<int>870</int>
<int>869</int>
</PoolProfitList>
<PredefinedPoolWorkerList>
<StringPair>
<Key>NiceHash</Key>
<Value>3AYwhcya4KktWxM8BQ47qTNhnXjMsNfpGy</Value>
</StringPair>
<StringPair>
<Key>BlockMasters</Key>
<Value>3NhW4ZakVjn3FFgbzxG81MwSYzSBEhrKso</Value>
</StringPair>
</PredefinedPoolWorkerList>
<CustomWorkerList />
<UseCustomPoolWorker>false</UseCustomPoolWorker>
<CustomPoolWorker />
<CustomPoolWallet />
<UseStartClockingProfile>true</UseStartClockingProfile>
<StartClockingProfile>175</StartClockingProfile>
<StartClockingProfileType>Single</StartClockingProfileType>
<UseStopClockingProfile>true</UseStopClockingProfile>
<StopClockingProfile>160</StopClockingProfile>
<StopClockingProfileType>Single</StopClockingProfileType>
<GpuSelectionType>All</GpuSelectionType>
<GpuSelectionList />
<IsGenericWithMonitoring>false</IsGenericWithMonitoring>
<BatchCommandsAsAdmin>true</BatchCommandsAsAdmin>
<UseGpuMapping>true</UseGpuMapping>
<GpuOrderList>
<int>0</int>
<int>1</int>
<int>2</int>
<int>3</int>
<int>4</int>
<int>5</int>
</GpuOrderList>
<RunAsAdmin>false</RunAsAdmin>
<IsTemplate>false</IsTemplate>
<HasTemplateWorkerSuffix>false</HasTemplateWorkerSuffix>
<HasTemplateCommandLine>true</HasTemplateCommandLine>
<HasTemplateClockingProfile>true</HasTemplateClockingProfile>
<ProfitUseStartClockingProfile>false</ProfitUseStartClockingProfile>
<ProfitStartClockingProfile>-1</ProfitStartClockingProfile>
<ProfitStartClockingProfileType>Single</ProfitStartClockingProfileType>
<ProfitUseStopClockingProfile>false</ProfitUseStopClockingProfile>
<ProfitStopClockingProfile>-1</ProfitStopClockingProfile>
<ProfitStopClockingProfileType>Single</ProfitStopClockingProfileType>
</ManagedMiner>
Show Posts
