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

Quote from: katar14 on May 31, 2019, 02:38:42 PM

algo Cryptonight HeavyX and MTP when? Huh

HeavyX for X-cash is already available, it's called cnv8_dbl in TRM. We're still debating how to prioritize MTP. The issue is the big investment in time for building the custom stratum protocol, submitting those huge proofs etc, all for a single coin and algo.

there will be new coins on mtp np; very good project tecracoin, mtp has a future

how do you know MTP is the future? Huh

what do I know progpow -maybe it's the future.. why MTP it is Huh

He said "mtp HAS a future" not "is the future" that's not exactly the same meaning

alexcrys1

newbie

Activity: 60

Merit: 0

Quote from: kerney666 on May 27, 2019, 06:39:51 PM

Quote from: kerney666 on May 27, 2019, 06:39:51 PM

algo Cryptonight HeavyX and MTP when? Huh

HeavyX for X-cash is already available, it's called cnv8_dbl in TRM. We're still debating how to prioritize MTP. The issue is the big investment in time for building the custom stratum protocol, submitting those huge proofs etc, all for a single coin and algo.

there will be new coins on mtp np; very good project tecracoin, mtp has a future

how do you know MTP is the future? Huh

what do I know progpow -maybe it's the future.. why MTP it is Huh

katar14

newbie

Activity: 20

Merit: 0

Quote from: kerney666 on May 30, 2019, 09:11:28 AM

algo Cryptonight HeavyX and MTP when? Huh

HeavyX for X-cash is already available, it's called cnv8_dbl in TRM. We're still debating how to prioritize MTP. The issue is the big investment in time for building the custom stratum protocol, submitting those huge proofs etc, all for a single coin and algo.

there will be new coins on mtp np; very good project tecracoin, mtp has a future

ku4eto

jr. member

Activity: 194

Merit: 4

Quote from: ku4eto on May 28, 2019, 08:25:45 AM

Hey Kerney.

I had PMed you in the MMP OS Discord for a weird issue.

2 days ago, i experencied a crashed GPU, its a 570 4GB.

System is Win 10 1703, AMD 19.2.1, 4GB RAM, i5-3470.

The GPU would die for no reason (maybe timings).

The GPU stats reporting will stop, and only the share submitting will remain. API is getting killed as well.
But the miner itself does not seem to react properly with the dead GPU, as no SICK/DEAD is declared (and the API should still be responsive).

Miner does not initiate properly the shutdown process, or at the very least, output is not shown. The GPUs did stop mining though.

Trying to invoke the Task Manager or the AMD Radeon Settings freezes them almost right away. Even the driver does not know if its crashed or not Cheesy

EDIT2: Here are the screenshots.
https://imgur.com/a/fu3Zkxj

I presume, it could be overheating, since yesterday crashed again at 81*C.

EDIT: Also, i see that the Interleaving adjustment happens primarily on the GPU0 (shortly after the miner initialization).

EDIT3: When the card was run with lower voltage (core + IMC), it crashed, and it was detected and declared as DEAD. Will try again, by raising the voltage, to see if the issue will repeat.

Hi ku4eto! Thanks for the edit updates. Any more info after bumping voltage a little?

Okay, after some testing, i got in the past 2 days, 3-4 more crashes in total.

After playing with the voltage for that card (retesting the stability, in case it has degraded), but the voltage initially used was indeed correct.
Bumping up the voltage by 2 steps (2x6.25mV) had no difference.

I set the fan today to 95% for above 75*C (was for 85*C before that). I have not observed the issue still.

I will check for 2 more days, before calling it 100% an thermal issue.

Its a RX 570 Gigabyte Aorus. Not sure, but i believe some cards had a different thermal limit for some elements, compared to the rest. Although, i did compare the BIOS, and it had the same temp limits defined, as the rest of my cards.

wei0339

newbie

Activity: 12

Merit: 1

Quote from: MinersRus on May 29, 2019, 11:10:48 PM

Quote from: ku4eto on May 28, 2019, 08:25:45 AM

I may have missed it, but:
What does the

Quote

GPU0 thread 0 interleave adjust xxx ms

