Claymore's ZCash/BTG AMD GPU Miner v12.6 (Windows/Linux)

[mettalmag]

after updating to V8 since the release day only three rigs out of 84 has the problem

Code:

Watchdog: GPU 0 hangs in OpenCL call, exit

and after that
Reset control for GPU 0 ...
and miner stops and hangs the PC
in V7 there wasn't a problem like this
any solutions ?

Use -wd 0

When that GPU dies, you need to manually restart computer before re-running the miner.

So far so good with -wd 0
also I wonder is it mandatory to set 16gb virtual memory ?

[1714737802]

1714737802

[1714737802]

1714737802

[1714737802]

1714737802

[1714737802]

1714737802

[1714737802]

1714737802

[1714737802]

1714737802

[adaseb]

after updating to V8 since the release day only three rigs out of 84 has the problem

Code:

Watchdog: GPU 0 hangs in OpenCL call, exit

and after that
Reset control for GPU 0 ...
and miner stops and hangs the PC
in V7 there wasn't a problem like this
any solutions ?

Use -wd 0

When that GPU dies, you need to manually restart computer before re-running the miner.

So far so good with -wd 0
also I wonder is it mandatory to set 16gb virtual memory ?

No idea but most of us have like 500gb of free hard drive space so why not.

[tanatana]

https://i.imgur.com/ZcZB2S2.png

is that a problem?
after few hours appears incorrect data

this could be due to excessive overclocking or undervolting.

not overcklock, not undervolt, there is change bios
did not claymore 5, 6, 7 only 8

Try reducing the intensity. Use -i 5 or 4 or 3. The V8 stress the GPU more. I had the same problem with V8.

voltage increases on the problematic card
1,09 -> 1.15
problem again
2*7950 card
-------------------------------------
Now I reduced the intensity of 3

thanks. is fine

[mettalmag]

after updating to V8 since the release day only three rigs out of 84 has the problem

Code:

Watchdog: GPU 0 hangs in OpenCL call, exit

and after that
Reset control for GPU 0 ...
and miner stops and hangs the PC
in V7 there wasn't a problem like this
any solutions ?

Use -wd 0

When that GPU dies, you need to manually restart computer before re-running the miner.

So far so good with -wd 0
also I wonder is it mandatory to set 16gb virtual memory ?

No idea but most of us have like 500gb of free hard drive space so why not.

That will be a huge issue for my, most of my SSDs are 16 and 32Gb..
One of three did the same hangs opencl call other two are working fine so far

[adaseb]

after updating to V8 since the release day only three rigs out of 84 has the problem

Code:

Watchdog: GPU 0 hangs in OpenCL call, exit

and after that
Reset control for GPU 0 ...
and miner stops and hangs the PC
in V7 there wasn't a problem like this
any solutions ?

Use -wd 0

When that GPU dies, you need to manually restart computer before re-running the miner.

So far so good with -wd 0
also I wonder is it mandatory to set 16gb virtual memory ?

No idea but most of us have like 500gb of free hard drive space so why not.

That will be a huge issue for my, most of my SSDs are 16 and 32Gb..
One of three did the same hangs opencl call other two are working fine so far

With -i4 each GPU uses like 1.5GB. so you need at least that amount of virtual memory.
If you don't have enough virtual memory, the hashing will fail to start. The GPU 0 hang is something else.

[mettalmag]

after updating to V8 since the release day only three rigs out of 84 has the problem

Code:

Watchdog: GPU 0 hangs in OpenCL call, exit

and after that
Reset control for GPU 0 ...
and miner stops and hangs the PC
in V7 there wasn't a problem like this
any solutions ?

Use -wd 0

When that GPU dies, you need to manually restart computer before re-running the miner.

So far so good with -wd 0
also I wonder is it mandatory to set 16gb virtual memory ?

No idea but most of us have like 500gb of free hard drive space so why not.

That will be a huge issue for my, most of my SSDs are 16 and 32Gb..
One of three did the same hangs opencl call other two are working fine so far

With -i4 each GPU uses like 1.5GB. so you need at least that amount of virtual memory.
If you don't have enough virtual memory, the hashing will fail to start. The GPU 0 hang is something else.

after setting wd to 0 I also did i to 0 too
lets see what will happen

[Flickspeed]

It currently seems that there is much more progress to make for the RX 4xx cards. The v8 miner is not utilizing the full memory speed of the 480s as it seems. Lowering the memory speed from 2200 to 2000 yields same hashrate. While lowering the core clock makes a bigger impact. This should not be the case since the 480 has a faster core than the 390 and the 390 is getting much better results, why? Am I wrong about anything?

