Search content
Sort by
Showing 17 of 17 results by jenci
а тем временем с моего горячего кошелька с биржы 12 часов тому эфир (прибывший туда 11 дней тому) отправился на адрес 0xF7a0A59Fe1Ddb38CB9b2159a6C407318d1D8710B к больше чем 4000 своим братьям. или эта тема не про это? 
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v9.5 (Windows/Linux)
http://imgur.com/a/0te75
anyone have same problem?
i found, sorry
Just quoting Optiminer's GitHub:
Quote
Windows
Full speed can only be achieved under Catalyst 15.12 drivers! See below for how to install the older driver version.
RX4*0 cards are not supported by Catalyst 15.12, I strongly recommend to use linux for mining on them!
Full speed can only be achieved under Catalyst 15.12 drivers! See below for how to install the older driver version.
RX4*0 cards are not supported by Catalyst 15.12, I strongly recommend to use linux for mining on them!
I use Windows, therefore Optiminer is not a very good option, according to them!
when using a pool is a 20% fluctuation in daily earnings normal to see?
on dwarfpool is ok. on flypool isn't...Which PCIE slot are you connecting your 1x3 card into?
It is my understanding that each GPU requires a minimum of 1 PCIE lane/pipeline to transmit data. That means you would have to plug the 1x3 card into a slot with at least 3 lanes/pipelines (in the real world that means a 4x, 8x, or 16x slot). The H81 Pro BTC has a single 16x slot and five 1x slots. You could only ever run the 1x3 card on the 16x slot.
If I'm wrong on this I am open to correction. I've actually been wanting to play around with the exact setup you describe.
i plug the pcie switch card to pcie x1 slot on asus m4a78 motherboard. to x16 slot on mb plugged over usb riser r9 290. next 3x 290 plugget to pcie switch.
work fine more that 1 week on dualminer.
280x:
240 -> 331 H/s but loads of rejects
some time ago i have same problem. >>30% of rejects! decrease the intensity. for me on v9.2 -i 7, on v11 -i 4 . hashrate approx 250 hash/s240 -> 331 H/s but loads of rejects
yeah, everything is at stock clocks, I have not over-clocked any card or CPU. Also, I rechecked, it started at v9.2, in v9.1 it does not kill the system:
Is anyone experiencing complete system halt (windows 10) due to the watchdog??
I have been having troubles with the miner since v9.3. I have a system of 5 RX480 8GB cards and every time I run the miner, after about 5-10 min, the terminal shows "Thread hanging, about to restart" but instead, the whole system freezes.
Any suggestions on how to solve this issue??
I have:
- Updated/Downgraded drivers, currently v16.11.3 as suggested at initialization.
- Enabled/Disabled options: asm, intensity, algorithm, watchdog.
all stock?if no, try reset overclock. i have same problem when overdecrease core voltageI have been having troubles with the miner since v9.3. I have a system of 5 RX480 8GB cards and every time I run the miner, after about 5-10 min, the terminal shows "Thread hanging, about to restart" but instead, the whole system freezes.
Any suggestions on how to solve this issue??
I have:
- Updated/Downgraded drivers, currently v16.11.3 as suggested at initialization.
- Enabled/Disabled options: asm, intensity, algorithm, watchdog.
280x 3Gb
nanopool 250-260H/s - after 8 minute work 25% rejects (on v10.0 same situation)
dwarfpool 300-335H/s immediately after start many rejects 5 min >30%
win 10 driver 16.10.3
it is my problem?!
UPD: algo 2 intensity 7, no overclock, no bios mod
nanopool 250-260H/s - after 8 minute work 25% rejects (on v10.0 same situation)
dwarfpool 300-335H/s immediately after start many rejects 5 min >30%
win 10 driver 16.10.3
it is my problem?!
UPD: algo 2 intensity 7, no overclock, no bios mod
intensity 2-3-4 solve your trouble
280x 3Gb
nanopool 250-260H/s - after 8 minute work 25% rejects (on v10.0 same situation)
dwarfpool 300-335H/s immediately after start many rejects 5 min >30%
win 10 driver 16.10.3
it is my problem?!
UPD: algo 2 intensity 7, no overclock, no bios mod
nanopool 250-260H/s - after 8 minute work 25% rejects (on v10.0 same situation)
dwarfpool 300-335H/s immediately after start many rejects 5 min >30%
win 10 driver 16.10.3
it is my problem?!
UPD: algo 2 intensity 7, no overclock, no bios mod
5x470 v9.3 1066H/s >>v10.0 1130H/s. 20 hour stable work. rejected shares 0.11%
on my "test rig" with one 280x (-a 2 -i 7) 220H/s but after 30-40 min hashrate up to 260H/s and many many rejects. pool is nanopool. 8 hour of work approx 25% of rejected shares. revert to 9.2
on my "test rig" with one 280x (-a 2 -i 7) 220H/s but after 30-40 min hashrate up to 260H/s and many many rejects. pool is nanopool. 8 hour of work approx 25% of rejected shares. revert to 9.2
Maybe you should read 1st post before start mining!?
question: possibile restart miner every 24h (-r 1440) and execute reboot.bat if any problem with miner?Quote
-wd watchdog option. Default value is "-wd 1", it enables watchdog, miner will be closed (or restarted, see "-r" option) if any thread is not responding for 1 minute or OpenCL call failed.
Specify "-wd 0" to disable watchdog.
-r Restart miner mode. "-r 0" (default) - restart miner if something wrong with GPU. "-r -1" - disable automatic restarting. -r >20 - restart miner if something
wrong with GPU or by timer. For example, "-r 60" - restart miner every hour or when some GPU failed.
"-r 1" closes miner and execute "reboot.bat" file ("reboot.bash" or "reboot.sh" for Linux version) in the miner directory (if exists) if some GPU failed.
So you can create "reboot.bat" file and perform some actions, for example, reboot system if you put this line there: "shutdown /r /t 5 /f".
Specify "-wd 0" to disable watchdog.
-r Restart miner mode. "-r 0" (default) - restart miner if something wrong with GPU. "-r -1" - disable automatic restarting. -r >20 - restart miner if something
wrong with GPU or by timer. For example, "-r 60" - restart miner every hour or when some GPU failed.
"-r 1" closes miner and execute "reboot.bat" file ("reboot.bash" or "reboot.sh" for Linux version) in the miner directory (if exists) if some GPU failed.
So you can create "reboot.bat" file and perform some actions, for example, reboot system if you put this line there: "shutdown /r /t 5 /f".
in my case after ~28-30h of work miner produce many invalid shares. but if any problem with gpu thread after autorestart miner is hold before "settings intensity"
czm v 9.2, 5x470 gigabyte g1, win 10 driver 16.9.2
all my stable 6 X 470 rigs become crazy with 9.2. Their gpu0 always hangs.
i have same problem 2 times after update to 9.2. increase core voltage from 973 to 1000 mV and after 28 hour work no more hangs.The now my share found is 147 ms...
I have 2 x 750W PSU, each PSU runs 3 cards.
I dont blame Claymore 9.0 or 9.1, I had this problem since the first time I use claymore, since 5.0. There will be 1 card always not working, will hash 0 H/s. After a certain of time, watchdog says that GPU hangs and reset.
No matter how many GPU I use, there will be 1 not working.
My temporary fix was keep rebooting until all GPUs working, but now that ways seems not work anymore.
I dont blame Claymore 9.0 or 9.1, I had this problem since the first time I use claymore, since 5.0. There will be 1 card always not working, will hash 0 H/s. After a certain of time, watchdog says that GPU hangs and reset.
No matter how many GPU I use, there will be 1 not working.
My temporary fix was keep rebooting until all GPUs working, but now that ways seems not work anymore.
if you overclock your GPUs try downclock it little or increase core voltage. i use claymore zcash miner from the first version. never had problem but after v9.0 i have problem with psu and gpu hangs. after adding second PSU and changing overclock settings problems is gone
I belive that 3. But it could depend on your hashrate, best - check it for self
20 hours ago i tested dwarfpool.In 3 hours of mining,I got tonns of rejects. I had to wait 20-60 sec for new jobs. Accepts 100...3000ms. (ping to zec-ru1.dwarfpool.com 50-70ms)
now after 1,5 hours -- 0 rejects. but 5 hours no block found
5x470 v8.0->900H/s v9.0->1030H/s nice speed up!!! but...
1000W Navitas gold with 4 undervolted, underclocked (1200/950) 470-s it crashes. i try start v9.0 miner with power limit -35 and -i 4 but no changes, after 1-20 min work system turn off. temporary back to v8.0, with 5x470(~1280/990 -i 6) work stable
5 year old Tagan TG500-U33 with athlon 64 x2, 2Gb ram and 2x290 v9.0 -i 8 ~500H/s cvoltage -37 powlimit+10 1070core/1300mem work absolutly stable
1000W Navitas gold with 4 undervolted, underclocked (1200/950) 470-s it crashes. i try start v9.0 miner with power limit -35 and -i 4 but no changes, after 1-20 min work system turn off. temporary back to v8.0, with 5x470(~1280/990 -i 6) work stable
5 year old Tagan TG500-U33 with athlon 64 x2, 2Gb ram and 2x290 v9.0 -i 8 ~500H/s cvoltage -37 powlimit+10 1070core/1300mem work absolutly stable