means?

For dual thread CN mining to keep its highest hashrate over time you need to make sure the two threads are running with the appropriate separation in time. If they gravitate and become too close to running synchronously, the whole point of running dual threads disappears. Therefore, it's better to delay one of the threads a little before starting the next hash run. This is the "interleave adjustment" logged above. As long as your hashrate is stable (and high) over time, it's nothing to worry about, everything is working as intended.

Asking, because i saw it on only one card. And this one tends to crash every week or two.

I have the same problem.
VEGA 56 is normal in the case of "mode 16+14".
However, the same problem occurs after using AMD Mem Tweak & "--cn_config 1x*1x".
And after a while, it will drop from 2000 h/s to 16xx h/s.
Is it an overclocking problem? Is there any solution?

I have had issues with various Vega 56's that had the same problems that you mention (drop from 2000 h/s to 16xx h/s or just crash). The problems usually a few days to happen. The solution I have found is to increase the core voltage in small increments until the problems disappear. I also had to down the core clock speed.

Example: Vega 56: Core 920mv and 1300 MHz core. I also run the mode as 14*14. I still get around 2000 H/s (no memory tweak done yet)

Core 920 mv, much better than before.
Thank you.

kerney666

member

Activity: 658

Merit: 86

Hey Kerney.

I had PMed you in the MMP OS Discord for a weird issue.

2 days ago, i experencied a crashed GPU, its a 570 4GB.

System is Win 10 1703, AMD 19.2.1, 4GB RAM, i5-3470.

The GPU would die for no reason (maybe timings).

The GPU stats reporting will stop, and only the share submitting will remain. API is getting killed as well.
But the miner itself does not seem to react properly with the dead GPU, as no SICK/DEAD is declared (and the API should still be responsive).

Miner does not initiate properly the shutdown process, or at the very least, output is not shown. The GPUs did stop mining though.

Trying to invoke the Task Manager or the AMD Radeon Settings freezes them almost right away. Even the driver does not know if its crashed or not Cheesy

EDIT2: Here are the screenshots.
https://imgur.com/a/fu3Zkxj

I presume, it could be overheating, since yesterday crashed again at 81*C. May

EDIT: Also, i see that the Interleaving adjustment happens primarily on the GPU0 (shortly after the miner initialization).

EDIT3: When the card was run with lower voltage (core + IMC), it crashed, and it was detected and declared as DEAD. Will try again, by raising the voltage, to see if the issue will repeat.

Hi ku4eto! Thanks for the edit updates. Any more info after bumping voltage a little?

kerney666

member

Activity: 658

Merit: 86

Quote from: pbfarmer on May 30, 2019, 12:35:34 AM

I may have missed it, but:
What does the

Quote

GPU0 thread 0 interleave adjust xxx ms

means?

For dual thread CN mining to keep its highest hashrate over time you need to make sure the two threads are running with the appropriate separation in time. If they gravitate and become too close to running synchronously, the whole point of running dual threads disappears. Therefore, it's better to delay one of the threads a little before starting the next hash run. This is the "interleave adjustment" logged above. As long as your hashrate is stable (and high) over time, it's nothing to worry about, everything is working as intended.

Asking, because i saw it on only one card. And this one tends to crash every week or two.

I have the same problem.
VEGA 56 is normal in the case of "mode 16+14".
However, the same problem occurs after using AMD Mem Tweak & "--cn_config 1x*1x".
And after a while, it will drop from 2000 h/s to 16xx h/s.
Is it an overclocking problem? Is there any solution?

watch your hbm temps. you may be over-temp throttling

Hi! When you exit the miner after this happens, do you get a clean shutdown or is one thread timing out? The 2000 to 1600 h/s drop is very close to the expected single threaded performance, I’m guessing one thread has died.

pbfarmer

member

Activity: 340

Merit: 29

I may have missed it, but:
What does the

Quote

GPU0 thread 0 interleave adjust xxx ms

means?

For dual thread CN mining to keep its highest hashrate over time you need to make sure the two threads are running with the appropriate separation in time. If they gravitate and become too close to running synchronously, the whole point of running dual threads disappears. Therefore, it's better to delay one of the threads a little before starting the next hash run. This is the "interleave adjustment" logged above. As long as your hashrate is stable (and high) over time, it's nothing to worry about, everything is working as intended.

