Quote from: dudee on June 03, 2019, 06:44:48 PM

getting bsod "thread stuck in device driver"
trying diffrent low safe oc still bsod. 6x rx570 18.5.1
i will try later newest driver.

Hmm Thats something new I have not seen with my miner yet - did you have any trouble with that rig before on an other software? Normally it should not get stuck in driver unless you do too much OC and bits flip in the kernel code. (By the way: on which algo?)

Quote from: geck on May 30, 2019, 08:03:37 AM

Hi,

Grin 31 is working on my rx vega cards, however it doesn't seem to be working on my gtx 1080 cards. On the rx vega it uses the 8gb kernel but on the 1080 it uses the 4gb kernel. It shows hashrate of 0 and continues to run without errors. Is this normal?

edit: should have mentioned i'm running windows 10

I have to admit I did not test it much on Nvidias - the grin code is more optimized for AMD since there are good CUDA miners for Nvidia around. What can happen - why it flips to 4G kernel - is that Windows takes some of the memory of the GPU even if there is no screen connected - and that is already enough to make the algo not work. We had that e.g. on 3G / 4G card when mining Beam as well - that runs well on Linux, but not on Win.

If you got the time please check nvidia-smi (comes with drivers) when no miner is running how much memory is reported as free. The current 8G grin code needs almost the full 8G (I am working on a new one, hope that saves more)

Quote from: ivcelmik on May 29, 2019, 04:11:24 PM

I've Rx 580 8Gb but the miner selects 4G solver on Ubuntu 16.04 for Grin 31 any idea how to set 8 G solver?
Thx in advance

Is a screen attached? Its likely that the GPU reports too few free memory. Can you send me the output of clinfo in a private msg?