Search content
Sort by
Showing 20 of 33 results by PandaPanda!
2 PandaPanda:
It's some rare problem. Though hardware watchdog would help in this situation.
It's some rare problem. Though hardware watchdog would help in this situation.
I have 16 rigs running the same setup - Biostar H81S2 mainboard with 5 x Sapphire Nitro RX470 and 8GB ram. Pretty normal miner's setup. Not sure why i'd be having issues. Is there a way to fix this? Why is it that Windows can do a reboot when hash rate drops and everything works perfectly again? This is the only issue that's stopping me from moving my farm to HiveOS.
It would also be nice if you could add email alerts if hash rate drops or miner goes offline, as well as adding GPU mining for XMR-Stak so we can mine monero with our GPUs. Thanks again.
I am having issues with HiveOS. Everything was working perfectly for almost 2 days and then claymore watchdog reported that one of the GPUs died. HiveOS then attempts to restart the miner, and then the hash rate on all my GPUs dropped from 28.5mh to 4mh each. HiveOS then reboots the system but after rebooting, all the GPUs are still mining at 4mh. The only way to solve this is by switching the power off and then back on again. When this rig was running windows, a simple system reboot would fix any hash rate issues. Is there a way to solve this? I really like HiveOS and want to migrate my farm to it, but if it can't fix a simple situation like this, then I will have to look elsewhere.
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v9.3 (Windows/Linux)
@Claymore - your warning system on ethmon is not working properly. When the batch file runs, it always returns "1" for %2 variable, regardless of whether the rig is overheating, low hash, or offline - it will always return "1". Please fix this! Thanks!
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v9.3 (Windows/Linux)
I have one rig in my farm which keeps crashing every 3 hours or so.
Usually I can open up the log file and find out which particular GPU is causing issues, and rectify the problem without much headache. But this time, i'm getting this message...
13:18:08:445 5ac buf: {"id":4,"jsonrpc":"2.0","result":true}
13:18:08:445 5ac parse packet: 38
13:18:08:445 5ac ETH: Share accepted (47 ms)!
13:18:08:445 5ac new buf size: 0
13:18:09:865 eb8 GPU0 t=70C fan=82%, GPU1 t=67C fan=78%, GPU2 t=65C fan=81%, GPU3 t=65C fan=74%, GPU4 t=71C fan=79%
13:18:09:865 eb8 em hbt: 0, fm hbt: 16,
13:18:09:865 eb8 watchdog - thread 0, hb time 250
13:18:09:865 eb8 watchdog - thread 1, hb time 32
13:18:09:865 eb8 watchdog - thread 2, hb time 32
13:18:09:865 eb8 watchdog - thread 3, hb time 19906
13:18:09:865 eb8 watchdog - thread 4, hb time 234
13:18:09:865 eb8 watchdog - thread 5, hb time 32
13:18:09:865 eb8 watchdog - thread 6, hb time 297
13:18:09:865 eb8 watchdog - thread 7, hb time 94
13:18:09:865 eb8 watchdog - thread 8, hb time 125
13:18:09:865 eb8 watchdog - thread 9, hb time 328
13:18:09:865 eb8 WATCHDOG: GPU error, you need to restart miner
13:18:09:865 eb8 Rebooting
Its not specifically telling me which GPU is having issues, although i'm assuming its whatever was working on "thread 3" - how can I find out which GPU is working on thread 3? Claymore, please help! This is driving me nuts. This rig usually hangs after the "Rebooting" message.
Usually I can open up the log file and find out which particular GPU is causing issues, and rectify the problem without much headache. But this time, i'm getting this message...
13:18:08:445 5ac buf: {"id":4,"jsonrpc":"2.0","result":true}
13:18:08:445 5ac parse packet: 38
13:18:08:445 5ac ETH: Share accepted (47 ms)!
13:18:08:445 5ac new buf size: 0
13:18:09:865 eb8 GPU0 t=70C fan=82%, GPU1 t=67C fan=78%, GPU2 t=65C fan=81%, GPU3 t=65C fan=74%, GPU4 t=71C fan=79%
13:18:09:865 eb8 em hbt: 0, fm hbt: 16,
13:18:09:865 eb8 watchdog - thread 0, hb time 250
13:18:09:865 eb8 watchdog - thread 1, hb time 32
13:18:09:865 eb8 watchdog - thread 2, hb time 32
13:18:09:865 eb8 watchdog - thread 3, hb time 19906
13:18:09:865 eb8 watchdog - thread 4, hb time 234
13:18:09:865 eb8 watchdog - thread 5, hb time 32
13:18:09:865 eb8 watchdog - thread 6, hb time 297
13:18:09:865 eb8 watchdog - thread 7, hb time 94
13:18:09:865 eb8 watchdog - thread 8, hb time 125
13:18:09:865 eb8 watchdog - thread 9, hb time 328
13:18:09:865 eb8 WATCHDOG: GPU error, you need to restart miner
13:18:09:865 eb8 Rebooting
Its not specifically telling me which GPU is having issues, although i'm assuming its whatever was working on "thread 3" - how can I find out which GPU is working on thread 3? Claymore, please help! This is driving me nuts. This rig usually hangs after the "Rebooting" message.
2 threads per GPU in their order, "time 19906"
So thread 3 is GPU1?
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v9.3 (Windows/Linux)
I have one rig in my farm which keeps crashing every 3 hours or so.
Usually I can open up the log file and find out which particular GPU is causing issues, and rectify the problem without much headache. But this time, i'm getting this message...
13:18:08:445 5ac buf: {"id":4,"jsonrpc":"2.0","result":true}
13:18:08:445 5ac parse packet: 38
13:18:08:445 5ac ETH: Share accepted (47 ms)!
13:18:08:445 5ac new buf size: 0
13:18:09:865 eb8 GPU0 t=70C fan=82%, GPU1 t=67C fan=78%, GPU2 t=65C fan=81%, GPU3 t=65C fan=74%, GPU4 t=71C fan=79%
13:18:09:865 eb8 em hbt: 0, fm hbt: 16,
13:18:09:865 eb8 watchdog - thread 0, hb time 250
13:18:09:865 eb8 watchdog - thread 1, hb time 32
13:18:09:865 eb8 watchdog - thread 2, hb time 32
13:18:09:865 eb8 watchdog - thread 3, hb time 19906
13:18:09:865 eb8 watchdog - thread 4, hb time 234
13:18:09:865 eb8 watchdog - thread 5, hb time 32
13:18:09:865 eb8 watchdog - thread 6, hb time 297
13:18:09:865 eb8 watchdog - thread 7, hb time 94
13:18:09:865 eb8 watchdog - thread 8, hb time 125
13:18:09:865 eb8 watchdog - thread 9, hb time 328
13:18:09:865 eb8 WATCHDOG: GPU error, you need to restart miner
13:18:09:865 eb8 Rebooting
Its not specifically telling me which GPU is having issues, although i'm assuming its whatever was working on "thread 3" - how can I find out which GPU is working on thread 3? Claymore, please help! This is driving me nuts. This rig usually hangs after the "Rebooting" message.
Usually I can open up the log file and find out which particular GPU is causing issues, and rectify the problem without much headache. But this time, i'm getting this message...
13:18:08:445 5ac buf: {"id":4,"jsonrpc":"2.0","result":true}
13:18:08:445 5ac parse packet: 38
13:18:08:445 5ac ETH: Share accepted (47 ms)!
13:18:08:445 5ac new buf size: 0
13:18:09:865 eb8 GPU0 t=70C fan=82%, GPU1 t=67C fan=78%, GPU2 t=65C fan=81%, GPU3 t=65C fan=74%, GPU4 t=71C fan=79%
13:18:09:865 eb8 em hbt: 0, fm hbt: 16,
13:18:09:865 eb8 watchdog - thread 0, hb time 250
13:18:09:865 eb8 watchdog - thread 1, hb time 32
13:18:09:865 eb8 watchdog - thread 2, hb time 32
13:18:09:865 eb8 watchdog - thread 3, hb time 19906
13:18:09:865 eb8 watchdog - thread 4, hb time 234
13:18:09:865 eb8 watchdog - thread 5, hb time 32
13:18:09:865 eb8 watchdog - thread 6, hb time 297
13:18:09:865 eb8 watchdog - thread 7, hb time 94
13:18:09:865 eb8 watchdog - thread 8, hb time 125
13:18:09:865 eb8 watchdog - thread 9, hb time 328
13:18:09:865 eb8 WATCHDOG: GPU error, you need to restart miner
13:18:09:865 eb8 Rebooting
Its not specifically telling me which GPU is having issues, although i'm assuming its whatever was working on "thread 3" - how can I find out which GPU is working on thread 3? Claymore, please help! This is driving me nuts. This rig usually hangs after the "Rebooting" message.
I'm currently testing a 1060 3GB rig (Samsung memory) and with a stable overclock (running over 24hours now without any crashes), pulling in 300-315sol/s per card on ZCash with EWBF's miner. Less power, less heat, and considerably faster than an equally priced RX470 4GB. Of course, ETH mining only gets around 24-25MH compared to 30MH on a 470, but if its all about the power consumption and keeping the heat down, then you can't go wrong with a 1060. I'm actually going to purchase another couple rigs with these cards. They are super easy to configure and just work. No need for BIOS mods or anything tricky.
If you compare pricing between 1060/1070/1080, you will notice that you get the best $/hash with a 1060. 1070 is more than double the price of a 1060, yet the hash rate is only around 1.5x.
If you compare pricing between 1060/1070/1080, you will notice that you get the best $/hash with a 1060. 1070 is more than double the price of a 1060, yet the hash rate is only around 1.5x.
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v9.1 (Windows/Linux)
@Claymore, I have a small feature request with ethmon. I'm sure many others here would like this option too if possible.
"Execute .BAT file if miner has problems"
Can we separate this into 3 separate batch files?
One that runs if there are GPU temp issues
One that runs if there are hash rate issues
One that runs if the rig goes offline
If you could implement this, I would be grateful
Thanks again for an awesome miner!
"Execute .BAT file if miner has problems"
Can we separate this into 3 separate batch files?
One that runs if there are GPU temp issues
One that runs if there are hash rate issues
One that runs if the rig goes offline
If you could implement this, I would be grateful
Thanks again for an awesome miner!
It can be achieved with additional parameter to BAT file that EthMan calls.
Ok I will add it.
If this is already achievable, can you show us a batch file example on how to separate the 3 different error events?
I have already created a batch file which sends me an email and alerts me of which rig in my farm is having issues. I have been using this method for a few months now, as its quicker and allows for less downtime to have ethmon alert me than waiting almost an hour for the pool to alert me. However, it would be nice to know the specific problem the rig is having (whether it be overheat, hash rate, or offline). Thanks again
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v9.1 (Windows/Linux)
@Claymore, I have a small feature request with ethmon. I'm sure many others here would like this option too if possible.
"Execute .BAT file if miner has problems"
Can we separate this into 3 separate batch files?
One that runs if there are GPU temp issues
One that runs if there are hash rate issues
One that runs if the rig goes offline
If you could implement this, I would be grateful
Thanks again for an awesome miner!
"Execute .BAT file if miner has problems"
Can we separate this into 3 separate batch files?
One that runs if there are GPU temp issues
One that runs if there are hash rate issues
One that runs if the rig goes offline
If you could implement this, I would be grateful
Thanks again for an awesome miner!
I'm wondering as well as eastshore has PinIdea miners for sale when their miners are out of stock on the actual PinIdea website.
Eastshore probably bought a huge amount of stock from PinIdea, and has leftover stock to sell. Just because the main manufacturer ran out, doesn't mean another retailer would have had to run out too.
Someone else also asked about this website yesterday. I ordered a couple gridseed gblade asics from eastshore's aliexpress.com storefront a few years back. They delivered fast and were helpful throughout the process. Thumbs up from me.
I once tried 6 x 7990s, but it wouldn't work with more than 8 GPUs in Windows, so i gave up trying
I'm surprised you can still mine with your 7990s.. all of mine died after 1 year of mining. 7990s are terrible for mining unless you have them water-cooled.
I'm surprised you can still mine with your 7990s.. all of mine died after 1 year of mining. 7990s are terrible for mining unless you have them water-cooled.
My farm is a mess with v12.0 - i'm moving back to v11.1 until claymore sorts out all the issues with crashing GPUs etc.
The strange part is that it seems v12.0 actually messed up my Fury cards somehow so now when I revert to 11.x they still crash. Could be some kind of odd coincidence but it seems unlikely.
You know, its funny you say that - i've just noticed the stability I had when I was originally using 11.1 has now gone after downgrading from 12.0 back to 11.1. This is strange.. However, the instability seems to be coming from only my 2xx/3xx cards.. RX4xx series cards seem to be running okay.
Question: I have a few Bios modded Rx 470/480 that I'm trying to get running under Windows 10 ver. 1607. On install they show as 'problem detected, code 43' in device manager. Do I have to use modded driver files and disable signature check etc. to solve the issue? I tried 15.12 and 16.3 and I get the issue with both.
Anyone of you scholars that know?
Anyone of you scholars that know?
Use 16.11.5 - will work perfectly. 16.12 and up won't work with modded BIOSes as far as i know.
Re: [ANN][POOL] Mining Pool Hub - Multipool. Multialgo, Auto Exchange to any coin.
No problems currently.
I restarted asia pool for monero fix few minutes ago. Maybe you connected right that moment. Can you try it again?
If it doesn't work, please share your commandline so that I can test it from my side.
OK its all working again now. Thanks
Re: [ANN][POOL] Mining Pool Hub - Multipool. Multialgo, Auto Exchange to any coin.
Monero Mining Pool Hub
There was a block creation failure issue on Monero pool due to hardfork's logic changes.
Pool credited x4 of block height 1220751 reward to compensate.
Pool didn't find blocks for that period, but anyway I will distribute coins from my pocket.
Sorry about this issue.
I do my best but sometimes I miss something.
If you are not satisfied with compensation amount, please tell me. I'll give you coins according to your hashrate.
There was a block creation failure issue on Monero pool due to hardfork's logic changes.
Pool credited x4 of block height 1220751 reward to compensate.
Pool didn't find blocks for that period, but anyway I will distribute coins from my pocket.
Sorry about this issue.
I do my best but sometimes I miss something.
If you are not satisfied with compensation amount, please tell me. I'll give you coins according to your hashrate.
OK Fair enough, i've moved my miners back to your pool.. However, now none of my miners are able to connect to the asian servers.. is there something wrong with them?
Is anyone else having problems controlling their rigs via ethmon with v8.0?
For my farm, v8.0 seems to have broken the communications between my miners and ethmon. Everything is in read-only mode, even when I specify the correct -mport settings. I have checked all firewall settings, including application-specific settings, and everything is normal. I've even disabled the firewall to see if that was the issue. Still doesn't work. I can see stats on ethmon, but I can't tell ethmon to restart my rig. It is very important I have control via ethmon, as I have over 40 rigs. Whats going on?
For my farm, v8.0 seems to have broken the communications between my miners and ethmon. Everything is in read-only mode, even when I specify the correct -mport settings. I have checked all firewall settings, including application-specific settings, and everything is normal. I've even disabled the firewall to see if that was the issue. Still doesn't work. I can see stats on ethmon, but I can't tell ethmon to restart my rig. It is very important I have control via ethmon, as I have over 40 rigs. Whats going on?