Quote from: f5alcon on June 19, 2017, 02:24:07 PM

Quote from: superyin on June 19, 2017, 02:12:55 PM

Quote from: war4peace on June 18, 2017, 07:01:04 PM

Hi all,

I started mining with Claymore a few days ago and I am seeing an upsetting thing.
My GPU is an EVGA GTX 1080 FTW, watercooled, MSI Afterburner reports a RAM frequency of 5000 MHz, which is fine... but when mining with Claymore, the RAM frequency automatically drops to 4500 MHz. If I stop mining and start a game, the frequency goes back to 5000 - the 4500 MHz behavior only appears when mining using Claymore.

I suspect the driver somehow knows I am using Claymore and taxes me for that.
If I boost RAM frequency by +1000, it goes up from 4500 to 5500 MHz and the hash speed goes from 20.5 MH to over 25 MH - 25% boost - but this solution is clumsy, because whenever I stop mining I have to dial back the frequency boost, otherwise as soon as the GPU encounters any regular load, it tries to boost from 5000 to 6000 MHz and the memory can't handle it.

What should I do to keep mining with Claymore, but at correct RAM frequencies?

Hi, I don't have GTX1080 card, but I am currently mine on GTX970 which have similar issue. Try to use the NVSMI tools to raise the card power state from P2 to P0.
NVIDIA card stay in P2 power state when CUDA computing, memory speed will be limited in P2. Raise to P0 to unleash the full clock speed. Hope it will solve your problem.

ref: http://cryptomining-blog.com/tag/nvidia-force-power-state/

This doesn't work on 10 series cards right now, there is a nvidia driver bug.

Confirmed, indeed it looks like the board enters some mixed state between P2 and P0, the core clock jumps to 2000 but the RAm clock only jumps to 4514, which is the exact same value shown under the P2 state under nVidia Inspector.
I can't set the P2 State to anything, as soon as I try setting it up, the values jump back to defaults.

Code:

nvidia-smi -ac 5005,2000
Setting applications clocks is not supported for GPU 0000:01:00.0.
Treating as warning and moving on.
All done.

Question is: why is this only happening in some cases? i have friends who have GTX 1070, GTX 1080 Ti and they don't see this behavior. Is this specific to GTX 1080 only? Or am I just unlucky?