Topic: [ANN] TeamRedMiner v0.10.10 - Ironfish/Kaspa/ZIL/Kawpow/Etchash and More - page 121. (Read 211959 times)

The problem is from the way the miner is being started and stopped.

So far, stopping only happens with "CTRL+C", and since its started via .BAT script, it would throw a user prompt for

Watchdog could not restart the miner.

[2018-12-03 08:41:38] GPU 7: detected DEAD (09:00.0), will execute restart script watchdog.bat
[2018-12-03 08:41:38] Watchdog triggering miner shutdown after restart script execution.
[2018-12-03 08:41:38] Shutting down...
Watchdog restarting miner in 30 secs.

Bpeмя oжидaния 30 ceк., нaжмитe любyю клaвишy для пpoдoлжeния ...
[2018-12-03 08:41:38] GPU 3 CN thread 1 exiting.
[2018-12-03 08:41:38] GPU 0 CN thread 1 exiting.
[2018-12-03 08:41:38] GPU 4 CN thread 1 exiting.
[2018-12-03 08:41:38] GPU 9 CN thread 0 exiting.
[2018-12-03 08:41:39] GPU 6 CN thread 0 exiting.
[2018-12-03 08:41:39] GPU 8 CN thread 0 exiting.
               29[2018-12-03 08:41:39] GPU10 CN thread 0 exiting.
[2018-12-03 08:41:39] GPU 1 CN thread 1 exiting.
[2018-12-03 08:41:39] GPU 5 CN thread 0 exiting.
[2018-12-03 08:41:39] GPU 2 CN thread 0 exiting.
[2018-12-03 08:41:39] GPU 0 CN thread 0 exiting.
[2018-12-03 08:41:39] GPU 9 CN thread 1 exiting.
[2018-12-03 08:41:39] GPU 8 CN thread 1 exiting.
[2018-12-03 08:41:39] GPU10 CN thread 1 exiting.
[2018-12-03 08:41:39] GPU 4 CN thread 0 exiting.
[2018-12-03 08:41:39] GPU 6 CN thread 1 exiting.
[2018-12-03 08:41:39] GPU 3 CN thread 0 exiting.
[2018-12-03 08:41:39] GPU 2 CN thread 1 exiting.
[2018-12-03 08:41:39] GPU 1 CN thread 0 exiting.
               28[2018-12-03 08:41:40] GPU 5 CN thread 1 exiting.
               20[2018-12-03 08:41:48] GPU 7 thread 0 shutdown timed out.
[2018-12-03 08:41:48] GPU 7 thread 1 shutdown timed out.
[2018-12-03 08:41:48] Unclean shutdown.
                0
          Team Red Miner version 0.3.8
[2018-12-03 08:42:40] Auto-detected AMD OpenCL platform 0

Faced a problem. The miner just stops working. It does not hang and can be closed.

Just got 6.11H/s C1280 m2120

This is 580 card on my pulse 570 with pure hynix (same memory) i get easily same result.

Maybe I got spoiled with samsung

The Hynix AJR and the Elpida BABG are really good. They may not clock up high, but they do like tight timings.
With both of them, i was getting around 1Kh/s on XMR-Stak at ~1300Mhz core.

Worst possible combo

edw4032babg Micron/Eplida
h5gc4h24ajr Hynix

6.06Kh/s ? Thats still an OK result. I would assume the Hynix memory is MJR. They are notreally good.

It's a good result anyway, I have couple rigs 6x NITRO+ with with hynix can't pass 6.06 for entire rig with c1280 m2110 

18.2.1.

Which drivers?

I have Nitro+ 4gb samsung they work slightly better onBeta then on 18.6.1

I'm getting identical results as you

Yes, the memclock changes do take effect. And yes, on Windows 10.

That is indeed a bug.  Sorry about that.  We'll fix it in the next release.

Our tests have shown that memory clock should have a noticeable effect.  Are you testing on windows?  Did you make sure that your memclock changes are taking effect by checking actual memclock speeds in say hwinfo?

As for the HWs, that is the number of shares that the GPU found that failed CPU verification.  This indicates that something went wrong on the GPU and it performed the share calculations incorrectly.  Typically, this is due to errors from aggressive core/mem clocks and/or voltages.
The miner does not submit these shares to the pool as it already knows that they are invalid.

Is there a watchdog.sh available on Linux?

i'm trying to get a watchdog for Linux, I googled around, I could not find anything...

On nicehash pool many rejects "Error code: 2 - job not found." Can it be fixed?

hi  same here on 1 rig.

whatchdog says gpu X is dead but no:/
and stop working at the reload...."unclean quit" or something like that

Thanks for the info 

Another API woe:

GPU3 crashed, and was declared Dead, but the API status was still showing Alive.

http://i67.tinypic.com/2s7gxi1.png

The program seen there checks the JSON data and the Status Field specifically is like this:

I know what you mean, but i tested the scaling and....



First is Memory clock scaling, then Core clock scaling.

GPU 0/3 -> 570/580 Elpida.
GPU 1 -> 580 Samsung.
Seems weird, for 75Mhz Memclock increase, to get only about 10Hs. Usually, it should be around 30H/s for ~75Mhz increase (at least on XMR-Stak).


EDIT: For clarification, are HWs actually considered Bad shares, that failed CPU check (meaning, GPU worked on them, and before submitting, it failed) ?

It think it's because CryptoNight seems depending very much at memory, not so much at core performance. Like my RX 550 8 CU gets better hashrates than my RX 560 with 14/16 CUs. All about memory performance I think. I run all of my RX 550/560/570/580s at a very low core clock (1050-1150 MHz) and gets a good hashrate even then..