Asking, because i saw it on only one card. And this one tends to crash every week or two.

I have the same problem.
VEGA 56 is normal in the case of "mode 16+14".
However, the same problem occurs after using AMD Mem Tweak & "--cn_config 1x*1x".
And after a while, it will drop from 2000 h/s to 16xx h/s.
Is it an overclocking problem? Is there any solution?

watch your hbm temps. you may be over-temp throttling

MinersRus

member

Activity: 214

Merit: 24

I may have missed it, but:
What does the

Quote

GPU0 thread 0 interleave adjust xxx ms

means?

For dual thread CN mining to keep its highest hashrate over time you need to make sure the two threads are running with the appropriate separation in time. If they gravitate and become too close to running synchronously, the whole point of running dual threads disappears. Therefore, it's better to delay one of the threads a little before starting the next hash run. This is the "interleave adjustment" logged above. As long as your hashrate is stable (and high) over time, it's nothing to worry about, everything is working as intended.

Asking, because i saw it on only one card. And this one tends to crash every week or two.

I have the same problem.
VEGA 56 is normal in the case of "mode 16+14".
However, the same problem occurs after using AMD Mem Tweak & "--cn_config 1x*1x".
And after a while, it will drop from 2000 h/s to 16xx h/s.
Is it an overclocking problem? Is there any solution?

I have had issues with various Vega 56's that had the same problems that you mention (drop from 2000 h/s to 16xx h/s or just crash). The problems usually a few days to happen. The solution I have found is to increase the core voltage in small increments until the problems disappear. I also had to down the core clock speed.

Example: Vega 56: Core 920mv and 1300 MHz core. I also run the mode as 14*14. I still get around 2000 H/s (no memory tweak done yet)

wei0339

newbie

Activity: 12

Merit: 1

I may have missed it, but:
What does the

Quote

GPU0 thread 0 interleave adjust xxx ms

means?

For dual thread CN mining to keep its highest hashrate over time you need to make sure the two threads are running with the appropriate separation in time. If they gravitate and become too close to running synchronously, the whole point of running dual threads disappears. Therefore, it's better to delay one of the threads a little before starting the next hash run. This is the "interleave adjustment" logged above. As long as your hashrate is stable (and high) over time, it's nothing to worry about, everything is working as intended.

Asking, because i saw it on only one card. And this one tends to crash every week or two.

I have the same problem.
VEGA 56 is normal in the case of "mode 16+14".
However, the same problem occurs after using AMD Mem Tweak & "--cn_config 1x*1x".
And after a while, it will drop from 2000 h/s to 16xx h/s.
Is it an overclocking problem? Is there any solution?

ku4eto

jr. member

Activity: 194

Merit: 4

Hey Kerney.

I had PMed you in the MMP OS Discord for a weird issue.

2 days ago, i experencied a crashed GPU, its a 570 4GB.

System is Win 10 1703, AMD 19.2.1, 4GB RAM, i5-3470.

The GPU would die for no reason (maybe timings).

The GPU stats reporting will stop, and only the share submitting will remain. API is getting killed as well.
But the miner itself does not seem to react properly with the dead GPU, as no SICK/DEAD is declared (and the API should still be responsive).

Miner does not initiate properly the shutdown process, or at the very least, output is not shown. The GPUs did stop mining though.

Trying to invoke the Task Manager or the AMD Radeon Settings freezes them almost right away. Even the driver does not know if its crashed or not Cheesy

EDIT2: Here are the screenshots.
https://imgur.com/a/fu3Zkxj

I presume, it could be overheating, since yesterday crashed again at 81*C. May

EDIT: Also, i see that the Interleaving adjustment happens primarily on the GPU0 (shortly after the miner initialization).

EDIT3: When the card was run with lower voltage (core + IMC), it crashed, and it was detected and declared as DEAD. Will try again, by raising the voltage, to see if the issue will repeat.

kerney666

member

Activity: 658

Merit: 86