How do I force P0 state on my rig of 1080's?

[dragonmike]

Right.
So all my cards are in P2 state... DESPITE me having a nvidiainspector script running every few minutes automatically specifying the following:

SET GPU0=-setBaseClockOffset:0,0,110 -setMemoryClockOffset:0,0,650 -setPowerTarget:0,80 -setTempTarget:0,0,67 -forcepstate:0,0
SET GPU1=-setBaseClockOffset:1,0,110 -setMemoryClockOffset:1,0,650 -setPowerTarget:1,80 -setTempTarget:1,0,67 -forcepstate:1,0
SET GPU2=-setBaseClockOffset:2,0,110 -setMemoryClockOffset:2,0,650 -setPowerTarget:2,80 -setTempTarget:2,0,67 -forcepstate:2,0
SET GPU3=-setBaseClockOffset:3,0,110 -setMemoryClockOffset:3,0,650 -setPowerTarget:3,80 -setTempTarget:3,0,67 -forcepstate:3,0
SET GPU4=-setBaseClockOffset:4,0,110 -setMemoryClockOffset:4,0,650 -setPowerTarget:4,80 -setTempTarget:4,0,67 -forcepstate:4,0
C:\Users\drago\Desktop\nvidiaInspector\nvidiaInspector.exe %GPU0% %GPU1% %GPU2% %GPU3% %GPU4%

Using "nvidia-smi -q -d SUPPORTED_CLOCKS | more" shows all supported clocks as "N/A".

Any suggestions?

[CarlOrff]

Right.
So all my cards are in P2 state... DESPITE me having a nvidiainspector script running every few minutes automatically specifying the following:

SET GPU0=-setBaseClockOffset:0,0,110 -setMemoryClockOffset:0,0,650 -setPowerTarget:0,80 -setTempTarget:0,0,67 -forcepstate:0,0
SET GPU1=-setBaseClockOffset:1,0,110 -setMemoryClockOffset:1,0,650 -setPowerTarget:1,80 -setTempTarget:1,0,67 -forcepstate:1,0
SET GPU2=-setBaseClockOffset:2,0,110 -setMemoryClockOffset:2,0,650 -setPowerTarget:2,80 -setTempTarget:2,0,67 -forcepstate:2,0
SET GPU3=-setBaseClockOffset:3,0,110 -setMemoryClockOffset:3,0,650 -setPowerTarget:3,80 -setTempTarget:3,0,67 -forcepstate:3,0
SET GPU4=-setBaseClockOffset:4,0,110 -setMemoryClockOffset:4,0,650 -setPowerTarget:4,80 -setTempTarget:4,0,67 -forcepstate:4,0
C:\Users\drago\Desktop\nvidiaInspector\nvidiaInspector.exe %GPU0% %GPU1% %GPU2% %GPU3% %GPU4%

Using "nvidia-smi -q -d SUPPORTED_CLOCKS | more" shows all supported clocks as "N/A".

Any suggestions?

From my own experiences :
GTX 1070/1080/1080Ti are not supported P0 at this time (only P2 and more). Perhaps with a future driver version,
In the same way : nvidia-smi is not implemented identically with all the driver versions : some don't accpet the frequency tuning.
Not very easy...

[dragonmike]

Ok, for anyone's benefit... I managed to do it using the latest version of nvidia profile inspector. The older version I had didn't have the option.

[bathrobehero]

Ok, for anyone's benefit... I managed to do it using the latest version of nvidia profile inspector. The older version I had didn't have the option.

Did you gain any hashrate increase?

[joshuajones02]

Ok, for anyone's benefit... I managed to do it using the latest version of nvidia profile inspector. The older version I had didn't have the option.

Did you gain any hashrate increase?

I imagine it would increase Ethash algo maybe but not Equihash, just the ones heavy in memory

[salmanahmedone]

Lol, you can't, they can't handle that. You are trying to go against what the software is trying to fix and insisting over and over with it. You are trying to shove a round peg in a square hole and when it says no, you try to force it anyway. Never going to make that happen, let the software do its job and stop thinking you know more than the coder.

[szafa]

What is the PO?

[cvsea]

You can indeed do this with the latest nvidia profile inspector. Look for "force p2 state" under "common" and turn it off (remember to save  ).
Not much benefit to it though...

[dragonmike]

idiotic ramblings

Tough luck buddy, I managed to change it using nvidia profile inspector.
Are you also one of those claiming undervolting, overclocking and bios modding are works of the devil? Shame on those people who'd think they know more than the coder!

Now for the more sensible people out there, forcing P0 state is not to increase hashrate, it's mainly to try to gain a little stability (especially when algo-switching). You see, when the nemos, megaminers and sniffdogs out there close and reopen the miner window, the GPUs switch P-state. This can increase the chances of the rig crashing/hanging. By keeping P0 throughout, it might prevent a few of those events. You then of course have to adjust your overclock offsets bearing in mind your starting basis will be different.

[bathrobehero]

Lol, you can't, they can't handle that. You are trying to go against what the software is trying to fix and insisting over and over with it. You are trying to shove a round peg in a square hole and when it says no, you try to force it anyway. Never going to make that happen, let the software do its job and stop thinking you know more than the coder.

You're talking nonsense. With GPU Boost 3 a bunch of shitty changes were made, like you can't setup a temperate target which the card aims for and downclocks itself if it's reaching the limit - which was a super convenient thing for miners and previous generation cards had that "feature". Now that's locked away by your precious coders. Now if a card let's say have a faulty fan, the card will reach >90°C and cooks itself instead of downlocking to near-idle speeds and keep the card at let's say 70°C.
Also, everything now changing on the fly dynamically makes things worse (without the option to turn that off) and not just for miners but for gamers as well. Removing the option to use safe and established options and forcing specific "features" is always a bad idea.

[blackhorse7]

I have 1060, and it has blocked P0 state too (option exactly is named "CUDA - force P2 state" in nvidiaProfileInspector 2.1.3.6). Default it is on, after disabling my card's memories dont decrease by -200MHz on mining.
I am using nvidiaInspector too with command line similar to yours, and it works - I use nvidiaInspector 1.9.7.8

Code:

"nvidiaInspector - command line options\nvidiaInspector.exe" -setBaseClockOffset:0,0,80 -setMemoryClockOffset:0,0,500 -setPowerTarget:0,80 -setTempTarget:0,0,70
"nvidiaInspector - command line options\nvidiaInspector.exe" -setBaseClockOffset:0,0,80 -setMemoryClockOffset:0,0,-500 -setPowerTarget:0,50 -setTempTarget:0,0,66

Maybe other versions of those programs dont do that properly (I saw that thoughts somewhere during my google investigation of this problem)