another question, I have asked before but I cannot figure it out --
how do I set different profit profiles for my SHA256 miners? I have tried adding additional ones but whatever I set for one SHA256 miner it sets all of the SHA256 miners to the same one. This does not work for me as some are S9's (all of which do not use the same power) some are T15's and some are T17's --- all of them use different amounts of electricity and I would like to set it for each one separately.
First of all you need more than one profit profile. Please make sure you define for example a S9 and T15 profile in the Options dialog, Profit profile section, where you can add additional profiles. Each profile are configured independently, making it possible for you to specify one hashrate+power for the S9 profile and completely different numbers for the T15 profile. In the Properties for a miner, you can then select if it should use the S9 profile or the T15 profile as "Profit profile". |
|
|
|
Awesome miner could add support for device selection in TRM, as currently using the device selection doesnt add the correspondin '-d ' command to the miner. That may solve ur issues. As for the crashes, I have no clue, mine works fine. Which algo and clocks/timing are you running? Edit: @Patrik : would be possible to intergrate device selection and builtin watchdog( --watchdog_script=X.bat ) to TRM, the script could be almost same as the SRB one that u have intergrated in AM.  I will look into the device selection for TRM. For watchdog script - I can look into that as well - but do you have any example of what the script would do in the TRM scenario? For SrbMiner it's needed for terminating the SrbMiner process - in order to let Awesome Miner restart the mining process instead. |
|
|
|
latest version with a minor and a major problem 1. Awesomeminer shows me wrong GPU if i dont use all GPU“s for example my 8 card Vega Rig: TRM 0.5.0(also on 0.5.1) -d 0 -> it show a not active card but i see shares in "Progress" tab https://ibb.co/rZBzR4R-d 0,1,2,3 -> 2 cards are maped correctly but two cards in the list are not active https://ibb.co/bBchQvT2. if i use awesomeminer the rig dont find shares after some minutes - some minutes later the whole rig is not reachable anymore the same thing with SRBMiner i DDU drivers and reinstall - underclock every card and put mv to 950 (instead of 860-880mv the last weeks/month works perfectly) ---- only solution i found out today...not using awesome miner - means -> i start TRM with normal batch on the Rig and dont have any problems is there any way to disable something (or start debug log) in awesomeminer to verify that it could be a problem with the agent or api or whatever? I use TRM and AM. 1. use TRM with --bus_reorder and then map the GPU in AM in the ascending order of the PCI BUS ID. This worked for me, cause Default TRM uses Opencl order, --bus_reorder uses BusID order and AM uses the driver order by default. 2. Right click the miner and select view details -> process information. Verfiy that the command line param are correct. Right click the miner in AM and select diagnostics -> u should be able to see what went wrong. I can personally confirm that TRM and SRB works fine on my remote 6x Vega Rig for months. i have other rigs that also work...but like you can see at the screenshots (the links) that it dont matter to use or not use bus-reorder...Awesomeminer show me wrong GPU and after 10-30 minutes no shares and TRM and SRB stop working and i cant close or restart or reboot or anything...i have to power off and restart without using Awesomeminer (and using same parameters in batch, that i use in awesomeminer) it workes for hours now Hi, Please us the "Map to system monitoring" dialog to change the order of the cards using the Up and Down arrow. In your first screenshot I think you should put Device#7 on top for example. For the mining related issues and the command line - is the Diagnostics output (click the Diagnostics button in the toolbar) in Awesome Miner giving the exact same command line arguments as you have in your batch file? The Diagnostics will show exactly how Awesome Miner started the mining software and it will include both the command line arguments generated by Awesome Miner in combination with any manual commands you added. You could also try to launch the mining software via Awesome Miner - then close down Remote Agent when the mining has started. Do you still get the crashes? |
|
|
|
Yes, it will be included in the next release.
thank you Patrike also, I have not read all the back posts - have you managed a way to get ssh into the bitmain miners yet? or have they released a firmware allowing it? There are no solution to the SSH limitations yet and it looks like Bitmain are continuing to release new firmware with SSH disabled. I've been trying to get Bitmain to implement a setting to enable Privileged API access, but unfortunately no progress on that request either. A while ago I added the features to set Default Pools and Reboot by connecting to the Antminer web interface instead of SSH - but those where just workarounds for the fact that SSH wasn't available. |
|
|
|
does AM properly support the bw L21 miners? my AM detected the miners and shows that they are mining but the stats are all wrong - no temps, doesnt show pool info, the accepted shares are in the trillions with zero rejected and zero hw errors - it also does not show the hash rate.
This miner is supported, at least previous revisions of it. Even in the past this ASIC has always reported crazy number for the total number or share and total hashrate. What Awesome Miner do is to detect that it's a miner of this kind and then recalculate everything based on each individual ASIC device to get numbers that are accurate. It might be that more recent revisions of this ASIC is a bit different and Awesome Miner isn't able to detect it correctly. Could you please send me the API report (toolbar: Tools -> API Report) via mail or PM and I will see what changes they might have introduced and how to do another workaround. Thanks! pm sent with the API log Perfect - thanks for the log! I had to make a small adjustment to get Awesome Miner to detect this miner as a BW-L21. Once that detection was updated, it shows up fine. nice! so in a future update? Yes, it will be included in the next release. |
|
|
|
does AM properly support the bw L21 miners? my AM detected the miners and shows that they are mining but the stats are all wrong - no temps, doesnt show pool info, the accepted shares are in the trillions with zero rejected and zero hw errors - it also does not show the hash rate.
This miner is supported, at least previous revisions of it. Even in the past this ASIC has always reported crazy number for the total number or share and total hashrate. What Awesome Miner do is to detect that it's a miner of this kind and then recalculate everything based on each individual ASIC device to get numbers that are accurate. It might be that more recent revisions of this ASIC is a bit different and Awesome Miner isn't able to detect it correctly. Could you please send me the API report (toolbar: Tools -> API Report) via mail or PM and I will see what changes they might have introduced and how to do another workaround. Thanks! pm sent with the API log Perfect - thanks for the log! I had to make a small adjustment to get Awesome Miner to detect this miner as a BW-L21. Once that detection was updated, it shows up fine. |
|
|
|
Hey Patrike,
Is there a way to set the Global Electricity Price (per kWh) via HTTP API?
Thank you!
There are no feature to set the value via API today. You can set the price via the Rules, where you can use the Action called Set Property. You can for example use the rules to define different electricity prices depending on time or day. Rule actions can also be triggered via the API if needed. I do understand this doesn't give as much flexibility as having an API method for setting an exact price from an external application. Please let me know if you still prefer the API method and I will look into supporting it when possible. Thanks! Hey Patrike, If you could add it to your ever expanding "to-do list" that would be awesome! That would help me a lot! Here in Texas we have the option to go with a variable rate electricity plan that changes the price per kWh every 5 minutes. I'm currently monitoring the real-time price and have different rules and profiles setup in AM for my miners. For example, if the price per kWh goes crazy, up to say $1.00 /kWh, then my mine basically shuts down until the price drops. If the price goes negative (which happens often at night), the miners will overclock and go nuts! One more thought that might open up a whole new world of possibilities for AM: What if you gave us the option to pass a variable into AM via API that could be used elsewhere in the application? Maybe just a few empty variable slots (Var1, Var2, Var3, etc.) then those variables could be used as "Triggers" inside a rule. Just a thought. Thanks again! The API method for electricity price should be possible to include in the near future as it's only a matter of exposing a feature already available. Thanks for the suggestion about variables, that would make sense as well. Another concept available already today via the triggers are Miner Tags. You can set Tags on miners via the API and you can have trigger looking at certain tags. A short update about the API method for setting the global electricity price: POST http://mypc:17790/api/settings/electricity_price?value=0.075This feature is available in Awesome Miner 6.5.3 |
|
|
|
Awesome Miner version 6.5.3
Features
- Access to formatting of hashrate using MH/s and similar units via the Customize Progress Field feature
Thx again !! Currently using this: "Efficiency : " + Math.Round(status.KHashAvg * 1000 / Math.Max(miningHelper.GetPowerUsage(), 1), 2) + " H/W" Couldnt find the documentation for the endpoint for the formating if its mininghelper or status object. Would like to have a heads up on how it works. Thanks for all nice feedback. I've also updated the documentation page and you will find the solution at the bottom of this page: https://support.awesomeminer.com/support/solutions/articles/35000086023-customize-progress-field"Efficiency: " + miningHelper.FormatValue(Math.Round(status.KHashAvg * 1000 / Math.Max(miningHelper.GetPowerUsage(), 1), 2)) + " H/W" |
|
|
|
|
Awesome Miner version 6.5.3
GPU mining
- Added setting to specify if Ctrl+C should be used to stop a mining process, configurable in the Options dialog, Mining Settings section
- Show GPU vendor name for nVidia devices when running Remote Agent on Linux
Features
- Access to formatting of hashrate using MH/s and similar units via the Customize Progress Field feature
User interface
- Added additional coin icons
- Display number of miners in the Mining History dialog, Mining Performance section
Rules
- Increased the maximum delay allowed to be configured for SSH actions
- Time trigger to display name of day in the trigger summary if only a single day is selected
API
- Added API to set Electricity Price via API
Mining software
- TeamRedMiner 0.5
- WildRig Miner 0.17.4
- CpuMiner-Opt 3.9.2.3
|
|
|
|
https://www.dropbox.com/s/k05h0exde8qljrx/4.png?dl=0and again, and all day like that. That miner has stayed offline, has reboot and it works. But I already said that I reboot too many times a day, every rig more than 20 or 30 times a day, practically every change. Normally they are the Rig3 and 5 that are 1080TI, but also it happens with less frequency in other rigs of RTX, 1070 etc ... Or the native OC does not go well with administration, the aftherburner influences, I do not know if the others that happen to him have the same aftherburner, or there some different fault, but that makes this has become unstable. And having seen that the same thing happens to other people, I insist on the problem. In addition to my previous response about troubleshooting - I also see that you list quite a number of potential problematic areas. After you made the troubleshooting I suggested earlier - please also consider to try to eliminate all these factors that could have an impact on the overall system stability. What happens if you modify you overclocking to only be a single percent of overclocking (so the overclocking code is used, but doesn't do much)? What happens if you remove all clocking for one of the miners? What happens if you close down Afterburner? The OC of winter I have reduced it by 20% for summer, and I have even tried very low OC to see if it happened and if it happens, that was the first thing I did. What I have not tried has been to remove the Aftherburner until there is a global FAN solution. I can not be defining a curve in each profile when I have 100 or more, and the heat is heat whatever the protocol. I will try to remove the Aftherburner from 1 machine, the most prone and force several changes. At first you said that it would not affect but it could be. I ask for a global Fan curve for each rig, regardless of the protocol. That would help me remove Aftherburner. Perfect that you lowered the OC for the summer - that makes sense. Over the years I've seen the same trend every time it's May or June - I get reports about mining software crashing more frequently with clocking levels that worked fine a few months earlier. |
|
|
|
https://www.dropbox.com/s/zynzi5nd4ywsk9s/5.png?dl=0Another sample of bugs from the native OC. If we see the capture, RIG3 would be 6x1080ti, gives the hash of 6, gives the consumption of 6 cards, but then the Profit is 1 card, also only gives the temperature of 1 card. I have created a rule that counts the cards in case of missing only 1 reboot. But the curious thing that marks me the hash and consumption of 6, temperature and profit of only 1. Something is not right. He has been like this all night and has not done auto switch because he marked a hash he was not getting. But of course the Switch does it for the hash profile of the currency not for the hash obtained, otherwise X16r would skip all the time. AM could bring a predefined rule to detect dropped devices. It is not shown that AM does not get the data right, it can not be working only 1 card and the hash of 6 and the consumption of 6 remain. So I can not make a rule like "if it consumes less than X trigger" This is more related to what GPU's are being reported as active from the mining software rather than being OC related. When you run into this issue where Awesome Miner only includes one temperature reading - the following would be interesting to know: 1) On the GPU tab for this selected miner, how many GPU's are the mining software reporting. Only one, because the other failed in some way? 2) Next time the mining software report something that looks strange, please generate an API report and sent it to me via PM or mail. I can then review what the mining software is reporting. 3) Did the mining software console window indicating that it was only mining on a single GPU or all 6 GPU's where mining perfectly fine? It's possible that there is some case where GPU's are being partially reported correctly from the mining software and the display in Awesome Miner gives a temperature and power summary that looks strange - but we need the information above in order to really tell if that's the case. |
|
|
|
Hi.
I had another thought along these lines. would it be possible to add support for turning on these wifi activated power switches to turn an ASIC miner on after sun up(for solar users), or during a cheap power period(like this user has) and then off again as needed?
i guess this could be done with a C# script... so to set the asic miner as enabled, then turn the power switch on.
anyone done this?
Hi, As I don't have too much experience in this area I will only to be able to give a general answer form an Awesome Miner point of view, but hopefully someone else with more experience in this field can give additional details. There are some power switches that can be controlled via HTTP requests and there are some that requires an command line application to be executed that will send the command to the power plug/switch. I do know that there are a number of users that uses Awesome Miner to interact with different kinds of smart plugs/switches. From an Awesome Miner point of view you can define your own rules (Options dialog, Rules section) and add them to the Action toolbar button, where you can either have actions to send HTTP requests (Webhook action) or to run an executable. You can also use the rules to schedule these operations to run at a specific time if needed. |
|
|
|
New TRM - TeamRedMiner Version 0.5
Thanks for your assistance in collecting all the new/missing algorithm names. |
|
|
|
does AM properly support the bw L21 miners? my AM detected the miners and shows that they are mining but the stats are all wrong - no temps, doesnt show pool info, the accepted shares are in the trillions with zero rejected and zero hw errors - it also does not show the hash rate.
This miner is supported, at least previous revisions of it. Even in the past this ASIC has always reported crazy number for the total number or share and total hashrate. What Awesome Miner do is to detect that it's a miner of this kind and then recalculate everything based on each individual ASIC device to get numbers that are accurate. It might be that more recent revisions of this ASIC is a bit different and Awesome Miner isn't able to detect it correctly. Could you please send me the API report (toolbar: Tools -> API Report) via mail or PM and I will see what changes they might have introduced and how to do another workaround. Thanks! |
|
|
|
https://www.dropbox.com/s/k05h0exde8qljrx/4.png?dl=0and again, and all day like that. That miner has stayed offline, has reboot and it works. But I already said that I reboot too many times a day, every rig more than 20 or 30 times a day, practically every change. Normally they are the Rig3 and 5 that are 1080TI, but also it happens with less frequency in other rigs of RTX, 1070 etc ... Or the native OC does not go well with administration, the aftherburner influences, I do not know if the others that happen to him have the same aftherburner, or there some different fault, but that makes this has become unstable. And having seen that the same thing happens to other people, I insist on the problem. In addition to my previous response about troubleshooting - I also see that you list quite a number of potential problematic areas. After you made the troubleshooting I suggested earlier - please also consider to try to eliminate all these factors that could have an impact on the overall system stability. What happens if you modify you overclocking to only be a single percent of overclocking (so the overclocking code is used, but doesn't do much)? What happens if you remove all clocking for one of the miners? What happens if you close down Afterburner? |
|
|
|
Version: 6.5.2
API command: /api/v1/status
I've only had a quick look so far, but the interesting part is the first few lines of the API report. It indicates the API command Awesome Miner sends to the mining software and the line after is the response. In this case Awesome Miner sends a request to: http://IpAddressOfTheMiner:4028/api/v1/statusFor this mining software the API is based on HTTP. There are other software where non-HTTP connections are used. The next few lines in the report are empty - indicating that the mining software didn't respond to this request. One you get to the lines further below (starting with "<?xml version") it's just Awesome Miner that log internal information. There are two things you can do to find out why Awesome Miner didn't get any API response from the miner: 1) As this specific mining software happen to run HTTP, you could try to open a web browser and navigate to: http://IpAddressOfTheMiner:4028/api/v1/statusReplace with the correct IP address of the miner. This suggestion will however not be applicable for all mining software - which is why the point below can be of interest. 2) You could add an External Miner in Awesome Miner, where you select the mining software you want to connect to and specify the "Remote Host" like: 192.168.0.123:4028 Use the IP address of the Remote Agent computer where the mining is running. The port may not be 4028, please right click on the Managed Miner and select View Details to find the mining software API port number in the command line. If the External Miner shows up as Disconnected, it's a sign that it's not possible to get any response from the mining software. |
|
|
|
Another PAtrike suggestion. In the OC theme, it is becoming more complete, although I use the Aftherburner fan system.
The OC that is saved is for the whole rig, not card to card. I have some multi-brand rigs and also all the same cards. But it happens that there is always 1 that heats more than others with difference and just that card is the one that marks me the maximums of OC that I can do in that machine.
If you could save OC that you keep the OC for each card separately, I could to that card lower the CORE or Power of source disintinta to the others. That way I could take more advantage of the RIG and above all avoid being stopped by reaching the limit marked by my 84 degrees that only 1 card does, the others may be at 70 degrees or less.
The menu we have it, where we operate on each card separately in the new quick menu, now the ideal would be to save that configuration with the data of each card by independent and many problems solved. I'm lazy to put captures but right now I have a rig with
59 62 78 65 63 66
Obviously the card at 78 degrees is limiting me, if I could make that hot card work less, at least I could be calmer if I did not reach the temperature limit, which almost never arrived, but there is still a lot of summer left. In even the rest of the cards could be slightly raised while under power at 78 degrees, it would have stability and more hash.
I repeat about the OFFLINE in the miners and reboot, almost always the culprit is Trex miner, but I have it with a low intensity and still keeps doing it, every change of currency that implies Trex and be the 1080ti, stays in OFFLINE although is working, after a while the rule, reboot rig and it works, I can restart the rig 20-40 times a day, that is not ideal for the machine or to take advantage of all the time in mining. and this is only happening to me since I activated native OC with administrator, which I need because I use the Limit voltage function to control the power to the cards and not reach the point of heat shutdown, at the same time I reduce TDP and core , but many times there are cards in the same rig that some consume 790 and other 900 mv, with this I put a general limit and I avoid a lot of unnecessary heat.
Right now the only way to apply different fan or clocking settings per GPU is to make use of the "Clocking profile groups" in the Options dialog, GPU Clocking Profiles section. For a Clocking Group you can define that you want one Clocking Profile for GPU 0,1,3,4,5 and another Clocking Profile for GPU 2. I can agree that it would be nice to have an easier way to setup this (like you refer to as 'new quick menu'), to make this setup process easier. This can be a future improvement. I also have a question to you about the Fan curve concept, as I've received similar feedback from other users. In recent version of Awesome Miner you can define a Fan/Temperature curve for AMD GPU's, as AMD provides this feature in their recent drivers. For nVidia there are no similar concept and instead it has to become an application feature where for example Awesome Miner could look as the temperature all the time and individually adjust the fan of each GPU based on this. If Awesome Miner would have a global Fan/Temperature concept similar to MSI Afterburner that could work on both AMD and nVidia - would that be useful? Or is there a need for more flexibility than a global setting? |
|
|
|
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. |
|
|
|
Awesome Miner version 6.5.2
Features
- Access to miner power usage via the Customize Progress Field feature
Thank You !!  Any tips on how to make it run the units shown in the performance column ? eg: in Cryptonight KH is good, but on Raven it would be nice if it switches to MH based on the units(KH or MH) reported by the performance column. Feature Request : The Power usage mode could be refactored to the Profit Profiles. Eg: AMD - Power detection is poor, but based on wall power monitor the power is constant - So need "Static Mode" Nvidia - Power detection is accurate, So need "Actual GPU Mode(Fallback to Static)" As of now, the mode is globally fixed, would like to have the flexibility as an override ~~ I think it would be easier if Awesome Miner would do the hash unit formatting. I will look into exposing a helper method for that. Thanks for the additional suggestions as well. It's correct that AMD power usage isn't very accurate, where the AMD drivers reports lower power usage than what you measure from the well. To some extent you can compensate by specifying a percent increase for AMD in Options -> GPU Settings. |
|
|
|
Hi Patrike, I've been away for a couple of weeks. Awesome Miner happily churned away without any issues. Love the program! Just updated everything to the latest versions and ran into a small issue when benchmarking. It seems that the long term benchmarks (10 minutes, 20 minutes, 1 hour, etc) are quitting after a few minutes, similar to the "Fast" or "Precise" benchmarks. The following is (I think) the relevant log entries: 2019-06-02 9:39:21 AM.202 [001] [S]Running benchmark for miner: [ManagedMiner#5 - Desktop]
2019-06-02 9:39:21 AM.206 [057] [S]PoolServiceManager.GetAsPools, pools: 339
2019-06-02 9:39:21 AM.206 [057] [S]PoolServiceManager.GetAsPools, disabled for profit switching: nicehash.com:3334, SHA256
2019-06-02 9:39:21 AM.206 [057] [S]PoolServiceManager.GetAllEnabledPools, pools: 35
2019-06-02 9:39:21 AM.206 [057] [S]PoolServiceManager.GetAllEnabledPools, SinglePoolCM predefined count: 342
2019-06-02 9:39:21 AM.221 [057] [S]Prepare benchmarking X16r. Engine Type: CcCryptoDredgeEngine, Auto Download: True, EnginePath: , Subtype: Disabled, CustomExecutable:
2019-06-02 9:39:21 AM.226 [057] [S][ManagedMiner#5 - Desktop] Run Miner Command: Benchmark
2019-06-02 9:39:21 AM.226 [037] [S]Command request: Benchmark
2019-06-02 9:39:21 AM.226 [007] [S][ManagedMiner#5 - Desktop] Execute command: Benchmark
2019-06-02 9:39:21 AM.226 [059] [S]Benchmark: Starting Engine Type: CcCryptoDredgeEngine, Auto Download: True, EnginePath: , Subtype: Disabled, CustomExecutable: , Timeout: 600
2019-06-02 9:39:21 AM.226 [059] [S][ManagedMiner#5 - Desktop] Starting Mining Software
2019-06-02 9:39:21 AM.226 [059] [S][ManagedMiner#5 - Desktop] Setting up Miner Engine. Instance: 1
2019-06-02 9:39:21 AM.226 [059] [S][ManagedMiner#5 - Desktop] Engine Type: CcCryptoDredgeEngine, Auto Download: True, EnginePath: , Subtype: Disabled, CustomExecutable:
2019-06-02 9:39:21 AM.226 [059] [S]EngineSetup: CcCryptoDredgeEngine
2019-06-02 9:39:21 AM.233 [059] [S][ManagedMiner#5 - Desktop] Executing batch commands as admin: "C:\Program Files (x86)\MSI Afterburner\MSIAfterburner.exe" -Profile1
2019-06-02 9:39:21 AM.234 [059] [S]ChannelFactoryProvider: Create Channel Factory: IntelliBreeze.Maintenance.Service.Contracts.ServiceContracts.IMaintenanceService
2019-06-02 9:39:21 AM.248 [059] [S]Execute task successfully registered: C:\Users\jbwin\AppData\Local\AwesomeMiner\cryptodredge_0.19.1_cuda_10.0_windows_1\CryptoDredge_0.19.1\awesome.bat
2019-06-02 9:39:21 AM.305 [059] [S]Executed task successfully: C:\Users\jbwin\AppData\Local\AwesomeMiner\cryptodredge_0.19.1_cuda_10.0_windows_1\CryptoDredge_0.19.1\awesome.bat
2019-06-02 9:39:22 AM.324 [059] [S][ManagedMiner#5 - Desktop] Sucessfully executed batch commands
2019-06-02 9:39:22 AM.324 [059] [S][ManagedMiner#5 - Desktop] : GetStaticSortedPools, Enginetype: CcCryptoDredgeEngine, Algorithms: Allium, Argon2dDyn, Argon2d250, Argon2d4096, Bcd, Bitcore, Blake2s, CryptoNightLiteV7, CryptoNightFast2, CryptoNightGpu, CryptoNightHaven, CryptoNightHeavy, CryptoNightV8, CryptoNightSaber, CryptoNightStelliteV4, CryptoNightTurtle, CuckaRoo29, Cuckoo, Hmq1725, Lyra2REv3, Lyra2z, Lyra2zz, Mtp, NeoScrypt, Phi2, Skunkhash, Tribus, X16r, X16rt, X16s, X17, X21s, X22i
2019-06-02 9:39:22 AM.324 [059] [S][ManagedMiner#5 - Desktop] : Adding pool: stratum+tcp://x16r.usa.nicehash.com:3366
2019-06-02 9:39:22 AM.341 [059] [S]Device nVidia, GlobalId: 0, VendorId:0, PciBusId: 1, Name: GeForce RTX 2080 Ti
2019-06-02 9:39:22 AM.341 [059] [S]Select devices 0
2019-06-02 9:39:22 AM.341 [059] [S]Device selection ordering: Standard Device ID
2019-06-02 9:39:22 AM.341 [059] [S]Device selection input: Nvidia, ID type: VendorId, GlobalID List:
2019-06-02 9:39:22 AM.341 [059] [S]Device selection, VendorID List: 0
2019-06-02 9:39:22 AM.343 [059] [S]ChannelFactoryProvider: Create Channel Factory: IntelliBreeze.Maintenance.Service.Contracts.ServiceContracts.ISecurityService
2019-06-02 9:39:22 AM.379 [059] [S]Added rule for: C:\Users\jbwin\AppData\Local\AwesomeMiner\cryptodredge_0.19.1_cuda_10.0_windows_1\CryptoDredge_0.19.1\CryptoDredge.exe
2019-06-02 9:39:22 AM.379 [059] [S][ManagedMiner#5 - Desktop] Properties: (WindowMode: NoWindow, EngineType: CcCryptoDredgeEngine, IsProfitMiner: True)
2019-06-02 9:39:22 AM.379 [059] [S][ManagedMiner#5 - Desktop] ====================================================================================================
2019-06-02 9:39:22 AM.379 [059] [S][ManagedMiner#5 - Desktop] C:\Users\jbwin\AppData\Local\AwesomeMiner\cryptodredge_0.19.1_cuda_10.0_windows_1\CryptoDredge_0.19.1\CryptoDredge.exe -R 5 -r 2 --timeout 65 -p c=BTC,d=10 -a x16r -i 7 -d 0 -o stratum+tcp://x16r.usa.nicehash.com:3366 -u 175TRmpBHbmnjhSkAydoDiqkdGnfGpMXpU --no-watchdog -b 0.0.0.0:4028
2019-06-02 9:39:22 AM.379 [059] [S][ManagedMiner#5 - Desktop] Configured command line:
-R 5 -r 2 --timeout 65 -p c=BTC,d=10
2019-06-02 9:39:22 AM.379 [059] [S][ManagedMiner#5 - Desktop] ====================================================================================================
2019-06-02 9:39:22 AM.692 [059] [S]Saving configuration to: C:\ProgramData\AwesomeMinerService\ServiceDataIntegrated.xml.tmp
2019-06-02 9:39:22 AM.704 [059] [S]--> C:\ProgramData\AwesomeMinerService\ServiceDataIntegrated.xml
2019-06-02 9:39:22 AM.707 [059] [S][ManagedMiner#5 - Desktop] Mining Engine Process started, PID: 13208
2019-06-02 9:42:05 AM.707 [059] [E]System.NullReferenceException: Object reference not set to an instance of an object.
2019-06-02 9:42:05 AM.707 [059] [E] at #=zemuLnLwVEmJAeDku1zK6N4B_dmsCMAzdJ2Q87w8le3sN.#=zYIfDucFn62epe5yedA==()
2019-06-02 9:42:05 AM.707 [059] [S]Benchmark: Stopping miner process ...
2019-06-02 9:42:05 AM.707 [059] [S][ManagedMiner#5 - Desktop] Prepare stopping Mining Software
2019-06-02 9:42:05 AM.707 [059] [S][ManagedMiner#5 - Desktop] Stopping Mining Software
2019-06-02 9:42:05 AM.707 [059] [S] Closing process: 13208
2019-06-02 9:42:06 AM.209 [059] [S] Process closed
2019-06-02 9:42:06 AM.209 [059] [S]Benchmark: Completed
Thanks, ...jim EDIT: It also occurs on the "Fast" and "Precise" benchmarks, sometimes. Depends on how quickly the error occurs. it happens to me exactly the same as this user I implemented a change for this in version 6.5.2. Can you please verify if you still can reproduce the same problem with Remote Agent is running version 6.5.2? |
|
|
|
|
Show Posts