[oslak]

It currently seems that there is much more progress to make for the RX 4xx cards. The v8 miner is not utilizing the full memory speed of the 480s as it seems. Lowering the memory speed from 2200 to 2100 yields same hashrate. While lowering the core clock makes a bigger impact. This should not be the case since the 480 has a faster core than the 390. Am I wrong about anything?

You are wrong on everything. LOL

[Flickspeed]

It currently seems that there is much more progress to make for the RX 4xx cards. The v8 miner is not utilizing the full memory speed of the 480s as it seems. Lowering the memory speed from 2200 to 2100 yields same hashrate. While lowering the core clock makes a bigger impact. This should not be the case since the 480 has a faster core than the 390. Am I wrong about anything?

You are wrong on everything. LOL

Do some testing before making such useless posts. Hashrate doesn't even change when lowering the memory clock to 2000. So someone needs to explain why the rx480 is performing so porrly compared to the 390.

[mamedesign]

https://pbs.twimg.com/media/CyQsBvTUUAAGYlv.jpg:large

[deadsix]

It currently seems that there is much more progress to make for the RX 4xx cards. The v8 miner is not utilizing the full memory speed of the 480s as it seems. Lowering the memory speed from 2200 to 2100 yields same hashrate. While lowering the core clock makes a bigger impact. This should not be the case since the 480 has a faster core than the 390. Am I wrong about anything?

You are wrong on everything. LOL

Do some testing before making such useless posts. Hashrate doesn't even change when lowering the memory clock to 2000. So someone needs to explain why the rx480 is performing so porrly compared to the 390.

He doesn't need testing, he (apparently) has spent some time reading about the Algo to know that Equihash is completely compute dependent, and on the current RX cards that's the limiting factor so increasing memory clocks will not help much. Coding for algo's like these is about working on the limiting factors untill you hit their limit or something else becomes the limiting factor. In this case we have hit the limit of the GPU and untill we can surpass it handily memory clocks do not matter beyond a point. It is also the reason much older cards do well on equihash because they have a large number of cores on the GPU. It would do you good to read up about the algo as well, before getting pissed at people.

[Claymore]

I see some posts that V8 reached hardware limits and there is no way to improve speed anymore. It's not true.
I'm working on new version with another good speedup, though it takes more time and efforts.

[Flickspeed]

Thank you for clarifying Claymore. Looking forward to the next release.

[Bllacky]

Has anyone noticed that mining speed with the 380X is a lot lower than with the 280X ?

I get 200 on the 280X but only 140 on the 380X .

[mfsmarques]

I'm mining in coinmine with 1 kh/s, the difficulty goes up to 58283.01 and then after a few hours this message appears:

ZEC:: No new jobs were received for 10 mins - something wrong with the pool, disconnect.

And the difficulty returns to 1024 and begins to rise.
This is normal?

[xtrembash]

maybe lower yr fee now you re a rich man & u accumulated a lot of money from years ..
   
or u prefer continue to pick up more money like Uncle Scrooge & all those rotten rich people in the world ..

[oslak]

Put label/name on each version of your miner, @claymore.

[mitache365]

I see some posts that V8 reached hardware limits and there is no way to improve speed anymore. It's not true.
I'm working on new version with another good speedup, though it takes more time and efforts.

And whats the point?? High temperatures, more electricity and same profit, cuz all are with the new miner. Your new versions are not helpful, do you know that? Also some cards have really bad speed

[Claymore]

I see some posts that V8 reached hardware limits and there is no way to improve speed anymore. It's not true.
I'm working on new version with another good speedup, though it takes more time and efforts.

And whats the point?? High temperatures, more electricity and same profit, cuz all are with the new miner. Your new versions are not helpful, do you know that?

My miner does not support Linux, Nvidia, CPUs. They will not get any speedups from my miner.
Though I'm ready to stop development if most of people think so. It's not a problem for me at all. Make a vote somewhere to see results.

[Batelk]

Has anyone noticed that mining speed with the 380X is a lot lower than with the 280X ?

I get 200 on the 280X but only 140 on the 380X .

The 380X should be slower than the 280X. It only has 256 bit memory bus while the 280X has 384 bit. 280X was marketed as top end card.

https://en.wikipedia.org/wiki/List_of_AMD_graphics_processing_units